1 Systems V & V, Quality and Standards Dr Sita Ramakrishnan School CSSE Monash University.

Slides:



Advertisements
Similar presentations
Accelerating The Application Lifecycle. DEPLOY DEFINE DESIGN TEST DEVELOP CHANGE MANAGEMENT Application Lifecycle Management #1 in Java Meta, Giga, Gartner.
Advertisements

Configuration management
IBM Software Group ® Traceability From Need To Solution What, Why and How Tammy Lavi Alon Bar-Ner.
RMTrak Requirements Management Tracking/Tracing Tool
Requirements Management
RequisitePro Tutorial
Detailing Requirements with Requisite Pro
Manage Your Requirements with RequisitePro Kim Werner Ajilon Consulting
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Building Enterprise Applications Using Visual Studio ®.NET Enterprise Architect.
Requirements Specification
Functional Requirements Status and Plans Christopher Neyman W. M. Keck Observatory Viswa Velur California Institute of Technology Keck NGAO Team Meeting.
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
SE 555 Software Requirements & Specification Requirements Management.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
Databases and Database Management Systems
Recall The Team Skills Analyzing the Problem
© Siemens Product Lifecycle Management Software Inc. All rights reserved Siemens PLM Software Solid Edge ST4 Training Revising assemblies.
Configuration Management
Jouhayna Al-Ayoubi SWEN 5230 – Software Project Management.
My Site Collaborative Features. About Me Support Team Leader with Webteksolutions Primary.
Working with SharePoint Document Libraries. What are document libraries? Document libraries are collections of files that you can share with team members.
Requirements Management Plan - Documents
The Integration Story: Rational Quality Manager / Team Foundation Server / Quality Center Introductions This presentation will provide an introduction.
Overview of Change Management ClearQuest Overview for CORUG January, 2008.
This chapter is extracted from Sommerville’s slides. Text book chapter
RUP Requirements RUP Artifacts and Deliverables
RequisitePro (2) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
Tutorial 10 Adding Spry Elements and Database Functionality Dreamweaver CS3 Tutorial 101.
Chapter 4 User Experience Model. User experience model (Ux) Visual specification of the user interface Visual specification of the user interface Both.
Why use RequisitePro RequisitePro is a comprehensive tool that supports any of today's requirements management processes. The predominant requirements.
Rational Unified Process Fundamentals Module 4: Disciplines II.
 To explain the importance of software configuration management (CM)  To describe key CM activities namely CM planning, change management, version management.
OHT 11.1 © Marketing Insights Limited 2004 Chapter 9 Analysis and Design EC Security.
Tutorial 121 Creating a New Web Forms Page You will find that creating Web Forms is similar to creating traditional Windows applications in Visual Basic.
2/6/01D-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Using PARTS to Illustrate Requirements Concepts.
Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.
INCOSE TOULOUSE - FRANCE 1. 2 James C. Helm Associate Professor, Systems Engineering School of Science and Computer Engineering 2700 Bay Area Boulevard.
Introduction to ASP.NET T.Ahlam Algharasi. The Visual Studio IDE Start page 2.
Notes of Using RequisitePro cyt. 2 Type of user –Requirements viewers –Requirements contributors –Requirements authors –Project administrator Rational.
1 INNOVATIONS 2001 Organized by The Clear Lake Council Of Technical Societies (CLCTS) in cooperation with and co-sponsored by CLCTS member organizations.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
® IBM Software Group © IBM Corporation Introduction to Requirements Management & Analysis Solution Luis Castañeda Cubas IBM.
Requirements Management Traceability Planning for Change Methodology Tools.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Course 2138 Empowering Agile Development With CaliberRM  Jerry D. Odenwelder Jr.  Principal Software Engineer.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
 Dr. Syed Noman Hasany.  Review of known methodologies  Analysis of software requirements  Real-time software  Software cost, quality, testing and.
1 James C. Helm Assistant Professor, Systems Engineering School of Natural and Applied Sciences 2700 Bay Area Boulevard Houston, Texas VPN
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.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with the IBM Rational Software Architect, V7.5 Module 15: Traceability and Static Analysis.
Essentials of Modeling with IBM Rational Software Architect V7.5
Copyright © 2007, Oracle. All rights reserved. Using Document Management and Collaboration Appendix B.
Requirements Management with Use Cases Module 4: Analyze the Problem Requirements Management with Use Cases Module 4: Analyze the Problem.
Requirements Management with Use Cases Module 5: Define The System To Be Built Requirements Management with Use Cases Module 5: Define The System To Be.
Murach's C# 2012, C2© 2013, Mike Murach & Associates, Inc. Slide 1.
QC – User Interface QUALITY CENTER. QC – Testing Process QC testing process includes four phases: Specifying Requirements Specifying Requirements Planning.
Easy Access with templates I: Create a database Lesson 16 By the end of this lesson you will be able to complete the following: Find the best database.
Requirement Engineering Management Amna Shifia Nisafani Feby Artwodini M. Department of Information Systems Subject : Requirement Engineering.
1 Requirements Management - II Lecture # Recap of Last Lecture We talked about requirements management and why is it necessary to manage requirements.
 This lab accompanies the software engineering course to support the content in the course. The overall goals of this lab are to introduce examples of.
