Page 67 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 3: Software Requirements

Software Engineering Institute’s Capability Maturity Model for Software (CMM), the relatively Notes
new field of RE does not enjoy well-established, proven strategies for improving or assessing
the requirements process. This leads to a strong need for assessment and measurement of
effects of rigorous RE practice in software development. Many practical guides naturally
focus on the RE process within the larger software development process, but deliberately
present their material vaguely, reminding practitioners that good requirements engineering
(process) depends on the organization, its development process, its tools and particular
circumstances, or even that every project needs a different process. These sentiments offer
little comfort to the practitioner. These same guides warn that revolutionary change is not
practical; that instead careful evolutionary improvements are more fruitful. Practitioners are
encouraged to measure results to gauge effectiveness, but topics on empirical assessment are
largely left to the imagination, as an exercise for the reader. Further, the role of requirements
engineering in software development has been discussed in the literature as important in
planning activities such as: determining the nature of the problem, exploring solutions
through feasibility studies, and ultimately deciding precisely what to build. It is notified
that the opportunity for RE to improve all subsequent stages of the development life-cycle,
ultimately leading to broader improvements in software quality and user satisfaction. An
important note is that the RE process improvements at ACUS occurred in parallel with
initiatives for improvement in other processes in the organization, such as software quality
assurance, project planning and project tracking.
Questions

1. What is the reengineering process?
2. What are its advantages and disadvantages?

Self Assessment Questions

6. Software Engineering …………. provides the technical “how to” for Building the software
(a) Tools (b) Methods
(c) Data (d) Process

7. A good specification should be?
(a) Unambiguous (b) Distinctly Specific
(c) Functional (d) All of these.

8. If every requirement stated in the Software Requirement Specification (SRS) has only one
interpretation, SRS is said to be:
(a) Correct (b) unambiguous.

(c) Consistent (d) verifiable.
9. SRS is also known as specification of

(a) White box testing (b) Stress testing
(c) Integrated testing (d) Black box testing
10. The feature of the object oriented paradigm which helps code reuse is:
(a) Object (b) class

(c) Inheritance (d) aggregation

LOVELY PROFESSIONAL UNIVERSITY 61