Systems Engineering Example Using Cognition Cockpit

  • Uploaded by: David M Cronin
  • 0
  • 0
  • May 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Systems Engineering Example Using Cognition Cockpit as PDF for free.

More details

  • Words: 1,618
  • Pages: 53


Overview Of INCOSE Tool Vendor Challenge

Using Cognition Cockpit Version 5.4 (A Web 2.0 Application) (Presented by Cognition as part of a Systems Engineering challenge for a simulated automated parking system for a worldwide hotel chain) “NotilHotel Parking System”

© 2009 Cognition Corporation



INCOSE Challenge Problem Statement

1. General Background NotilHotels is a world-wide hotel chain with head-offices in Paris, specializing in low-cost, high valued business hotels in city centers around the world. Each hotel has some space for parking, but the space is often occupied by people working in nearby offices, causing arriving guests not to find space for parking their car near the hotel. In order to secure parking space for their guests, they plan to develop an automated parking system that can regulate the use of the limited parking space.

© 2009 Cognition Corporation



INCOSE Challenge Problem Statement

2. The requirements specified by the management are: -One or two parking lots per hotel -Optimum service to hotel guests -User-friendly, minimum hassle operation -Payment of a reasonable parking fee included in the hotel bill, or payable separately -Easily adaptable to the local environment, because there are hotels in 50 different countries -In case there is more space than expected guests on a given day, the remaining parking space is to be made available to non-guests, in order to maximize revenues - The system must be operational at the opening of their newest hotel January 25, XXXX

© 2009 Cognition Corporation



INCOSE Challenge Problem Statement 3. Vendors are asked to provide the following: -Compose the system specification -Demonstrate requirements handling -Define the system in its environment -Define logical sub-systems, flows from sub-systems to the environment and flows between sub-systems -Define sub-system activities -Don’t forget to include the particularities of the human sub-systems (=humans) that are part of the total system -Describe the functional modes of the system and transfers between them -Draw a timeline for the development of the system - Show how your tool supports the System Engineering activities © 2009 Cognition Corporation



INCOSE Challenge Problem Statement

4. Questions to the Customer From Thursday June 12th, participants may send “questions to the customer” ([email protected]). We (the customer) will do our best to answer these questions to all contact persons about once a day. However, the customer may have to think for some time about some questions and may have no good answer to some questions. Just a typical customer. At the symposium, the Challenge and the questions (if any) will be posted on the designated Tool Vendor Challenge notice board. Questions may be submitted until Monday (June XX) 17:30. Questions should state the organization asking the question. All challenge participants and (at the Symposium) all conference attendees will be able to see all the questions and the answers.

© 2009 Cognition Corporation



Schematic View Of Cognition Cockpit

© 2009 Cognition Corporation



Risk Plans, FTA & System FMEA

Automatic Status Tracking, Workflow States & Reporting

Legend: Data flow from template to template

...

One or more system/user-defined PDP templates or worksheets © 2009 Cognition Corporation

Flow-down to Sub-System Requirements Including CPM

Version Control, Baselining, Visual Differencing, Markups, Action Items, etc. Transfer Function Definition, Cpk/PNC Computation, Monte Carlo, DOE, etc.

LEAN EXECUTION AND FULL TRACEABILITY

Sub-System Verification Test Protocols & Trace Matrices

Failure Modes

Test Plans & Trace Matrices

Verification Tests

Concept Selection, Pugh, Benchmarking, Voting, Attachments, Electronic Notebooks, QFD, etc.

COMPLIANT FORMATTING & AUTOMATIC PREPARATION OF PDP DELIVERABLES Sub-System, Component & Process Requirements

System Requirements Definition, Documentation & Prioritization

System Risks

Hazard Assessment and Mitigation Planning

Meeting Minutes, Interview Guides, Electronic Affinity Diagramming (KJ)

Validation Tests

PREDEFINED OR CUSTOM DATA-FLOW THROUGH PDP STEPS System/Product Requirements

VOC/VOB/... Requirements Definition & Weighting

User Hazards

Customer/Busines s Requirements

Other Influencers

Customer Needs

Business Needs

Cognition Cockpit Will Help You By Automatically Generating Your Process Steps & Documents

Sub-System, Component & Process FMEAs

...



Conduct Customer Interviews We Used Built In Templates To Import Interviews With Hotel Managers

© 2009 Cognition Corporation



KJ Analysis / Affinity On Customer Inputs Here Are Your Inputs You Organized With Our Electronics “Sticky Notes”

© 2009 Cognition Corporation



Team Voting on Voices / Requirements Scores Your Three Top Managers Voted On Customer Input Rankings

© 2009 Cognition Corporation



Rank Voices / Requirements We Used The Inputs And Voting To Prioritize The Customer Inputs

© 2009 Cognition Corporation



Process & Data Flow We Use Embedded Visio To Map The Project Data Flows

© 2009 Cognition Corporation



Model The Use Cases: Use Visio Embedded In Cockpit Including Version Control And History Of The Visio Files

© 2009 Cognition Corporation



Model The Use Cases: Create Directly In Cockpit Here Is The Use Case For A Car Approaching The Gate From Outside

© 2009 Cognition Corporation



Automatically Generate Requirements Documentation We Will Have Cockpit Create Your Documents

Create New Document / Deliverable

Choose From Template Library

© 2009 Cognition Corporation



Your Current System Requirements Document

