Software Requirements and Design Class 4 Khalid Ishaq.

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Advertisements

EC Requirements Elicitation Originally developed by Michael Madigan, StorageTek Manager, PAL Engineering For ECEN4033/5033 Software Engineering of Standalone.
1 Team Skill 2 Chapter 8: The Challenge of Requirements Elicitation Due to The "Yes, But" Syndrome The "Undiscovered Ruins" Syndrome The "User and the.
Understanding User and Stakeholder Needs
CS3773 Software Engineering Lecture 03 UML Use Cases.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
Design analysis implementation testing maintenance Waterfall Development Process Linear one phase is completed before the next begins in practice, must.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Documenting Requirements using Use Case Diagrams
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Kari R. Schougaard, PhD Stud. Værktøjer og Teknikker, 2006 UNIVERSITY OF AARHUS Department of Computer Science Unified Modeling Language Visual language.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews 2. Workshops 3. Brainstorming.
Requirements Management Course Plan System Group Company – Training Department By: Dr. Ahmad Abdollahzadeh.
Team Skill 2 Understanding Stakeholders Needs
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
RUP Requirements RUP Artifacts and Deliverables
UML - Development Process 1 Software Development Process Using UML (2)
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 5: Understand Stakeholder Needs.
Use Cases College of Alameda Copyright © 2007 Patrick McDermott.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
© 2000 Ian Alexander - Introduction to Scenarios Introduction to Scenarios A range of techniques for engineering better systems Ian Alexander
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Requirement Handling
Team Skill 2 Understanding User and Stakeholder Needs The Challenge of Requirements Elicitation (8)
Gerhard Dueck -- CS3013Requirements Capture 1  From Vision to Requirements  Why it is difficult?  Developers are not users  Inadequate requirements.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Requirements Management with Use Cases Module 5: Understand Stakeholder Needs Requirements Management with Use Cases Module 5: Understand Stakeholder Needs.
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Assignment Help From Requirements Elicitation to Elicitation.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 1: Introduction.
MADALINA CROITORU Software Engineering week 4 Practical Madalina Croitoru IUT Montpellier.
1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.
Unit-3 Identifying use cases Object Analysis Classification
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Lecture 4/2/16. Learning Objective Establishing requirements Define requirements Requirements discovery vs requirements gathering Classifying Requirements.
Team Skill 2 Understanding User and Stakeholder Needs The features of a Product or System (9)
Requirements in the product life cycle Chapter 7.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
Object Oriented Systems Design
IST 311 – Object-Oriented Design & Software
Interviewing S.Vidya,AP/CSE.
EKT 421 SOFTWARE ENGINEERING
Object Oriented Systems Development
James Miller, Julia John
System Modeling Chapter 4
The role of the Analyst in requirements Elicitation
Recall The Team Skills Analyzing the Problem (with 5 steps)
UML: Unified modeling language
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
The Challenge of Requirements Elicitation
The Features of a Product or System
Use Cases & Use Case Diagrams
Need for the subject.
CS 426 CS 791z Topics on Software Engineering
CS 426 CS 791z Topics on Software Engineering
Presentation transcript:

Software Requirements and Design Class 4 Khalid Ishaq

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

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

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

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

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

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

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

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

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

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

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

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

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