System Architecting. Collect facts. Integrate facts, create vision

Transcription

1 Apply and earn credit Collect facts Communicate Integrate facts, create vision Frogs vei 41 P.O. Box 235, NO-3603 Kongsberg Norway Abstract This book addresses the role of the system architect and the role of the system architecting process within the business: What is the role and the task of the (system) architect? How does the architect do his work? What are the main activities of the architect? How does the architect fit in the organization? What kind of person is the architect? How does architecting fit in the business? Note: this book is likely to be refactored in smaller books in the future. Distribution This article or presentation is written as part of the Gaudí project. The Gaudí project philosophy is to improve by obtaining frequent feedback. Frequent feedback is pursued by an open creation process. This document is published as intermediate or nearly mature version to get feedback. Further distribution is allowed as long as the document remains complete and unchanged. All Gaudí documents are available at: version: 1.8 status: preliminary draft October 20, 2017

2 Contents Introduction xviii System Architecture: The Silver Bullet? xix 0.1 Introduction xix 0.2 Why System Architecture? xix The Quest for Certainty xx Disclaimer; Setting the Expectations to a realistic level.. xxi 0.3 How: Critical Success Factors xxi Know-How xxi Common Sense xxii Pragmatics xxii Critical attitude xxii Drive xxii Vision xxiii 0.4 Summary xxiii 0.5 Acknowledgements xxiii I Processes 1 1 Process Decomposition of a Business Introduction Process Decomposition Process versus Organization Value Chain and Feedback Decomposition of the Customer Oriented Process Extended Process Decomposition; Generic Developments Acknowledgements What is a Process? Introduction What is a process

3 2.3 The relation between Processes and Organizations Process Improvement Acknowledgements The Product Creation Process Introduction The Context of the Product Creation Process Phases of the Product Creation Process Evolutionary models for Product Creation Milestones and Decisions Organization of the Product Creation Process Hierarchical decomposition Further decomposition of the Product Creation Process Design Control Operational Management Marketing Product Creation Teams Acknowledgements The Importance of Feedback for Architecture Introduction Why Feedback? Control Learning Applicability Theory versus Practice Conclusions The System Architecture Process Introduction System Architecture in the Business Context Purpose of the Process The System Architect as Process Owner in Product Creation Context Acknowledgements Products, Projects, and Services; similarities and differences in architecting Introduction Products and Projects Services System of Systems October 20, 2017 version: 1.8 page: iii

4 II The System Architect as a Person 40 7 The Awakening of a System Architect Introduction The Development of a System Architect Generalist versus Specialist Acknowledgements Systems Titles and Roles Introduction Cultural differences in terms Title versus skills and actual job Systems roles and titles The Role and Task of the System Architect Introduction Deliverables of the System Architect System Architect Responsibilities What does the System Architect do? Task versus Role Acknowledgements Function Profiles; The Sheep with Seven Legs Introduction Systems Architect Profile Most discriminating characteristics Test Engineer Profile Developer Profile Operational Leader Profile Line Manager Profile Commercial Manager Profile Definition of Characteristics Interpersonal skills Know-how Reasoning Power Executing Skills Process Skills Project Management Skills Commercial Skills Human Resource Management Skills Acknowledgements October 20, 2017 version: 1.8 page: iv

5 11 Dynamic Range of Abstraction Levels in Architecting Introduction From System-of-Interest to Context Architecture and Architecting Revisiting Design and Engineering Architecting and Design in Practice Architecting Interaction Styles Introduction Provocation Facilitation Leading Empathic Interviewing White-board simulation Judo tactics The Tool Box of the System Architect Introduction Overview of Systems Architecting Tools Human Experience Based tools Low-tech tools Facilitation tools Borrowed Advanced Tools Architecting Specific Tools General Purpose computer based tools Tools prescribed by the organization infrastructure Process Oriented Standards Concept oriented Standards Artifact Oriented Standards Human versus Computer Assisted Tools Flow: from Data to Overview and Understanding III Market, Requirements, Roadmapping Short introduction to basic CAFCR model Introduction The CAFCR model Who is the customer? Life Cycle view October 20, 2017 version: 1.8 page: v

