Showing papers on "System of systems engineering published in 1997"

Classification of research efforts in requirements engineering

Abstract: Requirements engineering is the branch of software engineering concerned with the real-world goals for, functions of, and constraints on software systems. It is also concerned with the relationship of these factors to precise specifications of software behavior, and to their evolution over time and across software families. Of all the areas in which computer scientists do research, requirements engineering is probably the most informal, interdisciplinary, and subjective. Although these qualities are inherent to the topic under investigation, they make scientists and mathematicians uncomfortable. Given these circumstances, a rigorous classification of research efforts in requirements engineering-if comprehensive and intelligible-might have several benefits, including: 1. It would delineate the area and would encourage research coverage of the whole area. 2. It would provide structure that might encourage the discovery and articulation of new principles. 3. It would assist in grouping similar things, such as competing solutions to the same problem. These groupings would be a great help in comparing, extending, and exploiting results. This article proposes and justifies a trial classification scheme. An earlier version was used to organize the papers submitted to this symposium, and the scheme has been refined somewhat in response to inadequacies discovered during the process of selecting the program. It is offered in hopes of stimulating discussion and eventual consensus. The fist issue to be tackled is the heterogeneity of the topics usually considered part of requirements engineering. They include Tasks that must be completed: elicitation, validation, specification. Problems that must be solved: barriers to communication, incompleteness, inconsistency. Solutions to problems: formal languages and analysis algorithms, prototyping, metrics, traceability. Ways of contributing to knowledge: descriptions of practice, case studies, controlled experiments. Types of system:: embedded systems, safety-critical systems, distributed systems. A list with all these topics is intended to be comprehensive, but its heterogeneity undermines all chance of bringing order to the field. There seems to be a need for several orthogonal dimensions of classification. While multiple dimensions will certainly help us cope with the heterogeneity of concerns, there is a danger of making the classification scheme too complex to use. I have compromised by settling on two dimensions, which are presented separately in the next two sections.

The new taxonomy of systems: toward an adaptive systems engineering framework

Abstract: Systems engineering is developing rapidly, while new standards are created and new tools are being developed. However, the theoretical understanding and the conceptual foundation of systems engineering are still in their early stages. For example, although real-world systems exhibit considerable differences, there is very little distinction in the literature between the system type and the description of its actual system engineering pursuit. We suggest here a new approach to systems engineering. It is based on the premise that the actual process of systems engineering must be adaptive to the real system type. Using this concept, we present a two-dimensional (2-D) taxonomy in which systems are classified according to four levels of technological uncertainty, and three levels of system scope. We then describe the differences found in systems engineering styles in various areas, such as system requirements, functional allocation, systems design, project organization, and management style. We also claim that adapting the wrong system and management style may cause major difficulties during the process of system creation. Two examples will be analyzed to illustrate this point: the famous Space Shuttle case and one of the system development projects we studied.

Research and development challenges for agent-based systems

Abstract: The increasing sophistication of today's information era poses certain challenges to traditional information technology (IT) systems. Agent-based software technology is rapidly evolving to meet the demands of this new information era. However, before agent-based solutions can be routinely and successfully exploited in real-world problems, certain fundamental research and software engineering issues have to be addressed. Some of the key challenges for the research and development of agent-based software systems are discussed. Our discussion is carried out from the twin viewpoints of fundamental research questions and software engineering issues.

A methodology of human factors analysis for systems engineering: theory and applications

Abstract: This paper discusses a methodology for studying human erroneous behavior that comprises four modeling phases, namely: (1) a paradigm of human behavior; (2) a taxonomy and related tables for human erroneous actions; (3) a set of data and correlations from the real working environment; and (4) a procedure for application of the methodology to different types of analysis, at different levels of complexity. The methodology has been developed to support possible applications of human factors to design and safety assessment of technological systems. The results of some applications are presented for prospective and retrospective studies in the domains of nuclear reactors and civil aviation.

Toward Mass Customization in the Age of Information: The Case for Open Engineering Systems

