Systems engineering

From Wikipedia, the free encyclopedia
  (Redirected from Systems Design Engineering)
Jump to: navigation, search
Systems engineering techniques are used in complex projects: spacecraft design, computer chip design, robotics, software integration, and bridge building. Systems engineering uses a host of tools that include modeling and simulation, requirements analysis and scheduling to manage complexity.

Systems engineering is an interdisciplinary field of engineering that focuses on how to design and manage complex engineering systems over their life cycles. Issues such as reliability, logistics, coordination of different teams (requirements management), evaluation measurements, and other disciplines become more difficult when dealing with large or complex projects. Systems engineering deals with work-processes, optimization methods, and risk management tools in such projects. It overlaps technical and human-centered disciplines such as control engineering, industrial engineering, organizational studies, and project management. Systems Engineering ensures that all likely aspects of a project or system are considered, and integrated into a whole.

History[edit]

QFD House of Quality for Enterprise Product Development Processes

The term systems engineering can be traced back to Bell Telephone Laboratories in the 1940s.[1] The need to identify and manipulate the properties of a system as a whole, which in complex engineering projects may greatly differ from the sum of the parts' properties, motivated various industries to apply the discipline.[2]

When it was no longer possible to rely on design evolution to improve upon a system and the existing tools were not sufficient to meet growing demands, new methods began to be developed that addressed the complexity directly.[3] The continuing evolution of systems engineering comprises the development and identification of new methods and modeling techniques. These methods aid in better comprehension of engineering systems as they grow more complex. Popular tools that are often used in the systems engineering context were developed during these times, including USL, UML, QFD, and IDEF0.

In 1990, a professional society for systems engineering, the National Council on Systems Engineering (NCOSE), was founded by representatives from a number of U.S. corporations and organizations. NCOSE was created to address the need for improvements in systems engineering practices and education. As a result of growing involvement from systems engineers outside of the U.S., the name of the organization was changed to the International Council on Systems Engineering (INCOSE) in 1995.[4] Schools in several countries offer graduate programs in systems engineering, and continuing education options are also available for practicing engineers.[5]

Concept[edit]

Some definitions
"An interdisciplinary approach and means to enable the realization of successful systems"[6]INCOSE handbook, 2004.
"System engineering is a robust approach to the design, creation, and operation of systems. In simple terms, the approach consists of identification and quantification of system goals, creation of alternative system design concepts, performance of design trades, selection and implementation of the best design, verification that the design is properly built and integrated, and post-implementation assessment of how well the system meets (or met) the goals."[7]NASA Systems Engineering Handbook, 1995.
"The Art and Science of creating effective systems, using whole system, whole life principles" OR "The Art and Science of creating optimal solution systems to complex issues and problems"[8]Derek Hitchins, Prof. of Systems Engineering, former president of INCOSE (UK), 2007.
"The concept from the engineering standpoint is the evolution of the engineering scientist, i.e., the scientific generalist who maintains a broad outlook. The method is that of the team approach. On large-scale-system problems, teams of scientists and engineers, generalists as well as specialists, exert their joint efforts to find a solution and physically realize it...The technique has been variously called the systems approach or the team development method."[9]Harry H. Goode & Robert E. Machol, 1957.
"The systems engineering method recognizes each system is an integrated whole even though composed of diverse, specialized structures and sub-functions. It further recognizes that any system has a number of objectives and that the balance between them may differ widely from system to system. The methods seek to optimize the overall system functions according to the weighted objectives and to achieve maximum compatibility of its parts."[10]Systems Engineering Tools by Harold Chestnut, 1965.

Systems engineering signifies only an approach and, more recently, a discipline in engineering. The aim of education in systems engineering is to simply formalize the approach and in doing so, identify new methods and research opportunities similar to the way it occurs in other fields of engineering. As an approach, systems engineering is holistic and interdisciplinary in flavour.

Origins and traditional scope[edit]