6 15 Fundamentals of Requirements Engineering Introduction Definition of Requirements System as a black box Stakeholders Requirements for Requirements Key Drivers How To Introduction Example Motor Way Management CAF-views and Key Drivers Requirements Elicitation and Selection Introduction Viewpoints on Needs Requirements Value and Selection Business Strategy; Methods and Models Introduction Basic Concepts Methods for Strategy Support Examples of strategic choices Innovation The role of roadmapping in the strategy process Process decomposition of a business Framework for architecting and roadmapping From vision to roadmap to plan and further Summary Acknowledgements Roadmapping Introduction What is in a roadmap? Why Roadmapping? How to create and update a roadmap Roadmap deployment Roadmap Essentials Selection of most important or relevant issues Key drivers as a means to structure the roadmap Nothing is certain, ambiguity is normal Use facts whenever possible Do not panic in case of impossibilities October 20, 2017 version: 1.8 page: vi

7 20.7 Acknowledgements Change Management; Introducing Systems Architecting Aspects Introduction Earning Credit, Work on Urgent Issues Example: Bootstrapping the Roadmapping Process Market Product Life Cycle Consequences for Architecting Introduction Observed Life Cycle Curve in Practice Life Cycle Model Acknowledgements IV Product Families, Generics and Software Product Families and Generic Aspects Introduction Why generic developments? Granularity Of Generic Developments Modified Process Decomposition Modified Operational Organization of Product Creation Models for Generic Developments Lead Customer Carrier Product Platform Alternative Generic Development Scenarios Common Pitfalls Acknowledgments Product Familiy Business Analysis And Definition Introduction Roadmapping Reference Architecture Business Architecture Application Architecture Functional Architecture YoYo-View over time Relation with the Technical Architecture Requirements Capturing Feature Space Exploration and Value Engineering Scope Determination Acknowledgements October 20, 2017 version: 1.8 page: vii

8 25 The Role of Software in Systems Introduction Why is Software a Bottleneck in Product Development? Growth of software effort Roles of the disciplines in a system Characterization of disciplines System or Software Issues? Acknowledgments V Management and Architects The Tense Relation between Architect and Manager Introduction What is a Manager? Comparison of Architect and Manager Responsibility View on Solutions View on Changes Personal Characteristics Leadership Values Personal Ambition How to improve the relationship Acknowledgments How to present architecture issues to higher management Introduction Preparation The presentation material The Presentation Exercise Simplistic Financial Computations for System Architects Introduction Cost and Margin Refining investments and income Adding the time dimension Financial yardsticks Acknowledgements October 20, 2017 version: 1.8 page: viii

9 29 How to appraise or assess an architect? Introduction When is the architect successful? How to assess the architect? October 20, 2017 version: 1.8 page: ix

10 List of Figures 1 Personal key driver to avoid nasty surprises xxi 1.1 Simplified decomposition of the business in 4 main processes Decomposition of the business in 4 main processes, characterized by their financial meaning The value chain and the feedback flow in opposite direction Decomposition of the Customer Oriented Process The Process Decomposition extended with a generic developments creation process Process Attributes A process within an abstraction hierarchy Organization Attributes Weaknesses of the organizational view McKinsey 7S model A phased approach of the Product Creation Process, showing the participation of all disciplines during the entire process A phased approach of the Product Creation Process, showing the progress of the different design deliverables Advantages and Disadvantages of a phased approach Characteristics of a phase model V-model versus Incremental or Evolutionary development models How to deal with large impact decisions The simplified hierarchy of operational entities in the Product Creation Process form the core of this process Decomposition of the Product Creation Process Commitment of the operational leader to the project charter The Operational Triangle of responsibilities; The operational leader commits to the timely delivery of the specification within the agreed budget, with the "standard" quality level The operational teams managing the Product Creation Process.. 23

