Showing papers on "System of systems engineering published in 1994"
01 Jan 1994
TL;DR: R reverse engineering technology developed as part of the Rigi project is presented, concerned with the analysis of existing software systems to make them more understandable for maintenance, re-engineering, and evolution purposes.
Abstract: Software engineering research has focused primarily on software construction, neglecting software maintenance and evolution. Observed is a shift in research from synthesis to analysis. The process of reverse engineering is introduced as an aid in program understanding. This process is concerned with the analysis of existing software systems to make them more understandable for maintenance, re-engineering, and evolution purposes. Presented is reverse engineering technology developed as part of the Rigi project. The Rigi approach involves the identi cation of software artifacts in the subject system and the aggregation of these artifacts to form more abstract system representations. Early industrial experience has shown that software engineers using Rigi can quickly build mental models from the discovered abstractions that are compatible with the mental models formed by the maintainers of the underlying software.
125 citations
TL;DR: A framework currently being used to reverse engineer selected legacy information systems in DoD's heterogeneous environment, developed to recover organizational business rules, business domain information, system functional requirements, functional dependencies, and system data architectures, is reported on.
Abstract: As with most large organizations, the Department of Defense has both strategic and economic needs to capitalize on and to consolidate existing information systems. This paper reports on a framework currently being used to reverse engineer selected legacy information systems in DoD's heterogeneous environment. This generic approach was developed to recover organizational business rules, business domain information, system functional requirements, functional dependencies, and system data architectures, largely in the form of normalized logical data models. We are applying the approach as a series of pilot studies on systems ranging from those using home grown languages and database management systems developed during the late 1960's to those using high order languages and commercial network database management systems. These pilot studies are being used to validate and refine the framework with real-life systems; to develop a baseline approach for reverse engineering DoD legacy information systems; and to scope and estimate future system re-engineering costs. Furthermore, the results of these projects will help to determine the economic viability of re-engineering, reverse, and forward engineering efforts for these legacy systems.
69 citations
TL;DR: A multidisciplinary framework for curricula planning in systems engineering is described and any formal program for such training should consist of the following five chapters: basic studies, disciplinary studies, specific systems, systems engineering concepts and tools, and, (5) management studies.
Abstract: Systems engineering is a multidisciplinary function dedicated to controlling design so that all elements are integrated to provide an optimum, overall system/spl minus/as contrasted with the integration of optimized sub-elements. A systems engineer is a person who is capable of integrating knowledge from different disciplines and seeing problems with a "holistic view" by applying the "systems approach." Since no complex system is created by a single person, systems engineering is strongly linked to management. The question addressed in this paper is how can knowledge and skills in systems engineering management be developed through a formal training program. We describe a multidisciplinary framework for curricula planning in systems engineering and suggest that any formal program for such training should consist of the following five chapters: (1) basic studies, (2) disciplinary studies, (3) specific systems, (4) systems engineering concepts and tools, and, (5) management studies. We also advise that any multidisciplinary program of this nature should be established as a cooperative effort of an engineering school and a management school. >
44 citations
24 May 1994
TL;DR: The report addresses the need for an ECBS discipline, identifies current practice and needed research, and suggests improvements that are achievable today.
Abstract: Advances in microprocessor and network technology have led to the proliferation of complex systems with distributed processing and databases, internal communication systems, and heterogeneous components. The processing components can by themselves comprise a system, or they can be embedded in a physical system such as an automobile aircraft, or medical diagnostic system. Both the encompassing system and the processing system are known as computer-based systems (CBSs). Developing large computer-based systems with complex dynamics and component interdependencies requires analysis of critical end-to-end processing flows to determine feasibility and proper allocation. Currently, no engineering discipline provides the knowledge base for the necessary trade-off studies concerning software, hardware and communication components; a new discipline is needed at the systems engineering level. The paper defines the need for a discipline devoted to engineering of computer based systems, identifies current practice and needed research, and suggests improvements that are achievable today. >
44 citations
TL;DR: The author examines two widely held beliefs: requirements describe a system's "what", not its "how" and requirements must be represented as abstractions.
Abstract: Requirements engineering is likely to be a major issue in this decade. The author examines two widely held beliefs: requirements describe a system's "what", not its "how". Requirements must be represented as abstractions. >
40 citations
Book•
01 Mar 1994
TL;DR: A brief history of industrial engineering production systems design production systems control management total quality management productivity operations research systems the future can be found in this paper. But the focus of this paper is on the future.
Abstract: A brief history of industrial engineering production systems design production systems control management total quality management productivity operations research systems the future.
25 citations
01 Jul 1994
TL;DR: The need for defining human factors and human-computer interaction engineering activities that contribute to the design, development, and evaluation of usable and useful interactive systems is identified and a rationale for integrating these activities with software engineering and incorporating them into the system life cycle is presented.
Abstract: Engineering processes and methodologies used in building tomorrow''s systems must place a greater emphasis on designing usable systems that meet the needs of the systems'' users and their tasks. This paper identifies the need for defining human factors and human-computer interaction (HCI) engineering activities that contribute to the design, development, and evaluation of usable and useful interactive systems, and presents a rationale for integrating these activities with software engineering and incorporating them into the system life cycle.
23 citations
TL;DR: An original design for a process model is presented which is considered to be capable of unifying the systems engineering function with project management activities and makes use of a graphical technique for the representation of natural language expressions, known as the systemigram.
Abstract: This article presents an original design for a process model which is considered to be capable of unifying the systems engineering function with project management activities. This design has been developed using an original soft systems methodology which is based on a unique conceptual modelling system for requirements specification. This makes use of a graphical technique for the representation of natural language expressions, known as the systemigram. Systemigrams provide a generic means of enabling systems engineers and project managers to obtain a more enlightened understanding of their problematique.
22 citations
24 May 1994
TL;DR: This paper attempts to reconcile and extend two information models that have been developed independently to describe information capture in systems engineering activities to provide a basis for integrated tools that support the several methodologies.
Abstract: This paper attempts to reconcile and extend two information models that have been developed independently to describe information capture in systems engineering activities. An internationally accepted information model is a major step toward understanding different methodologies in use in different organizations. It can provide a basis for integration of tools that support the several methodologies. The information model describes the static structure of the information used in the systems engineering steps. The information model is structured so that it maps readily to a process model which describes systems engineering behavior: the engineering steps, input and output of the steps, and the sequences, concurrencies, and branches among the steps. >
19 citations
20 Sep 1994
17 citations
TL;DR: The author describes how the key to this process is translating a customer's need into a set of specifications that drive the system's design.
Abstract: "Do it right first time" is the slogan of systems engineering. The approach can benefit all types of development projects, from smaller commercial products to large government projects, because the objective is the same: to design a high-quality product as fast and efficiently as possible. The author describes how the key to this process is translating a customer's need into a set of specifications that drive the system's design. >
AT&T1
TL;DR: In this paper, the authors explore the relationship between process and tools for systems engineering, and propose a paradigm for understanding the PMTE elements for system engineering, which can cover the gaps in a project SE Management Plan (SEMP).
Abstract: This paper explores the relationship between process and tools for systems engineering. There is much interest now in process maturity, yet there are many cases of processes being developed and deployed with little effect on the bottom line. In fact, there are times when the overall health of the engineering organization is not improved with the use of standardized processes and tools.
It is important to have a proper balance among process, methods, tools, and environment (PMTE) when performing systems engineering (SE) tasks. An improper balance leads to increased costs and lower quality, in addition to frustration for engineers and for management. The particular PMTE elements appropriate for a project should be defined and documented in an SE Development Environment (SEDE) Plan which can cover the gaps in a project SE Management Plan (SEMP). This paper proposes a paradigm for understanding the PMTE elements for systems engineering.
Book•
22 May 1994
TL;DR: Systems, Scientific Principles, and Computers: Introduction and Overview, Systems, Elements, and Units, and Mathematical Modeling Fundamentals.
Abstract: Systems, Scientific Principles, and Computers: Introduction and Overview. Systems, Elements, and Units. Mathematical Modeling Fundamentals. Idealization and Simplification. First and Second Order Systems. Systems Analogies and Equations, Mathematical Methods. Computer Methods and Programming Languages. Control Systems. Transient and Frequency Analyses. Simulation Techniques and Methodologies: Computer Simulation Analysis. Machinery Systems. Machine Systems. Machine-Soil Systems. Human-Body Systems. Biological Servosystems. Man-Machine Systems. Operational Systems. Simulation Techniques and Applications: Soil-Water-Environmental Systems. Plant Systems. Soil-Plant-Environment Systems. Greenhouse-Structure-Environment Systems. Drying/Curing-Structure-Environment Systems. Structure-Environment-Biological Systems. Machine-Ecological Systems. Biophysical Controls Systems. Index.
01 Jan 1994
TL;DR: This paper presents a meta-annotation-based meta-modelling framework that automates the very labor-intensive and therefore time-heavy and expensive and expensive process of manually annotating semantic annotations.
Abstract: ing Modelling Languages: A Reutilization Approach . . . . . . . . . . 127 Juan de Lara, Esther Guerra, and Jesús Sánchez-Cuadrado Logical Invalidations of Semantic Annotations . . . . . . . . . . . . . . . . . . . . . . . 144 Julius Köpke and Johann Eder XIV Table of
TL;DR: Concurrent engineering can reduce the lead time and cost of developing, and improve the quality of, new or modified products as mentioned in this paper. But, to achieve these benefits, design, engineering, and manufacturing knowl...
Abstract: Concurrent engineering can reduce the lead time and cost of developing, and improve the quality of, new or modified products. To achieve these benefits, design, engineering, and manufacturing knowl...
Dissertation•
01 Jan 1994
TL;DR: This survey paper presents a thorough description of fundamentals of engineering based expert systems and their knowledge representation techniques.
Abstract: This survey paper presents a thorough description of fundamentals of engineering based expert systems and their knowledge representation techniques. The most important expert system development tools and existing operational expert systems in many different engineering domains are also presented.
01 Aug 1994
TL;DR: The joining of systems engineering with object technology provides a seamless engineering path for projects which will implement software in an object-oriented fashion and integration with existing methodologies is straight forward.
Abstract: This paper extends Systems Engineering methods to include object technology, which has been developing in modern software engineering, (Rumbaugh et. al. 1991). It applies the principles of Model Based Systems Engineering, MBSE, (Oliver 1993a), (Oliver 1993b) to the systems engineering process itself. This results in a layered process description which is tailorable and supports aerospace or commercial methodologies.
Multiple phases of engineering - concept phase, requirements analysis phase, and systems architecture and design phase - are supported with a single core set of engineering steps. The additions of semantics and notations from object technology provides a capability to describe the choices of components and the mapping of behavior to components that lead to alternative architectures. Strong emphasis is placed on the systems engineering traditions of trade-off analysis and sequential build and test which have been weak in software engineering methodologies.
The joining of systems engineering with object technology provides a seamless engineering path for projects which will implement software in an object-oriented fashion. Integration with existing methodologies is straight forward because existing methodologies can be defined by selecting among the core MBSE steps.
TL;DR: In the new degree, which is derived from the telecommunications stream in electrical engineering and from computer systems engineering, students will receive a comprehensive education ranging from a one and one-half gear common core to communications theory, design and practice with consideration of economic, regulatory, and social issues with a strong background in real-time computer systems.
Abstract: Communications engineering, a new undergraduate degree program, is being introduced in the Department of Systems and Computer Engineering at Carleton University in Ottawa, Canada. At a time when increased specialization is questionable, the case is made that communications engineering, i.e., telecommunications and computers, is such a broad and fundamental area that a distinct degree is an appropriate approach to meet the requirements for engineering in this area. The objectives of the new program and the role that its graduates will play are discussed. The curriculum proposed for the new degree is presented. In the new degree, which is derived from the telecommunications stream in electrical engineering and from computer systems engineering, students will receive a comprehensive education ranging from a one and one-half gear common core, to communications theory, design and practice, with consideration of economic, regulatory, and social issues with a strong background in real-time computer systems. Graduates will participate in the engineering of a variety of private and public telecommunications systems, and be at home in many related areas of information technology and signal processing. >
16 May 1994
TL;DR: SOOSA/SOD is a coherent development methodology for computer-based systems developed by IMA at the University of Karlsruhe, Germany based on strong system theoretic principles that defines clear interfaces to the encompassing engineering process.
Abstract: Systemobject-Oriented Structured Analysis and Service-Oriented Design (SOOSA/SOD) is a coherent development methodology for computer-based systems developed by IMA at the University of Karlsruhe, Germany. It is based on strong system theoretic principles and is formal in a way that allows for execution of the specifications by simulation and partially automated implementation. It defines clear interfaces to the encompassing engineering process by covering all the engineering steps of an underlying tailorable engineering process model. Both, the development methodology and the process are supported by prototype tools forming an integrated computer-based systems engineering environment.
02 Oct 1994
TL;DR: An explicit process for designing a unified system of systems (S2) is defined, based upon previous system of system notions as well as combinatoric functional analysis, and the features of a prototype software system known as EGADS are presented.
Abstract: An explicit process for designing a unified system of systems (S2) is defined, based upon previous system of systems notions as well as combinatoric functional analysis. The vagaries of selecting a set of compatible systems that upgrade and improve the functionality of a given system of systems are explored. Incompatible systems are screened out and a variety of system "views" place in evidence how well the candidate unified systems are apt to satisfy requirements. Generalizations and computer support of the process are discussed. The features of a prototype software system known as EGADS are presented. This decision support system (DSS) can assist the user in developing the overall architecture for a unified system of systems. >
01 Jan 1994
TL;DR: The world market is clearly changing, with a demand for increased customization, faster delivery and higher quality products without losing control of costs.
Abstract: The world market is clearly changing The outdated view of ‘do you want it fast or do you want is right?’ has been replaced by a demand for increased customization, faster delivery and higher quality products without losing control of costs
24 May 1994
TL;DR: The paper describes the need for the establishment of new engineering discipline the Engineering of Computer Based Systems (ECBS), the scope of CBS and their context, the context of their engineering, standardization issues of CBS representations, engineering ofCBS and its relation to software engineering, and required education and training.
Abstract: Modern computer-based systems (CBS) are complex multi-systems connected by complex computer-based communications. Each of the systems is in many cases, also a multicomputer system. The systems in a multisystem can be either geographically distributed or locally connected. Typical examples of CBS are; telephone and communications systems, management information systems (MIS), process control and manufacturing automation systems, space systems, transport systems (car, train, and traffic control), medical instruments, automation systems, and commercial electronics. The paper describes the need for the establishment of new engineering discipline the Engineering of Computer Based Systems (ECBS), the scope of CBS and their context, the context of their engineering, standardization issues of CBS representations, engineering of CBS and its relation to software engineering, and required education and training. >
01 Aug 1994
TL;DR: The New Generation Education (NGE) project as mentioned in this paper is a systems engineering project to simultaneously redesign and evolve education and the unique balances this project requires within the processes and procedures of systems engineering can do much to teach us how to tailor our profession to other emerging applications.
Abstract: There are many alternative areas where the benefits of systems engineering can be applied. One of the premier emerging areas of structured design today is in the design or redesign of social systems. The redesign of the education system, as a social system, is a prime candidate for the application of systems engineering. New Generation Education (NGE) is a systems engineering project to simultaneously redesign and evolve education. The unique balances this project requires within the processes and procedures of systems engineering can do much to teach us how to tailor our profession to other emerging applications.
02 Nov 1994
TL;DR: In this paper, a discussion of the system engineering process is presented based on the assumption that it would be applied by a system operator who is also the system design and integration authority.
Abstract: Systems engineering was developed in order to address the complexity of projects. Such complexity usually arises when projects are multidisciplinary in terms of the technologies required for their achievement and involve practical difficulties in their definition. The discussion of the systems engineering process in the paper is based on the assumption that it would be applied by a system operator who is also the system design and integration authority. >
01 Aug 1994
TL;DR: A draft classification of tools is provided that may be useful to systems engineers in understanding tool choices for the automation of their work and establishes the interfaces between tool types.
Abstract: The goal of this paper is to provide a draft classification of tools that may be useful to systems engineers in understanding tool choices for the automation of their work. An accepted classification will require input from NCOSE members and modification of the draft.
The tools automate the systems engineering process. Each kind of tool performs particular functions and captures particular sets of information. In this paper the tools are mapped to a meta-model for the systems engineering process. That meta-model describes the core systems engineering steps and gives an information model for each step. Mapping the tools to the meta-model defines the functions performed by each tool type and the information it captures. The mapping also establishes the interfaces between tool types.
24 Feb 1994
TL;DR: This paper identifies four problems that must be addressed to improve the quality of teaching a software engineering course that mirrors the real world and identifies the pedagogical implications of these problems.
Abstract: We identify four problems that must be addressed to improve the quality of teaching a software engineering course that mirrors the real world: We have to start teaching iterative and incremental design, we need to introduce students to the problems of negotiation, co-ordination and team-work, we have to leam how to re-use large com plex systems across project courses and we must overcome the inadequacy of tradi tional means of dissemination ofcourse materials. We identify the pedagogical implications of these problems that have to be addressed before we can hope to improve software engineering education. The ideas presented in this paper are cur rently investigated in the framework of a senior undergraduate course at Camegie Mellon University.
Journal Article•
11 Oct 1994
TL;DR: In this paper, the different perspectives of what systems engineering means to different people are shown, and different process models developed over time for systems engineering are then presented, and future trends in system engineering are highlighted.
Abstract: An introduction to systems engineering is given. The different perspectives of what systems engineering means to different people are shown. The different process models developed over time for systems engineering are then presented. Certain fundamentals of the systems engineering approach are listed and discussed. Finally, future trends in systems engineering are highlighted.
14 Sep 1994
TL;DR: This paper presents the computer-based environment MUSE-SEPIA, a combination of features that fulfils a broad range of requirements found in the analysis of the application domain and Hypermedia functionality enables the system to represent the required multitude of information units and their interrelations.
Abstract: In this paper we present the computer-based environment MUSE-SEPIA for the modelling and validation of complex technical systems. It provides specific views on the representation of the technical system. They act as filters showing information that is relevant to the tasks of the designers and the validators. Hypermedia functionality enables our system to represent the required multitude of information units and their interrelations, the integration of different media, and the integration of powerful external applications. CSCW techniques are employed to support the collaboration between designers and validators. This combination of features fulfils a broad range of requirements found in the analysis of the application domain.