Other Requirement Artifacts

Slides:



Advertisements
Similar presentations
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Advertisements

IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Chapter 7 Other Requirements Good Fast Cheap Pick any two. 1CS John Cole.
Object-Oriented Analysis and Design
Chapter 3 Understanding Requirements
Requirements wg RUP Materiały na seminarium „Metodyki tworzenia SI” Wykonał Marcin Wiącek Styczeń 2006 Wojskowa Akademia Techniczna Wydział Cybernetyki.
Gerhard Dueck -- CS3013Capturing Requirements as Use Cases 1 Capturing the Requirements as use Cases  Requirements Description  We need to describe –The.
Requirements Analysis CMPT 371 Fall 2004 J.W. Benham.
NJIT 1 Domain Model Visualizing Concepts Chapter 9 Applying UML and Patterns Craig Larman.
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.
Source: Peter Eeles, Kelli Houston, and Wojtek Kozaczynsky, Building J2EE Applicationa with the Rational Unified Process, Addison Wesley, 2003 Prepared.
Domain-Specific Software Architecture
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
1 A Use Case-Driven Approach to Requirements Gathering Materials gathered from chapter title (above) – Kulak and Guiney and Use Case Driven Object Modeling.
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Rational Unified Process (Part 1) CS3300 Fall 2015.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
Lecture 3: Information Engineering Dr. Taysir Hassan Abdel Hamid November 3, 2014.
Case Study :. Introduction The ATM network will consist of a large number of ATM machines distributed over a wide geographical area. The network must.
E-Store System for MEHE Final status report Team #2 Sandeep, Vijay, Jennifer, Ali, Meghna April 6 th, 2007.
Chapter 6 Use Case –The interaction between an actor and the system.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Chapter 7 Applying UML and Patterns -Craig Larman
Chapter 7 Applying UML and Patterns Craig Larman
The Great Gatsby Chapter Two What are the ingredients of a successful 1(a) question? (particularly when you’re dealing with a novel rather than a poem)
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
Object-Oriented Analysis and Design Jan 21, 2009.
EXPLORING BIOMIMETIC INTERFACES July , 2013 PROJECT TITLE One phrase project description.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Use Case Model Use case diagram. Relevant Requirements Artifacts Use-Case Model Supplementary Specification Use-Case Specifications... Glossary Actors.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Software Engineering 1 Object-oriented Analysis and Design Applying UML and Patterns An Introduction to Object-oriented Analysis and Design and Iterative.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
VENTURE PLAN EXECUTIVE SUMMARY. should be only one to two pages in length, designed to capture the reader’s interest.
Use Case Model Use case description.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
Requirement Discipline Spring 2006/1385 Semester 1.
Larman chapter 41 Inception Larman chapter 4 and 7.
Defining Text Features. Unit Title  Reviewing the unit titles can be helpful in giving the “big picture” of the topic.
KIWI KAPERS Species Weight(kg)Height (cm) Region/Gender.
Use Cases Discuss the what and how of use cases: Basics Benefits
Evolutionary requirements
1.8 Solving Absolute-Value Equations and Inequalities
Use Case Analysis Chapter 5.
Use Case Model Use case diagram.
Object-Oriented Analysis Principles using UML
Use Case Model Use case description.
Patent services for business community
Chapter 6 Use Case The interaction between an actor and the system.
RI.03 - Analyze how the author unfolds an analysis or a series of ideas or events, including the order in which the points are made, how they are introduced.
פחת ורווח הון סוגיות מיוחדות תהילה ששון עו"ד (רו"ח) ספטמבר 2015
Product Life cycle (RUP)
Project Analysis Course
Beginning and Ending the Speech
Summarizing vs. Paraphrasing
Developing and Communicating a Vision
Getting Around Non-Fiction like
Developing and Communicating a Vision
Law making through the courts- statutory interpretation
Business Modeling - Domain Analysis
Chapter 5 Evolutionary requirements
Crafting a Design Strategy Feature Brief
Pierce County Opioid Task Force
Lecture 10 Proposals.
Other System Requirements
Presentation transcript:

Other Requirement Artifacts

Other Requirement Artifacts Supplementary specification Identifies requirements not captured in use cases (typically non-functional requirements) Glossary Terms and definitions Vision Terse description of big ideas Business rules (domain rules)

Vision Problem statement Summary of system features Summary statement of problem Summary of system features Similar to but different from a list of use cases (see p. 112)

How to write Vision Sequence suggested (p. 114) Write a brief first draft of Vision Identify user goals and supporting use cases Write some use cases Refine the vision based on above

Glossary A list of important terms and their definitions Helps reduce ambiguity and improve communication Plays role of data dictionary Start early