AP233 Overview

853 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
853
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • AP233 Module Sets The following identifies and describes the Module Sets for AP233, the STEP Systems Engineering Project.  Requirements - a data model that describes requirements as text strings with traceability, allocation, weighting and risk identified with each requirement [ Text-based Requirements ( TBR ) ] and that describes requirements as structured and quantified formalisms that maybe decomposed from text-based requirements; can include tables, spreadsheets, graphs, charts, pictures and equations [ Property-based Requirements (PBR) ]. 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. 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. 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. Risk Analysis - a data model that identifies risk(s), describes their status, specifies relationships, likelihood, consequence, impact approach strategy and contingencies. [ may collaborate/reuse PLCS Risk Model ] Cost Models - a data model that describes direct, indirect, fixed, variable, material, administrative, finance, and contingency costs; provides linkage to system product structure(s) 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 ] [ may include features from AP221 and AP212 ] 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 ] 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 ] Organizational Structure - a data model that provides relationships, functional roles, skill qualification and documentation that defines an organizational structure.  [ work with PLCS ] 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 ]
  • AP233 Overview

    1. 1. AP233 STEP Systems Engineering Project Jim U’Ren September 29, 2005
    2. 2. Scope of AP233 Systems Engineering from a “Big Picture” Point of View <ul><li>Requirements </li></ul><ul><li>Functional structure </li></ul><ul><li>Physical structure and allocation </li></ul><ul><li>Configuration and traceability </li></ul><ul><li>Project and data management </li></ul><ul><ul><li>Schedule </li></ul></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Risk </li></ul></ul><ul><li>Consistent with INCOSE’s vision of Systems Engineering </li></ul>
    3. 3. AP233 Approach <ul><li>AP233 uses a modularized approach </li></ul><ul><ul><li>Partitioned a large problem space </li></ul></ul><ul><ul><li>Allows sequential deliveries </li></ul></ul><ul><ul><li>Develope APIs and Reference Implementations </li></ul></ul><ul><li>Work with other standards organizations </li></ul><ul><ul><li>OMG’s SysML Team </li></ul></ul><ul><ul><li>INCOSE </li></ul></ul>
    4. 4. Scope of AP233 Planned Module Sets <ul><li>Requirements--complete </li></ul><ul><li>Structural Models </li></ul><ul><li>Behavioral Models </li></ul><ul><ul><li>Function-based </li></ul></ul><ul><ul><li>State-based </li></ul></ul><ul><li>Project Management </li></ul><ul><ul><li>WBS </li></ul></ul><ul><ul><li>Scheduling </li></ul></ul><ul><ul><li>Cost </li></ul></ul><ul><ul><li>Organizational Structure </li></ul></ul><ul><li>Risk Analysis* </li></ul><ul><li>Rules* </li></ul><ul><li>Validation and Verification </li></ul><ul><li>PDM Extensions </li></ul><ul><li>Security </li></ul><ul><li>Data Representation </li></ul>Legend : Green -complete, Yellow italics -in process, White-TBD * Active collaboration with other teams: Risk with AP239, Rules with AP210
    5. 6. Systems Engineering Participants <ul><li>NASA - H. Frisch, G. Siebes </li></ul><ul><li>Eurostep – J. U’Ren D. Price, P. Spiby </li></ul><ul><li>OSJTF – D. Hardy </li></ul><ul><li>BAE SYTEMS - J. Johnson </li></ul><ul><li>NIST - P. Denno, A. Barnard-Feeney </li></ul><ul><li>Georgia Tech - R. Peak & Co. </li></ul><ul><li>Boeing - G. Smith </li></ul><ul><li>John Deere - R. Burkhart </li></ul><ul><li>IBM - L. Balmelli </li></ul><ul><li>MoD UK – M. Gibson </li></ul><ul><li>Lockheed Martin - S. Friedenthal </li></ul><ul><li>General Motors - M. Loeffler </li></ul><ul><li>Volvo - M. Lindeblad </li></ul><ul><li>United Technologies - R. Cohen </li></ul><ul><li>Northrop Grumman – R. Wood </li></ul><ul><li>Motorola – R. Bruce, T. Robar </li></ul><ul><li>EADS – H. Eisenmann, R. Eckart </li></ul><ul><li>Syntell – Erik Herzog </li></ul><ul><li>INCOSE - D. Oliver, M. Dickerson </li></ul><ul><li>OMG - SE DSIG, SysML, DODAF Teams </li></ul><ul><li>NDIA - J. Hollenbach </li></ul><ul><li>Vendors Participating : </li></ul><ul><li>UGS – TeamCenter Requirements </li></ul><ul><li>ThreeSL - Cradle </li></ul><ul><li>i-Logix - Statemate, Rhapsody </li></ul><ul><li>Artisan – Real-time Studio </li></ul><ul><li>Vitech - CORE </li></ul><ul><li>Telelogic – Doors </li></ul><ul><li>ITI – QFD </li></ul>
    6. 7. Systems Engineering Near-term Plans <ul><li>Release AP233 WD2 in Oct 2005 </li></ul><ul><ul><li>Work Breakdown </li></ul></ul><ul><ul><li>Schedule </li></ul></ul><ul><ul><li>Structure (system breakdown) </li></ul></ul><ul><ul><li>Function-based Behavior </li></ul></ul><ul><ul><li>State-based Behavior </li></ul></ul><ul><li>Test </li></ul><ul><ul><li>Test data exchanges using AP233/STEP modules </li></ul></ul><ul><li>Complete mapping of STEP/AP233 to DODAF database </li></ul><ul><li>Work with AP239 to get Risk Modules to ballot </li></ul>
    7. 8. Implementations of Interest <ul><li>UGS TeamCenter Requirements </li></ul><ul><ul><li>Using AP233 to update customers data from v4 to v5 </li></ul></ul><ul><li>Motorola Requirements Integration </li></ul><ul><ul><li>DOORS and IBM RequisitePro integrated using Eurostep’s SAs </li></ul></ul><ul><li>ThreeSL Cradle </li></ul><ul><ul><li>Included AP233 Demonstration Tool on distribution CD to enable customers to move requirements data between formats </li></ul></ul><ul><li>PTC </li></ul><ul><ul><li>Developing prototype implementation driving parametric models from AP233 property-based requirements (whitepaper in development) </li></ul></ul>
    8. 9. Systems Engineering Project Challenges <ul><li>SC4 Management and Rules Changes </li></ul><ul><ul><li>Recent changes in SC4’s timeframes between stages (NWI, WD, CD, DIS, FDIS, IS) have created thresholds that could threaten project cancellation </li></ul></ul><ul><li>Resources </li></ul><ul><ul><li>Marketing SE project and PDES, Inc. capabilities to potential sponsors - need to close “the deal” </li></ul></ul><ul><li>Infrastructure Support for AP233 </li></ul><ul><ul><li>Resource constraints limiting updates and bugfixes of key infrastructure pieces. </li></ul></ul>
    9. 10. Systems Engineering Project Assessment <ul><li>AP233 continues to gain visibility </li></ul><ul><li>Vendor involvement in implementations continues </li></ul><ul><li>Industry groups (e.g., INCOSE, NDIA) show interest </li></ul><ul><li>Testing is important—initial plans made for a Systems Engineering Implementors Forum (SE-IF) </li></ul><ul><li>Resources to complete the Project are tight </li></ul>
    10. 11. Systems Engineering Project Back-Up Slides
    11. 12. 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 Operational Systems Technical AP2xx AP233 DARS CADM CADM
    12. 13. AP233 Module Sets <ul><li>Text-based Requirements [TBR] - a data model that describes requirements as text strings with traceability, allocation, weighting and risk identified with each requirement </li></ul><ul><li>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 </li></ul><ul><li>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 </li></ul>-- more--
    13. 14. AP233 Module Sets <ul><li>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 </li></ul><ul><li>Data Representation - &quot;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&quot; [from Intelligent Sematics PWI RDD] </li></ul>-- more--
    14. 15. AP233 Module Sets <ul><li>Risk Analysis - a data model that identifies risk(s), describes their status, specifies relationships, likelihood, consequence, impact approach strategy and contingencies </li></ul><ul><li>Cost Models - a data model that describes direct, indirect, fixed, variable, material, administrative, finance, and contingency costs; provides linkage to system product structure(s) </li></ul><ul><li>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] </li></ul>-- more--
    15. 16. AP233 Module Sets <ul><li>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 ]  </li></ul><ul><li>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 ] </li></ul><ul><li>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 ]  </li></ul>-- more--
    16. 17. AP233 Module Sets <ul><li>Organizational Structure - a data model that provides relationships, functional roles, skill qualification and documentation that defines an organizational structure.  [ work with PLCS ] </li></ul><ul><li>Validation and Verification Model - a data model that describes the plan, infrastructure and status of validation and verification processes </li></ul><ul><li>Allocation Model - a data model that describes structures necessary to allocate requirements, schedule, costs, risks and other functions associated with a body of work </li></ul><ul><li>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 ] </li></ul>
    17. 18. Tools Used in Testing AP233 Requirements Exchanges <ul><li>Eurostep TBR Demonstrator Tool </li></ul><ul><li>UGS TeamCenter Requirements </li></ul><ul><ul><li>EDS Slate </li></ul></ul><ul><li>ThreeSL CRADLE </li></ul><ul><li>Telelogics DOORS </li></ul><ul><li>Rational RequisitePro </li></ul><ul><li>LKSoft STEP Book </li></ul><ul><li>Expresso </li></ul><ul><li>Vitech CORE </li></ul><ul><li>Eurostep SAS </li></ul><ul><li>MS Excel </li></ul><ul><li>MS Word </li></ul>

    ×