CS605 Final Term Solved Subjective with References by Moaaz

CS605 – Soft Engendering II · Solved Subjective · From Final Term Papers · 16 July,2013 · PSMD01 · characteristics of risk

Answer: (Page 84) A risk has two characteristics:

• Uncertainty – the risk may or may not happen
• Loss – if the risk becomes a reality, unwanted consequences or losses will occur.

types of reviews

Answer: (Page 110) There are many types of reviews. In general they can be categorized into two main categories namely informal and formal technical reviews.

when a system called legacy system

Answer: (Page 134) A system is considered to be a legacy system if it has been in operation for many years. A legacy system has many components. These include business processes, business rules, application software, application data, support software, and system hardware.

diff btw synchronous and open paradigm

Answer: (Page 32)

• open paradigm—attempts to structure a team in a manner that achieves some of the controls associated with the closed paradigm but also much of the innovation that occurs when using the random paradigm
• synchronous paradigm—relies on the natural compartmentalization of a problem and organizes team members to work on pieces of the problem with little active communication among themselves

If SCM is not its proper place then what are disadvantages?

Answer: (Page 119) Software configuration management (SCM) is one of the five KPA required for an organization to be at CMM level 2. That means, according to SEI, effective project management is not possible without having a proper SCM function in place. The basic idea behind SCM is to manage and control change. As mentioned by Bersoff, no matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. It is therefore essential that we manage and control it in a fashion that this continuous change does not convert into chaos.

requirement attributes

Answer: (Page 127) We need to tag requirements with certain attributes in order to manage them in an orderly fashion. Attributes are used to establish a context and background for each requirement. They go beyond the description of intended functionality. They can be used to filter, sort, or query to view selected subset of the requirements. A list of possible attributes is enumerated as below:

1. Requirement ID
2. Creation date
3. Created by
4. Last modified on
5. Last modified by
6. Version number
7. Status
8. Origin
9. Subsystem
10. Product Release
11. Priority

2 Marks

Why in the software engineering measurements are collected?

Answer: (Page 65) Because Measurement helps in identification of the problem as well as in determining the effectiveness of the remedy. A software engineers collects measures and develops metrics and indicators.

Fault tree can be used to predict the chain of events?

Answer: (Page 117) Analysis techniques such as fault tree analysis can be used to predict the chain of events that can cause hazards and the probability that each of these events will occur to create the chain.

“Message chain” can be a bad smell in the coding justifies it with reason?

Answer: (Page 144) A client asks an object for another object and then asks that object for another object etc. Bad because client depends on the structure of the navigation

CCB stands for what?

Answer: (Page 124) CCB stands for Change Control Board

Marks 3…

Write down the guide line to make a review meeting success full?

Answer: (Page 113) The followings are guide lines to make review meeting successful:

• Avoid drift
• Limit debate and rebuttal
• Enunciate problem areas but don’t try to solve all problems
• Take written notes
• Limit the number of participants and insist upon advanced preparation
• Develop a checklist for each product that is likely to be reviewed
• Allocate resources and schedule time for FTRs
• Conduct meaningful training for all reviewers
• Review your early reviews
• Determine what approach works best for you

What characteristics of extreme programming make it different to the other life cycle models?

Answer: (Page 23) One very important feature of eXtreme programming is the concept of pair programming. In this, a team of two developers develop the software, working in team as a pair to the extent that they even share a single computer.

If the requirements are not traceable then what will be the impact on the requirement management?

Answer: (Page 133) Requirement traceability is a very important consideration for requirement management. It is really hard to manage requirements that are not traceable.