MONITORING THE DEFINITION AND DEVELOPMENT PROCESS OF LARGE SOFTWARE SYSTEMS
David Kaslow, Jeffrey K. Shupp · INCOSE International Symposium · 1996
Abstract In developing large software systems, systems engineers too often pay more attention to the allocation of the mission functional requirements based on system specifications and less to operator based or design requirements derived from design concepts. However, the success of any large system development lies with the maturation of these design concepts and requirements. Of special importance are the concepts covering requirements key to satisfying the mission objective, or the concepts which span functional components, made up of hardware and software configuration items (CIs) and manual operations, within the system. This paper discusses a criteria which, when applied to a given design concept, identifies the concept as key. Key concepts must be identified early, analyzed thoroughly, and checked for consistency with the requirements that drive them throughout the definition and development process. If the proper level of analysis and design is performed against these concepts, the system will have a minimum number of issues to resolve as it approaches operational status.