11 4.1 The deviation of the actual direction of product development with respect to the desired direction as function of the time Example with different feedback cycles (1, 2, and 3 months) showing the time to market decrease with shorter feedback cycles Four different schools of architecting, showing the presence of the architect in relation to the policy and planning process and the product creation process Theoretical versus Practical system architecture work in relation to the development life cycle Feedback per development phase The main System Architecture activities in the Business Context Map of the System Architecture Process and neighboring processes Contribution of to the the Coupling of Policy and Planning Process and the Product Creation Process Projects versus Products Convergence of Projects and Products Simplified process diagram for project business Example of extensive complex of services for smart phone type of device Model of operational services showing that the boundary between provider and customer can be defined at different levels System of Systems and the consequences of this approach Typical Development of a System Architect Generalist versus Specialist; depth versus breadth Generalists and Specialists are both needed in complex products, they have complementary expertise Growth in technical breadth, intermediate functions from specialist to system architect Four quadrants to classify architect and titles System Roles mapped on the development life cycle Deliverables of a system architect consists of artifacts forming a stack of paper when printed More specific list of deliverables of a System Architect The primary responsibilities of the system architect are not tangible and easily measurable (Incomplete) list of secondary responsibilities of the system architect and the related primary owner October 20, 2017 version: 1.8 page: xi

12 9.5 The System Architect performs a large amount of activities, where most of the activities are barely visible for the environment, while they are crucial for the functioning of architects Bottom up elicitation of high level views The visible outputs versus the (nearly) invisible work at the bottom The function profile of the systems architect The function profile of the test engineer The function profile of the developer The function profile of the operational leader The function profile of the line manager The function profile of the commercial manager Connecting System Specification to Detailed Design From system to Product Family or Portfolio Product Family in Context Architecture: the Essence of System and Context Positioning design and engineering in the dynamic range of abstraction levels Frequently observed gaps in practice Interaction styles for architects Classification of Architecting Tools Quadrant analysis of computerized and human tools Tools Support Processing of Large Amounts of Details From Data to Understandable Information Data Flow Early in Creation Process Data Flow Mapped on Pyramid Formality Levels in Pyramid The CAFCR model Five viewpoints for an architecture. The task of the architect is to integrate all these viewpoints, in order to get a valuable, usable and feasible product CAFCR can be applied recursively Which person is the customer? CAFCR+ model; Life Cycle View The flow of requirements System as a Black Box October 20, 2017 version: 1.8 page: xii

13 15.3 A simplified process decomposition of the business. The stakeholders of the requirements are beside the customer self, mainly active in the customer oriented process and the product creation process Requirements for Requirements The key driver graph of a Motor way Management System The flow from Key Drivers via derived application drivers to requirements Method to define key drivers Recommendations when defining key drivers Complementary viewpoints to collect needs The selection process produces a product specification and a phasing and characterization of requirements to prevent repetition of discussion Simple methods for a first selection Quantifiable Aspects for Requirements Selection Some Basic Concepts BAPO framework SWOT analysis Core, Key or Base technology Examples of Business Models Where in the Value Chain? Innovation requires all major contributors Simplified decomposition of the business in 4 main processes Tension between processes Platform strategy adds one layer CAFCR framework for architecting Five viewpoints for an architecture. The task of the architect is to integrate all these viewpoints, in order to get a valuable, usable and feasible product CAFCR can be applied recursively Structure of a roadmap From generic mission to factual roadmap From Market, Product, Technology to People, Process People estimate, discipline view People estimate, program view Roadmap of people skills Operational axis is more dynamic From roadmap to planning October 20, 2017 version: 1.8 page: xiii