The traditional scope of engineering embraces the design, development, production and operation of physical systems, and systems engineering, as originally conceived, falls within this scope. "Systems engineering", in this sense of the term, refers to the distinctive set of concepts, methodologies, organizational structures (and so on) that have been developed to meet the challenges of engineering functional physical systems of unprecedented complexity. The Apollo program is a leading example of a systems engineering project.

Evolution to broader scope[edit]

The use of the term "systems engineer" has evolved over time to embrace a wider, more holistic concept of "systems" and of engineering processes. This evolution of the definition has been a subject of ongoing controversy,[11] and the term continues to apply to both the narrower and broader scope.

Traditional systems engineering was seen as a branch of engineering in the classical sense, that is, as applied only to physical system, such as space craft and aircraft. More recently, systems engineering has evolved to a take on a broader meaning especially when humans were seen as an essential component of a system. Checkland, for example, captures the broader meaning of systems engineering by stating that 'engineering' "can be read in its general sense; you can engineer a meeting or a political agreement." [12]

Consistent with the broader scope of systems engineering, the Systems Engineering Body of Knowledge (SEBoK) [13] has defined three types of systems engineering: (1) Product Systems Engineering (PSE) is the traditional systems engineering focused on the design of physical systems consisting of hardware and software. (2) Enterprise Systems Engineering (ESE) pertains to the view of enterprises, that is, organizations or combinations of organizations, as systems. (3) Service Systems Engineering (SSE) has to do with the engineering of service systems. Checkland [14] defines a service system as a system which is conceived as serving another system. Most civil infrastructure systems are service systems.

Holistic view[edit]

Systems engineering focuses on analyzing and eliciting customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem, the system lifecycle. Oliver et al. claim that the systems engineering process can be decomposed into

  • a Systems Engineering Technical Process, and
  • a Systems Engineering Management Process.

Within Oliver's model, the goal of the Management Process is to organize the technical effort in the lifecycle, while the Technical Process includes assessing available information, defining effectiveness measures, to create a behavior model, create a structure model, perform trade-off analysis, and create sequential build & test plan.[15]

Depending on their application, although there are several models that are used in the industry, all of them aim to identify the relation between the various stages mentioned above and incorporate feedback. Examples of such models include the Waterfall model and the VEE model.[16]

Interdisciplinary field[edit]

System development often requires contribution from diverse technical disciplines.[17] By providing a systems (holistic) view of the development effort, systems engineering helps mold all the technical contributors into a unified team effort, forming a structured development process that proceeds from concept to production to operation and, in some cases, to termination and disposal.

This perspective is often replicated in educational programs, in that systems engineering courses are taught by faculty from other engineering departments, which helps create an interdisciplinary environment.[18][19]

Managing complexity[edit]

The need for systems engineering arose with the increase in complexity of systems and projects,[20][21] in turn exponentially increasing the possibility of component friction, and therefore the unreliability of the design. When speaking in this context, complexity incorporates not only engineering systems, but also the logical human organization of data. At the same time, a system can become more complex due to an increase in size as well as with an increase in the amount of data, variables, or the number of fields that are involved in the design. The International Space Station is an example of such a system.

The International Space Station is an example of a largely complex system requiring Systems Engineering.

The development of smarter control algorithms, microprocessor design, and analysis of environmental systems also come within the purview of systems engineering. Systems engineering encourages the use of tools and methods to better comprehend and manage complexity in systems. Some examples of these tools can be seen here:[22]

Taking an interdisciplinary approach to engineering systems is inherently complex since the behavior of and interaction among system components is not always immediately well defined or understood. Defining and characterizing such systems and subsystems and the interactions among them is one of the goals of systems engineering. In doing so, the gap that exists between informal requirements from users, operators, marketing organizations, and technical specifications is successfully bridged.

Scope[edit]

The scope of systems engineering activities[23]

