Abstract – This paper describes ongoing research exploring systems thinking at the team level. Termed collaborative systems thinking by the authors, the concept of higher level systems thinking is envisioned as a means both to build workforce competency and to explicitly deal with system complexity at a higher level within an organization. This paper introduces the key research questions, an initial definition of collaborative systems thinking, demographic and technical motivators, and summarizes the research progress to date and plan for completion. The results of this research will inform the design of technical processes and provide empirical knowledge to support workforce development interventions aimed at developing systems thinking within engineering teams. The role of organizational culture is also considered as a factor in enabling collaborative systems thinking.

This paper discusses the topic of functional behaviour representations from a data exchange point of view. The motivation comes from our work with developing a standard information model for systems engineering data exchange — ISO 10303-233. In this setting it is not sufficient that the exchanged model displays the same behaviour as the original one. When possible, the structure of the original specification shall be maintained. The paper reviews behaviour formalisms identified as being relevant to systems engineering and discusses different options for supporting the behaviour formalisms in the ISO10303-233 systems engineering data exchange information model. The structure of the functional behaviour part of the current

Copyright © 2007 by Caroline Lamb and Donna Rhodes. Published and used by INCOSE with permission. Abstract. Standardized processes are being used to address three issues in engineering today: increasing system complexity; shifting demographics; and longer development cycles that result in a dearth of experiential learning for young engineers. There is obvious value in having engineers who can see the big picture and effectively broker design tradeoffs: engineers capable of systems thinking. However, what is the impact of standardized processes on the ability of teams of engineers to make these critical tradeoffs? This paper lays the groundwork for research investigating ways in which standardized process usage facilitates or hinders systems thinking within engineering teams—termed collaborative systems thinking.

The System Architecture Process is positioned in the business context. This process bridges the gap between the Policy and Planning Process and the Product Creation Process.

This article or presentation is written as part of the Gaudf project. The Gaudf 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

This article describes the course System Architecture by the Center for Technical Training CTT[4]. Trainer is the author of this article Gerrit Muller. At this moment this course is only accessible for Philips Employees.

This book bundles the course descriptions of courses based on the Gaudi systems architecting material. The courses address systems architecting, stakeholders and requirements engineering.

This article describes the condensed version the course System Architecture by the Center for Technical Training CTT. Trainer is the author of this article Gerrit Muller. At this moment this course is only accessible for Philips Employees.

Present-day products contain one order of magnitude more software code than is actually needed. The causes of this bloating are explored. If we are able to reduce the bloating significantly, then the product creation process is simplified tremendously. Potential handles to attack the bloating are discussed. 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: http://www.extra.research.philips.com/natlab/sysarch/ version: 1.2 status: finished 1st April 2004 1

The stakeholder part of the Embedded Systems Architecting (ESA) course is described. The program existing of 6 modules is described. The course format, iterating theory, illustration and interaction is explained.