System Fundamentals as Facilitating CubeSat Development Marcus Bever EagleSat Systems Engineer Embry-Riddle Aeronautical University

Presentation Outline The value of systems engineering Relating the elements of design Communication o Model Based Systems Engineering (MBSE) o Hierarchy diagrams o Functional flow block diagrams Tailoring Conclusion

Why Make the Effort Requirement verification o Meet the goal Design traceability o Answer the question of “Why?” Design update compatibility o Manage flow down of modifications System level documentation o Communicate the big picture without missing the details

What’s the Focus? Top down design Design triangle o Requirements: what is being done o Functions: how is it being accomplished o Hardware: what is accomplishing it Iterative and recursive application

C OMMUNICATION Words

Model Based Systems Engineering Communication through diagrams o Represents traceability graphically o Clearly shows interrelationships o Maintains organization through numbering Includes clarifying descriptions Satellite = Sat +Light

Hierarchies: Tool of Systems Thinking Clear representation of requirement, function, and hardware breakdown Numbering Relationship Classification Title

Functional Flow Block Diagrams Functional model of operations, sequencing, and conditions Numbering Project Operational Flow Title

Tailoring Not every document is suited for every project Tools vary with resources and program o Website development Website development o Tailored documentation o Meetings Support team in satellite development o Various tools  selection of most appropriate

Conclusion Communicate o MBSE: hierarchies, functional flow black diagrams o Choosing the right tool Coordinate o Traceability and documentation o Don’t miss the details! Collaborate o Support the technical progress of the satellite

Questions Marcus Bever Embry-Riddle EagleSat