FRAT – A BASIC FRAMEWORK FOR SYSTEMS ENGINEERING By Brian W. Mar and Bernard G. Morais

1. FRAT – A BASIC FRAMEWORK FOR SYSTEMS ENGINEERING By Brian W. Mar and Bernard G. Morais

2. FRAT - FUNDAMENTALS 1. Anything can be viewed as a system 2. Utilize basic system concepts 3. Four views of a system are needed 4. Three interacting systems important

3. 1. Anything can be viewed as a system ORGANIZATIONS SOFTWARE ELECTRONICS PROCESSES PARTIES HARDWARE

4. 2. Utilize basic system concepts Define boundaries and input/outputs flows flows Decompose whole into parts trees

5. 3. Four views of a system are needed Function view describes actions Requirements view describes metric Answer view describes what it is Test view describes v&v

6. requirement answer test System description is incomplete unless all four FRAT views presented function

7. Typical descriptions fail to provide all views completely function requirement answer test

8. DIFFERENCE IN FRAT VIEWS Functions access internet view pictures run programs play music affordable compact Requirements Microsoft Office and windows compatible cost less than $1000 smaller than text for this class Answer model x01p Runfast lap top Tests all functions and requirements demonstrated to user prior to sale

9. IDEAL - F R A T COTS - A T R F Processes used to generate FRAT descriptions

10. IDEAL - F R A T COTS - A T R F Processes used to generate FRAT descriptions SE literature - R F A T

11. Define goals and objectives Define desired system’s functions Define system’s requirements Identify alternatives System Engineering Process Stakeholders customers Establish Decision criteria regulations Constraints Select and implement Validate and verify

12. Upper Level FRAT Data Provides Scope For Next Level Lower Level Must Roll - Up and Map to Upper Level Each Level of FRAT Establishes a BASELINE Simulation Models Provide Dynamic Views of FRAT Systems thinking -each of the FRAT views can be described with

13. WHY USE FRAT? Ensures developer understands what the product is suppose to do before it is built Provides a basis for evaluation of product before acceptance and payment Provides a shared vision of how to develop and use the product Supports a structured and discipline approach to information capture and tracing

14. 4. Three interacting systems important development and operating environment process system product system

15. EIA/IS 731 Key Areas and Processes PROJECT OR MANAGEMENT AREAS Plan and Organize Monitor and Control Integrate Disciplines Coordinate With Suppliers Manage Risk Manage Data Manage Configuration Ensure Quality ENGINEERING, TECHNICAL, AND SYSTEMS ENGINEERING AREAS Define Stakeholders and System Level Requirements Define Technical Requirements Assess and Select Integrate System Verify System Validate System