TechMIS LLC Proprietary Tracking Requirements And Compliance Engineering (TRACE ) Steve Collier/B. Squires/TechMIS LLC An affordable and user friendly.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

PRINCIPLES OF A CALIBRATION MANAGEMENT SYSTEM
Methods in Enterprises 2 BPMBPM BABA UXUX SOASOA EIMEIM MDD / TDD / XP EAEA PMBOK / CMMI-DEV ITILITIL Scrum / Kanban Business/IT Strategy.
All content in this presentation is protected – © 2008 American Power Conversion Corporation Rael Haiboullin System Engineer Change Manager.
CCMDB 7.2.
A framework for describing IT Project Management Processes and Tool Set Features Enterprise Project Management Framework.
Introduction to the State-Level Mitigation 20/20 TM Software for Management of State-Level Hazard Mitigation Planning and Programming A software program.
Program Management Overview (An Introduction)
SE 555 Software Requirements & Specification Requirements Management.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
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.
Chapter 8: Network Operating Systems and Windows Server 2003-Based Networking Network+ Guide to Networks Third Edition.
Lecture Nine Database Planning, Design, and Administration
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Managing Risk to Reduce Construction Claims (And Improve Project Success) Presented by Laurie Dennis, PE, CVS-Life, FSAVE.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 11 System Test Design
Software Configuration Management
Slide 1 of 9 Presenting 24x7 Scheduler The art of computer automation Press PageDown key or click to advance.
Michael Solomon Tugboat Software Managing the Software Development Process.
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.
What is Business Analysis Planning & Monitoring?
An Introduction to AlarmInsight
Project Management An overview. What is a Project A temporary job to accomplish a specific task A temporary job to accomplish a specific task Attributes.
IT Project Management Cheng Li, Ph.D. August 2003.
Introduction to Software Quality Assurance (SQA)
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Software System Engineering: A tutorial
NIST Special Publication Revision 1
Business Analysis and Essential Competencies
1 Process Engineering A Systems Approach to Process Improvement Jeffrey L. Dutton Jacobs Sverdrup Advanced Systems Group Engineering Performance Improvement.
Module 6 Session 6.1 Visual 1 Module 6 Preparing the Work Breakdown Structure (WBS), Responsibility Matrix, and Master Summary Schedule Session 6.1 Preparing.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Enterprise Reporting Solution
Software Project Management
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.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Slide 1. © 2012 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Develop Project Charter
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a: Architectural Design Software Engineering: A Practitioner’s Approach, 6/e Chapter 10a:
0 eCPIC User Training: Portfolios Module These training materials are owned by the Federal Government. They can be used or modified only by FESCOM member.
© 2013 IBM Corporation IBM Tivoli Composite Application Manager for Transactions Transaction Tracking Best Practice for Workspace Navigation.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
GRC: Aligning Policy, Risk and Compliance
2009 copyright Leslie Munday University Requirements Management and Traceability For IIBA By Leslie Munday.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Creating a Work Breakdown Structure with Microsoft Project.
Configuration Management
Chapter 11: Software Configuration Management
Configuration Management
Software Requirements
Chapter 11: Software Configuration Management
Twin Cities Business Architecture Forum 1/19/2016
Time Scheduling and Project management
UML Design for an Automated Registration System
Presentation transcript:

TechMIS LLC Proprietary Tracking Requirements And Compliance Engineering (TRACE ) Steve Collier/B. Squires/TechMIS LLC An affordable and user friendly Program and Requirements Management System for large, medium, and small programs ®

TechMIS LLC Proprietary Requirements Traceability and Analysis Tool Set Basic Capabilities: Top-to-bottom traceability Closed-loop system to manage and track*:  Requirement accountability  Technical Feasibility  Program and performance Issue tracking  Issue management and mitigation Planning (assignment of mitigation processes) Execution  Verification management  Program planning  Program health/status reporting Supports small, medium and large (20K plus) programs Inherent benefits and functionality: User friendly interfaces Minimal training Little-to-no additional software expenses Use as standalone system or as an adjunct to CRADLE or DOORS System tailored to meet user needs Flexible configuration control Requirement trace depicted in the most compact and intuitive to understand format possible Enterprise read-write access Accommodates unclassified and classified ** requirements User selects which modules are required to meet their needs ** Supported through program or business partner’s secure data servers TRACE ®