14 19.15Example of committal plan Overview of strategic entities Summary of role in business The contents of a typical roadmaps The roadmap is documented at several levels of detail Management based on a limited horizon can result in a binary control of product policy decisions Management with a broader time and business perspective results in more moderate control: work with some more or some less people on the feature Creation or Update of a roadmap in "Burst-mode" The roadmap activities visualized in time The roadmap is used to create a budget and resource allocation. The operational programs and projects use more detailed plans for control Three planning tiers and their characteristics Earn Credit and Work by Example Bootstrapping the Roadmap Process Bootstrapping the roadmap process requires a repetition of 4 steps, as visualized by this spiral Compared with ideal bathtub curve Market product life cycle phases Examples of product classes on the curve Attributes per phase Different names for development strategies that strive to harvest synergy Advantages which are often claimed for generic developments Drivers of Generic Developments Granularity of generic developments shown in 2 dimensions Modified process decomposition Financial viewpoint of processes Feedback and Value flow Operational Organization of the Product Creation Process, modified to enable generic developments Models for SW reuse The introduction of a new feature as part of a platform causes an additional latency in the introduction to the market Sources of failure in generic developments October 20, 2017 version: 1.8 page: xiv

15 24.1 Methods for Family Analysis Product Family Reference Architecture, zooming in on the views determined by the business analysis and family definition process Questions addresses in the business model The analysis and definition of a family requires a number of iterations over the views in the reference architecture Technical Architecture for a Product Family Subjects requiring special attention for Product Families From Feature Exploration to Valuation per Product Market Feature Map Product Feature Map Example of Valuation Criteria Product Feature Map with substituted Numbers Commercial and Technical Viewpoint on Product Families The relative contribution of software effort as function of time The Control Hierarchy of a system along the Technology dimension Characterization of disciplines, ordered along the level of abstraction Quality Checklist annotated with the relation with software System design aspects that are strongly SW related List of Software Mechanisms that are frequently applied to solve the system level design aspects Managers frequently interacting with architects Comparison of caricature of architect and manager List of modern management techniques that can be used to improve the relation between managers and architects Architectural issues related to managerial viewpoints Characteristics of managers in higher management teams How to prepare Recommended content Mentioned info, shown info and backup info Form is important Don t force your opinion, understand the audience How to cope with managerial dominance Exercise presentation to higher management Schedule of the presentation exercise The relation between sales price, cost price and margin per product Profit as function of sales volume Investments, more than R&D Income, more than product sales only October 20, 2017 version: 1.8 page: xv

16 28.5 The Time Dimension The Hockey Stick What if...? Stacking Multiple Developments Fashionable financial yardsticks The function of an architect is difficult to evaluate Tangible deliverables based upon many invisible activities Criterions for successful architecting Yardsticks for architect assessment degree assessment Ranking as trigger for discussions October 20, 2017 version: 1.8 page: xvi

17 List of Tables 1 Nasty Surprises of Reality xx 2 Critical Success Factors for an effective application of a System Architecture Process xxii 3 Critical Attitude: Examples of questions to be asked by the System Architect xxiii 4 Summary xxiii

18 Introduction This book bundles the articles and intermezzo s produced by the Gaudí project. At this moment the book is in its early infancy. Most articles are updated based on feedback from readers and students. The most up to date version of the articles can always be found at [16]. The same information can be found here in presentation format. Chapters can be read as autonomous units. The sequence choosen here is more or less top down, hopping from one viewpoint to the next. On a regular base a sidestep ("Intermezzo") is being made, either to describe a more fundamental notion, or to propose a more challenging point of view. Note: this book is likely to be refactored in smaller books in the future.