BSA 385 Week 3 Individual Assignment Frequent Shopper Program Part 2 Check this A+ tutorial guideline at
Building Enterprise Applications Using Visual Studio®
CIS 245 Lab.
Computer Aided Software Engineering (CASE)
Presentation transcript:

1 Systems V & V, Quality and Standards Dr Sita Ramakrishnan School CSSE Monash University

© S Ramakrishnan2 Software Test Automation zTopic: y Rational Test Studio xRequisitePro Software requirements management tool to help with team collaboration & reduce project risk Offers DB & MS Word RequisitePro’s architecture enables live requirements that are dynamically linked to a DB for easy query & sorting facilities Helps you to easily organize and prioritize your requirements Helps with tracing relationships between requirements, and track changes that affect them Visual traceability helps one to view the impacts of changes on the project; do impact analysis and make informed decision about resource allocation, scoping of project etc Captures the change history for each requirement, and so, provides a paper audit of the evolution of requirements.

© S Ramakrishnan3 Software Test Automation xCreating a Rational RequisitePro Project RequisitePro project includes a DB & can include documents RequisitePro includes project templates, which provide project structure information for the DB The DB stores document types, requirement types, requirement attributes, and information about requirement traceability Project templates included with RequisitePro are: – Use-Case Template (using a use-case methodology) – Traditional Template (using standard software requirements) –Composite Template (to incorporate use-case & trad.) Can create a new template or create a project using a blank template

© S Ramakrishnan4 Software Test Automation Requisitepro ShellRequisitepro Shell – The Explorer is RequisitePro's primary navigation window. Project artifacts (documents, requirements, views, and packages) are displayed hierarchically in a tree browser in the navigation window. Project information is organized in packages Within each package, artifacts are organized in the following order: –documents (alphabetically by name) –views (by type and then alphabetically within the type), and requirements (by type and then by tag) –Open RequisitePro and … create a Project

© S Ramakrishnan5 Software Test Automation Creating a Document in a RequisitePro ProjectCreating a Document in a RequisitePro Project –You create a document in RequisitePro in Word –When you create a document, RequisitePro adds the new document to the project directory - you must specify the name, type, directory, and other information related to the document. –Document is based on outlines & outlines used to organise your requirements document. Outlines available appear on the Document Properties dialog box –Different types of documents are written at different stages of the project, and you create specific types of requirements in specific types of documents. –In the Vision document, you document the features your project should include, and in the use-case document, you describe how the system behaves. The use cases should relate to features in the Vision document.

© S Ramakrishnan6 Software Test Automation Creating requirements in a Document in a RequisitePro ProjectCreating requirements in a Document in a RequisitePro Project All requirements are stored in the project database. You can create requirements in a document, in the RequisitePro Explorer, or directly in the database through a view. RequisitePro provides some requirement types (for example, feature, spec. requirements, supplementary, use case, and glossary terms with tag prefixes - FEAT, SC, SUPP, UC & TERM respectively) Each type is numbered separately Each type has a unique set of user-defined attributes Requirement types are useful for grouping similar requirements in a project

© S Ramakrishnan7 Software Test Automation Managing requirements in a RequisitePro ProjectManaging requirements in a RequisitePro Project –RequisitePro View shows requirements that are stored in the project DB –Requirements, their attribute matrix (priority & difficulty (high, medium, low), status (proposed, approved, validated, incorporated), and their relationships with other requirements are displayed and managed in views. –You can use views to organize and track your requirements. –You can also use a Traceability Matrix to view the relationships between requirements of the same or of different types

© S Ramakrishnan8 Software Test Automation Managing requirements in a RequisitePro ProjectManaging requirements in a RequisitePro Project –Traceability feature to manage changes in reqs. –can link two requirements of the same type or of different types to show that they are related to or dependent on each other -> tracing a requirement to or from another requirement –E.g. from Rational site – develop a retail store which notifies customers by when orders have been shipped – To cater for this feature requirement, develop a system in which this notification is part of the procedure (use case requirement). –You can trace this use case req. to feature requirement –When traceability is included between 2 requirements, any change to one req. requires you to check that the traceability is still valid. RequisitePro gives visual clues asking you to re-examine & check if it is valid

© S Ramakrishnan9 Software Test Automation Managing requirements in a RequisitePro ProjectManaging requirements in a RequisitePro Project –Traceability feature to manage changes in reqs. –can link two requirements of the same type or of different types to show that they are related to or dependent on each other -> tracing a requirement to or from another requirement –E.g. from Rational site – develop a retail store which notifies customers by when orders have been shipped – To cater for this feature requirement, develop a system in which this notification is part of the procedure (use case requirement). –You can trace this use case req. to feature requirement –When traceability is included between 2 requirements, any change to one req. requires you to check that the traceability is still valid. RequisitePro gives visual clues asking you to re-examine & check if it is valid Look at Rational RequisitePro Tutorial, White Papers and get ready for the Assignment –Just a few pointers about RequisitePro given in these slides. Look at Rational RequisitePro Tutorial, White Papers and get ready for the Assignment