Requirements Development An Introduction to the Process and Artifacts November 20, 2001 SIS Analysis Model System Analysis Model SIS Use Case Model System.

Slides:



Advertisements
Similar presentations
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Advertisements

Information System Design IT60105 Lecture 3 System Requirement Specification.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
1 / 26 CS 425/625 Software Engineering Software Requirements Based on Chapter 5 of the textbook [Somm00] Ian Sommerville, Software Engineering, 6 th Ed.,
1 CS 425 Software Engineering Project Preparation Use Case Modeling [Based on Chapters 3 & 4, Arlow and Neustadt, “UML and the Unified Process,” Addison-Wesley,
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
S R S S ystem R equirements S pecification Specifying the Specifications.
1 CMPT 275 Software Engineering Requirements Analysis Phase Overview of Requirements Analysis Activity System Context Diagrams.
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Team Skill 1 Analyzing the Problem Business Modeling (6) 1.
RUP Requirements RUP Artifacts and Deliverables
Lesson 7 Guide for Software Design Description (SDD)
CSIS 4850: Senior Project Fall 2008 Scope Statement and Project Plan.
Software Engineering CS B Prof. George Heineman.
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
Computer Science School of Computing Clemson University Introduction to Formal Specification Murali Sitaraman Clemson University.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
CMPT 275 Software Engineering
IS 466 ADVANCED TOPICS IN INFORMATION SYSTEMS LECTURER : NOUF ALMUJALLY 22 – 10 – 2011 College Of Computer Science and Information, Information Systems.
Requirements. Terminology: Requirements XYZ Requirements gathering (also known as “requirements elicitation”) : what is to be accomplished, how the system.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
CSC 480 Software Engineering OOAD Process. Topics Overview: OOAD Process The object model Identifying classes Responsibilities and collaborations Hierarchy:
Process Improvement. Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
9/01RUT1 NASA OSMA SAS '01 R equirements U se case T ool James R. McCoy SRS Information Services NASA Software Assurance Technology Center
CS 4850: Senior Project - Spring 2009 CS 4850: Senior Project Spring 2009 Scope Statement and Project Plan.
CS 4850/01: CS Senior Project Fall 2014 Scope Statement and Project Plan.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University Department of Computer Information Systems CIS 499 Yarmouk University.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 7: Requirements Engineering Software Engineering: A Practitioner’s Approach, 6/e.
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Requirements specification Why is this the first major stage of software development? –Need to understand what customer wants first Goal of requirements.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
CSE 403, Software Engineering Lecture 3 Requirements.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
System Requirements Specification
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Prof. Hany H. Ammar, CSEE, WVU, and
Software Requirements Specification Document (SRS)
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
SynergySoft™ Distributed Meeting Scheduler Requirements Review Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Developing Business Processes Developing an activity diagram of the business processes can provide us with an overall view of the system.
 System Requirement Specification and System Planning.
An Overview of Requirements Engineering Tools and Methodologies*
Introduction to Quantitative Research
Unified Modeling Language
Use case diagrams A use case diagram is UML’s notation for showing the relationships among a set of use cases and actors A use case diagram can help the.
Business Models Modeling.
SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.
Requirements Analysis
Unified Modeling Language
Software Design Lecture : 15.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Uml diagrams In ooad.
Software Development Process Using UML Recap
General Workflow of Use-Case Driven Development
Presentation transcript:

Requirements Development An Introduction to the Process and Artifacts November 20, 2001 SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 2 Objectives Complete, consistent, accurate requirements. Faster and higher quality impact analysis. Foundation to begin design Faster and more systematic testing. Decrease new team member’s learning curve. Single source of a system’s requirements.

Requirements Development Process Use Case Models Class Diagrams Use Case Scenarios Sequence Diagrams Story Boards Software Reqmts Spec Identify Use Cases Model Problem Realize Use Case Scenarios Specify Requirements Specify Use Case Scenarios Storyboard Use Case Scenarios

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 4 Use Case Model

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 5 Use Case Scenario

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 6 Analysis in Brief Use Cases are used to gather requirements, they are: 1. Kept as independent of each other as possible Issue: Interference, concurrency, and conflicts among use cases may thus be unresolved 2. Described using the language of the customer Issue: Precision and details may be unresolved 3. Structured to form a complete and intuitive specification of functionality Issue: Redundancies among described requirements may be unresolved The primary purpose of analysis is to resolve these issues

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 7 Analysis Model

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 8 Receive Order Sequence Diagram

Direct+ Sequence Diagram

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 10 Software Requirements Specification

Test Case Use Case Driven SRS Centric Use Case Driven SRS Centric

SIS Analysis Model System Analysis Model SIS Use Case Model System Use Case Model 12 Impact Analysis Analyze User Requirements Specify New Use Case Change Use Case Modify Existing Requirement Modify Class Diagram Realize Use Case Use Case Models Class Diagrams Use Case Scenarios Sequence Diagrams Story Boards Software Reqmts Spec

OK Fail Class/Code Desired End State SIS Requirements System Requirements Design Test Implemen-tation Class/Code OK Fail SIS Analysis ModelSystem Analysis Model System Requirements Design ModelImplementation Model Test Model SIS Use Case ModelSystem Use Case Model Design Implemen-tation Test

SIS Use Cases vs System Use Cases A C B Actor 1Actor 2 System of Interconnected Systems (SIS) Actor 2 A1 B1 A2 B2 C2 A3 C3 Actor 2System X A2 B2 C2 System Z System XSystem YSystem Z System Y