19 System Architecture: The Silver Bullet? Unchangeable Specifications Avoid nasty Surprises Certainty Avoid risks Unchangeable Schedules 0.1 Introduction The expectation level with respect to processes in general and the system architecture process in particular can vary from skeptical to blind faith. The skeptics have experienced that horrible specifications and designs can be pursued under the grand name of Architecture. The followers with blind faith are at the opposite end of the spectrum, their believe in processes inhibits them from seeing the limitations and constraints from the processes applied. The central message of this Intermezzo is: Silver Bullets do not exist. This Intermezzo intends to set realistic expectation levels with respect to the System Architecture Process, and describes the ingredients for successful application. 0.2 Why System Architecture? is a means to create systems efficient and effective, by supplying overview, by guarding consistency and integrity, and by balancing. In other words the System Architect helps the development team to find its way in a rather complex, dynamic and uncertain world. From psychological point of view people apply their own survival mechanisms, when they perceive a threat. One of the most common survival mechanisms is The Quest for Certainty, see subsection

20 Unfortunately will never remove all uncertainties, see subsection The application of a system architecture process can help in the risk management, amongst others by prevention, and by minimizing impact. Successful application of system architecture is far from trivial, section 0.3 describes how the System Architecture Process should be applied to meet the goals of efficiency and effectively The Quest for Certainty This section provides a caricatural view on human behavior based on a free interpretation of the Maslow Hierarchy of Needs, as discussed for instance in [7]. This exaggerated view matches with the security needs in the lower Maslow Hierarchy. Note that less defensive behavior can be triggered by needs in the higher layers, were words such as adventurous en explorative are being used. The majority of people, including managers and engineers, have a need for certainty. Their ideal is to have stable, unchangeable sets of specifications, schedules et cetera. This (hopefully) isolates them from the nasty surprises of reality see table 1. incompetent people human mistakes lack of collaboration or synergy misunderstanding or miscommunication changing markets fast moving competition unforeseen physical, chemical, mechanical properties mother nature (illnesses, floods) Table 1: Nasty Surprises of Reality Unfortunately these nasty surprises are a fact of life. Our human capability to control these phenomena is quite limited. Risk management can help to be more robust. However risk management certainly does not remove these phenomena and it also does not reduce the consequences to zero. Risk management balances probability, effect, and cost. People with a need for certainty are willing to accept any method or process which promises certainty. In other words certainty appears to be their personal key driver. It is better to rephrase this key driver as to avoid nasty surprises, which is closer to the internal motivation at the one hand and which gives a handle later on to manage the expectations. Figure 1 visualizes these drivers. October 20, 2017 version: 1.8 page: xx

21 Avoid nasty Surprises Certainty Avoid risks Unchangeable Specifications Unchangeable Schedules Figure 1: Personal key driver to avoid nasty surprises Disclaimer; Setting the Expectations to a realistic level The Gaudí Project will not deliver a Plug-and-Play System Architecture Process. System architects which have read all the articles and followed the course will not automatically be successful. The Gaudí project will deliver a large set of consistent background material for system architects. This material ranges from process and architecture principles, providing insight and understanding, to more specific how-to s which provide more directly applicable guidelines. The competent system architect will use the material by customizing it to the specific problem to be addressed. At the same time the system architect will have to interact with the environment to share this customized way of working. Whenever the material is applied literal, this is a strong indication that the organization and the system architect do not work explicit enough on the way of working. 0.3 How: Critical Success Factors Ingredients for an effective application of a system architecture process are shown in table 2. No method or process will function without these critical success factors. A process can not be used as substitute for know how or common sense Know-How The core of the system architecture work is know-how, ranging from pure technology know-how to application and business know-how. Active control on a broad basis is a prerequisite for a system architect. October 20, 2017 version: 1.8 page: xxi

