Presentation is loading. Please wait.

Presentation is loading. Please wait.

Software Requirements and Design Class 4 Khalid Ishaq.

Similar presentations


Presentation on theme: "Software Requirements and Design Class 4 Khalid Ishaq."— Presentation transcript:

1 Software Requirements and Design Class 4 Khalid Ishaq

2 The Business Model A problem Analysis Technique –Use Case Modeling –Object Models

3 The Business Model Use Cases –Consists of actors and use cases to model the intended functions of the business model

4 The Business Model Object Models –Describe the entities that deliver the functionality to realize the business use cases and how these entities interact

5 The Business Model Methodologies –UML (Unified Modeling Language) –Developed by Booch, Jacobson and Rumbaugh and other methods after much public feedback and revision process

6 Requirements Elicitation The three endemic syndrome The “Yes, But” Syndrome The “Undiscovered Ruins” Syndrome The “User and the Developers“ Syndrome

7 Requirements Elicitation The “Yes, But” Syndrome –Users thinking changes from the beginning till the end of the project

8 Requirements Elicitation The “Undiscovered Ruins” Syndrome –The more that are found, the more you know remain

9 Requirements Elicitation The “User and the Developers“ Syndrome Users cannot articulate the problem Users think they know what they want until developers show them what they think they wanted Analyst think they understand the problem better than the users Everybody believes everybody else is politically motivated

10 Requirements Elicitation The “User and the Developers“ Syndrome Users cannot articulate the problem Users think they know what they want until developers show them what they think they wanted Analyst think they understand the problem better than the users Everybody believes everybody else is politically motivated

11 Requirements Elicitation Techniques –Interviews –Workshops –Brainstorming and Idea Reduction –JAD –Storyboards and Use Cases –Prototyping

12 Requirements Elicitation Needs and Features –What “I need” –How “What I think the system should do to address my needs” –Abstraction –Attributes Status Priority/Benefits Effort Risk Stability Target release Assigned to Reason

13 Requirements Elicitation Interviews –Simple and direct technique –Context Free questioning –Scenarios

14 Requirements Elicitation Tips –Prepare some Questions and review them before the interview –Research the background of the stakeholders –Either tape or note down the answers –Try using a template to ask the right questions


Download ppt "Software Requirements and Design Class 4 Khalid Ishaq."

Similar presentations


Ads by Google