Inception Is there a project in there? What’s the vision, scope & business case?

Slides:



Advertisements
Similar presentations
ניתוח ועיצוב מערכות תוכנה אביב 2012
Advertisements

Chapter 4: Inception is Not the Requirements Phase
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
COMP 350: Object Oriented Analysis and Design Lecture 3 Case Studies, Inception & Use Cases References: Craig Larman Chapters 3-6.
NJIT From Inception to Elaboration Chapter 8 Applying UML and Patterns Craig Larman.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” - may be of.
Fall 2009ACS-3913 Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,
Understanding Requirements
6/8/991 Analysis Tuesday 09/14/99 Revised: September 11, 2000 (APM)
Use Cases and Scenarios
Copyright ©2004 Cezary Z Janikow 1 Use Cases n Within Requirements discipline/workflow n Verbal descriptions of important functional (behavioral, transactional,
Jan 8, Ron McFadyen1 Waterfall Spiral UP Case study UML Use Cases.
Iterative development and The Unified process
From Inception to Elaboration Chapter 8 Applying UML and Patterns -Craig Larman.
Object-Oriented Analysis and Design
Chapter 9 THE ACQUISITION CYCLE— PURCHASING AND RECEIVING
Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.
Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 Use cases: deciding what you want.
Domain Modeling Chandan R. Rupakheti and Steve Chenoweth Week 5, Day 1.
The first step in getting what you want is to decide what you want.
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative Development Part III Elaboration Iteration I – Basic1.
TRANSACTION PROCESSING SYSTEM Liew Woei Song Muhammad Hofiz Achoson.
Solution Overview for NIPDEC- CDAP July 15, 2005.
Project Semester 1 Group 3 Robert, Pavel, Ulfar, Svetomir
Software Engineering 1 Object-oriented Analysis and Design Chap 30 Relating Use Cases.
IDENTIFYING OTHER REQUIREMENTS Write a Supplementary Specification, Glossary, and Vision. Compare and contrast system features with use cases. Relate the.
Point-of-sale terminal. Name : Minkcy Chiu Student number : (1) Class : 4F.
Product/Service & Distribution P.O.S. System Nick Mercuro, Evan Klipple, Austin Moore.
Chapter 6 Use Cases. Use Cases: –Text stories Some “actor” using system to achieve a goal –Used to discover and record requirements –Serve as input to.
Sept Ron McFadyen1 Section 10.1 Domain Models Domain Model: a visual representation of conceptual classes or real-world objects in a domain.
Software Architecture in Practice Architectural description (The reduced version)
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
TK2023 Object-Oriented Software Engineering CHAPTER 3 CASE STUDY: POS SYSTEM.
1 Unified Modeling Language Michael K. Wildes University of California, Riverside – Extension Program Presentation 2.
USE CASE Bayu Adhi Tama, MTI Faculty of Computer Science, University of Sriwijaya Slides are adapted from Petrus Mursanto
Petals SAP Point of Sale System M.Tech. Team SE 15 (Saturday) Team 08 5-Apr-2008.
1 OrderPro Point of Sale (POS) Training Prepared by Christina Van Metre Independent Educational Consultant CTO, Business Development Team © Training Version.
Object-Oriented Analysis and Design Jan 14, 2009.
Chapter 7 Applying UML and Patterns Craig Larman
LOGO Team Assignment 1 Software Architectures. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery.
OOSE Use Case. Requirement Functional: –Features, capabilities, and security Non Functional: –Usability: Human factors, help, and documentation –Reliability:
Chapter 9 Applying UML and Patterns -Craig Larman
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
OO Methodology Inception Phase.
R R R CSE870: Advanced Software Engineering: UML-- Use Cases1 Use Cases and Scenarios.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
Chapter 4. Inception is NOT Requirements: Inception is a short, initial stage. Its purpose is a common vision and scope measurement. needed to do: –analyze.
Software Engineering 1 Object-oriented Analysis and Design Chap 24 Iteration 2 More Patterns.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
Week 2. Topics Inception phase Evolutionary requirements Use cases.
PRESENTATION ON USE CASE. Use Case Modeling Use case diagrams describe what a system does from the standpoint of an external observer. The emphasis is.
Chapter 6: Use Cases.
Understanding Requirements
Chapter 8: Iteration 1 - Basics.  We review here the requirements for first iteration of our case studies. They are a subset of the requirements as described.
Chapter 3: Case Studies What is and is not Covered in the Case Study?  Traditional business software applications include UI elements, core application.
Chapter 8. Iteration 1, Elaboration: book view differs from reality for pedagogical reasons not doing “risk-driven” up front uses many OOA/D skills should.
Larman chapter 41 Inception Larman chapter 4 and 7.
PART II INCEPTION Chapter 4 Inception is Not The Requirements Phase.
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
Anytime, Anywhere Access Benefits Functionality Work Order Administration Dispatch Work Order Work Order Details New Work Order Additional Functionality.
Jan Ron McFadyen1 Use Cases Used to capture functional requirements – there are other requirements categories such as usability, reliability,
Elaboration popo.
Use Cases and Scenarios
Writing Use Cases.
Unified Process (UP).
Chapter 4 Inception CS John Cole.
Software Requirements
Other System Requirements
Presentation transcript:

Inception Is there a project in there? What’s the vision, scope & business case?

Analogy from oil business 1. Decide if there is evidence (business case) to justify exploratory drilling 2. If so, do measurements and exploratory drilling 3. Provide estimates … Inception is like step 1: a feasibility study Another analogy: consulting with a doctor to do exploratory surgery Is inception the same as requirements analysis?

Inception objectives Establish vision, scope and business case  Vision: What do we want?  Scope: What do we include and not include?  Business case: Who wants it and why? Determine primary scenarios as Use Cases  Completeness not necessary, maybe just 10% Estimate feasibility and risks Start defining terms in a glossary. Why?

Example vision & business case (Larman, p. 102) Introduction We envision a next generation fault-tolerant point-of-sale (POS) application, NextGen POS, with the flexibility to support varying customer business rules, multiple terminal and user interface mechanisms, and integration with multiple third-party supporting systems. Business Case Existing POS products are not adaptable to the customer's business, in terms of varying business rules and varying network designs (for example, thin client or not; 2, 3, or 4-tier architectures). In addition, they do not scale well as terminals and business increase. None can work in either on-line or off-line mode, dynamically adapting depending on failures. None easily integrate with many third-party systems. None allow for new terminal technologies such as mobile PDAs. There is marketplace dissatisfaction with this inflexible state of affairs, and demand for a POS that rectifies this.

Brief format Use Case (Larman, p 63) A story of an actor using a system to meet a goal Process Sale: A customer arrives at a checkout with items to purchase. The cashier uses the POS system to record each purchased item. The system presents a running total and line-item details. The customer enters payment information, which the system validates and records. The system updates inventory. The customer receives a receipt from the system and then leaves with the items.

Glossary (exceprt from Larman, p. 115) TermDefinitionFormatAliases itemA product or service for sale Payment authorization Validation by an external payment authorization service that they will make or guarantee the payment to the seller. UPCNumeric code that identifies a product. Usually symbolized with a bar code placed on products. 12-digit code of several subparts Universal Product Code

Inception is lightweight Artifacts such as use case model should only be partially completed (10-20%) Purpose is feasibility investigation Quick prototypes may be useful – why? You know you don’t understand inception when it takes more than “a few” weeks, or when estimates or plans are expected to be reliable, etc. When will you complete inception for your projects? What artifacts will you develop?