22 Know-How Common Sense Pragmatics Critical attitude Social skills Drive Vision Table 2: Critical Success Factors for an effective application of a System Architecture Process Common Sense Most problems encountered during Product Creation require common sense to solve them. Mechanistic approaches severely limit the solution space, resulting in complex solutions. System architects are capable of "lateral" thinking, allowing solutions in previously unexpected directions Pragmatics The holistic approach can easily derail in a sea of seemingly conflicting requirements and viewpoints. The system architect needs a significant amount of pragmatism to be selective and focused, while being holistic in the back of his mind Critical attitude Clear diagrams, tables with facts and smooth presentations give the impression of high quality and increase the confidence. However these same diagrams, tables and presentations conceal the forgotten, misinterpreted, or underestimated facts. The system architect must always be alert, for instance by asking questions as shown in table Drive A good system architect has a passion for his architecture, it has an emotional value. An architect which is working entirely according to the book, obediently going through the motions, will produce a clinical architecture without drive or ownership. Good architectures have an identity of themselves, which originate in the drive of the architect. Such an architecture is an evolving entity, which is appreciated by the stakeholders. October 20, 2017 version: 1.8 page: xxii

23 Do we address the right problem or requirement? Is the customer/user on-board? Is this design adequate? Consists the input data from facts, wishes or ideas? Do we need so many people for the implementation? Does this process or organization fit the problem? Table 3: Critical Attitude: Examples of questions to be asked by the System Architect Vision The system architect needs to have a vision to be able to provide direction. A vision enables an evolution of existing architectures to desired architectures. Having vision is not trivial, it requires a good understanding of needs (the problem) and means (the solution) plus the trends (opportunities and threats) in both needs and means. 0.4 Summary The one sentence summary of this intermezzo is: Silver bullets do not exist. Table 4 gives a bullet-wise summary. Most people want to avoid nasty surprises Most people are looking for certainty Silver Bullets do not exist System Architecture is not a golden bullet Critical Success Factors: Know-How, Common Sense, Pragmatics, Critical attitude, Drive and Vision Table 4: Summary 0.5 Acknowledgements Hans Gieles suggested improvements to increase the cohesion and the red line in this Intermezzo. Henk Obbink and Angelo Hulshout and many others pointed out that The Golden Bullet should have been The Silver Bullet, which has been changed October 20, 2017 version: 1.8 page: xxiii

24 finally. Adriaan van den Brand pointed out the forgotten change of golden into silver. Eugene Ivanov pointed out that evolution aspects were missing. The result is the addition of vision as critical success factor. Steve R. Nanning indicated unclarity in the abstract and criticized the too negative phrasing of the Quest for Certainty. Stephen Boggess added a question to the list in Section Critical Attitude. Ning Lu added more surprises and critical success factors. October 20, 2017 version: 1.8 page: xxiv

25 Part I Processes

26 Chapter 1 Process Decomposition of a Business customer Customer Roadmap Business Drivers Information Order Product $$ Support Policy and presales sales logisticsproduction service material $$ Planning Process Customer-Oriented Process Technology, Process, and People roadmaps Budgets Product roadmap Budget, plan Product Needs and feedback Product Creation Process Technical Product Documentation Needs and Feedback Product-related processes Needs and Feedback People Technology Process People Technology Process People, Process, and Technology Management Process 1.1 Introduction This chapter positions the system architecting process in a wider business scope. The objective of this chapter is to provide system architects insight in the business processes and especially in the processes where system architects actively contribute. The focus is on companies that create physical products. Other types of businesses, such as solution providers, services, courseware, also need systems architecting. The process structure will deviate somewhat from the structure presented here. See Intermezzo Products, Projects, and Services for a discussion on the processes in these other businesses. 1.2 Process Decomposition The business process can be decomposed in 4 main processes as shown in Figure 1.1. We have on purpose ignored the supporting and connecting processes. This simplification will allow us to get a number of more fundamental insights in the main processes.

