摘要:

AbstractThis is the first in a series of papers documenting the author's vision for implementation of system engineering principles in the conduct of a municipal government. The author has worked in a strict system engineering environment for over 15 years. This experience has been on a variety of government programs in the aerospace field ranging from missile systems to ground based weapons and communications systems to spacecraft. He has worked with many tools and in support of many different agencies. He has been involved in the application of these principles to commercial ventures. In late 1994, he became city councilmember for a small municipality in Southern California and set out to identify what the mission is for the city government and how system engineering principles could ultimately be utilized to achieve this mission. This is a look at early observation, actions and results.

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01985.x

年代:1996

数据来源: WILEY

摘要:

AbstractMission‐directed public‐sector research facilities are experiencing increasingly severe budget environments while seeing expanding missions and responsibilities. In an effort to identify research leveraging methodologies an information search was conducted in conjunction with some efforts to find the proper links to systems engineering fundamentals. The result is an initial model for use in a pre‐concept/phase‐1 engineering design organization, with a goal of improving the organizations perf

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01986.x

年代:1996

数据来源: WILEY

摘要:

AbstractMany organizations are endeavoring to apply systems engineering (SE) to the development of commercial products. However, the challenge of doing this in a traditionally commercial organization (TCO) is very different from doing it in a traditionally government‐oriented organization (TGO). This paper provides a set of guidelines based on the experiences of the author in both types of organizations. Among the tenets espoused are the respect for the tribal knowledge of the commercial organization, the preservation of useful processes, the recognition that much SE is already practiced in the organization, the insistence on content rather than form in the SE process, the respect for traditional commercial terminology where it may apply, the importance of training, the importance of an internal “champion,” and the use of Integrated Product Development (IPD). The paper also cautions against the disease of arrogance and implores the reader to be grateful for incremental progress. Most important are the complete buy‐in from top management in the organization and the necessity to stand firm on the principles of systems engi

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01987.x

年代:1996

数据来源: WILEY

摘要:

AbstractAnalysis of the Year 2000 (Y2K) problem is a systems‐engineering job. This analysis considers the business and technical elements of the problem and produces a specification of acceptance criteria which software must meet to be deemedcentury‐compliant. This paper identifies and discusses four criteria that form the basis of any specification for century compliance. A specification for century compliance may be used both as a standard in Year 2000 program efforts and where applicable in a company's day‐to‐day b

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01988.x

年代:1996

数据来源: WILEY

摘要:

AbstractMost of us are familiar from childhood with the Uncle Remus story where Br'er Rabbit escapes being the main dinner course by imploring his captor to “Throw me in that briar patch!”. Following defense secretary Perry's initiative to move DoD toward commercial standards and best practices, many DoD systems engineers have wondered what distinguishes commercial systems engineering from traditional aerospace processes and practices. This paper describes the experiences and observations from a DoD systems engineer's transition into a pure commercial product development environment. Topics include: What is ‘commercial’ systems engineering? What practices from DoD provide the highest added value in the commercial world? What are the unique challenges to application of systems engineering in the commercial world? What lessons can DoD learn from commercial industry? And, finally, is this commercial ‘briar patch’ a viable future address for you as an aerospace‐trained sys

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01989.x

年代:1996

数据来源: WILEY

摘要:

AbstractIn the spring of 1995, the author, as Adjunct Professor of Engineering at the University of Southern California, developed a new graduate level course in risk management applied to problems in systems engineering and program management. The class project for this course was the near‐earth‐object (NEO) threat. Risk management has been one of the most recent arrivals to be recognized within systems engineering, but it is usually ad hoc and qualitative. The core of this new course established risk management on the foundation of probabilistic decision theory. For the class project, the students were asked to develop decision networks, probability assessments, and alternative criteria relating to the conduct of a planetary defense program. A good consensus was obtained: all investments for acceleration of NEO detection and characterization as well as preliminary design of mitigation systems were shown to be very cost effective, key risk reduction tests on mitigation technologies were recommended within limits, and the full deployment of actual mitigation systems should be paced by the results of the NEO detection prog

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01990.x

年代:1996

数据来源: WILEY

摘要:

AbstractThe bridge between business process and information systems reengineering is all too often missing from the roadmap of reengineering efforts. When process and system engineers get to this transition, they discover a rickety old bridge with steep terrain on either side of a wide chasm. Recognizing this dilemma, we developed the Business Reengineering for Information Technology (BRIT) approach that systematically transitions from business process to information systems engineering. BRIT is designed to handle a wide range of reengineering factors including: “best practices,” COTS applications, non‐standard business processes, and change situations ranging from continuous improvement to radical restructuring. This proven approach is described here with relevant examples of its applica

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01991.x

年代:1996

数据来源: WILEY

摘要:

AbstractThis paper examines the Internet for its worth from the viewpoint of a practicing systems engineer. Are there resources strewn across the Internet for systems engineers to discover? Have the paths to systems engineering gems on the Internet been explored? If systems engineers are not using the Internet, what are they missing? Because the very nature of the Internet makes it an “unsecure” medium of communications, does that mean that information received over the Internet is possibly not authentic?The systems engineer has special needs (not unique needs) and expectations of the Internet. This paper presents a list of the systems engineer's requirements for Internet usage and examines how the Internet satisfies most of the requirements.The examples and Internet sites presented in this paper are not inclusive. The reader is encouraged to explore the Internet, develop strategies to find information and share the findi

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01992.x

年代:1996

数据来源: WILEY

摘要:

AbstractIn an effort to radically reduce system development times and necessary resources, the Department of Defense (DoD) is emphasizing utilization of “Commercial‐Off‐The‐Shelf (COTS)” or “Non‐Developmental Items (NDI)” in the development of new systems and the upgrade of existing systems. This paper outlines a methodology, involving the integrated application of Quality Function Deployment (QFD) and Analytic Hierarchy Process (AHP), to facilitate the prerequisite analysis and evaluation before making a commitment to a COTS/NDI alternative. While this COTS/NDI analysis and evaluation methodology is generic in its applicability within the system engineering process, in its current state the model based on this process has a system supp

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01993.x

年代:1996

数据来源: WILEY

摘要:

AbstractThe nuclear waste management community has opted to use process flows to depict the activities and goals necessary to meet the enormous challenge of nuclear/chemical waste environmental clean‐up. The process flow methodology leads to decomposition of functions much the same as functional flows; however, the methodology to ensure integration of the processes differs from standard Department of Defense (DOD) systems engineering. Examples of other functions necessary to complete the life cycle of the system are described, including the rationale for potential inclusion into the FRAT method. The discussion that follows is a comparison of process flows and functional flows with examples of each method. Recommended changes to the systems engineering environment in an M&O program follow the discussion of method

ISSN:2334-5837    

DOI:10.1002/j.2334-5837.1996.tb01994.x

年代:1996

数据来源: WILEY