Skip to main content

Currently Skimming:


Pages 9-14

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 9...
... 9   S E C T I O N 2 is section describes the proposed system that results from the desired changes or user needs specied in the model ConOps. It describes the proposed system in a high-level manner, indicating the operational features that are to be provided without specifying design details.
From page 10...
... 10 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors e proposed system (see Figure 3) builds on the capabilities described in Section 2.3.
From page 11...
... General System Description 11   M o d e D efinitio n Mode 1: Normal Operating Conditions Indicates that all key systems and equipment are operating correctly. Some secondary systems and equipment may be partially or fully non- operational due to a localiz ed failure or scheduled maintenance; however, overall operations and management of the system are not significantly impacted, and remediation actions are already in place ( e.g., maintenance personnel were notified)
From page 12...
... 12 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors • Connected Vehicle Roadside Equipment is anticipated to be only sparsely located along rural corridors. • Connected Vehicle Roadside Equipment is provisioned to send and receive messages to facilitate information receipt and dissemination.
From page 13...
... General System Description 13   2.6 Actor Characteristics is section denes the actors of the system and the roles and responsibilities of each of the users of the system. Table 2 is an example based on the proposed system context diagram (Figure 2)
From page 14...
... 14 Initiating the Systems Engineering Process for Rural Connected Vehicle Corridors • e role of expert sta within the agency on developing forecasts or operational strategies by segment based on the new information produced by the proposed system • Cost-eective real-time monitoring of key assets across the deployment area to support the proposed system 2.8 Operational Scenarios (or Use Cases) e operational scenarios (also called use cases)

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.