CS605 Midterm Solved Subjective with References by Moaaz

Solved Subjective · From Midterm Papers · 16 May,2013 · PSMD01 · 1: why we need metrics? 2 marks

Answer: (Page 66) 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.

2: Degree of Rigor? 2 marks

Answer: (Page 96) 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.

3: uses of control chart. 3 marks

Answer: (Page 75) 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.

4: if the bugs are fix then what will effect on quality of software? 5 marks

Answer: (Page 75) 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

2. Effort validation. 2

Answer: (Page 93) 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.

3. do you think Flexibility and maintainability is same thing. tell reason. 3

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.

4. If spoilage is decreasing then what effect on maintainability. 3

Answer: (Page 68) 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.

Define ''baseline data''?

Answer: (Page 72) 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.

Differentiate between casual and structured rigor. 2 marks

Answer: (Page 96)

• 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.

Can we guarantee 100% risk free software development i.e. can we develop a software without risk by following some software procedure? Comment it. 5 marks

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.

Do you agree with the statement that ILFs and EIFs are both user identifiable group of data? Comment it. 3 marks

Answer: (Page 42) 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.

Given the data, draw a moving range control chart in order to explain whether the process is stable or unstable? 5 marks