27 customer Customer Roadmap Business Drivers Policy and Planning Process Technology, Process, and People roadmaps Budgets Information Order Product $$ Product roadmap Support Budget, plan Product Needs and feedback presales sales Needs and Feedback Product Creation Process Needs and Feedback material logistics production service Customer-Oriented Process Technical Product Documentation People Technology Process Product-related processes People Technology Process $$ People, Process, and Technology Management Process Figure 1.1: Simplified decomposition of the business in 4 main processes The function of the 4 main processes is: Customer Oriented Process performs in repetitive mode all direct interaction with the customer. This process is the cash flow generating part of the enterprise. All other processes only spend money. Product Creation Process feeds the Customer Oriented Process with new products. This process ensures the continuity of the enterprise by creating products that keep the company competitive. In this way the Product Creation Process enables the Customer Oriented Process to generate cash flow in the near future as well. People, Process, and Technology Management Process manages the competencies of the employees and the company as a whole. The competencies of the employees and the company are the main assets of a company. Policy and Planning Process is the management process. The Policy and Planning Process defines the strategy, the long term direction of the company, and it balances the shorter term tensions between the three other main processes. The Policy and Planning Process uses roadmaps and budgets to define the October 20, 2017 version: 1.1 page: 3

28 direction for the other processes. Roadmaps give direction to the Product Creation Process and the People, Process and Technology Management Process. For the medium term these roadmaps are transformed in budgets and plans, which are committal for all stakeholders. customer Customer Roadmap Business Drivers Policy and Planning Process Management Technology, Process, and People roadmaps Budgets Product roadmap Budget, plan Product Needs and feedback material Information Product Creation Process presales sales logisticsproduction service $$ Customer Oriented Process People Technology Process Order Tomorrow's Cashflow Assets Product Product-related processes People and Technology Management Process $$ Support Cashflow Generation Needs and Feedback Technical Product Documentation People Technology Process Figure 1.2: Decomposition of the business in 4 main processes, characterized by their financial meaning The 4 processes as described here are different in nature. The Customer oriented process executes over and over a well defined set of activities. The system architect does not participate in active role in this process. However since the Customer Oriented Process is the main customer of the Product Creation Process, it is crucial that the system architect understands, or better has experienced, the Customer Oriented Process. The system architect is in continuous interaction with many stakeholders, mostly about technical aspects. From this perspective the architect will generate inputs for the People and Technology Management Process. This might even result in participation in this process for instance by coaching, participation in the appraisal process, or participation in technology studies. The number of instances of each process is related to different entities: Customer Oriented Process: Depends on geography, customer base, and supply chain. Product Creation Process: One per entity to be developed, where such an entity can be a product family, a product, or a subsystem. People and Technology Management Process: One per competence, where a competence is a cohesive set of technologies and methods. October 20, 2017 version: 1.1 page: 4

29 Policy and Planning Process: One per business. This is the pro-active integrating process. The evolutionary developments of product variants and new releases are seen as individual instances of the Product Creation Process. For example the development of a single new feature for an existing product is performed by following the entire Product Creation Process. Of course some steps in the process will be (nearly) empty, which does not cause any harm. 1.3 Process versus Organization This process decomposition is not an organization, see Intermezzo What is a Process. A single person can (and often will) fulfill several roles in different processes. System architects specifically spend most of their time in Product Creation Process (circa. 75%), a considerable amount of time in the Policy and Planning Process (circa 20%), and a small fraction of their time in the People, Process and Technology Management Process. Most engineers will spend a small amount of time in the People, Process, and Technology Management Process, working on technologies and capabilities, while the majority of their time is spend in the Product Creation Process. 1.4 Value Chain and Feedback customer Customer Roadmap Policy and Planning Process Technology, Process, and People roadmaps Business Drivers Budgets Product roadmap Budget, plan Product Needs and feedback material Information Requirements and Feedback Feedback Technical Product Documentation People Technology Process Order Value Product Creation Process Product Product related processes $$ People Technology Process Support Customer-Oriented Process $$ People, Process, and Technology Management Process Figure 1.3: The value chain and the feedback flow in opposite direction October 20, 2017 version: 1.1 page: 5

