1. Requirements Management Course Plan System Group Company – Training Department By: Dr. Ahmad Abdollahzadeh

2. General Information  Title: Requirements Management  Training Mode: Training the Trainees  Objective: A detailed discussion on requirements management activities including, requirements elicitation, requirements documentation, requirements analysis, requirements tracing and requirements review.  Attendees: System Analysts, Business Analysts, Software Engineers  Duration: 60 Hours

3. References (1/2)  Whitten, Jeffry L., Bentley L. D. and Dittman K. C. Systems Analysis and Design Methods, 5th Edition, McGraw-Hill, 2001.  Pressman Roger, Software Engineering: A Practitioner's Approach, 5th Edition, McGraw-Hill, 2001.  Sommerville, Ian, Software Engineering, Sixth Edition, Addison- Wesley, 2000.  Kendall K., Kendall J., Systems Analysis and Design, 5th Edition, Prentice Hall, 2001.  Ghezzi, C., Jazayeri Mehdi, Mandiroli, N., Fundamentals of Software Engineering, 2nd Edition, Prentice-Hall, 2002.  Bennett S., McRobb S. and Farmer R., Object-Oriented Systems Analysis and Design using UML, McGraw-Hill, 2001.  Schach, Stephen, Object-Oriented and Classical Software Engineering, 5th Edition, McGraw-Hill, 2001.

4. References (2/2)  Bruegge, B., Dutoit A. H., Object-Oriented Software Engineering: Using UML, Patterns and Java, Prentice-Hall, 2004.  Fowler, M. UML Distilled: A Brief Guide to Standard Object Modeling Language, 2nd Edition, Addison-Wesley, 2000.  Booch G, Rumbaugh J, Jacobson I, The Unified Modeling Language: User Guide Addison Wesley, 1999.  Rumbaugh J, Jacobson I, Booch G. The Unified Modeling Language: Reference Manual Addison Wesley 1999.

5. Overall Course Plan  An overview of Requirements Management  Requirements Elicitation  Requirements Analysis  Requirements Validation  Requirements Specification  Requirements Change Management

6. An Overview of Requirements Management  What is a Requirement?  Types of Requirements Functional Requirements Non-Functional Requirements  Requirements Specifications  Requirements Traceability

7. Requirements Elicitation (1/2)  Problem Analysis  Application Domain Understanding  Business Understanding  Understanding Needs and Constraints of Stakeholders  Elicitation Techniques

8. Requirements Elicitation (2/2)  Elicitation Techniques Document Study Observation Interviews Questionnaires Requirements Workshop Brainstorming & Idea Reduction Use Cases Role Playing Business Modeling

9. Requirements Analysis (1/2)  What is Requirements Analysis?  Why Requirements Analysis?  Modeling  Modeling Language  Requirement Analysis Methods  Object Oriented Analysis (OOA)

10. Requirements Analysis (2/2)  OOA Activities Use-case Modeling Class Modeling Behavioral Modeling  Design Patterns  Requirements Analysis Tools

11. Requirements Validation  What is Requirements Validation?  Requirements Review  Requirements Review Techniques  Requirements reviews  Prototyping  Acceptance tests  Model Validation and Automated consistency analysis

12. Requirements Specification  What is Software Requirements Specification?  How Requirements are Specified?  Who Uses SRS?  What are specification techniques?  What are the factors for choosing appropriate technique?

13. Requirements Change Management  Requirements Change Factors  Documenting and Storing Requirements  Requirements Traceability  Change Management