CS-605 Software Engineering II
Course Page
Q & A
Short Question & Answers
Q26: Define Compartmentalization with context of project schedule.
The project must be compartmentalized into a number of manageable activities and tasks. To accomplish compartmentalization, both the product and process are decomposed.
Q27: In order to assess the overall project risks, what questions need to be addressed? Give any five?
In order to assess the overall project risks, the following questions need to be addressed: • Have top software and customer managers formally committed to support the project? • Are end-users committed to the project and the system/product to be built? • Are requirements fully understood? • Have customers been involved fully in requirement definition? • Do end-users have realistic expectations? • Does the software team have right mix of skills? • Are project requirements stable? • Does the project team have experience with the technology to be implemented? • Is the number of people on the project team adequate to do the job?
Q28: Three External input counting rules.
The data or control information is received from outside the application boundary. At least one ILF is maintained if the data entering the boundary is not control information that alters the behavior of the system. For the identified process, one of the following three statements must apply: Processing logic is unique from the processing logic performed by other external inputs for the application. The set of data elements identified is different from the sets identified for other external inputs for the application. The ILFs or EIFs referenced are different from the files referenced by other external inputs in the application.
Q27: Why software Engineers use measure?
A good software engineer would adopt mechanisms to measure the quality of the analysis and design models, the source code, and the test cases. At the project level, the primary focus is to measure errors and defects and derive relevant metrics such as requirement or design errors per function point, errors uncovered per review hour, errors per thousand lines of code.
Q28: Interdependency of each compartmentalized activity or task must b determined? If interdependency is not determined than what impact will be on overall project?
The interdependency of each compartmentalized activity or task must be determined. Some tasks must occur in sequence while others can occur in parallel. Some activities cannot commence until the work product produced by another is available.
Q29: Define project projection.
Risk Projection: Risk projection is concerned with risk estimation. It attempts to rate risks in two ways: Likelihood and consequences. There are four risk project activities. These are: • Establish a scale that reflects the perceived likelihood of risk • Delineate the consequences • Estimate impact • Note the overall accuracy of risk projection.
Q30: How design of software is measured quantitatively.
The quality of the architectural design can be measured by measuring its complexity as shown below:
Structural complexity S = (fout) 2 – Data complexity D = v/ (fout + 1)
‘v’ is the number of input and output variables – System complexity C = Σ (Si + Di)
Q31: Difference b\w generic and product specific risks.
Generic risks are threats to every project whereas Product specific risks are specific to a particular project.
Q32: What is EIF?
An external interface file (EIF) is a user identifiable group of logically related data or control information referenced by the application, but maintained within the boundary of another application.
Q33: Responsibilities of project manager.
In order to plan and run a project successfully, a project manager needs to worry about the following issues:
1. Product quality: what would be the acceptable quality level for this particular project and how could it be ensured?
2. Risk assessment: what would be the potential problems that could jeopardize the project and how could they be mitigated?
3. Measurement: how could the size, productivity, quality and other important factors be measured and benchmarked?
4. Cost estimation: how could cost of the project be estimated?
5. Project schedule: how could the schedule for the project be computed and estimated?
6. Staffing: how many people with what kind of resources would be needed and how that requirement could be fulfilled?
7. Other resources: what other hardware and software resources would be needed for the project?
8. Project monitoring: how the progress of the project could be monitored?
9. Customer communication: what kind of communication with the customer would be needed and how could it be established and maintained consistently?
Q34: Describe the types of risks.
Each project is faced with many types of risks. These include:

Project risks: Will impact schedule and cost – Includes budgetary, schedule, personnel, resource, customer, requirement problems

Technical risks: Impact the quality, timelines, and cost – Implementation may become difficult or impossible – Includes design, implementation, interface, verification and maintenance problems – Leading edge technology.

Business risks: Marketability – Alignment with the overall business strategy – How to sell – Losing budget or personnel commitments
Q35: Give appropriate RETS for a situation.
In a human resource management an employee is - Employee Permanent Contract -Employee Married Single
Course Instructor

Dr. Fakhar Lodhi
D.Sc. Computer Science
George Washington University, USA.
Software Engineering
 by Ian Sommerville
 Software Engineering: A Practitioner’s Approach
 by Roger S. Pressman