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

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

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

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

5. 3. Four views of a system are needed F unction view describes actions A nswer view describes what it is R equirements view describes metric T est view describes v&v

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

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

8. 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 DIFFERENCE IN FRAT VIEWS

9. Processes used to generate FRAT descriptions IDEAL - F RAT COTS - A TRF

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

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

12. Systems thinking - each of the FRAT views can be described with 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

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. ENGINEERING, TECHNICAL, AND SYSTEMS ENGINEERING AREAS Define Stakeholders and System Level Requirements Define Technical Requirements Assess and Select Integrate System Verify System Validate System 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