One way to understand the motivation behind systems engineering is to see it as a method, or practice, to identify and improve common rules that exist within a wide variety of systems.[citation needed] Keeping this in mind, the principles of systems engineering – holism, emergent behavior, boundary, et al. – can be applied to any system, complex or otherwise, provided systems thinking is employed at all levels.[24] Besides defense and aerospace, many information and technology based companies, software development firms, and industries in the field of electronics & communications require systems engineers as part of their team.[25]

An analysis by the INCOSE Systems Engineering center of excellence (SECOE) indicates that optimal effort spent on systems engineering is about 15-20% of the total project effort.[26] At the same time, studies have shown that systems engineering essentially leads to reduction in costs among other benefits.[26] However, no quantitative survey at a larger scale encompassing a wide variety of industries has been conducted until recently. Such studies are underway to determine the effectiveness and quantify the benefits of systems engineering.[27][28]

Systems engineering encourages the use of modeling and simulation to validate assumptions or theories on systems and the interactions within them.[29][30]

Use of methods that allow early detection of possible failures, in safety engineering, are integrated into the design process. At the same time, decisions made at the beginning of a project whose consequences are not clearly understood can have enormous implications later in the life of a system, and it is the task of the modern systems engineer to explore these issues and make critical decisions. No method guarantees today's decisions will still be valid when a system goes into service years or decades after first conceived. However, there are techniques that support the process of systems engineering. Examples include soft systems methodology, Jay Wright Forrester's System dynamics method, and the Unified Modeling Language (UML)—all currently being explored, evaluated, and developed to support the engineering decision process.

Education[edit]

Education in systems engineering is often seen as an extension to the regular engineering courses,[31] reflecting the industry attitude that engineering students need a foundational background in one of the traditional engineering disciplines (e.g., aerospace engineering, automotive engineering, electrical engineering, mechanical engineering, industrial engineering)—plus practical, real-world experience to be effective as systems engineers. Undergraduate university programs in systems engineering are rare. Typically, systems engineering is offered at the graduate level in combination with interdisciplinary study.

INCOSE maintains a continuously updated Directory of Systems Engineering Academic Programs worldwide.[5] As of 2009, there are about 80 institutions in United States that offer 165 undergraduate and graduate programs in systems engineering. Education in systems engineering can be taken as Systems-centric or Domain-centric.

  • Systems-centric programs treat systems engineering as a separate discipline and most of the courses are taught focusing on systems engineering principles and practice.
  • Domain-centric programs offer systems engineering as an option that can be exercised with another major field in engineering.

Both of these patterns strive to educate the systems engineer who is able to oversee interdisciplinary projects with the depth required of a core-engineer.[32]

Systems engineering topics[edit]

Systems engineering tools are strategies, procedures, and techniques that aid in performing systems engineering on a project or product. The purpose of these tools vary from database management, graphical browsing, simulation, and reasoning, to document production, neutral import/export and more.[33]

System[edit]

There are many definitions of what a system is in the field of systems engineering. Below are a few authoritative definitions:

  • ANSI/EIA-632-1999: "An aggregation of end products and enabling products to achieve a given purpose."[34]
  • DAU Systems Engineering Fundamentals: "an integrated composite of people, products, and processes that provide a capability to satisfy a stated need or objective."
  • IEEE Std 1220-1998: "A set or arrangement of elements and processes that are related and whose behavior satisfies customer/operational needs and provides for life cycle sustainment of the products."[35]
  • ISO/IEC 15288:2008: "A combination of interacting elements organized to achieve one or more stated purposes."[36]
  • NASA Systems Engineering Handbook: "(1) The combination of elements that function together to produce the capability to meet a need. The elements include all hardware, software, equipment, facilities, personnel, processes, and procedures needed for this purpose. (2) The end product (which performs operational functions) and enabling products (which provide life-cycle support services to the operational end products) that make up a system."[37]
  • INCOSE Systems Engineering Handbook: "homogeneous entity that exhibits predefined behavior in the real world and is composed of heterogeneous parts that do not individually exhibit that behavior and an integrated configuration of components and/or subsystems."[38]
  • INCOSE: "A system is a construct or collection of different elements that together produce results not obtainable by the elements alone. The elements, or parts, can include people, hardware, software, facilities, policies, and documents; that is, all things required to produce systems-level results. The results include system level qualities, properties, characteristics, functions, behavior and performance. The value added by the system as a whole, beyond that contributed independently by the parts, is primarily created by the relationship among the parts; that is, how they are interconnected."[39]

