Process definition for capturing legacy system requirements

0Citations
Citations of this article
3Readers
Mendeley users who have this article in their library.
Get full text

Abstract

An engineering process that addressed mining prototype systems for production rehost on a commercial-off-the-shelf (COTS) based architecture was defined to guide the development of an expanded system that provides aircraft pilots with improved geographical positioning information. This paper describes the re-engineering process, including the activities and associated tasks, to develop the geolocation system. The process is based on TRW's system and software engineering process assets. The process description includes a discussion of the engineering activities and the principal system engineering processes used to direct the work effort: (1) system analysis and design, which includes both the requirements definition and analysis to establish the scope of the product, and critical item prototyping and design to extract the applications and define the architecture and infrastructure; (2) implementation, which establishes the infrastructure and provides the baseline for the application development; (3) testing and evaluation; and (4) transition activities, which prepare the system for full operational status. The process was defined to guide the system implementation; the work was part of a concurrent engineering effort.

Cite

CITATION STYLE

APA

Markel, S. D. (1997). Process definition for capturing legacy system requirements. In IEEE Aerospace Applications Conference Proceedings (Vol. 4, pp. 401–410). https://doi.org/10.1109/aero.1997.577523

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free