Premium
MONITORING THE DEFINITION AND DEVELOPMENT PROCESS OF LARGE SOFTWARE SYSTEMS
Author(s) -
Kaslow David E.,
Shupp Jeffrey K.
Publication year - 1996
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1996.tb02067.x
Subject(s) - key (lock) , computer science , functional requirement , systems engineering , consistency (knowledge bases) , requirements analysis , software engineering , process (computing) , non functional requirement , system requirements , development (topology) , software design , software , systems design , software development , software system , software construction , engineering , programming language , artificial intelligence , computer security , mathematics , mathematical analysis , operating system
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.