Chapter 2

Software Requirements
Engineering

By
Santosh Ramdasi

1 3/11/2021
 Ppt 2.1 Software Engineering Practices

Definition:- Software Engineering practices can be

defined as set of Concepts, Principles, Methods And
Tools that are used by software practitioners on day to
day basis for developing software product.
Elements Of Software Practice:-
1. Concept
2. Principles
3. Methods
4. Tools

2 3/11/2021
Ppt 2.2 Core Principles of S/W Engineering
David Hooker Proposed seven core principles

Principle 1# Reason At all exist.

Principle 2# Keep it simple but perfect

Principle 3# Maintain the Vision

Principle 4# What you produce, others will consume

Principle 5# Be open to the Future

Principle 6# Plan Ahead For Reuse

3 Principle 7# Think 3/11/2021

 Ppt 2.3 Communication Practices
⚫ Principle 1: Listen Carefully
⚫ Principle 2: Be prepared before you communicate
⚫ Principle 3: Be prepared to facilitate the activity.
⚫ Principle 4: Face to face communication
⚫ Principle 5: Take notes and document decision
⚫ Principle 6: Strive for collaboration
⚫ Principle 7: Stay focused, modularize your discussion
⚫ Principle 8: If something is unclear, draw a picture
⚫ Principle 9: Keep the discussion to “move on”.
⚫ Principle 10: Negotiation is successful when both the
parties agree.
4 3/11/2021
 Ppt 2 .4 Planning Practices
⚫ Principle 1: Understand the scope of project
⚫ Principle 2: Involve the customer in planning activities
⚫ Principle 3: Recognize that planning is iterative
⚫ Principle 4: Estimate based on what you know
⚫ Principle 5: Consider risk as you define the plan
⚫ Principle 6: Be realistic
⚫ Principle 7: Adjust granularity as you define the plan
⚫ Principle 8: Define how you are going to achieve quality
⚫ Principle 9: Describe how you aim to accommodate
change
⚫ Principle 10: Always keep track of plan and make changes
as required
5 3/11/2021
 Continued…
⚫ Boehm suggests WHH principles for
planning practices as
1. Why is the system being developed?
2. What will be done?
3. When will it be accomplished?
4. Who is responsible for function?
5. Where are they organizationally
located?
6. How will the job be done technically
6
and managerially? 3/11/2021
 Ppt 2.5 Modeling Practices

⚫ Analysis Model

⚫ Design Model

7 3/11/2021
 Principles

⚫ The information Domain of problem must be

clearly represented
⚫ The functions of the software must be defined
clearly
⚫ Behaviors of system must be defined clearly
⚫ The clear hierarchy among information, functions
and behavior must be shown
⚫ Analysis should be clear enough to convert it into
design model

8 3/11/2021
 Ppt 2.5 .2 Design Modeling
Principles

⚫ Design should be traceable from analysis model.

⚫ Consider the architecture of the system to be built
⚫ Design of data is as important as design of
functions
⚫ Internal as well as external interfaces must be
designed
⚫ User interface design must satisfy all need of end
user

9 3/11/2021
 Continued….
⚫ Component level design should be
functionally independent
⚫ Components should be loosely coupled
to one another and to the external
environment
⚫ Design modules should be easy to
understand
⚫ Accept that design modeling is
10 iterative. 3/11/2021
Fig. State Transition Diagram for Photocopier
11 So ware 3/11/2021
 Ppt 2.6 Construction Practices
Construction activity includes
1. Coding &
2. Testing
Following are the sequential steps of testing process.
I. Unit Testing (units as individual)
II. Integration Testing (focus on design&integration)
III. Validation Testing (focus on requirements)
IV. Acceptance Testing (at client side)

12 3/11/2021
 Ppt 2.6.2 Coding Principles

1. Understand exact problem for which you are trying.

2. Understand basic design and concepts
3. Select appropriate programming language
4. Perform unit tests after each unit completion
5. Algorithm must follow structured programming
6. Use suitable data structures
7. Keep minimum nested conditions and loops
8. Keep meaningful variables and use comments

13 3/11/2021
 Ppt 2.6.3 Testing Principles
1. Test must be conducted to validate customer
requirement
2. Test should be well planned
3. Pareto principle(80% errors traceable to 20%) is
applicable to software testing
4. Testing starts from individual unit and goes towards
the testing of whole system
5. Accept that testing all paths is not possible

14 3/11/2021
 Ppt 2.7 Deployment Practices
1. Manage customer’s expectations
2. Assemble and test complete delivery package
3. Record keeping mechanism must be established for
customer support
4. Provide essential instructions, documentations and
manual
5. Don’t deliver any defective or buggy software to the
customer

15 3/11/2021
 Engineering
1. It is carried out through execution of seven
functions.
a) Inception
b) Elicitation
c) Elaboration
d) Negotiation
e) Specification
f) Validation
g) Requirement Management.

16 3/11/2021
specification

⚫ SRS is a special kind of document which contains

user requirement for a system which states
properties and constraints that must be satisfied by
a software system .
⚫ SRS is also called as requirement document .
⚫ It should be easily changeable if any changes occur
⚫ SRS document record

17 3/11/2021
 Advantages of SRS

⚫ Software SRS contains the base for agreement

among the client and the company who develop the
product on expected work of software product
⚫ A high quality SRS decrease the cost of
development .

18 3/11/2021
 Characteristics of SRS
⚫ CORRECT

⚫ Unambiguous

⚫ Complete

⚫ Ranked for importance's

⚫ Modifiable

⚫ Traceable

⚫ verifiable

19 3/11/2021
Product Requirements SRS

20 3/11/2021
 Question Bank
Q1 Enlist core principal of software engineering practices
explain any two.
Q2 what are communication principles? Explain their meaning
Q3 State need of software requirement specification (SRS)
Q4 list and explain planning principles any two.
Q5 List and explain deployment principles any two
Q6 what are major tasks of requirements of engineering
Q7 Enlist characteristics of SRS
Q8 Explain cardinality with example
Q9 With a neat diagram explain analysis model
Q10 Explain the various elements of analysis modeling in
detail

21 3/11/2021
Question Bank 2 marks
Question
Sr.no Question Bloom
Level

1 Enlist core principal of software engineering Knowledge

2 what are communication principles? Remember

3 With a neat diagram analysis model Knowledge

4 List deployment principles any four Remember

5 State need of software requirement specification (SRS) Knowledge

22 3/11/2021
Question Bank 4 marks
Question
Sr.no Question Bloom
Level

1 Enlist core principal of software engineering Knowledge

practices explain any two.

2 list and explain planning principles any two. Understand

3 Explain cardinality with example Knowledge

4 Explain the various elements of analysis modeling in detail Remember

23
5 List and explain deployment principles any two Understand
3/11/2021