The systems engineering process[edit]

Depending on their application, tools are used for various stages of the systems engineering process:[23]

Systems Engineering Process.jpg

Using models[edit]

Models play important and diverse roles in systems engineering. A model can be defined in several ways, including:[40]

  • An abstraction of reality designed to answer specific questions about the real world
  • An imitation, analogue, or representation of a real world process or structure; or
  • A conceptual, mathematical, or physical tool to assist a decision maker.

Together, these definitions are broad enough to encompass physical engineering models used in the verification of a system design, as well as schematic models like a functional flow block diagram and mathematical (i.e., quantitative) models used in the trade study process. This section focuses on the last.[40]

The main reason for using mathematical models and diagrams in trade studies is to provide estimates of system effectiveness, performance or technical attributes, and cost from a set of known or estimable quantities. Typically, a collection of separate models is needed to provide all of these outcome variables. The heart of any mathematical model is a set of meaningful quantitative relationships among its inputs and outputs. These relationships can be as simple as adding up constituent quantities to obtain a total, or as complex as a set of differential equations describing the trajectory of a spacecraft in a gravitational field. Ideally, the relationships express causality, not just correlation.[40]

Tools for graphic representations[edit]

Initially, when the primary purpose of a systems engineer is to comprehend a complex problem, graphic representations of a system are used to communicate a system's functional and data requirements.[41] Common graphical representations include:

NOPE

graphical representation relates the various subsystems or parts of a system through functions, data, or interfaces. Any or each of the above methods are used in an industry based on its requirements. For instance, the N2 chart may be used where interfaces between systems is important. Part of the design phase is to create structural and behavioral models of the system.

nope the requirements are understood, it is now the responsibility of a systems engineer to refine them, and to determine, along with other engineers, the best technology for a job. At this point starting with a trade study, systems engineering encourages the use of weighted choices to determine the best option. A decision matrix, or Pugh method, is one way (QFD is another) to make this choice while considering all criteria that are important. The trade study in turn informs the design, which again affects graphic representations of the system (without changing the requirements). In an SE process, this stage represents the iterative step that is carried out until a feasible solution is found. A decision matrix is often populated using techniques such as statistical analysis, reliability analysis, system dynamics (feedback control), and optimization methods.

Other tools[edit]

Systems Modeling Language (SysML), a modeling language used for systems engineering applications, supports the specification, analysis, design, verification and validation of a broad range of complex systems.[42]

Lifecycle Modeling Language (LML), is an open-standard modeling language designed for systems engineering that supports the full lifecycle: conceptual, utilization, support and retirement stages.[43]

Related fields and sub-fields[edit]

Many related fields may be considered tightly coupled to systems engineering. These areas have contributed to the development of systems engineering as a distinct entity.

