These are my notes from reading some books, and I find these as important concepts that should always have attention focused on them.
1- Never forget that the system being addressed by one group of engineers is the subsystem of another group and the supersystem of yet a third group. ( elevating the idea of Enterprise Systems)
2- System Engineers must identify the stakeholders needs throughout the system's lifecylce and define objects in the triad of cost, schedule, and performance ---- cheaper, faster, and better.
3- Design during the engineering of a system is the preliminary activity that has the purpose of satisfying the stakeholders requirements, and begins in the mind of the system engineer, and has to be transformed into models employing visual formats in a highly skilled manner for success to be achieved.
4- One of the legends of Systems Engineering to me could be Joe Shea, his involvement in large scale projects, definition of Systems Engineering, dedication shown by working three shifts, SE fashion icon by wearing red socks, and finally nervous breakdown for overworking himself ( duuhh!!!), but we salute him for his hard work.
5- Requirement vs Specification: Specification is a collection of requirements that completely define the constraints and performance requirements for a specific physical entity that is part of the system.
6- Design Decomposition of Architectures and Specs:
Operational Req
Sys Op Arch (Segment specs)
Segment Operational Arch (element spec)
Element Operational Architecture ( Component Specs)
Component Operational Architecture ( CI specs)
7- Originating Requirements are found in Operational needs, or operational requirements Document, (ORD), and the restatement and derivation of the system requirements becomes System Requirement Document (SRD).