Abstract: In the Industrial Era, manufacturers used "dedicated" engineering systems to mass produce their products. In today's increasingly competitive markets, the trend is toward mass customization, something that becomes increasingly feasible when modern information technologies are used to create open engineering systems. Our focus is on how designers can provide enhanced product flexibility and variety (if not fully customized products) through the development of open engineering systems. After presenting several industrial examples, we anchor our new systems philosophy with two real engineering applications. We believe that manufacturers who adopt open systems will achieve competitive advantage in the Information Age.

Engineering systems integration for civil infrastructure projects

Abstract: Public infrastructure owners continue to explore a range of project delivery and financing strategies to meet current and future needs, including Design-Bid-Build, Design-Build, turnkey, Design-Build-Operate, Build-Operate-Transfer, and Build-Own-Operate-Transfer. In the midst of these activities, a new engineering discipline is emerging. This new discipline, Engineering Systems Integration, treats project delivery and finance methods as variables to be managed in the infrastructure development process, rather than as constants with respect to which engineers and planners have no input or control. The engineering systems integrator is engaged in the optimization of the project delivery and finance configuration at both project and system levels. Four years of research examined more than 3,000 infrastructure projects in the United States and Hong Kong and has produced an operational framework to model the robust environment in which Engineering Systems Integration occurs. The paper presents this framework, describes how it is being incorporated into engineering curricula at the Massachusetts Institute of Technology, and applies the framework to a major multimodal transportation facility at an Environmental Protection Agency Superfund site north of Boston, Massachusetts.

Understanding the nature of design

Abstract: AI in design includes the modeling of designer activity, the representation of designer knowledge, and the construction of either systems that produce designs or systems that assist designers.1 Through these activities, we hope to gain better insight both into the nature of design processes and representations, and into methods for developing systems to support design activities. More generally, these studies contribute to our understanding of intelligent behavior. This area has various names, including AI in Design (AID), Knowledge-Based Design Systems (KBDS), Intelligent CAD (IntCAD or ICAD), and Knowledge Integrated CAD (KIC).2 Areas of related work include concurrent engineering, simultaneous engineering, and concurrent design. Design researchers use a variety of AI techniques, such as constraint satisfaction, search, negotiation, and knowledge representation. Because design is inherently multidisciplinary, researchers often draw on results from fields such as cognitive psychology, decision theory, optimization, language theory, and architecture.3,4 The task of design (as opposed to, say, diagnosis) and the domains in which design is being done (for example, computer design and bridge design) influence how these techniques are used.

Soft Computing Techniques in Knowledge-Based Intelligent Engineering Systems: Approaches and Applications

Abstract: Knowledge-based Intelligent Systems. Neural Network Paradigms. Fuzzy Logic in Engineering. Introduction to Evolutionary Computing Techniques Developing Knowledge-based Applications in Engineering. Real-Time Knowledge-based Systems: Concepts, Issues, Approaches. Analogue/Digital Circuits Representation for Design and Trouble Shooting in Intelligent Environment. Applications of Neural Networks in Engineering. Evolution of Neural Structures Based on Cellular Automata. Further Applications of ART Paradigms. Fuzzy Control - Design and Engineering Applications.

Back to basics again – a scientific definition of systems engineering

Abstract: The major confusion with the understanding of systems engineering and improving its scientific basis is the failure to define the system of interest. Given a clear definition of the system of interest, engineered functions of that system can be identified, and applications of systems engineering concepts to those activities can be examined. A systems framework is suggested to classify basic engineering and systems engineering activities. This framework allows a better definition and search for scientific foundations of systems engineering.

Engineering of complex systems with models

Abstract: The value of systems engineering and a vision of automation to aid the search for near optimal system designs is described. Realizing that vision requires application of modeling to system development and the definition of systems engineering itself. The approach is a synthesis of systems engineering best practices with the rigor of software engineering. The basic abstractions and processes required are described. The resulting meta-process description is highly tailorable to organization need and culture.

Using contemporary tools to teach dynamics in engineering technology

