2. 1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313

3. 2 Syllabus  Instructor; Rob Oshana  Office hours: By appointment  Phone; (281) 274-3211  Fax; (214) 768-3085  E-mail; oshana@airmail.netoshana@airmail.net  Web site; www.engr.smu.edu/cse/roshana/cse7313

4. 3 Syllabus  Required Text Book: Managing Software Requirements; A Unified Approach, by Dean Leffingwell and Don Widrig, Addison Wesley, ISBN 0201615932  Supplementary Texts (Do not purchase these)  Software Requirements: Objects, Functions, and States - Revised Edition, Prentice-Hall, ISBN 0-13-805763-X

5. 4 Syllabus  Practical Software Requirements - A Manuel of Content and Style, Benjamin L. Kovitz, Manning, ISBN 1-884777-59-7

6. 5 Grading  Student Evaluation; The course grade will be computed as follows:  Midterm Exam30%  Final Exam30%  Homework15%  Project 25%

7. 6 Course goals  Provide pragmatic team skills to help you and your team perform effective requirements management  Understand user and stakeholder needs  Define a system based on those needs  Manage scope of software intensive system  Refine the system definition  Build the right system

8. 7 What the course is not  This is not a UML course  This is not a coding/implementation course  This is not an OO course  This is not a requirements tools course

9. 8 Course layout (Requirements)  Module 1; Requirements engineering introduction  Module 2; Analyzing the problem  Module 3; Problem solving  Module 4; Understanding the problem domain  Module 5; Problem framing  Module 6; Types of problem frames

10. 9 Course layout  Module 7; Understanding stakeholder needs; user, function, and task analysis  Module 8; Requirements elicitation techniques  Module 9; Requirements elicitation techniques; Use Cases  Module 10; Requirements elicitation techniques; Prototyping 1

11. 10 Course layout  Module 11; Requirements elicitation techniques; Prototyping 2  Module 12; System modeling; Conceptual modeling (UML)  Module 13; Modeling techniques using UML  Module 14; System modeling; Finite State Machines and State Transition Diagrams

12. 11 Course layout  Module 15; System modeling; Dialog Maps, Data Flow Diagrams, and Entity- Relationship diagrams  Module 16; System modeling; Behavior specification using sequence enumeration  Module 17; Developing a Software Requriements Specification and Interface Design Specification  Module 18; Managing scope

13. 12 Course layout  Module 19; Risk management and managing change  Module 20; Writing good requirements  Module 21; Overview of Software Requirements Management Tools  Design topics to follow

14. 13 Assignments and additional reading  Homework assignments will be posted on the web with due dates  Project definition will be posted on the web in the next two weeks  Work from previous semesters  Additional readings will be posted on the web and discussed at indicated times  Please let me know if you will have a problem meeting a due date

15. 14 Outline TripTopicsReadings 1 The requirements problem Introduction to requirements management Problem analysis Leffingwell, Chapters 1- 4 2 Analyzing the problem Understanding user needs Elicitation techniques Leffingwell, Chapters 5- 10 3 More on understanding user needs Defining the system Leffingwell, Chapters 11- 18

16. 15 Outline TripTopicsReadings 4 Managing scope Refining the system definition Leffingwell, Chapters 19 - 26 5 Sequence enumeration Design patterns Design techniques Notes TBD 6 Design techniquesTBD

17. 16 Testing style CompetenceTest question cues KnowledgeList, describe ComprehensionSummarize, discuss, describe EvaluationExplain, compare AnalysisAnalyze, explain, compare