FOR MORE PAPERS, GO TO VUINSIDER.

COM

CS605 Mid Term

Reliability of a software is a

► functional requirement

► non-functional requirement

► Design Requirement

► None of the given

Build and Fix model is a ___________ type of software development activity.

► Mathematical

► Perfect

► Haphazard

► Planned

Every task should be assigned to a specific team -------------.

► Member (Page 93)

► Manager

► Organizer

► None of the given

Which one is not the Software project planning activity carried out by the
project manager for estimation?

Page 1 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

► Software scope estimation

► Resources requirements

► Time requirements

► Product Quality (Page 80)

While performing risk analysis, the impact of risk can not be measured
quantitatively

► True

► False

Degree of uncertainty that the product will meet its requirements and be fit for
its intended use is the

► Cost risks

► Schedule risks

► Performance risks (Page 87)

► None of the given choices

Proactive risk management philosophy is also some times termed as Indiana

Jones school of risk management

► true

► false (Page 84)

Page 2 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

The number of people required for a software project is determined

► after an estimate of the development effort is made.

► from an assessment of the technical complexity of the system.

► by the size of the project

► all of the given

Defect Removal Efficiency (DRE) can be measured by where E is Errors found

delivery and D is error found after delivery (typically within the first year of
operation)

► DRE= E/(E+D) (Page 69)

► DRE= E - (E+D)

► DRE= E * (E+D)

► None of the given

Integrity means that the software should

► help the users to enjoy usability

► none of the given

► withstand the attack from a hacker (Page 69) rep

► help the hacker to hack the system

In function point analysis technique EO stands for

Page 3 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

► Export operation

► Export output

► External output (Page 49)

► None of these

Which of these software characteristics are used to determine the scope of a

software project?

► context, lines of code, function

► context, function, communication requirements

► information objectives, function, performance (Page 34)

► communications requirements, performance, information objectives

In ____________a team is structured loosely and depends on individual

initiative of the team members

► Random paradigm (Page 32)

► closed paradigm

► synchronous paradigm

► open paradigm

In _________________ a team is structured along a traditional hierarchy of

authority

Page 4 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

► closed paradigm (Page 32)

► synchronous paradigm

► random paradigm

► open paradigm

______________ is the first stage of waterfall lifecycle model

► Requirement definition (Page 15)

► Operation

► Unit testing

► Implementation

___________ is not the part of software development loop.

► Status Quo

► Problem definition

► Technical development

► Task set (Page 10) rep

__________ is not the management part of software development activities.

► Coding p7

► Configuration Management

Page 5 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

► Quality Assurance

► Project planning (Page 7) not sure

Questions:
1. Do you think Flexibility and maintainability is same thing. tell reason. 3

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.

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

3. Define ''baseline data''?

Page 6 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

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.

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

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

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
Page 7 of 8
For more papers, go to VUInsider.com
 FOR MORE PAPERS, GO TO VUINSIDER.COM

CS605 Mid Term

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.

Page 8 of 8
For more papers, go to VUInsider.com