Detailing Requirements with Requisite Pro

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

IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Rational Rose 2000 Interaction Diagrams.
RequisitePro Tutorial
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Static Structure: Process Description
Rational Unified Process
Requirements Specification
©1998, 1999, 2000 Rational Software - All rights reserved Session VM08 Structuring Your Rational Rose Model Robert Bretall Rational Software.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
SE 555 Software Requirements & Specification Requirements Management.
1 Systems V & V, Quality and Standards Dr Sita Ramakrishnan School CSSE Monash University.
Rational Rose Basics Visual Modeling Textbook – Chapter 3
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Object Oriented Analysis and Design Using the UML
Object-Oriented Analysis and Design
Requirements Management Plan - Documents
Copyright © Craig Larman All Rights Reserved Requirements.
RUP Requirements RUP Artifacts and Deliverables
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
UML - Development Process 1 Software Development Process Using UML (2)
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Prepared by: Sanaz Helmi Hoda Akbari Zahra Ahmadi Sharif University of Tech. Summer 2006 An Introduction to.
1 Quality Center 10.0 NOTE: Uninstall the current version of QC before downloading QC All QC 10.0 documents can be located on the BI Shared Services.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Sequence & Statechart Diagrams Month Day, Year. Agenda Training Plan Overview Actors and Use Case Diagrams Sequence Diagrams Diagram Elements Evolution.
Lecture 7: Requirements Engineering
Notes of Using RequisitePro cyt. 2 Type of user –Requirements viewers –Requirements contributors –Requirements authors –Project administrator Rational.
Systems Analysis and Design in a Changing World, 3rd Edition
Introduction to RUP and Visual Modeling Month Day, Year.
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.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Introduction to Rational Rose 2000 v6.5 Copyright © 1999 Rational Software, all rights reserved 1 Rational Rose 2000 Class Diagrams.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
Copyright 2007, Paradigm Publishing Inc. ACCESS 2007 Chapter 3 BACKNEXTEND 3-1 LINKS TO OBJECTIVES Modify a Table – Add, Delete, Move Fields Modify a Table.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
Identifying & Creating Use Cases – Part 1 Month Day, Year.
1 Class Diagrams. 2 Overview Class diagrams are the most commonly used diagrams in UML. Class diagrams are for visualizing, specifying and documenting.
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.
RequisitePro Software Requirement Management Tool A peresentation by: Mojdeh Jalali-Heravi Maryam Daneshi.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Prof. Hany H. Ammar, CSEE, WVU, and
Essentials of Modeling with IBM Rational Software Architect V7.5
Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts Rational Unified Process Fundamentals Module 3: Core Workflows I - Concepts.
Chapter 3: Introducing the UML
UML - Development Process 1 Software Development Process Using UML.
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.
Using Rational Rose XDE Month Day, Year. Agenda Training Plan Overview XDE Review Next Steps.
MSOffice Access Microsoft® Office 2010: Illustrated Introductory 1 Part 1 ® Database & Table.
Requirement Discipline Spring 2006/1385 Semester 1.
Using ClearCase Month Day, Year. Agenda Training Plan Overview ClearQuest Review Next Steps.
Using Rational Administrator Month Day, Year. Agenda Training Plan Overview Using Rational Administrator Review Next Steps.
Identifying & Creating Use Cases – Part 2
Analysis Classes Unit 5.
IBM Rational Rhapsody Advanced Systems Training v7.5
Analysis models and design models
Identifying & Creating Use Cases - Part 3
Presentation transcript:

Detailing Requirements with Requisite Pro Month Day, Year

Agenda Training Plan Overview Review UCs & ADs Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration Associating other requirements Creating views Review Homework Next Steps

Training Plan Overview Introduction Using Rational Administrator Using ClearCase Using ClearQuest Using Rational Rose XDE Identifying & Creating Use-Cases – Part 1 Identifying & Creating Use-Cases – Part 2 Detailing Requirements with RequisitePro Actors and Use-Case Diagrams Sequence and Statechart Diagrams Collaboration and Class Diagrams Integration and Development with the .NET Framework

Review – UCs and ADs Models Packages – used to organize the models Business Business Analysis Use-Case Analysis Design Implementation Deployment Packages – used to organize the models Logical breakdown of model elements Supports model management

Review – UCs and ADs Use Cases Describes activities 5 basic types of diagrams Use-Case Activity State Sequence Collaboration Text Requirements Other Media

Review – UCs and ADs Identifying Use Cases - Analysis Steps Identification Create a new package, use case, and related diagrams for the identified sub-use case Organization Hierarchy Levels of Abstraction Activity Diagram Definition: Defines the workflow associated with the use case Context Detail

Review – UCs and ADs Activity Diagram Model Elements Start State End State Activity Decision State Transition Regular Transition To Self Horizontal and Vertical Synchronization Note Note Anchor Text

Review – UCs and ADs Activity Diagrams Model Elements Types Events Regular With States With Swimlanes With Object Flows Model Elements Events Actions Stereotypes Conditional Threads Guard Conditions History States Nested Activities Transitions to Self Decision Guards States Decision Merges

