Lecture: Requirements Development - Vision and Scope.

Slides:



Advertisements
Similar presentations
Chapter 5 – Enterprise Analysis
Advertisements

Chapter 2 – Software Processes
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
ATM User Interface Design. Requirements A bank customer is able to access his or her account using an automatic teller machine. To be able to use an ATM.
June 1, 2000 Object Oriented Programming in Java (95-707) Java Language Basics 1 Lecture 4 Object Oriented Programming in Java Class Design Process.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
OO Development Process. UML and Process UML standardizes notation, not process –Increase likelihood of widespread acceptance There is significant variability.
8/28/2005ECEN5543 Req Elicitation1 Targets of Requirements Engineering ECEN 5543 SW Engineering of Standalone Programs University of Colorado, Boulder.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Documenting Requirements using Use Case Diagrams
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
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.
Bina Nusantara 7 C H A P T E R MODELING SYSTEM REQUIREMENTS WITH USE CASES.
© Copyright Eliyahu Brutman Programming Techniques Course.
Inception What needs to be done? Describe the vision and business case for this project. Determine if the project is feasible. Determine if the enterprise.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
Lecture Nine Database Planning, Design, and Administration
NJIT Inception is not the Requirements Phase Chapter 4 Applying UML and Patterns Craig Larman.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
RUP Requirements RUP Artifacts and Deliverables
BTS330: Business Requirements Analysis using OO Lecture 5 Requirements Development: Practices and Skills.
Requirements Management with Use Cases Module 6: Define the System Requirements Management with Use Cases Module 6: Define the System.
1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Logic Modeling Logic and timing are not represented on data flow diagrams or entity-relationship diagrams Processes contain logic - what happens under.
ITEC224 Database Programming
Business Analysis and Essential Competencies
1 BTS330 Vision and Scope. √ Determine a vision for the business √ Create initial use-case model showing key actors and use cases by business area Benefits.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
CS 360 Lecture 6.  A model is a simplification of reality  We build models to better understand the system being developed.  We build models of complex.
Software Requirements Engineering CSE 305 Lecture-2.
Introduction to the Requirements Document
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Software Engineering Management Lecture 1 The Software Process.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Integration Points Basic Setup Payroll Processing Key Implementation Tips Session focus.
Lecture 7: Requirements Engineering
BTS330: Business Requirements Analysis using OO Lecture 7: Understanding User Requirements.
UML-1 3. Capturing Requirements and Use Case Model.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
Payroll Administrator Payroll ManagerHR Assistant Compensation and Benefits Manager Release earning statement lines Edit earning statement.
Requirement engineering Good Practices for Requirements Engineering
Information Systems Analysis and Management Modeling Sys. Requirements with Use Cases Arnie Lund, Jeffrey Kim May 5, 2009 INFO380.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Systems Development Life Cycle
1 BTS330 Requirements Gathering Review. What are requirements? It depends who you ask… Requirements try to describe the whole system you are creating.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
1 Accounting systems design & evaluation Karen Lau 25 Feb 2002.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Requirements Analysis
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
ISMT221 Information Systems Analysis and Design Use case diagram Lab 4 Tony Tam.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
OBJECT-ORIENTED TESTING. TESTING OOA AND OOD MODELS Analysis and design models cannot be tested in the conventional sense. However, formal technical reviews.
Use Case, Component and Deployment Diagrams University of Sunderland.
Project Management Finals Lesson 1 - Principles - Techniques - Tools.
Types and Characteristics of Requirements
How does a Requirements Package Vary from Project to Project?
Presentation transcript:

Lecture: Requirements Development - Vision and Scope

 A Project is a sequence of unique, complex, and connected activities having one goal or purpose and that must be completed by a specific time, within budget, and according to specification. ( p. 65)

Elicitation AnalysisSpecificationValidation Clarify Correct and close gaps Rewrite Re-evaluate Text, p. 59

 Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

1. Define Vision/Scope 2. Identify users/stakeholders: classes, reps, decision makers 3. Select elicitation techniques 4. Identify, prioritize and develop use cases  Some modeling here (e.g. user interfaces)  Includes business rules

5. Specify quality attributes 6. Derive/create requirements specification  Including external interfaces? Constraints? 7. Model 8. Review 9. Prototype

10. Develop/evolve Architecture 11. Allocate requirements to (software) components 12. Develop test cases 13. Validate

 Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

 Common understanding of business requirements  Provides boundary  Vision: whole “product”  Scope: particular project or iteration or...

Product Vision Scope for Business Area 1 Scope for Business Area 2 And so on… These might be different releases

 For.. (target)..who.. (need).. the.. (product).. is.. (category).. that.. (key benefit).. unlike.. (current or competitor).. our product.. (advantages)  Text, (p.85)

 Features  Key Stakeholders  Operating Environment  Use Case Diagram

 Major Features  Describe functionality of each feature (include as much as you know!)  E.g. ▪ Payroll Creation: The payroll creation feature will allow the client to set up and execute a regularly scheduled process to calculate employee wages owing for a specific time period, to make appropriate deductions, and to generate an electronic deposit to each employee’s bank account. A pay slip will also be printed for each employee.

 Key Stakeholders  Who needs to be part of the development?  Who will use the system and how?

 Operating Environment  Physical environment ▪ Distribution? ▪ Locations?  Availability/Performance/Integrity requirements

 Revisit the requirements development cycle  Revisit the requirements development process  Vision and Scope  Exercise

 In Your Group  Create a vision statement for the entire system

In Your Group  Identify the Business Areas of the that must interface with each other and decide how

 Define initial scope for each business area within ▪ Create a description of major system features ▪ If you finish then: ▪ Identify key stakeholders ▪ Define operating environment