Homework Title / No: 2 Course Code: CSE-314 Course Instructor: Sir Kirandeep singh D.O.A:15 sep 2010 D.O.

S:01 oct 2010 Students Roll No.RD1802B55 Section No. : D1802 Registration number: 10810314

Declaration: I declare that this assignment is my individual work. I have not copied from any other students work or from any other source except where due acknowledgment is made explicitly in the text, nor has any part been written for me by another person. Students Signature: sheetal

CSE314 Home Work 2

Part A Q1. Software cost and effort estimation will never be an exact science. Too many variables human, technical, environmental, politicalcan affect the ultimate cost of software and effort applied to develop it. Do you support this statement? Justify your answer with a suitable example.

Ans.1. Yes I do support the above given statement because for a good project good engineering is essential. The bulk of the cost of software development is due to the human resources needed and most estimation procedures focus on estimating effort in terms of persons per month. Estimates can be based on subjective opinion of some person or determined through the use of models. The accuracy of the estimate will depend on the amount of reliable information of the final product.

This statement is true because the management of software begins with a set of activities that are collectively called project planning. Estimation is important it need not be conducted in an unorganized manner. Estimation lays a foundation for all other project planning activities and project planning, thus provides a road map for successful software engineering. Thus it is clear from the above points that software cost and estimation will never be exact science and a number of variables like human, technical environmental and political factors affect its development. For example: A top-down model can depend on many factors. The estimate of the efforts required for each phase can be determined from the total effort estimate.
Q2. Before the project can begin, the manager and the software team must estimate the work to be done, the resources that will be required, and the time that will elapse from start to finish. Ans.2. Before making a project we estimate the effort and scheduling. Estimation

gives us an idea of the size of the project. We can use the information about size to estimate the cost, effort, and duration of the project. This further helps plan for resources and schedule the project. Estimate the size of the product: - As size increases, the interdependency among various elements of the software grows rapidly. Thus size estimation is very important. Estimate the effort: - It tells about how many man per month are required for the development of software. Estimation of schedule: - It planes about the estimated time in which software must be completed.

Q3. What is the difference between a SCM audit and a formal technical review? Can their functions be folded into one review? What are the pros and cons?

Ans.3. SCM means Software Configuration Management. Planning for configuration management involves identifying the configuration items and specifying the procedures to be used for controlling and implementing changes to them. When SCM is a formal

activity, the SCM audit is conducted separately by the quality assurance group. Reviewers assess the SCI to determine consistency with other SCIs, omissions, or potential side effects. A formal technical review should be conducted for all but the most trivial changes. A software configuration audit complements the formal technical review by assessing a configuration object for characteristics that are generally not considered during review.
Part B Q4. Discuss in detail about Putnam allocation model elaborate by providing some example. Ans.4. The PUTNAM model is an empirical effort estimation model. The effort required to finish a software project of specified size. It also describes the time and effort

required to finish a software project of specified size. SLIM (Software Life cycle Management) is the name given by Putnam to the proprietary suite of tools developed based on his model.
Putnam Investments Sees Competitive Advantage in Building OTC Derivatives Pricing Engine InHouse. BELIEVING THERE IS A COMPETITIVE ADVANTAGE to be gained from a proprietary engine for pricing over-the-counter derivatives internally, Putnam Investments embarked on a large project three years ago to bring straight-through processing to OTC derivatives, relates Eric Meltzer, the firm's head of investment technology. According to Meltzer, the project included building a series of components related to analytics and theoretical pricing. Putnam's middle office is responsible for gathering all the prices that are provided to the firm daily. "For the vendors and brokers that are pricing instruments for us, we have built an in-house application that facilitates that on a daily basis," Meltzer reports. "As the prices come in, the middle-office staff can see the theoretical price of the data to validate against the pricing service to make sure things are within tolerance."

Q5. Elaborate on the issues that relates to the Risk analysis and Risk management of any software development process. Ans.5. RISK ANALYSIS:- It is an activity that must be undertaken during project planning. A risk is potential problem that may or may not occur. But regardless of

outcome it is good idea to identify it, access its probability of occurring and its impact. Risk management is followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities. Risks can come from uncertainty in financial markets, project failures.
RISK MANAGEMENT: Risk management is an attempt to minimize the chances of failure caused by unplanned events. The aim of risk management is not to avoid getting into projects that have risks but to minimize the impact of risks in the projects that are undertaken.

Q6. Cohesion & coupling in the software pay important role in the design phase of the software development process. Elaborate it using some suitable examples. Ans.6. COHESION: It is the concept that tries to capture the intra module. With cohesion, we determine how closely the elements of a module are related to each other. Cohesion occurs when there is no meaningful relationship among the elements of a module. A module is created to save duplicate code by combining some part of a code that occurs at many different places. A procedurally cohesive module contains elements that belong to a common procedural unit. Example: -A loop or a sequence of a decision statement in a module may be combined to form a separate module. A module with only procedural cohesion may contain only part of a complete function. COUPLING: Coupling between modules is the strength of interconnections between modules or a measure of interdependence among modules. The choice of modules decides the coupling between modules because the modules of the system software are created during system design. Coupling increases with the complexity and obscurity of the interface between modules.