STEP Systems Engineering Project

AP233STEP Systems Engineering Project Jim U’RenSeptember 29, 2005 : 

AP233STEP Systems Engineering Project Jim U’RenSeptember 29, 2005

Scope of AP233Systems Engineering from a “Big Picture” Point of View : 

Scope of AP233Systems Engineering from a “Big Picture” Point of View Requirements Functional structure Physical structure and allocation Configuration and traceability Project and data management Schedule Cost Risk Consistent with INCOSE’s vision of Systems Engineering

AP233 Approach : 

AP233 Approach AP233 uses a modularized approach Partitioned a large problem space Allows sequential deliveries Develope APIs and Reference Implementations Work with other standards organizations OMG’s SysML Team INCOSE

Scope of AP233Planned Module Sets : 

Scope of AP233Planned Module Sets Requirements--complete Structural Models Behavioral Models Function-based State-based Project Management WBS Scheduling Cost Organizational Structure Risk Analysis* Rules* Validation and Verification PDM Extensions Security Data Representation Legend: Green-complete, Yellow italics-in process, White-TBD *Active collaboration with other teams: Risk with AP239, Rules with AP210

Systems EngineeringParticipants : 

Systems EngineeringParticipants NASA - H. Frisch, G. Siebes Eurostep – J. U’Ren D. Price, P. Spiby OSJTF – D. Hardy BAE SYTEMS - J. Johnson NIST - P. Denno, A. Barnard-Feeney Georgia Tech - R. Peak & Co. Boeing - G. Smith John Deere - R. Burkhart IBM - L. Balmelli MoD UK – M. Gibson Lockheed Martin - S. Friedenthal General Motors - M. Loeffler Volvo - M. Lindeblad United Technologies - R. Cohen Northrop Grumman – R. Wood Motorola – R. Bruce, T. Robar EADS – H. Eisenmann, R. Eckart Syntell – Erik Herzog INCOSE - D. Oliver, M. Dickerson OMG - SE DSIG, SysML, DODAF Teams NDIA - J. Hollenbach

Systems EngineeringNear-term Plans : 

Systems EngineeringNear-term Plans Release AP233 WD2 in Oct 2005 Work Breakdown Schedule Structure (system breakdown) Function-based Behavior State-based Behavior Test Test data exchanges using AP233/STEP modules Complete mapping of STEP/AP233 to DODAF database Work with AP239 to get Risk Modules to ballot

Implementations of Interest : 

Implementations of Interest UGS TeamCenter Requirements Using AP233 to update customers data from v4 to v5 Motorola Requirements Integration DOORS and IBM RequisitePro integrated using Eurostep’s SAs ThreeSL Cradle Included AP233 Demonstration Tool on distribution CD to enable customers to move requirements data between formats PTC Developing prototype implementation driving parametric models from AP233 property-based requirements (whitepaper in development)

Systems Engineering Project Challenges : 

Systems Engineering Project Challenges SC4 Management and Rules Changes Recent changes in SC4’s timeframes between stages (NWI, WD, CD, DIS, FDIS, IS) have created thresholds that could threaten project cancellation Resources Marketing SE project and PDES, Inc. capabilities to potential sponsors - need to close “the deal” Infrastructure Support for AP233 Resource constraints limiting updates and bugfixes of key infrastructure pieces.

Systems Engineering Project Assessment : 

Systems Engineering Project Assessment AP233 continues to gain visibility Vendor involvement in implementations continues Industry groups (e.g., INCOSE, NDIA) show interest Testing is important—initial plans made for a Systems Engineering Implementors Forum (SE-IF) Resources to complete the Project are tight

OSJTF Sponsored Work(Open Systems Joint Task Force)Linking DODAF-SysML-STEP : 

OSJTF Sponsored Work(Open Systems Joint Task Force)Linking DODAF-SysML-STEP SV4 OMG SysML Other SE Views DODAF Detailed Design, Manufacturing, Life Cycle Support, … ISO 10303 STEP Standards specifies requirements for CADM = Core Architecture Data Model DARS = DoD Architecture Repository System

AP233 Module Sets : 

AP233 Module Sets Text-based Requirements [TBR] - a data model that describes requirements as text strings with traceability, allocation, weighting and risk identified with each requirement Property-based Requirements [PBR] - a data model that describes requirements as structured and quantified formalisms that maybe decomposed from text-based requirements; can include tables, spreadsheets, graphs, charts, pictures and equations Structural Models - a data model that describes how a system is built; defines the static relationships among the subsystems, components, or parts that actually constitute the system; describes what is designed, built and maintained; contains specifications for design, manufacture, and maintenance and information about actual manufactured parts and their verification and maintenance --more--

AP233 Module Sets : 

AP233 Module Sets Behavioral Models - a data model that describes how a system performs; includes functions, inputs, outputs and control operators which define the ordering of functions; the model describes Functional Flow Block Diagrams, Finite State Machines, Causal Chain, Data Flow Diagrams and Sequence Diagrams Data Representation - "a consistent set of “presentation mechanisms” and “advanced schematics product model definition”, which is designed to present the computer sensible model data (defined in representation model space) onto a human understandable schematic diagram (presentation space), conforming to conventional and/or future draughting standards" [from Intelligent Sematics PWI RDD] --more--

AP233 Module Sets : 

AP233 Module Sets Risk Analysis - a data model that identifies risk(s), describes their status, specifies relationships, likelihood, consequence, impact approach strategy and contingencies Cost Models - a data model that describes direct, indirect, fixed, variable, material, administrative, finance, and contingency costs; provides linkage to system product structure(s) Scheduling - a data model that identifies activities, dependencies, durations and milestones associated with products described in the WBS; includes WorkFlow Diagrams, Network Schedules, Gantt Charts and Resource Leveling. [work with PLCS] --more--

AP233 Module Sets : 

AP233 Module Sets Work Breakdown Structure - a data model that represents the structure used to represent the pieces of work necessary to complete a project.  [ work with PLCS ]  PDM - a data model that extends the STEP PDM Schema and PDM Modules to electro-mechanical, system engineering, product life-cycle and other non-physical domains.  [ work with PLCS and PDM ] Security - a data model that describes project, organization, country and user defined security levels as well as user authentication and intellectual property.  [ work with PLCS and PDM ] --more--

AP233 Module Sets : 

AP233 Module Sets Organizational Structure - a data model that provides relationships, functional roles, skill qualification and documentation that defines an organizational structure.  [ work with PLCS ] Validation and Verification Model - a data model that describes the plan, infrastructure and status of validation and verification processes Allocation Model - a data model that describes structures necessary to allocate requirements, schedule, costs, risks and other functions associated with a body of work AP Interface Models - a data model that describes the interfaces between domain specific data models such as mechanical, electronic, structural analysis, thermal analysis, manufacturing, etc. [ work with other STEP AP groups ]

Tools Used in Testing AP233 Requirements Exchanges : 

Tools Used in Testing AP233 Requirements Exchanges Eurostep TBR Demonstrator Tool UGS TeamCenter Requirements EDS Slate ThreeSL CRADLE Telelogics DOORS Rational RequisitePro LKSoft STEP Book Expresso Vitech CORE Eurostep SAS MS Excel MS Word