17.2 Residential Security Example Overview 437 data, and procedures (refer to Section 17.3.5). The Optimize and Evaluate Alternatives activity is invoked throughout the process to perform engineering analysis that supports system design trade studies and design optimization (refer to Section 17.3.6.). The Manage Requirements Traceability activity is used to manage traceability from the mission-level requirements to the component requirements (refer to Section 17.3.7). Each of these activities is further elaborated by applying this method to the residential security example in the rest of the chapter. Note that the simplified MBSE method in Chapter 3, Section 3.4, does not include the logical architecture design activity, and only includes a subset of the other activities. The level of detail of the process documentation is tailored according to organizational and project needs. The documentation can be further elaborated to describe the detailed process description for creating each modeling artifact, such as a use case. In addition, the process flows can be further refined to reflect the design iterations and the flow of inputs and outputs. This level of detail is not included in any of the process flows in this example to simplify the process description. The process can be documented in a process modeling and/or process authoring tool and published to a web environment. This approach facilitates maintenance and tailoring of the process, and use of the process information. In the example below, the process model is contained in package called OOSEM Process.