Premium
4.4.2 The Mission Analysis Discipline: Bringing focus to the fuzziness about Attaining Good Architectures
Author(s) -
Shupp Jeffrey K.
Publication year - 2003
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.2003.tb02644.x
Subject(s) - focus (optics) , architecture , process (computing) , computer science , work (physics) , space (punctuation) , software engineering , systems engineering , process management , engineering , engineering management , geography , mechanical engineering , physics , archaeology , optics , operating system
Abstract The systems and software engineering communities have experienced a veritable explosion of activity surrounding architectures and their role in developing complex systems. This activity has moved forward on two fundamental fronts: the ability to document an architecture, and the ability to evaluate one. Both of these themes have as their foundation the need for well articulated requirements. The architecture is the highest level design of a system, and as such is a response to the requirements. This paper addresses a third, largely overlooked, segment of the early systems development cycle called Mission Analysis, and the focus on the solution trade space through the generation of Technical Business Strategies. Making this topic a recognized discipline in its own right will help to focus early system development work in a way that hopefully makes the overall process less reliant on super system architects to produce good solutions for the long run.