Abstract: The following paper illustrates the usage of modern educational tools in teaching dynamics to students of engineering technology. Problems in engineering technology are traditionally skill based rather than theory based. As a result the instructor has to illustrate problems keeping the hands-on approach in mind. One of the best ways to exemplify theory, to meet the above requirements, is the usage of modern educational tools like multimedia, simulation software and visualization techniques. This helps the students to understand the engineering aspect of dynamics from the pure science aspect of the subject matterÐa key feature in satisfying our program requirement.

Development and Integration of Engineering Processes at Oerlikon Aerospace

Abstract: In order to reduce cycle time, increase customer satisfaction and lower costs, Oerlikon Aerospace has initiated, in 1992, a project to define and implement software and systems engineering processes. The initiative started by performing a formal assessment of current software engineering practices. An action plan was developed and multi-functional working groups were tasked to define and facilitate the implementation of software processes. A second initiative was started, in 1995, with the objective of defining and implementing a systems engineering process, and integrating to the systems engineering process the software engineering process already in use.

Toward Feature Engineering of Software Systems

Abstract: : The gulf between the user and the developer perspectives leads to difficulties in producing successful software systems. users are focused on the problem domain, where the system's features are the primary concern. Developers are focused on the solution domain, where the system's lifecycle artifacts are key. Presently, there is little understanding of how to narrow this gulf. This paper argues for establishing an organizing viewpoint that we term feature engineering. Feature engineering promotes features as first-class objects throughout the software lifecycle and across the problem and solution domains. The goal of the paper is not to propose a specific new technique or technology. Rather, it aims at laying out some basic concepts and terminology that can be used as a foundation for developing a sound and complete theory of feature engineering. The paper discusses the impact that features have on different phases of the lifecycle, provides some ideas on how these phases can be improved by fully exploiting the concept of feature, and suggests topics for a research agenda in feature engineering.

The systems engineering capability maturity model: where to start?

Abstract: The systems engineering capability maturity model is a tool designed to help companies measure and improve their system engineering processes. The architecture of the model is designed to provide the user with a lot of flexibility, and to not be overly prescriptive with regards to how companies should structure their improvement plans. However, the result is that the systems engineering capability maturity model can appear overly complex, leaving potential users confused and unable to develop an effective plan of attack for deploying the model within their own companies. By analyzing the data within the systems engineering capability maturity model one can organize the model content by level of difficulty or complexity. The author has organized the model content into five stages of difficulty, termed improvement stages. Organizations can use these improvement stages as an additional data point or as guidance when they are evaluating or improving systems engineering processes.

Demonstration of a Safety Analysis on a Complex System

Abstract: For the past 17 years, Professor Leveson and her graduate students have been developing a theoretical foundation for safety in complex systems and building a methodology upon that foundation. The methodology includes special management structures and procedures, system hazard analyses, software hazard analysis, requirements modeling and analysis for completeness and safety, special software design techniques including the design of human-machine interaction, verification, operational feedback, and change analysis. The Safeware methodology is based on system safety techniques that are extended to deal with software and human error. Automation is used to enhance our ability to cope with complex systems. Identification, classification, and evaluation of hazards is done using modeling and analysis. To be effective, the models and analysis tools must consider the hardware, software, and human components in these systems. They also need to include a variety of analysis techniques and orthogonal approaches: There exists no single safety analysis or evaluation technique that can handle all aspects of complex systems. Applying only one or two may make us feel satisfied, but will produce limited results. We report here on a demonstration, performed as part of a contract with NASA Langley Research Center, of the Safeware methodology on the Center-TRACON Automation System (CTAS) portion of the air traffic control (ATC) system and procedures currently employed at the Dallas/Fort Worth (DFW) TRACON (Terminal Radar Approach CONtrol). CTAS is an automated system to assist controllers in handling arrival traffic in the DFW area. Safety is a system property, not a component property, so our safety analysis considers the entire system and not simply the automated components. Because safety analysis of a complex system is an interdisciplinary effort, our team included system engineers, software engineers, human factors experts, and cognitive psychologists.

Supporting concurrent engineering using an intranet approach

