Download - Applied Technology Institute

Systems Engineering - RequirementsCourse # M231January 27-29, 2015Columbia, MarylandFebruary 23-26, 2015Live Virtual Online • (12:00pm - 4:30pm)$1895 (8:30am - 4:30pm)"Register 3 or More & Receive $100 00 eachOff The Course Tuition."Call for information about our six-course systems engineeringcertificate program or for “on-site” training to prepare for theINCOSE systems engineering exam.SummaryThis three-day (or four-day live instructor lead virtualonline) course provides system engineers,teamleaders, and managers with a clear understandingabout how to develop good specifications affordablyusing modeling methods that encourage identificationof the essential characteristics that must be respectedin the subsequent design process. Both the analysisand management aspects are covered. Each studentwill receive a full set of course notes and textbook,“System Requirements Analysis,” by the instructor JeffGrady.InstructorJeffrey O. Grady (MSSM, ESEP) is the president ofa System Engineering company. He has30 years of industry experience inaerospace companies as a systemengineer, engineering manager, fieldengineer, and project engineer plus 20years as a consultant and educator. Jeffhas authored ten published books in thesystem engineering field and holds a Master ofScience in System Management from USC. Heteaches system engineering courses nation-wide. Jeffis an INCOSE Founder and Fellow.What You Will Learn• How to model a problem space using proven methodswhere the product will be implemented in hardwareor software.• How to link requirements with traceability and reducerisk through proven techniques.• How to identify all requirements using modeling thatencourages completeness and avoidance ofunnecessary requirements.• How to structure specifications and manage theirdevelopment.This course will show you how to build goodspecifications based on effective models. It is notdifficult to write requirements; the hard job is toknow what to write them about and determineappropriate values. Modeling tells us what to writethem about and good domain engineeringencourages identification of good values in them.Course Outline1. Introduction2. Introduction (Continued)3. Requirements Fundamentals – Defines what arequirement is and identifies 4 kinds.4. Requirements Relationships – How arerequirements related to each other? We will look atseveral kinds of traceability.5. Initial System Analysis – The whole processbegins with a clear understanding of the user’s needs.6. Functional Analysis – Several kinds of functionalanalysis are covered including simple functional flowdiagrams, EFFBD, IDEF-0, and Behavioral Diagramming.7. Functional Analysis (Continued) –8. Performance Requirements Analysis –Performance requirements are derived from functions andtell what the item or system must do and how well.9. Product Entity Synthesis – The courseencourages Sullivan’s idea of form follows function so theproduct structure is derived from its functionality.10. Interface Analysis and Synthesis – Interfacedefinition is the weak link in traditional structured analysisbut n-square analysis helps recognize all of the waysfunction allocation has predefined all of the interfaceneeds.11. Interface Analysis and Synthesis – (Continued)12. Specialty Engineering Requirements – Aspecialty engineering scoping matrix allows systemengineers to define product entity-specialty domainrelationships that the indicated domains then apply theirmodels to.13. Environmental Requirements – A three-layermodel involving tailored standards mapped to systemspaces, a three-dimensional service use profile for enditems, and end item zoning for component requirements.14. Structured Analysis Documentation – How canwe capture and configuration manage our modeling basisfor requirements?15. Software Modeling Using MSA/PSARE –Modern structured analysis is extended to PSARE asHatley and Pirbhai did to improve real-time control systemdevelopment but PSARE did something else not clearlyunderstood.16. Software Modeling Using Early OOA and UML –The latest models are covered.17. Software Modeling Using Early OOA and UML –(Continued).18. Software Modeling Using DoDAF – DoD hasevolved a very complex model to define systems oftremendous complexity involving global reach.19. Universal Architecture Description FrameworkA method that any enterprise can apply to develop anysystem using a single comprehensive model no matterhow the system is to be implemented.20. Universal Architecture Description Framework(Continued)21. Specification Management – Specificationformats and management methods are discussed.22. Requirements Risk Abatement – Specialrequirements-related risk methods are covered includingvalidation, TPM, margins and budgets.23. Tools Discussion24. Requirements Verification Overview – Youshould be basing verification of three kinds on therequirements that were intended to drive design. Theselinks are emphasized.Register online at www.ATIcourses.com or call ATI at 888.501.2100 or 410.956.8805 Vol. 119 – 35