Review – UCs and ADs

Review – UCs and ADs

Review – UCs and ADs States Defines a condition of an object in which it performs some activity or waits for an event

Review – UCs and ADs Swimlanes Allow assignment of activities to the organizational units or roles

Review – UCs and ADs Object Flows Used to show how business entities are created and used in a workflow

Review – The Models Business Use-Case Model Business Analysis Model Describes processes of a business as a number of different business use cases, each of which represents a specific workflow in the business Business use-case describes the performance of a sequence of actions that produces a valuable result to a particular business actor Business Analysis Model Describes how business use-cases are realized within the business object model, in terms of collaborating objects Use-Case Model Describes processes of a system as a number of different use cases, each of which represents a specific workflow in the system Use-case describes the performance of a sequence of actions with a system that produces a valuable result to a particular actor Analysis Model Describes how use-cases are realized within the system object model, in terms of collaborating objects

RequisitePro - Benefits Manage project requirements comprehensively Promotes communication and collaboration among team members Reduces project risk

RequisitePro - Features Tool combing power of a database and Microsoft Word. Requirements documents that are dynamically linked to a database Powerful sort and query capabilities Requirements Organize Prioritize Trace relationships Manage requirement change Track changes Captures the change history for each requirement Paper audit Visually indicate how changes affect the project Perform real-time impact analysis Informed decisions Scope management Resource allocation

RequisitePro - Basic Concepts Requirements Management Plan Guidelines for establishing the requirements Documents Requirement Types Attributes Traceability

RequisitePro - Basic Concepts Requirements A condition or capability to which a system must conform FURPS+ model Functionality Usability Reliability Performance Supportability Design constraints Implementation requirements Interface requirements Physical requirements.

RequisitePro - Basic Concepts Requirement Types Features Use-cases Supplementary Specifications Requirement Attributes Priority Status Stability Document Types Glossary Vision Statement Views Attribute Matrix Traceability Matrix Traceability Tree

RequisitePro - Basic Concepts Requirement Types Use-Case Stakeholder Request Feature Supplementary Glossary Item

RequisitePro - Basic Concepts Attribute Types Feature Priority Type Status Difficulty Stability Risk Planned Iteration Actual Iteration Origin Contact Name Enhancement Request Defect Obsolete Stakeholder Request Priority Origin Glossary None

RequisitePro - Basic Concepts Attribute Types Supplementary Priority Status Difficulty Stability Risk Origin Contact Name Enhancement Request Defect Obsolete Use-Case Property Priority Status Difficulty Stability Risk Affects Architecture Contact Name Planned Iteration Actual Iteration Enhancement Request Defect Obsolete

RequisitePro - Basic Concepts Document Types Vision Overall view of the system Main characteristics Major features Key stakeholder needs Key services provided Glossary Consistent terms to express requirements Use-Case Specification Functional requirements in sequence Sequence of actions performed by a system that yields an observable result of value to a particular actor Functional software requirements Supplementary Requirement Specification Requirements that cannot be tied directly to any specific use case Nonfunctional requirements Design constraints Test Plan

RequisitePro - Basic Concepts Views Attribute Matrix Requirement vs. Attribute Illustrates the relationships between requirements and their attributes

RequisitePro - Basic Concepts Views Traceability Matrix Requirement vs. Requirement Illustrates the relationships between requirements of the same or different types

RequisitePro - Basic Concepts Views Traceability Tree Requirement vs. Requirement Displays all internal and external requirements traced to or from a requirement

RequisitePro - Advance Features Archiving Baselining Identifies activities and one version of every element visible in one or more components Created at project milestones Cross-Project Traceability Establish traceability between requirements that reside in different projects Manage requirements common to multiple projects Discussion Groups

RequisitePro – Create Database Start RequisitePro Select New tab Select Use Case Template and click OK.

RequisitePro – Create Database The Rational RequisitePro Project Properties dialog appears. Enter “ClassProject1” in the Name box. Enter “C:\Program Files\Rational\RequisitePro\Projects\ClassProject1” in the Directory edit box. Select “MS Access” as the Database type from the drop down list. Enter “Class project” in the Description edit box. Click OK Click Yes Close RequisitePro

RequisitePro – Associate Model Start XDE Open model Right click in Model Explorer, select AppliedProfiles, click the eclipses (…), and checkmark the RequisitePro profile Select Tools, Rational RequisitePro, Associate Model

RequisitePro – Associate Model Associate Model To RequisitePro Project dialog opens Click Browse next to the Project File field

RequisitePro – Associate Model Browse to RequisitePro project file with .rqs file extension Select the file Click Open

RequisitePro – Associate Model Select Use Case Specification from Default Document Type drop down list Select Use Case from Default Requirement Type drop down list Click OK

RequisitePro – Create Association Right click a use-case Select RequisitePro, New Association Select RequisitePro, Association Requirement A Requirement Properties dialog appears with the Attribute tab selected Select values from the attribute drop down lists

RequisitePro – Create Association Select the General tab Use-Case Name displayed in Text edit box Enter additional text, graphics, and objects that are included as part of the requirement, up to 16,000 characters Enter the Name Use the use-case name Click OK

