SOFTWARE REQUIREMENT

 SOFTWARE REQUIREMENT
ENGINEERING L T P C
3 0 0 3
UNIT I INTRODUCTION 9
Introduction - Requirements Problem –
Requirements management – Requirements
and software life cycle-software team.
UNIT II ANALYSING THE PROLEM 9
The five steps in problem analysis–
business modeling – Systems engineering of
software intensive systems – Understanding
user and stakeholders needs – Features of
a product or system –Interviewing –
Requirements workshops- Brain storming
and Idea
reduction- storyboarding
UNIT III DEFINING THE SYSTEM 9
Use case primer-Organizing requirement
Information-Vision Document-Product
Management-Managing scope-Establishing
Project scope-Managing customer
UNIT IV REFINING THE SYSTEM DEFINITION
9
Software requirement-Refining the use
cases-developing the supplementary
specification- Ambiguity and specificity -
Technical methods for specifying
requirements
UNIT V BUILDING THE RIGHT SYSTEM 9
From use cases to Implementation-From use
Cases to Test cases-Tracing
requirements-Managing Change-Assessing
Requirements Quality in Iterative
Development-Agile Requirement methods.
TOTAL : 45 PERIODS
TEXT BOOK:
1. Leffingwell, D., Widrig, D., “Managing
Software Requirements A Use case
approach”,
Second Edition, Pearson Education, 200UNIT
III
REFERENCES:
1.. Swapna Kishore, Rajesh Naik, “Software
Requirements and Estimation”, Tata
McGraw Hill, 2001
2. K.Weigers, Software Requirements,
Microsoft Press, 1999.
3 Ian Sommerville and P Sawyer,
“Requirements engineering a good practice
Guide”,
Wiley India, 1997