30 The value chain in these processes starts at the assets in the People, Process, and Technology Management Process. The assets are transformed into potential money by the Product Creation Process. The Customer Oriented Process finally turns it into real money. Figure 1.3 shows the value chain. The feedback flows in the opposite direction, from customer via the Customer Oriented Process and the Product Creation Process to the People Technology and Process Management Process. Customer will communicate mostly with sales and service people. Needs and complaints are filtered by the reporting system before the information reaches Product Creation Teams. Only a small part of the customer feedback reaches the People, Process, and Technology management. This simple model explains why the knowledge about the customer gets less deeper in the organization. The consequence is that internal technology and process provides show to little concern for urgent customer or business challenges; the sense of urgency seems to be lacking. We can take preventive measures, such as sending process and technology managers to customer sites, once we are aware of the gap caused by this natural information flow. 1.5 Decomposition of the Customer Oriented Process Information Order Product $$ Support Order Acquisition Material Order Order Realization Product Service Support $$ Customer-Oriented Process Figure 1.4: Decomposition of the Customer Oriented Process The Customer Oriented Process is often the largest process in terms of money. From business point of view it is an oversimplification to model this as one monolithic process. Figure 1.4 shows a further decomposition of this process. The Order Acquisition Process and the Service Support Process are operating quite close to the customer. The Order Realization Process is already somewhat distant from the customer. The owners of all these three processes are stakeholders of the Product Creation Process. Note that these owners have different interests and different characteristics. October 20, 2017 version: 1.1 page: 6

31 1.6 Extended Process Decomposition; Generic Developments customer Policy and Planning Process Product generics roadmap Product roadmap Budget, plan presales Product Creation Process Generic Developments Creation Process generics sales logistics production service Customer-Oriented Process People Technology Process Customer Roadmap Business Drivers Technology, Process, and People roadmaps Budgets Information Order Product $$ Budget, plan Support Product Needs and feedback material Needs and Feedback Technical Product Documentation Product-related processes People Technology Process People Technology Process $$ People, Process, and Technology Management Process Figure 1.5: The Process Decomposition extended with a generic developments creation process Companies which develop product families try to capitalize on the commonality between the members of the product family. This is often implemented by the development of common subsystems or functions. In the diagram 1.5 this is called Generic Developments Creation Process. A wide variety of names is used for this phenomena, such as re-use, standard design, platform et cetera. 1.7 Acknowledgements Discussions with and critical comments from Rard de Leeuw, Jürgen Müller, Henk Obbink, Ben Pronk and Jan Statius Muller helped to shape, to improve the structure and to sharpen the contents of the article "Positioning the System Architecture Process". This intermezzo is based on the first sections of this article. I am grateful for their contribution. Discussion with Ab Pasman helped to remove some architect bias from the process decomposition, by providing a further decomposition of the Customer Oriented Process. Jaap van der Heijden helped to improve the layout of the diagrams and with the document structure. October 20, 2017 version: 1.0 page: 7

32 Chapter 2 What is a Process? formalism is is principle drives process elaborated procedure supported tool in by template abstract specific and executable 2.1 Introduction We rely in this part heavily on the notion of a process. This intermezzo is defining process for the context of this book. We define process, since this word is heavily overloaded in our daily world. We also discuss the relationship of processes with organizations and the drive for process improvement. 2.2 What is a process We use process as an abstracted way of working. A process can be characterized the attributes shown in Figure 2.1 In [10] the following definition is given: A process is an activity which takes place over time and which has a precise aim regarding the result to be achieved. The concept of a process is hierarchical which means that a process may consist of a partially ordered set of subprocesses. This definition parallels the characterization above. It adds explicitly the potential hierarchical decomposition of the process itself. The notion of a process can be seen as one step in an abstraction hierarchy, as shown in 2.2. The most abstract notion in this hierarchy is the principle. A principle is a generic insight that can be used for many different purposes. An example of a principle is decomposition: Whenever we have something big, e.g.