An Assessment of the Advanced Weather Interactive Processing System Operational Test and Evaluation of the First System Build (1997) / Chapter Skim
Currently Skimming:
3 SYSTEMS ENGINEERING
3 SYSTEMS ENGINEERING
Pages 19-28
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 19... ...
The responsibilities of the systems engineer include compositing requirements, developing a system architecture, allocating requirements to subsystems and elements, identifying and managing performance and resource margins, and tracking the development process to evaluate results. Throughout the system life cycle, the systems engineer anticipates, recognizes, and solves problems to ensure that the system continues to fulfill requirements within project resources.
|
From page 20... ...
Continue testing incremental implementations (builds) to ensure that subsystems still meet their requirements; revise model and test mechanisms as required by redesign decisions, changes in system or subsystem requirements, or risk analyses that impact model assumptions; perform baseline regression testing.
|
From page 21... ...
, links to the NOAA National Centers for Environmental Prediction (for forecast model data) , and the National Environmental Satellite, Data, and Information Service (for weather satellite data)
|
From page 22... ...
CURRENT SYSTEMS ENGINEERING STRUCTURE Figure 3-1 summarizes the current systems engineering structure for AWIPS, along with organizational reporting and relevant functional flows.1 The key organizational components of systems engineering for AWIPS are the systems engineering team, which is shown in the center of the diagram, and the systems engineering component of the contractor hierarchy, which is indicated by the flow of information from subcontractors through the prime contractor' s director of engineering to the AWIPS acquisition manager. This complex organization may limit the NWS's ability to perform essential systems engineering functions.
|
From page 23... ...
"Prime contractor formally reports to acquisition manager but takes technical direction from AWIPS technical manager. hSubcontractors provide hardware; design, install, and maintain hardware systems; and provide other technical support to prime contractor.
|
From page 24... ...
Subsystem engineering responsibility and authority should coincide with functional subsystems. Integrating the Prime Contractor's Systems Engineering Component NWSM Committee members and advisors who have observed AWIPS development operations over the past several years report that systems engineering capability on the part of the prime contractor has improved greatly.
|
From page 25... ...
The AWIPS contractor's systems engineer should be formally and directly included on the AWIPS engineering team, and the contractor's systems engineering processes should be included in the overall AWIPS systems engineering functions. LOCALLY DEVELOPED CODE The AWIPS requirements were designed to include the capability of NWS field staff to write their own application software to run on AWIPS workstations.
|
From page 26... ...
Third, locally developed code presents special requirements for configuration management. Each site that supports local development must have a development environment separate from the AWIPS operating environment, just as the AWIPS software developers shown in Figure 3-1 must work in a development environment distinct from the operational AWIPS accessed by users.
|
From page 27... ...
A proven mechanism for transferring ownership of FSL-developed code to OSD (or to another AWIPS player) must be established as soon as possible for the FOA code and for additional AWIPS software modules.
|
From page 28... ...
Recommendation. Under the leadership of the AWIPS project systems engineer, AWIPS management should establish a process for transferring responsibility for, and the detailed knowledge of, software elements from the developing organization to the deploying organization and subsequently to the operating organization.
|
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.