To assist all stakeholders in a system engineering effort, the structure must support dependency relations and also be easily understood . For example, the problem manager makes sure that the same problem is not solved several times. The principle with concurrent processes and successive releases supports such cooperation. For complex systems a requirements specification cannot be fixed from the beginning, although writing one is a worthwhile effort. Tofs supports a dialogue that includes not only requirements , but also stated missions , problem management and an understandable formal description of the system's structure and behavior.
Requirements management is managed as a process in parallel with processes for development and test.
Working this way, reduces the risk of unrealistic requirements and also the risk of a never-ending project. Understanding a system's missions is important to get the requirements right . Integrating the missions in the object structure, makes it easier to get the right set of requirements and test cases to build the right system on schedule and within budget. These can be used as part of the requirements specification for implementation work. Tofs supports splitting of development work for large complex systems into well-defined areas suitable for a single developer or a small group of developers.