Abstract: Design and engineering processes are complex and inherently parallel. There is a need for a framework which allows document management for all phases of complex engineering tasks. The first part of the paper presents an introduction into the most challenging issues of this field. In the second part of the paper a case study from the area of car manufacturing is presented in which intranet technology is used to support design and engineering processes.

Teaching fundamentals of electromagnetics in the context of engineering practice

Abstract: A major hurdle in teaching engineering science courses in the framework of engineering applications has been the lack of suitable teaching resources. Engineering supplements, in keeping with the traditional emphasis on the mechanics of problem solving, invariably take the form of "so many solved problems in...". The project described is an attempt to address this deficiency in one of the key areas of the electrical engineering curriculum. The proposed supplement will provide case studies to accompany all key areas of electromagnetics as well as to address all major engineering issues. The scope of the present effort has been to develop and test a limited pilot version. The specific case studies included in the pilot version of the supplement and the engineering issues they address are presented.

A road map for implementing systems engineering

Abstract: Studies by academia, industry, and government indicate that applying a sound systems engineering process to development programs is an important tool for preventing cost and schedule overruns and performance deficiencies. There is an enormous body of systems engineering knowledge. Where does one start? How can the principles of systems engineering be applied in the Sandia environment? This road map is intended to be an aid to answering these questions.

System engineering issues in industrial inspection

Abstract: The design of industrial inspection systems, requires a broad spectrum of techniques and disciplines. These include electronic engineering (hardware and software design), engineering mathematics, physics (optics and lighting) and mechanical engineering (since industrial vision systems deal with a mainly mechanical world). However, many industrial vision systems continue to be designed from a purely software engineering perspective, without consideration for any of the other system disciplines. While it is acknowledged that the software engineering task in industrial inspection is a critical one, the other system elements are neglected at our peril. No single discipline should be emphasised at the expense of the others. Lately, a number of researchers have argued for the design of vision systems to be firmly placed back into a systems engineering framework. This arises from the belief that an inadequate amount of vision research deals with the genuine design and systems problems involved in the implementation of industrial vision systems. The aim of this paper is to discuss the current state of industrial inspection, as seen from a systems engineering perspective. (6 pages)

How Can Requirements Engineering Research Become Requirements Engineering Practice

Abstract: The path from conceptualization of a good idea to its widespread use in industry is usually long, complicated, and fraught with peril. Too often, research justified as satisfying the needs of industry begins with a wrong or simplified understanding of industry’s problems. Even given a real solution to a real problem, successful transfer of that solution into practice depends on many other factors such as funding, the emergence of champions, availability of tools, education, integration with existing methods, and all too often, plain luck. This panel will explore how methods for requirements engineering for realtime and embedded systems can be moved into practice. Representatives from industry will discuss their needs and problems using existing methods, members of the research community will discuss current research trends, and tool vendors will discuss the difficulties of moving a good solution to a real problem into practice. Each speaker will be asked to briefly state, with respect to requirements engineering for real-time, embedded systems:

Problem-based engineering design and assessment in a digital systems program

Abstract: Engineering design is being used to better prepare graduates for engineering practice by providing a balance between the theoretical and practical aspects of the engineering degree program. Capstone design courses have become increasingly popular, particularly with engineering educators in North America. However, there is some concern that the skills and experiences derived from design-based courses are occurring much too late in a students education and instead should be spread throughout the degree program. This paper describes a strategy for reaching digital systems which includes the integration of design and theory at all levels in the students' engineering education and which is particularly suitable for the early years of the engineering degree program. Student-based assessment is used in conjunction with open-ended design to develop problem-solving strategies and to encourage students to take more responsibility for their learning.

A multimedia based laboratory course for environmental engineering fundamentals and process design

Abstract: Many environmental engineering curricula across the nation are being redesigned to emphasize fundamentals of environmental engineering process dynamics and to acquire familiarity with the procedures for obtaining and determining design parameters for design of full-scale systems for treatment and remediation of water and wastewater. The objective of this proposal is to develop multimedia laboratory courseware to supplement these types of courses and provide students with an active learning environment in which conceptual theories can be visually observed and controlled.