Page 61 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 3: Software Requirements

Context of Measurement: It indicates the environments in which context the software measurements Notes
are applied. Common software measures, There are significant numbers of software measures.
The following are a few common software measures:
Size

It indicates the magnitude of software system. It is most commonly used software measure.
It is indicative measure of memory requirement, maintenance effort, and development time.

LOC
It represents the number of lines of code (LOC). It is indicative measure of size oriented software
measure. There is some standardization on the methodology of counting of lines. In this, the
blank lines and comments are excluded. The multiple statements present in a single line are
considered as a single LOC. The lines containing program header and declarations are counted.
3.4.3 Advantages of Prototyping

The advantages of prototyping outperform the problems of prototyping. Thus, overall, it is
a beneficial approach to develop the prototype. The end user cannot demand fulfilling of
incomplete and ambiguous software needs from the developer. One additional difficulty in
adopting this approach is the large investment that exists in software system maintenance. It
requires additional planning about the re-engineering of software. Because, it may be possible
that by the time the prototype is build and tested, the technology of software development is
changed, hence requiring a complete re-engineering of the product.

Prepare a flow chart to show the steps of testing software.

3.5 Software Requirement Specification Document (SRS)

Requirements engineering is the systematic use of proven principles, techniques and language
tools for the cost effective analysis, documentation, and on-going evaluation of user’s needs and
the specification of external behaviour of a system to satisfy those user needs. It can be defined
as a discipline, which addresses requirements of objects all along a system development process.
The output of requirements of engineering process is Requirements Definition Description (RDD).
Requirements engineering may be defined in the context of Software Engineering. It divides
the Requirements Engineering into two categories. First is the requirements definition and the
second is requirements management.
Requirements definition consists of the following processes:

1. Requirements gathering.
2. Requirements analysis and modelling.
3. Creation of RDD and SRS.

4. Review and validation of SRS as well as obtaining confirmation from user.
Requirements management consists of the following processes:
1. Identifying controls and tracking requirements.

2. Checking complete implementation of RDD.
3. Manage changes in requirements which are identified later.

LOVELY PROFESSIONAL UNIVERSITY 55