ATI Professional Development Short Course Universal Arhitecture Description Framework

548 views

Published on

ATI Professional Development Short Course Universal Arhitecture Description Framework

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

No Downloads
Views
Total views
548
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

ATI Professional Development Short Course Universal Arhitecture Description Framework

  1. 1. JOGSE Grand Systems Development Training Program Requirements Courses 521 Grand Systems Requirements Elicitation and Analysis 522 Grand Systems Requirements Management and Documentation 523 Grand Systems Requirements 524 Grand Systems Functional Analysis 525 Grand Systems MSA/PSARE 526 Grand Systems UML/SysML 527 Grand Systems IDEF/DoDAF 528 Universal Architecture Description Framework 541 Grand Systems Verification VERSION 12.0 c JOG System Engineering, Inc.
  2. 2. The Problem and the Prescription • When developing unprecedented systems all requirements in performance specifications should be derived from models • No single existing model is comprehensive • We will construct a comprehensive model that can be used on all programs no matter the nature of the physical product (hardware, software, people doing things) • Existing specification templates are not coordinated with modeling methods so we will build one that is VERSION 12.0 5282A-1-4 c JOG System Engineering, Inc.
  3. 3. Course Sequence • What are requirements and what kinds might we have to identify? • Next we will look at a very simple way to write requirements – Controlled characteristic, value and units, relation • Then, we will discuss ways these requirements are inter-related • In subsequent periods, we will construct a toolbox full of effective tools to help us identify appropriate requirements for systems, hardware, and software entities • These models will be combined to form universal architecture description frameworks using a universal specification template VERSION 12.0 5282A-1-5 c JOG System Engineering, Inc.
  4. 4. Who Is Jeff Grady? CURRENT POSITION President, JOG System Engineering, Inc. System engineering assessment, consulting, and training firm PRIOR EXPERIENCE U.S. Marines 1964 - 1965 General Precision, Librascope Div Customer Training Instructor, SUBROC and ASROC ASW Systems 1965 - 1982 Ryan Aeronautical, Teledyne Ryan Aeronautical Field Engineer, AQM-34 Series Special Purpose Aircraft Project Engineer, System Engineer, Unmanned Aircraft Systems 1982 - 1984 General Dynamics Convair Division System Engineer, Group Engineer Advanced Cruise Missile 1984 - 1993 General Dynamics Space Systems Division Engineering Manager, Systems Development Advanced Projects Systems Engineering FORMAL EDUCATION BA Math, SDSU; System Engineering Certificate, UCSD MS Systems Management, USC with Information Systems Certificate INCOSE First elected Secretary, Founder, Fellow, and CSEP Author System Requirements Analysis (93 and 06), System Integration, System Validation and Verification, System Engineering Planning and Enterprise Identity, System Engineering Deployment, System Verification VERSION 12.0 5282A-1-6 c JOG System Engineering, Inc.
  5. 5. Systems Jeff Grady Worked On USAF/GD Convair AQM 129 USN/Librascope Advanced Cruise Missile ASROC/SUBROC USAF/GD Atlas Missile Computer Systems USAF/Ryan AQM-81 Firebolt 1983 VERSION 12.0 5282A-1-7 c JOG System Engineering, Inc.
  6. 6. Ryan Aeronautical War Birds USAF Models 147J, NX, G, and H at Bien Hoa, SVN in 1968 USAF/Ryan AQM-34L Tom Cat U.S. Navy/Ryan 58 Combat Missions Model 147SK USAF/Ryan BGM-34C VERSION 12.0 5282A-1-8 c JOG System Engineering, Inc.
  7. 7. Course Outline 1 Introduction to System Definition 15 IDEF and DoDAF 2 Requirements Fundamentals 16 IDEF and DoDAF 3 Architecture and Modeling 17 Introduction to UADF 4 Functional Analysis 18 Universal Specification 5 Functional Analysis 19 TSA/MSA UADF 6 Performance Analysis and the RAS 20 TSA/MSA UADF 7 Product Entity Structure Synthesis 21 SysML/UML UADF 8 Interface Identification and Definition 22 SysML/UML UADF 9 Specialty Engineering Requirements 23 PSARE UADF 10 Environmental Requirements 24 Management Infrastructure 11 MSA and PSARE and the Future 12 MSA and PSARE 25 Allocated to Project 13 UML and SysML 26 Allocated to Project 14 UML and SysML 27 Allocated to Project Short course involves 24 hours over three day period and is primarily lecture. University quarter length course will provide for up to three hours of in-class time for workshop that is completed as home work. VERSION 12.0 5282A-1-9 c JOG System Engineering, Inc.
  8. 8. Definition of a System A system is said to be a collection of entities that interact through relationships (interfaces) to achieve a planned outcome within an environment. SYSTEM FUNCTIONAL R1 R3 FUNCTION, R2 COOPERATIVE THE NEED ENVIRONMENT F Q ALLOCATION PHYSICAL I1 SYSTEM I3 COOPERATIVE I2 ENVIRONMENT A Q VERSION 12.0 5282A-1-10 c JOG System Engineering, Inc.
  9. 9. Why is the problem of developing systems to solve complex problems so complex? Is there a better way? VERSION 12.0 5282A-1-11 c JOG System Engineering, Inc.
  10. 10. Systems requirements analysis is an important part of a problem solving technique for complex problems. We can make it serve us better by adopting a UADF. VERSION 12.0 5282A-1-12 c JOG System Engineering, Inc.
  11. 11. The System Development Sequence That Minimizes Risk • Define the problem – Specifications • Solve the problem – Design, material, and manufacturing • Prove it – Verification • Within a sound management infrastructure VERSION 12.0 5282A-1-13 c JOG System Engineering, Inc.
  12. 12. Requirement Defined Something wanted or ITEM necessary. Something essential to the existence or occurrence of something else. A necessary character- istic or attribute of some thing (or item). VERSION 12.0 5282A-1-14 c JOG System Engineering, Inc.
  13. 13. Requirements Types • Performance – Tells what the entity must do and how well it must do it – Derived from dynamic problem space models • Constraints – Derived from solution space models of three kinds – Interface • Derived through n-square diagrams – Specialty Engineering or Quality • Derived through application of a specialty engineering scoping matrix and individual specialty models – Environmental • Derived through application of a three-layer model VERSION 12.0 5282A-1-15 c JOG System Engineering, Inc.
  14. 14. Requirements Types VERIFICATION REQUIREMENTS OPERATIONAL PROCESS PRODUCT AND LOGISTICS SUPPORT REQUIREMENTS REQUIREMENTS PRODUCTION PROCESS REQUIREMENTS SUPPORT EQUIPMENT TOOLS PERFORMANCE REQUIREMENTS TRAINING CONSTRAINTS PROCEDURES INTERFACE FACILITIES ENVIRONMENTAL SPARES SPECIALTY ENGINEERING All of these requirements must be identified before product detailed design work is started and they must be mutually consistent. VERSION 12.0 5282A-1-16 c JOG System Engineering, Inc.
  15. 15. What is a Specification? A specification contains all of the requirements for a given item. VERSION 12.0 5282A-1-17 c JOG System Engineering, Inc.
  16. 16. In Writing a Specification, What Is the Target? VERSION 12.0 5282A-1-18 c JOG System Engineering, Inc.
  17. 17. We Are All Specialists Breadth of Knowledge Depth of Knowledge All Knowledge It Just Keeps Generalist Knowledge Base Getting Domain Knowledge Base Bigger Specialist Knowledge Base VERSION 12.0 5282A-1-19 c JOG System Engineering, Inc.
  18. 18. What is the Hard Job in Preparing a Specification? • Specifications are full of sentences. • You should have no problem writing a simple sentence in your language of choice • There are two difficult tasks in writing these sentences – What do we write them about? – What numerical values do we place in them? VERSION 12.0 5282A-1-20 c JOG System Engineering, Inc.

×