According to W. Edwards Deming, American companies require nothing less than a transformation of management style and of governmental relations with industry. In Out of the Crisis, originally published in 1982, Deming offers a theory of management based on his famous 14 Points for Management. Management's failure to plan for the future, he claims, brings about loss of market, which brings about loss of jobs. Management must be judged not only by the quarterly dividend, but by innovative plans to stay in business, protect investment, ensure future dividends, and provide more jobs through improved product and service. In simple, direct language, he explains the principles of management transformation and how to apply them.

Out of the Crisis

THE FIFTH DISCIPLINE The Art & Practice of the Learning Organization

House of Quality

Design and Marketing of New Products

End-User Development: An Emerging Paradigm- Psychological Issues in End-User Programming- More Natural Programming Languages and Environments- What Makes End-User Development Tick? 13 Design Guidelines- An Integrated Software Engineering Approach for End-User Programmers- Component-Based Approaches to Tailorable Systems- Natural Development of Nomadic Interfaces Based on Conceptual Descriptions- End User Development of Web Applications- End-User Development: The Software Shaping Workshop Approach- Participatory Programming: Developing Programmable Bioinformatics Tools for End-Users- Challenges for End-User Development in Intelligent Environments- Fuzzy Rewriting- Breaking It Up: An Industrial Case Study of Component-Based Tailorable Software Design- End-User Development as Adaptive Maintenance- Supporting Collaborative Tailoring- EUD as Integration of Components Off-The-Shelf: The Role of Software Professionals Knowledge Artifacts- Organizational View of End-User Development- A Semiotic Framing for End-User Development- Meta-design: A Framework for the Future of End-User Development- Feasibility Studies for Programming in Natural Language- Future Perspectives in End-User Development

End user development

The concept of Reference Architectures is novel in the business world However, many architects active in the creation of complex systems frequently use the term Reference Architecture Yet, these experienced architects do not collectively have a consistent notion of what constitutes a Reference Architecture, what is the value of maintaining the Reference Architecture, what is the best approach to visualizing a Reference Architecture, what is the most appropriate level of abstraction, and how should an architect make use of the Reference Architecture in their work? This paper examines current Reference Architectures and the driving forces behind development of them to come to a collective conclusion on what a Reference Architecture should truly be It will be shown that a Reference Architecture captures the accumulated architectural knowledge of thousands man-years of work This knowledge ranges from why (market segmentation, value chain, customer key drivers, application), what (systems, key performance parameters, system interfaces, functionality, variability), to how (design views and diagrams, essential design patterns, main concepts) The purpose of the Reference Architecture is to provide guidance for future developments The Reference Architecture incorporates the vision and strategy for the future The Reference Architecture is a reference for the hundreds of teams related to ongoing developments By providing this reference all these teams have a shared baseline of why, what and how It is the authors' goal that this paper will facilitate further research in the concepts and ideas presented herein © 2009 Wiley Periodicals, Inc Syst Eng

/pdf/the-concept-of-reference-architectures-58rgs8wwn6.pdf

The Concept of Reference Architectures

A fundamental challenge for system engineers is to capture a problem with an effective model or framework and then facilitate transferring the information of that captured problem to practical systems engineering tools and methods. The early problem definition phase requires an application of systems thinking with adequate modeling tools and methods. Then, the later problem definition phase and early system architecting phase requires transferring the captured problem to systems engineering tools and methods through emerging techniques such as model-based systems engineering (MBSE) using SysML (MBSE is the practice of using a modeling tools to capture systems engineering diagrams). This paper presents a method for capturing a problem through systemigrams and the Boardman soft systems methodology and then directly translating the systemigrams into SysML diagrams. With MBSE increasing in usage, this method could provide a time savings opportunity during model development along with the possibility of lowering information distortion or loss that can occur during transformation of systems thinking to systems engineering activities. This paper includes a case study which demonstrates how the proposed approach was applied on a problem being considered by the U.S. Army—Contingency Basing for Small Combat Units. Finally, this paper will provide the conclusion on the development of the method and describe future research directions that can allow systems thinking and MBSE to function in a congruent methodology.

Transitioning Systems Thinking to Model-Based Systems Engineering: Systemigrams to SysML Models

While much has been written about patterns in software engineering, little has been written about their application to systems architecting. This paper provides a discussion of patterns and their potential applicability to complex system architecting. A historical introduction to the concept of patterns is provided along with their evolution from the domain of civil architecture to other engineering disciplines and domains. The relevance and applicability of patterns to systems architecting is then examined. Research with regard to developing a pattern form for documenting patterns for systems architecting is presented, and this is demonstrated on a command and control pattern, using both IDEF0 and UML. The application of this pattern within a functional architecture is then explored. Finally, recommendations for the development and management of a systems architecting and architecting pattern repository are offered. © 2007 Wiley Periodiocals, Inc. Syst Eng 10: 138– 154, 2007

Applying the concept of patterns to systems architecture

Simulation Approaches for System of Systems: Events-based versus Agent Based Modeling☆

The need to perform faster systems integration of complex systems require the architect and design team to understand how the selected architecture and design components will impact the systems integration processes complexity (or difficulty). Systems integration process complexity is an outcome of the interaction between degree of feasibility and level of effort required to understand, describe, implement, manage, and document the systems integration process for a given system development and operational environment. This paper analyzes the cause-and-effect relationships between the system requirements, architecture and the systems integration processes complexity. In order to address systems integration issues upfront in the design phase it is necessary to determine if the architecture and design of components, subsystems, processes, and interfaces impacts (and to what extent) systems integration process complexity. This paper also defines and analyzes the impact of the different system architecture and requirements factors on systems integration process complexity. A research framework is developed to understand the cause-and-effect relationships between system requirements, architecture, and integration process. Finally, the paper proposes recommendations based on the causality results. These conclusions are based on research undertaken by the authors on eight development projects in the government sector.

/pdf/exploring-the-impact-of-systems-architecture-and-systems-3zdq9w3d8q.pdf

Robert Cloutier

Papers

The Concept of Reference Architectures

Transitioning Systems Thinking to Model-Based Systems Engineering: Systemigrams to SysML Models

Applying the concept of patterns to systems architecture

Simulation Approaches for System of Systems: Events-based versus Agent Based Modeling☆

Exploring the Impact of Systems Architecture and Systems Requirements on Systems Integration Complexity