Cognitive Systems Engineering 
Cognitive systems engineering (CSE) is a specific approach to the description and analysis of human-machine systems or sociotechnical systems.[44] The three main themes of CSE are how humans cope with complexity, how work is accomplished by the use of artifacts, and how human-machine systems and socio-technical systems can be described as joint cognitive systems. CSE has since its beginning become a recognized scientific discipline, sometimes also referred to as cognitive engineering. The concept of a Joint Cognitive System (JCS) has in particular become widely used as a way of understanding how complex socio-technical systems can be described with varying degrees of resolution. The more than 20 years of experience with CSE has been described extensively.[45][46]
Configuration management
Like systems engineering, configuration management as practiced in the defense and aerospace industry is a broad systems-level practice. The field parallels the taskings of systems engineering; where systems engineering deals with requirements development, allocation to development items and verification, configuration management deals with requirements capture, traceability to the development item, and audit of development item to ensure that it has achieved the desired functionality that systems engineering and/or Test and Verification Engineering have proven out through objective testing.
Control engineering
Control engineering and its design and implementation of control systems, used extensively in nearly every industry, is a large sub-field of systems engineering. The cruise control on an automobile and the guidance system for a ballistic missile are two examples. Control systems theory is an active field of applied mathematics involving the investigation of solution spaces and the development of new methods for the analysis of the control process.
Industrial engineering
Industrial engineering is a branch of engineering that concerns the development, improvement, implementation and evaluation of integrated systems of people, money, knowledge, information, equipment, energy, material and process. Industrial engineering draws upon the principles and methods of engineering analysis and synthesis, as well as mathematical, physical and social sciences together with the principles and methods of engineering analysis and design to specify, predict, and evaluate results obtained from such systems.
Interface design
Interface design and its specification are concerned with assuring that the pieces of a system connect and inter-operate with other parts of the system and with external systems as necessary. Interface design also includes assuring that system interfaces be able to accept new features, including mechanical, electrical and logical interfaces, including reserved wires, plug-space, command codes and bits in communication protocols. This is known as extensibility. Human-Computer Interaction (HCI) or Human-Machine Interface (HMI) is another aspect of interface design, and is a critical aspect of modern systems engineering. Systems engineering principles are applied in the design of network protocols for local-area networks and wide-area networks.
Mechatronic engineering
Mechatronic engineering, like systems engineering, is a multidisciplinary field of engineering that uses dynamical systems modeling to express tangible constructs. In that regard it is almost indistinguishable from Systems Engineering, but what sets it apart is the focus on smaller details rather than larger generalizations and relationships. As such, both fields are distinguished by the scope of their projects rather than the methodology of their practice.
Operations research
Operations research supports systems engineering. The tools of operations research are used in systems analysis, decision making, and trade studies. Several schools teach SE courses within the operations research or industrial engineering department[citation needed], highlighting the role systems engineering plays in complex projects. Operations research, briefly, is concerned with the optimization of a process under multiple constraints.[47]
Performance engineering
Performance engineering is the discipline of ensuring a system meets customer expectations for performance throughout its life. Performance is usually defined as the speed with which a certain operation is executed, or the capability of executing a number of such operations in a unit of time. Performance may be degraded when an operations queue to execute is throttled by limited system capacity. For example, the performance of a packet-switched network is characterized by the end-to-end packet transit delay, or the number of packets switched in an hour. The design of high-performance systems uses analytical or simulation modeling, whereas the delivery of high-performance implementation involves thorough performance testing. Performance engineering relies heavily on statistics, queueing theory and probability theory for its tools and processes.
Program management and project management.
Program management (or programme management) has many similarities with systems engineering, but has broader-based origins than the engineering ones of systems engineering. Project management is also closely related to both program management and systems engineering.
Proposal engineering
Proposal engineering is the application of scientific and mathematical principles to design, construct, and operate a cost-effective proposal development system. Basically, proposal engineering uses the "systems engineering process" to create a cost effective proposal and increase the odds of a successful proposal.
Reliability engineering
Reliability engineering is the discipline of ensuring a system meets customer expectations for reliability throughout its life; i.e., it does not fail more frequently than expected. Reliability engineering applies to all aspects of the system. It is closely associated with maintainability, availability (dependability or RAMS preferred by some), and logistics engineering. Reliability engineering is always a critical component of safety engineering, as in failure modes and effects analysis (FMEA) and hazard fault tree analysis, and of security engineering.
Risk Management
Risk Management, the practice of assessing and dealing with risk is one of the interdisciplinary parts of Systems Engineering. In development, acquisition, or operational activities, the inclusion of risk in tradeoff with cost, schedule, and performance features, involves the iterative complex configuration management of traceability and evaluation to the scheduling and requirements management across domains and for the system lifecycle that requires the interdisciplinary technical approach of systems engineering.
Safety engineering
The techniques of safety engineering may be applied by non-specialist engineers in designing complex systems to minimize the probability of safety-critical failures. The "System Safety Engineering" function helps to identify "safety hazards" in emerging designs, and may assist with techniques to "mitigate" the effects of (potentially) hazardous conditions that cannot be designed out of systems.
Scheduling
Scheduling is one of the systems engineering support tools as a practice and item in assessing interdisciplinary concerns under configuration management. In particular the direct relationship of resources, performance features, and risk to duration of a task or the dependency links among tasks and impacts across the system lifecycle are systems engineering concerns.
Security engineering
Security engineering can be viewed as an interdisciplinary field that integrates the community of practice for control systems design, reliability, safety and systems engineering. It may involve such sub-specialties as authentication of system users, system targets and others: people, objects and processes.
Software engineering
From its beginnings, software engineering has helped shape modern systems engineering practice. The techniques used in the handling of complexes of large software-intensive systems has had a major effect on the shaping and reshaping of the tools, methods and processes of SE.

