TRAC Software for creation of supplier contract risk profile

Slides:



Advertisements
Similar presentations
Software change management
Advertisements

QuEdge Testing Process Delivering Global Solutions.
Database Planning, Design, and Administration
Traceability James D. Palmer Presented by: Megan Heffernan.
SEBGIS 2005, Agia Napa, Cyprus, October 31 - November 4, 2005 MECOSIG Adapted to the Design of Distributed GIS F. Pasquasy, F. Laplanche, J-C. Sainte &
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.
Dr Gordon Russell, Napier University Unit Data Dictionary 1 Data Dictionary Unit 5.3.
Transformations at GPO: An Update on the Government Printing Office's Future Digital System George Barnum Coalition for Networked Information December.
Administration & Workflow
Software Quality Engineering Roadmap
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
7M822 Software Engineering: System Models 14 September 2009.
BUSINESS DRIVEN TECHNOLOGY
Software causes many failures - significant mission risk Hard to quantify effects on system risk of: software defects software development practices software.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Page 1 ISMT E-120 Introduction to Microsoft Access & Relational Databases The Influence of Software and Hardware Technologies on Business Productivity.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
United Nations Economic Commission for Europe Statistical Division Applying the GSBPM to Business Register Management Steven Vale UNECE
Overview of Change Management ClearQuest Overview for CORUG January, 2008.
This chapter is extracted from Sommerville’s slides. Text book chapter
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Introduction to Database Concepts
JumpStart the Regulatory Review: Applying the Right Tools at the Right Time to the Right Audience Lilliam Rosario, Ph.D. Director Office of Computational.
Overview of the Database Development Process
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
6-1 DATABASE FUNDAMENTALS Information is everywhere in an organization Information is stored in databases –Database – maintains information about various.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
STORING ORGANIZATIONAL INFORMATION— DATABASES CIS 429—Chapter 7.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.
Using a Comprehensive Occupational Exposure Database to Integrate Members of the Occupational Health Team and Improve Your Occupational Health Program.
Storing Organizational Information - Databases
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 7 Storing Organizational Information - Databases.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Software quality factors
ANKITHA CHOWDARY GARAPATI
Certification and Accreditation CS Unit 2:ITSEC System Classes LTC Tim O’Hara Ms Jocelyne Farah Mr Clinton Campbell.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Metadata By N.Gopinath AP/CSE Metadata and it’s role in the lifecycle. The collection, maintenance, and deployment of metadata Metadata and tool integration.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
Completing the Loop: Linking Software Features to Failures 31 July 2003 Copyright © 2003, Mountain State Information Systems, Inc. All rights reserved.
NURHALIMA 1. Identify the trade-offs when using CASE Describe organizational forces for and against adoption of CASE tools Describe the role of CASE tools.
Completing the Loop: Linking Software Features to Failures 20 July 2004 Copyright © 2004, Mountain State Information Systems, Inc. All rights reserved.
1 SAS ‘04 Reducing Software Security Risk through an Integrated Approach David P. Gilliam and John D. Powell.
Database Overview What is a database? What types of databases are there? How are databases more powerful than spreadsheets?
Appendix 2 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Overview of System Engineering
Chapter 4 Automated Tools for Systems Development
Database Development Cycle
Code search & recommendation engines
Modern Systems Analysis and Design Third Edition
Presentation transcript:

TRAC Software for creation of supplier contract risk profile 2 Searcher 1 Profiler TRAC 4 Manager 3 Interviewer Software for creation of supplier contract risk profile Single point search access software for supplier anomalies Interviewing software for surveillance contract risk plan generation System manager software 1

1 Software for creation of supplier contract risk profile: generates a semi-quantitative profile of a supplier from a risk perspective Software interviews project managers and others about their experience with suppliers for contract risk surveillance Risk profile questions verified and validated across NASA for accuracy and inclusiveness Generates a comprehensive list of supplier contract risk surveillance activities 2

Tests supplier contract risk surveillance activities for completeness 1 Software for creation of supplier contract risk profile: generates a semi-quantitative profile of a supplier from a risk perspective Correlates supplier contract risk surveillance activities to mission life-cycle stages Tests supplier contract risk surveillance activities for completeness Creates a matrix with profile attributes as columns & supplier contract risk surveillance activities as rows. 3

A Very Simplified Matrix Example 4

Does not alter existing databases or duplicate data storage 2 Search Software Provides single point of access from which to search and track NASA-wide supplier contract histories and anomalies Defines relationships between myriad of anomaly contract risk element databases across NASA Does not alter existing databases or duplicate data storage Uses single query 5

2 Search Software Users have access to all various NASA supplier contract risk element anomaly data repositories Supplier contract risk database facilitates statistical analyses of NASA-wide supplier contract risk element data for trends analyses Method similar to IBM Orthogonal Defect Classification (ODC) for software design and code used to compare and contrast the manner in which the database is semantically defined. ODC is adapted to include hardware anomalies. 6

3 Interviewing Software Interviewing software suggests supplier contract risk surveillance plan to the user based on supplier contract risk profile developed by user answers to interview Contract surveillance risk plan is tailored based on sensitivity analysis of users risk tolerance responses in interview Contract surveillance risk plan incorporates input from anomaly search engine software results Extensive NASA-wide beta testing followed by testing of TRAC user manual and submission of training recommendations 7

4 System Manager System Manager Software (SMS) tests all subsystems as an integrated unit and checks for system sensitivity to user needs SMS coordinates all software systems for application to a specific supplier contract risk surveillance plan SMS insures automatic transfer of the risk profile and contract risk anomaly trend analysis as input to the supplier contract risk interviewing software SMS offers supplier contract risk mitigation suggestions to the user based on user report requests 8