Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 1
    I don't understand the "refine" relationship between the Level 0 and Level 1. Perhaps it's because I don't understand what "Level 0" and "Level 1" are. In my experience, I would call Level 0 "System" and Level 1 (and lower) would be "Subsystem" or "Component". The relationship would not necessarily be "refine", but requirement would be allocated to subsystems or components and have various types of decomposition and refinement performed. Commented Aug 14, 2024 at 15:55
  • yeah, you need to put your level 0 etc in the context of some system of architecture planning for it to make sense. Level 1 requirements? Commented Aug 14, 2024 at 17:32
  • @ThomasOwens, If it works for your understanding, you can map Level 0 and Level 1 respectively to System and Subsystem/Component. The numbered levels start to get an advantage when you are building a system-of-systems and there are three or four levels of requirements before you can even start to make the distinction between hardware and software requirements. Commented Aug 15, 2024 at 7:08
  • You could have a look at MIL-STD-498 or its successors. The essence of this methodology is that requirements at level n are developped into a design at level n + 1 (which contains more than just an architecture model) for which requirements can be written at level n + 2, etc. This was once considered best practice. Commented Aug 15, 2024 at 12:08
  • 1
    @ThomasOwens as mentioned by Bart van Ingen Schenau, the levels are generically represented because we have at least 10 levels, since the system is big enough and has mechanics, electronics, SW, FPGA and so on. The "refine" relationship is just because it comes from SysUML (Enterprise Architecture) but it normally should be the relationship of "decomposes to" Commented Aug 19, 2024 at 7:15