4.3.2 An Information Model for Integrating Product Development Processes

Abstract

This paper describes some of the work products used or generated during the development of a softwareintensive system by integrated product teams (IPTs) working on the system elements. An information modeling approach represents the relationships among the information entities involved in the system-level management, design, verification, integration, and testing activities: the model has been extended to the subsystem, configuration item, and component levels. The purpose of the information model is to provide developers with additional knowledge about the work products composing the information flows defined in a process model. This additional knowledge makes it easier to adopt the process model, tailor it for use on a project, and understand the roles of the IPTs and their members.

3 The Future Systems Engineering Data Exchange Standard STEP AP‐233: Sharing the results of the SEDRES Project

“…For instance, there is work being performed within the INCOSE working groups (see the document Requirements for an Integrated Systems Engineering Environment, produced by the Tools Integration and Interoperability Working Group and available via www.incose.org/cmtes/tiiwg.html, and Jones et al, 1997, from the Requirements Working Group). There is also relevant work reported in groups outside INCOSE, such as the Software Productivity Consortium that may be relevant (Lykins et al 1998). Clearly other relevant areas of work will also emerge from the AP-233 working group attendees experiences.…”

“…Work in other areas outside the STEP community is also important, and needs to be considered. (Lykins et al 1998). Clearly other relevant areas of work will also emerge from the AP-233 working group attendees experiences.…”

5.3.3 Review of Papers Concerning Engineering Teams in INCOSE Symposia 1991 to 2002

“…IPPD is a methodology that reflects a systems approach in the development of products, but it is only effective when the IPTs are linked by Cross Product Teams to effect integration, and when the people are committed to the process (Dube, 1998). The problem of poor communication is the major potential weakness in the IPPD approach, with the problem of interteam communication, which relates to the quality of system integration, being the most serious (Lykins et al, 1998). One strategy to assist effective IPT operation is the commencement of teams with a short team building course (Wilson et al, 1998).…”

“…Another strategy is to provide IPTs with some training in SE process, in order that they will appreciate the context in which they work, and contribute in the correct way (Topf and Bellagamba, 1998). The solution to the communication problem presented by Lykins et al (1998) was to develop an Object Oriented model of information to form the framework of communication between IPTs in the project. Brezinski (1998) asserts that IPTs are a good organizational approach, but that in matrix organizations this results in dual reporting structures, which is very difficult.…”