- Software Engineering-II
- CS605 Midterm Solved Past Papers
- Q. Effort validation.
- Q. Do you think Flexibility and maintainability is same thing. tell reason.
- Q. If spoilage is decreasing then what effect on maintainability.
- Q. If the bugs are fix then what will effect on quality of software?
- Q. why we need metrics?
- Q. Types of risk.
- Q. Define ”baseline data”?
- Q. Degree of Rigor?
- Q. Uses of control chart.
- Q. Differentiate between casual and structured rigor.
- Q. Can we guarantee 100% risk free software development i.e. can we develop a software without risk by following some software procedure? Comment it.
- Q. Do you agree with the statement that ILFs and EIFs are both user identifiable group of data? Comment it.
- Q. Discuss the role of interdependency and time allocation to fulfill a realistic project schedule?
- Q. What is meant by Risk Projection?
- Q. Can we count a single logical file of both EIF and ILF for same application?
- Q. Define Compartmentalization with context of project schedule.
- Q. In order to assess the overall project risks, what questions need to be addressed? Give any five?
- Q. Why software Engineers use measure?
- Q.Responsibilities of project manager.
- Q. Three External input counting rules
- Q. Interdependency of each compartmentalized activity or task must b determined? If interdependency is not determined than what impact will be on overall project?
- Q. Project projection.
- Q. Difference b\w generic and product specific risks.
- Q. What is EIF?
CS605 Midterm Solved Past Papers
Q. Effort validation.
Answer:- Every project has a defined number of staff members. As time allocation occurs, the project manager must ensure that no more than the allocated number of people has been scheduled at any given time.
Q. Do you think Flexibility and maintainability is same thing. tell reason.
Answer:- No, these are not the same things because System flexibility describes the ease of expanding the product with new feature sets and capabilities. System maintainability, on the other hand, describes the ease of coding bug repairs and adding minor features. Both are determined by the architecture and techniques used to create the code and resulting quality of the code.
Q. If spoilage is decreasing then what effect on maintainability.
Answer:- A cost oriented metric used to assess maintainability is called Spoilage. It is defined as the cost to correct defects encountered after the software has been released to the users. Spoilage cost is plotted against the overall project cost as a function of time to determine whether the overall maintainability of software produced by the organization is improving.
Q. If the bugs are fix then what will effect on quality of software?
Answer:- Defect repair/maintenance is considered to be any activity that supports the release functionality specification and it may a fix for some bugs or some maintenance to enhance the performance of the application.
Q. why we need metrics?
Answer:- Metrics give you a better insight into the state of the process or product. These insights are not the problems but just the indicators of problems. A software engineers collects measures and develops metrics and indicators.
Q. Types of risk.
Answer:- ) Each project is faced with many types of risks.
• 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
– Alignment with the overall business strategy
– How to sell
– Losing budget or personnel commitments
Q. Define ”baseline data”?
Answer:- In order to use the data for estimation and drawing conclusions, it must be base-lined. In the baseline, data from past projects is collected, cleaned, and put in a database. Such metrics baseline is used to reap benefits at the process, project, and product level.
Q. Degree of Rigor?
Answer:- To determine the set of tasks to be performed the type of the project and the degree of rigor required needs to be established. The degree of rigor can also be categorized as Casual, Structured, Strict, or Quick Reaction.
Q. Uses of control chart.
Answer:- We have to determine whether the trend is statistically valid or not. We also need to determine what changes are meaningful. A graphical technique known as control charts is used to determine this. Control charts are of two types: moving range control chart and individual control chart.
Q. Differentiate between casual and structured rigor.
Answer:- • Casual All process framework activities are applied, but only a minimum task set is required. It requires reduced umbrella tasks and reduced documentation. Basic principles of SE are however still followed. • Structured In this case a complete process framework is applied. Appropriate framework activities, related tasks, and umbrella activities (to ensure high quality) are also applied. SQA, SCM, documentation, and measurement are conducted in streamlined manner.
Answer:- Let’s be clear: there’s no such thing as risk free software. You can’t do anythingwithout taking some risk. But what’s easy to overlook, is that not doing something is a risk, too. Not fixing a bug runs the risk that its more serious than you thought; more prevalent than you thought; that it could happen to an important customer, someone in the press, or a highly valued customer – with real revenue risk. You run the risk that it collides with another, as yet unknown bug, potentially multiplying the pain. Sometimes not releasing feels like the safest thing to do – but you’re releasing software because you know something is wrong. So what you gonna do? No business wants to accept risk, you have to mitigateit somehow. The simple, easy and wrong thing to do is to add more process. The braver decision, the right decision, is to make it easy to undo any mistakes.
Answer:- Yes, both are user identifiable group of logically related data. The primary intent of an ILF is to hold data maintained through one or more elementary processes of the application being counted. The primary intent of an EIF is to hold data referenced through one or more elementary processes within the boundary of the application counted. This means an EIF counted for an application must be in an ILF in another application.
Q. Discuss the role of interdependency and time allocation to fulfill a realistic project schedule?
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.
• Time allocation
Each task to be scheduled must be allocated some number of work units (e.g. person-days of effort). In addition, each task must be assigned a start date and an end date which is a function of the interdependencies and number of resources.
Q. What is meant by Risk Projection?
Answer:- 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
Q. Can we count a single logical file of both EIF and ILF for same application?
Answer:- A logical file cannot be counted as both an ILF and EIF for the same application. If the data group satisfies both rules, count as an ILF.
Q. Define Compartmentalization with context of project schedule.
Answer:- The project must be compartmentalized into a number of manageable activities and tasks. To accomplish compartmentalization, both the product and process are decomposed.
Q. In order to assess the overall project risks, what questions need to be addressed? Give any five?
Answer:- 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?
Q. Why software Engineers use measure?
Answer:- 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.
Q.Responsibilities of project manager.
Answer:- 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. Customer communication: what kind of communication with the customer would be needed and how could it be established and maintained consistently?
7. Staffing: how many people with what kind of resources would be needed and how that requirement could be fulfilled?
8. Other resources: what other hardware and software resources would be needed for the project?
9. Project monitoring: how the progress of the project could be monitored?
Q. 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:
o Processing logic is unique from the processing logic performed by other external inputs for the application.
o The set of data elements identified is different from the sets identified for other external inputs for the application.
o The ILFs or EIFs referenced are different from the files referenced by other external inputs in the application.
Answer:- 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.
Q. Project 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
Q. Difference b\w generic and product specific risks.
Answer:- Generic risks are threats to every project whereas Product specific risks are specific to a particular project.
Q. What is EIF?
Answer:- 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.