See also[edit]

References[edit]

  1. ^ Schlager, J. (July 1956). "Systems engineering: key to modern development". IRE Transactions EM–3 (3): 64–66. doi:10.1109/IRET-EM.1956.5007383. 
  2. ^ Arthur D. Hall (1962). A Methodology for Systems Engineering. Van Nostrand Reinhold. ISBN 0-442-03046-0. 
  3. ^ Andrew Patrick Sage (1992). Systems Engineering. Wiley IEEE. ISBN 0-471-53639-3. 
  4. ^ INCOSE Resp Group (11 June 2004). "Genesis of INCOSE". Retrieved 2006-07-11. 
  5. ^ a b INCOSE Education & Research Technical Committee. "Directory of Systems Engineering Academic Programs". Retrieved 2006-07-11. 
  6. ^ Systems Engineering Handbook, version 2a. INCOSE. 2004. 
  7. ^ NASA Systems Engineering Handbook. NASA. 1995. SP-610S. 
  8. ^ "Derek Hitchins". INCOSE UK. Retrieved 2007-06-02. 
  9. ^ Goode, Harry H.; Robert E. Machol (1957). System Engineering: An Introduction to the Design of Large-scale Systems. McGraw-Hill. p. 8. LCCN 56011714. 
  10. ^ Chestnut, Harold (1965). Systems Engineering Tools. Wiley. ISBN 0-471-15448-2. 
  11. ^ http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.86.7496&rep=rep1&type=pdf
  12. ^ Checkland, Peter, Systems Thinking, Systems Practice. John Wiley & Sons, 1999, p. 10.
  13. ^ Checkland, Peter. 1999. Systems Thinking, Systems Practice. New York: John Wiley & Sons. Pyster, Arthur, ed. 2012. Systems Engineering Body of Knowledge. 1.0 ed: Stephens Institute and the Naval Postgraduate School.
  14. ^ Checkland, Peter. 1999. Systems Thinking, Systems Practice. New York: John Wiley & Sons.
  15. ^ Oliver, David W.; Timothy P. Kelliher, James G. Keegan, Jr. (1997). Engineering Complex Systems with Models and Objects. McGraw-Hill. pp. 85–94. ISBN 0-07-048188-1. 
  16. ^ "The SE VEE". SEOR, George Mason University. Retrieved 2007-05-26. 
  17. ^ Ramo, Simon; Robin K. St.Clair (1998). The Systems Approach: Fresh Solutions to Complex Problems Through Combining Science and Practical Common Sense (PDF). Anaheim, CA: KNI, Inc. 
  18. ^ "Systems Engineering Program at Cornell University". Cornell University. Retrieved 2007-05-25. 
  19. ^ "ESD Faculty and Teaching Staff". Engineering Systems Division, MIT. Retrieved 2007-05-25. 
  20. ^ Yassine, A. and Braha, D. (2003). “Complex Concurrent Engineering and the Design Structure Matrix Approach.” Concurrent Engineering: Research and Applications 11 (3): 165-177.
  21. ^ Braha, D. and Bar-Yam, Y. (July 2007). “The Statistical Mechanics of Complex Product Development: Empirical and Analytical Results.” Management Science 53 (7): 1127-1145.
  22. ^ "Core Courses, Systems Analysis – Architecture, Behavior and Optimization". Cornell University. Retrieved 2007-05-25. 
  23. ^ a b Systems Engineering Fundamentals. Defense Acquisition University Press, 2001
  24. ^ Rick Adcock. "Principles and Practices of Systems Engineering" (PDF). INCOSE, UK. Archived from the original on 15 June 2007. Retrieved 2007-06-07. 
  25. ^ "Systems Engineering, Career Opportunities and Salary Information (1994)". George Mason University. Retrieved 2007-06-07. 
  26. ^ a b "Understanding the Value of Systems Engineering" (PDF). Retrieved 2007-06-07. 
  27. ^ "Surveying Systems Engineering Effectiveness" (PDF). Archived from the original on 15 June 2007. Retrieved 2007-06-07. 
  28. ^ "Systems Engineering Cost Estimation by Consensus". Retrieved 2007-06-07. 
  29. ^ Andrew P. Sage, Stephen R. Olson (2001). "Modeling and Simulation in Systems Engineering". Simulation (SAGE Publications) 76 (2): 90. doi:10.1177/003754970107600207. Retrieved 2007-06-02. 
  30. ^ E.C. Smith, Jr. (1962). Simulation in systems engineering (PDF). IBM Research. Retrieved 2007-06-02. 
  31. ^ "Didactic Recommendations for Education in Systems Engineering" (PDF). Retrieved 2007-06-07. 
  32. ^ "Perspectives of Systems Engineering Accreditation" (PDF). INCOSE. Archived from the original on 15 June 2007. Retrieved 2007-06-07. 
  33. ^ Steven Jenkins. "A Future for Systems Engineering Tools" (PDF). NASA. p. 15. Retrieved 2007-06-10. 
  34. ^ "Processes for Engineering a System", ANSI/EIA-632-1999, ANSI/EIA, 1999 [1]
  35. ^ "Standard for Application and Management of the Systems Engineering Process -Description", IEEE Std 1220-1998, IEEE, 1998 [2]
  36. ^ "Systems and software engineering – System life cycle processes", ISO/IEC 15288:2008, ISO/IEC, 2008 [3]
  37. ^ "NASA Systems Engineering Handbook", Revision 1, NASA/SP-2007-6105, NASA, 2007 [4]
  38. ^ "Systems Engineering Handbook", v3.1, INCOSE, 2007 [5]
  39. ^ "A Consensus of the INCOSE Fellows", INCOSE, 2006 [6]
  40. ^ a b c NASA (1995). "System Analysis and Modeling Issues". In: NASA Systems Engineering Handbook June 1995. p.85.
  41. ^ Long, Jim (2002). Relationships between Common Graphical Representations in System Engineering (PDF). Vitech Corporation. 
  42. ^ "OMG SysML Specification" (PDF). SysML Open Source Specification Project. p. 23. Retrieved 2007-07-03. 
  43. ^ (PDF\ title = LML Specification). LML Steering Committee. p. 4 http://www.lifecyclemodeling.org/spec/LML_Specification_1_0.pdf. Retrieved 2014-06-05.  Missing or empty |title= (help)
  44. ^ Hollnagel E. & Woods D. D. (1983). Cognitive systems engineering: New wine in new bottles. International Journal of Man-Machine Studies, 18, 583-600.
  45. ^ Hollnagel, E. & Woods, D. D. (2005) Joint cognitive systems: The foundations of cognitive systems engineering. Taylor & Francis
  46. ^ Woods, D. D. & Hollnagel, E. (2006). Joint cognitive systems: Patterns in cognitive systems engineering. Taylor & Francis.
  47. ^ (see articles for discussion: [7] and [8])

Further reading[edit]

External links[edit]