TechMIS LLC Proprietary User Tailored set of TRACE ® Modules 1. Requirement Trace Module: Complete Parent-Child Trace in easy to understand and analyze Format Scales to meet large program needs: 10K+ unique requirements 60K+ links due to multiple parent child relationships have been implemented Implemented as authoritative database (recommended) or linked to authoritative database (e.g. Cradle, DOORS, or other) Requirement owners assigned to every requirement Requirement owners assign priorities to the children of their requirements 2. Requirement Status Based on Bottoms-up Assessment Module*: Tailored to meet program milestone performance from: Concept to Technical Feasibility to Design Compliance to Verification to Acceptance: Requirement Status: Blue, Green, Yellow, and Red Supports Horizontal and Vertical coordination Provides requirement owners at all level with opportunity to highlight their issues 3. Issue Mitigation Module*: Technical performance and design integration issues are identified Appropriate issue mitigation processes assigned to each issue: Watch List TPM Risk Plan Proprietary Risk Plan and TPM Tools can be integrated but are not required Risk mitigation actions are established, monitored and reported 4. Verification Module*: Verification methods (Inspection, Analysis, Test) and plans associated with each requirement Bottoms-up trace used as logic to support verification method selection, planning and execution Used to assess and determine verification risk (Definition, Technical, Method/Tool) 5. Program Schedule Module (MS Project based): Bottoms-up trace provides right-to left task scheduling logic Bottoms-up trace ensures that plan is integrated, sequenced properly,and is complete Created directly from Requirement Trace Module 6. Graphic Trace Report Module (MS Project add-on): User tailored graphical view of requirement trace and status 7. Requirement and Program Status Reporting Module (Dashboard) Tailored to meet program management needs: Technical, schedule, and budget issues * Integrated as spreadsheet columns with the Requirement Trace Module

TechMIS LLC Proprietary Module 5. Program Schedule (MSProject based): Bottoms-up trace provides right-to left task scheduling logic. Bottoms-up trace ensures that plan is integrated, sequenced properly, and is complete. Created directly from Requirement Trace Module. Purpose: The management of program goals and requirements is a process that demands involvement throughout the entire organization. The TRACE process utilizes and deploys tools that personnel typically already have. Exotic, pricy tools are often detrimental to the process because their expense often puts these tools out of reach to the users who need it most. Schedule and requirement management is a grass roots process which the TRACE approach embraces. Features: The TRACE toolset also incorporates both schedule and cost elements which are essential components to effective risk identification, monitoring and mitigation. The TRACE toolset/program architecture facilitates the seamless exchange of information to and from MSProject. As an extension to the TRACE process, this module provides a “bottoms-up” schedule approach to efficiently identify risk and it’s overall effect throughout the Project. Highlights risk at every level so that it can be administered and mitigated at the lowest level and earliest opportunity. Conveys the health of each element of the project “on-demand” with summaries by Task and sub-task. TRACE ®

TechMIS LLC Proprietary Module 5. Program Schedule (MS Project based), continued: Example: Provides an intuitive, schedule-based representation of the TRACE process. Incorporates status icons which provide an immediate indication of requirement health. Helps organize and time-phase activities as a function of requirement interdependency. TRACE

TechMIS LLC Proprietary TRACE Module 6. Graphic Trace Report (MS Project add-on): User tailored graphical view of requirement trace and status Purpose: Provides an intuitive graphical representation of the TRACE process. Underscores and highlights root issues so that they can be promptly elevated to upstream stakeholders. Features: Nearly every conceivable project attribute, descriptive element or metric can be broadcast and displayed via the TRACE graphic interface. This type of organization gives users a “bird’s eye view” of issues and the impacts of these issues upon other areas of the program.

TechMIS LLC Proprietary Module 6. Graphic Trace Report (MS Project add-on), continued: Example: Provides an intuitive, based graphical representation of the TRACE process. Displays a visual representation of the root issue(s) and its effect upon the larger process. TRACE 1) Requirement Compliance Issue is found level 4 deep within the program. 2) Elevated Here3) Elevated Here 4) Ultimately Elevated Here

TechMIS LLC Proprietary 8 Module 6. Graphic Trace Report (MS Project add-on), continued: Example:  Graphical interface can also facilitate hyperlinks to supporting information allowing for real-time “hands-on” analysis, data handling and ensuing mitigation efforts.