1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313

2 Syllabus  Instructor; Rob Oshana  Office hours: By appointment  Phone; (281)  Fax; (214)  ;  Web site;

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

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

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

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

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

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

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

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

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

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

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

14 Outline TripTopicsReadings 1 The requirements problem Introduction to requirements management Problem analysis Leffingwell, Chapters Analyzing the problem Understanding user needs Elicitation techniques Leffingwell, Chapters More on understanding user needs Defining the system Leffingwell, Chapters

15 Outline TripTopicsReadings 4 Managing scope Refining the system definition Leffingwell, Chapters Sequence enumeration Design patterns Design techniques Notes TBD 6 Design techniquesTBD

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