CP7007 SOFTWARE REQUIREMENTS ENGINEERING

CP7007        SOFTWARE REQUIREMENTS ENGINEERING

UNIT I         DOMAIN UNDERSTANDING

Introduction  – Types of requirements – Requirements engineering process – Validating requirements – Requirements and design – Requirements and test cases – introduction to business domain – Problem analysis  – Fish bone diagram – Business requirements – Business process modeling – Business use cases – Business modeling notations – UML Activity diagrams. 

  

UNIT II       REQUIREMENTS ELICITATION

Introduction – Understanding stakeholders' needs – Elicitation techniques – interviews, questionnaire, workshop, brainstorming, prototyping – Documenting stakeholders' needs    

UNIT III          FUNCTIONAL REQUIREMENTS

Introduction – Features and Use cases – Use case scenarios – Documenting use cases – Levels of details – SRS documents. 

UNIT IV          QUALITY ATTRIBUTES AND USER EXPERIENCE 

Quality of  solution – Quality attributes – Eliciting quality attributes – Quality attribute workshop (QAW) – Documenting quality attributes – Six part scenarios – Usability requirements – Eliciting and documenting usability requirements – Modeling user experience – Specifying UI design  

UNIT V           MANAGING REQUIREMENTS

Defining scope of the project – Context diagram – Managing requirements – Requirements properties – Traceability – Managing changes – Requirements metrics – Requirements management tools.  

REFERENCES: 

1. Axel van Lamsweerde, "Requirements Engineering", Wiley, 2009 

2. Gerald Kotonya, Ian Sommerville, "Requirements Engineering: Processes and Techniques", John Wiley and Sons, 1998 

3. Dean Leffingwell and Don Widrig, “Managing Software Requirements: A Use Case Approach (2nd Edition) ”, Addison-wesley, 2003 

4. SEI Report, “Quality Attributes Workshop”, http://www.sei.cmu.edu/library/abstracts/reports/03tr016.cfm , 2003 

5. J Nielsen, “Usability Engineering”, Academic Press, 1993