© 2009 Cognition Corporation



Your Requirements Document In “PRD” Format

© 2009 Cognition Corporation



Your Requirements Document In “MIL STD 961E” Format

© 2009 Cognition Corporation



Automatically Generated Deliverables On Your Web Site

© 2009 Cognition Corporation



Link Inputs / Voices To Specific Requirements For Trace Use The Standard Template To Create The Trace Relationships

© 2009 Cognition Corporation



Competitive Assessment Of Project Performance Comparing You To Your Competitors

© 2009 Cognition Corporation



House Of Quality To Prioritize Requirements Mapping Your System Requirements To The Customer Inputs

© 2009 Cognition Corporation



Automatic Trace: Voices To Requirements Confirming All Customer Inputs Have A System Requirement

© 2009 Cognition Corporation



Automatic Trace: Requirements To Voices Confirming All System Requirements Have A Customer Input

© 2009 Cognition Corporation



The First House Of Quality With Excel Embedded In Cockpit

© 2009 Cognition Corporation



Pugh Concept Selection Ranking Your Two Main Concepts Against Customer Inputs

© 2009 Cognition Corporation



Flowdown / Cascade Requirements And Specifications Defining Your Lower Level Requirements

© 2009 Cognition Corporation



Test Plans We Automatically Created Your Test Protocols

© 2009 Cognition Corporation



Test Plans We Automatically Created Your V & V Plan

© 2009 Cognition Corporation

Real Time System Trace Matrix Checking The Trace: Inputs-Requirements-Specs-Tests

© 2009 Cognition Corporation





Statistical Analysis Of Critical Parameters We Will Now Analyze Some Of The Most Critical Requirements

© 2009 Cognition Corporation



Transfer Function Overview Transfer Functions are Required for Predictive Engineering Calculate nominal output value given a set of inputs y = f(x1, x2, … xn) or Y = f( x, y, n) Where: x = input specs, y = subordinate results, n = noise

 Popular Methods for Developing Transfer Functions  Explicit Engineering Equations  Experiments; DOE & Monte Carlo (Physical & Simulated)  Testing: Regression Analysis (Physical Only)  “Black Box” Application Software Tools  Company “Tribal Knowledge” © 2009 Cognition Corporation

Statistical Analysis Of A Requirement

© 2009 Cognition Corporation





Automatic Change Notification Of Numeric Changes If Your Booking Rate Goes Up . . .

© 2009 Cognition Corporation



This Requirement Will Improve: Note New Cpk

© 2009 Cognition Corporation



Status Summary Report Of “My Requirements” A Sub Team Is Monitoring Their Requirements’ Performance

© 2009 Cognition Corporation



Critical Parameter Management (CPM) Let’s Check Who Is Causing This Requirement To Miss Its Target

© 2009 Cognition Corporation



Cockpit’s Mind Map Mode Some People Like To Work In A Graphical Layout

© 2009 Cognition Corporation



You Can Modify Your Requirements In Mind Map Mode Feel Free To Explore, Change, And “What If” Various Configurations

© 2009 Cognition Corporation



Scorecard With Requirement Status Here Is Statistical Data On One Of Your Critical Requirements

© 2009 Cognition Corporation



Design And Test Values For A Requirement Let’s Look Even Deeper To Learn More

© 2009 Cognition Corporation



Design Margin Plot For A Requirement Let’s Look Real Time At This Requirement’s Behavior

© 2009 Cognition Corporation



Statistical Analysis Gives Us A Holistic Perspective Prioritize Requirements and Critical Parameters. Identify possible hot spots early in the process. Reduce cost by eliminating over design. Risk

Y’s

Y’s

X’s

Opportunity (overdesign) © 2009 Cognition Corporation



FMEA And Risk Plans We Created A System FMEA For Your Project

© 2009 Cognition Corporation



Associate Risks/Failures With Requirements We Can Tell You Which Requirements Have Which Failure Modes

© 2009 Cognition Corporation



Scoring The Causes In An FMEA Flowdown Exercise Here Are Your Project’s Biggest Possible Causes Of Failures

© 2009 Cognition Corporation



Automatically Generated FMEA Report We Have Risks, Causes, Mitigations, And Design Controls For You

© 2009 Cognition Corporation



Discovery Session Primary Tools We Have Combined Your Risks With Your Requirements Requirements Management Flow Down

Design Failure Modes & Effects Analysis (DFMEA)

Applied to “Optimistic” Requirements

Applied to “Pessimistic” Requirements

EX: What happens if a person forgets their car X: How do we ensure an easy walk to the car? What security problems might we have? How can we maximize space usage? System Radar Project

Subsystem

Comp

Vendor

Subsystem

Comp

Mat’l

Both Methods/Tools Capture Engineering “Tribal Knowledge” © 2009 Cognition Corporation



Cost Rollup And Cost Tracking Here Are The Cost Metrics For The Project

© 2009 Cognition Corporation



Cost Reports What Are The Key Cost Drivers For The Entry Gate?

© 2009 Cognition Corporation



Cost Waterfall Chart Are We Trending Towards Our Cost Goals For This System?

© 2009 Cognition Corporation



Automatic Graphical Trace For A Requirement Here Is The Graphic Mode Again Showing Some Of The Links

© 2009 Cognition Corporation



[email protected] 508-245-2142 www.cognition.us www.criticalparameters.com

© 2009 Cognition Corporation

Related Documents


More Documents from ""