摘要:

AbstractThis paper stresses the importance of the System Engineering (SE) process in the contractor funded R&D phase of a project. This practice, first, permits major decisions to be made before extensive resources are committed to hardware and software designs. Secondly, it directs R&D efforts for following years. Finally, it saves money by concentrating on technical content rather than formal documentation. Examples are shown for the McDonnell Douglas Aerospace funded Lunar Base Reference Design study. Sample formats are shown for simplified documentation. The process is called First‐Order Systems Engineering (FOSE

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01560.x

年代:1993

数据来源: WILEY

摘要:

AbstractOne of the goals of the original system engineering process defined in the Fort Belvoir Defense System Management College, System Engineering Management Guide and Army Field Manual 770–78 is to minimize changes during the system development process. With the rapid increase in the rate of technological change as well as the increase in the duration of major system development projects, this inability to accommodate change causes performance, cost and schedule problems. To address this need for change the author has developed a Dynamic System Engineering (DSE) Process that expands the bounds of the existing process to focus more attention on the front end of the system development proces

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01561.x

年代:1993

数据来源: WILEY

摘要:

AbstractEvery progressive corporation has a set of process mechanisms in place for accomplishing its business ends. In the engineering industry most elements of these process mechanisms remain manually intensive. However, just as mechanization transformed manufacturing, so too will mechanization of manually intensive tasks advance the state of engineering. This paper will focus on the new area of process enactment technology. Process enactment, which we view asmechanized mechanisms, is the automation of those time and resource consuming elements of a process that do not require the unique capabilities of the human intellect. Process enactment technology automates task management and support for the team, and controls schedule, team member tasks and interaction, and the movement, storage, and processing of all data.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01562.x

年代:1993

数据来源: WILEY

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01671.x

年代:1993

数据来源: WILEY

摘要:

AbstractThe conceptual and theoretical basis of systems engineering and project management are still in their early days. For example, almost all literature written in recent years in these areas tend to assume that all projects are fundamentally similar and their management consists of a universal set of functions and activities. Systems engineering books usually describe a system's lifecycle (phases) and typical systems engineering process activities along these phases. In practice however, there are salient differences among systems according to size, industry, customer type, contractor's organization, level of technology and other parameters.Based on an exploratory, on‐going field study we suggest in this paper a conceptual, two dimensional framework for the classification of projects and systems and show how this framework can be used to distinguish among systems engineering styles and practices for various types of engineering projects. Projects are classified according to their level of technological uncertainty at the moment of project initiation and their system scope which is their location on a hierarchy of systems and subsystems. The technological uncertainty dimension is divided into: low‐tech, medium‐tech, high‐tech, and, super high‐tech projects. System scope is divided into: assembly, system and array projects. Considerable differences were found among systems engineering methods along each one of the model's axes. Differences were also observed for a simultaneous change in both d

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01563.x

年代:1993

数据来源: WILEY

摘要:

AbstractThe NASA Systems Engineering Process Improvement Team (SEPIT) has developed a NASA generic life cycle model of systems engineering and technical activities, to serve as a template in the development of project specific life cycles. The life cycle model is built around engineering process flow diagrams and includes descriptions of the objectives, processes, and products for each phase of the life cycle from initial customer needs and objectives to operation and finally, disposal of the system. The Life Cycle Model serves as a framework for the understanding and use of the other SEPIT products. The closely related Control Gates Standard is also described in some detail. This document describes the reviews that are used to assess progress and readiness for transitions in the project activities. After appropriate review and approval, the life cycle and the other products will serve as reference standards and/or guidance for use in the development of program and project plans.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01564.x

年代:1993

数据来源: WILEY

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01672.x

年代:1993

数据来源: WILEY

摘要:

AbstractThis paper applies the principles of Model Based Systems Engineering,(Oliver 1992a), (Oliver 1992b), to the systems engineering process itself. This results in layering the process description so that it is tailorable and supports aerospace or commercial methodologies. A core set of engineering steps is defined using a behavioral or conceptual model. Existing methodologies can be described and compared by selecting the core steps they use and the sequences, concurrencies, and iterations of the core steps selected.An information model, design model, is defined for each core step. From these models the possible representations of information are listed for each core engineering step. The graphic or text representations of existing methodologies can be mapped onto the information models to compare methodologies or to examine a methodology for redundancy or completeness. The design models are a basis for an information standard or a meta‐model for information exchange among tools, or for the selection of tools or notatio

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01565.x

年代:1993

数据来源: WILEY

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01673.x

年代:1993

数据来源: WILEY

摘要:

AbstractThroughout AT&T Federal Systems Advanced Technologies (FSAT), many systems engineering processes were used by the various organizations, making it difficult to compare measures of effectiveness for each project's process. About one year ago, FSAT management chartered a Process Management Team (PMT) to develop a standard Systems Engineering process for FSAT. After one year, the PMT issued a generic Systems Engineering process document that will be used by all projects within FSAT. The process can be tailored to either commercial or government contracts and conforms to MIL‐STD‐499B. The standard process has been modeled in a computer‐aided engineering tool and is available to new projects on a computer disc. To support the process, special courses were developed to teach process fundamentals and give projects ajump‐start. In addition, a metrics program has been established that monitors and provides feedback to all projects using the standard or tailored

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1993.tb01566.x

年代:1993

数据来源: WILEY