RequisitePro – Edit Association Right click a use-case Select Requirement Properties, Open The Requirement Properties dialog appears with the Attribute tab selected Select tabs and edit as necessary Click OK

RequisitePro – View Association Right click a use-case Select View RequisitePro Association The RequisitePro Association dialog appears Click OK

RequisitePro – Other Requirements Stakeholder Requests Any type of requests a stakeholder might have on the system to be developed or any type of external parameter to which the system must comply Results of stakeholder interviews Results from requirements elicitation sessions and workshops Change Request Statement of work Request for proposal Mission statement Problem statement Business rules Laws and regulations Legacy systems Business models

RequisitePro – Other Requirements Features Abilities based on the benefits listed in your problem statements Examples FEATURE1: Ability to save and restore sort and filter criteria FEATURE2: Ability to save a RequisitePro document as a Microsoft® Word® document. FEATURE3: Ability to see deleted requirements in a view window.

RequisitePro – Other Requirements Supplementary Specifications System requirements that are not readily captured in behavioral requirements artifacts such as use-case specifications Legal and regulatory requirements, and application standards Quality attributes of the system to be built, including usability, reliability, performance, and supportability requirements Other requirements such as those for operating systems and environments, compatibility with other software, and design constraints

RequisitePro – Other Requirements Glossary Provide a consistent set of definitions Analysts Project-specific terms Clearly define business rules Ensure that requirement specifications make correct and consistent use of those terms Developers Terms defining defining the design and implementation classes, database tables, user-interfaces… Course developers and technical writers Training material and documentation using recognized terminology

RequisitePro – New Requirements Business Goal Describe the desired value of a particular measure at some future point in time and can therefore be used to plan and manage the activities of the business Attributes Property Name Brief Description UML Representation Business Rule Define a specific constraint or invariant that must be satisfied by the business May apply always (invariants) or only under a specific condition If the condition occurs, the rule becomes valid, and must therefore be complied with. Do not conflict Present an accurate picture of the principles that govern the way business is done Attributes Structural Constraints Behavioral Constraints

RequisitePro – New Requirements Interface Requirements Graphical Accessibility Branding Non-Graphical Programmable

RequisitePro – Requirement Linking Concepts Traceability Traceability is the ability to trace a project element to other related project elements, especially those related to requirements To Lists requirements to which the selected requirement is traced. From Lists requirements from which the selected requirement is traced

RequisitePro – Requirement Linking Two Requirements Different Can be same Select Use-Case Right click and select Properties Select the Traceability tab Click the Add button in the From section

RequisitePro – Requirement Linking Select the Requirement Type from the drop down list Select the Location from the drop down list Database Only Select the Requirement Click OK

RequisitePro – Requirement Linking

RequisitePro – Views View Types Attribute Matrix Traceability Matrix Requirement vs. Attribute Illustrates the relationships between requirements and their attributes Traceability Matrix Requirement vs. Requirement Illustrates the relationships between requirements of the same or different types Traceability Tree Displays all internal and external requirements traced to or from a requirement

RequisitePro – Views Default Views Use-Case Template

RequisitePro – Attribute Matrix Add View Right click a package Select New, View View Properties dialog appears Enter Name Enter Description

RequisitePro – Attribute Matrix Select View Type from drop down list Select Row Requirement Type from drop down list Optionally select Private Click OK

RequisitePro – Attribute Matrix

RequisitePro – Attribute Matrix Change View Right click view and select Displayed Attributes Displayed Attributes dialog appears Click All or None and CTRL click individual attributes to select Select an attribute and click Move Up or Move Down to change display order Click OK

RequisitePro – Traceability Matrix Add View Right click a package Select New, View View Properties dialog appears Enter Name Enter Description

RequisitePro – Traceability Matrix Select View Type from drop down list Select Row Requirement Type from drop down list Select Column Requirement Type from drop down list Optionally select Private Click OK

RequisitePro – Traceability Matrix

RequisitePro – Traceability Matrix Filters Right click upper left view corner and select either Query Row Requirements or Query Column Requirements The Select Attribute dialog appears Select a filter attribute Click OK

RequisitePro – Traceability Matrix The Query Requirements dialog appears Select the filter attribute values Select the Sort Order Select the When Traced Click OK

RequisitePro – Traceability Matrix Click Add to repeat with additional attribute filters Select a Query Criteria and click Modify to change Select a Query Criteria and click Remove to delete Click Move Up or Move Down to set order Optionally select Retain Hierarchical Display Click OK

RequisitePro – Traceability Tree Add View Right click a package Select New, View View Properties dialog appears Enter Name Enter Description

RequisitePro – Traceability Tree Select View Type from drop down list Select Row Requirement Type from drop down list Optionally select Private Click OK

RequisitePro – Traceability Tree

Next Steps Homework Classes Ahead Homework Model Continue to explode assigned packages Create a ReqPro Database Associate with XDE Model Add Use-Case Requirements Classes Ahead Actors and Use-Case Diagrams Sequence and Statechart Diagrams Collaboration and Class Diagrams Integration and Development with the .NET Framework