SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-01 Needs for Software Development Model Hiromichi Iwata Information Technologies & Services Nihon Unisys, Ltd. (tel) (fax) SPE-RFI Response Part 2 by Nihon Unisys.

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-02 General Requirements * Needs for drastic improvement of software development productivity and quality > Modernization of software development activity. * Project maturity level should be at least SEI-CMM Level > Institutionalization and clear definition of the project are essential. * Facilitating the organizational reuse > Information System for organizational reuse should be built. * Overcoming the limitation of I-CASE > Information network (i. e. model) covering all aspects and all life cycles of the project should be created.

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-03 Concepts * Software development activity := One of the business domains in enterprises * In traditional sense, to automate the business domain := To build the information system * There exists a unique information model for specific process / methodology or individual project. * Implementation of the model is resulted in the information system. This brings each project its own software development system. * Domain Specialist of the software development domain := IS people

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-04 Software Development Model Software Development Model Software Development Software Development Software Dev. System Software Dev. System Business Domain Business Domain Information System Information System Model Modeling Implement Order Entry Model Order Entry System Production Control Model Prod. Control System Automobile Body Design Model Body Design CAD

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-05 Enablers * UML facilitates : - understanding the model in a broad range, - also interoperability between various CASE tools * MOF standardizes the repository metamodel. * XMI facilitates the information interchange between tools. * CORBA, DCOM support the distributed objects environment.

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-06 Generic Reference Model of Software Development * Generic model, which contains the types of the elements common to almost all software developments. * It can be easily specialized and adapted to satisfy the specific process / methodology and/or individual project needs. * Resulted model (e.g. UML model diagrams) can be easily implemented on a repository as main part of the project's own information system. * It is constructed by the following packages: - Core Packages activities, deliverables, organization, roles, resources, rules/guides - Tool Integration Package - Subsystems (stereotype of package) a group of support functions

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-07 Level of Abstraction High Low Common Core Model Specialization for the Company Specialization for the Typical Process Specialization for the Specific Project specialize Generic Reference Model Institutionalized Model Typical Process/Methodology Model Specific Project’s Model Three Layers of the Process/Methodology Information Model

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-08 Generic Reference Model Generic Reference Model Information Model for Organizational Reuse Information Model for Organizational Reuse Information System for Organizational Reuse Information System for Organizational Reuse Specific Project’s Process/Methodology Model Specific Project’s Process/Methodology Model Specific Project’s Information System Specific Project’s Information System implement extend model system Generic Reference Model is specialized in various ways and the result is implemented as the specific “Software Development System”. Typical Process/Methodology Model Typical Process/Methodology Model Specialize customize Specialize

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-09 Generic Reference Model Core Package * Activities * Deliverable * Organization * Resources * Rules/Guides Tool Integration Package Subsystems * Configuration Management * Requirement Tracing * Risk Manage- ment * etc.

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-10 Concerns * SPE facility should provide : - Generic Reference Model (or some Metamodel) - Supports for adaptation and customization of the model * General architecture of tool integration must be defined. * Can the generic reference model be defined as a unified one ? * Is any UML extension necessary ?

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata 2-11 Specific Project’s Information System Specific Project’s Model References SPE Facility Language and/or Framework Project’s information system Project’s model metamodels models - Process/Methodology Metamodel - Typical Process Model - Generic Core Mode Implement R e p o s i t o r y tool - Specific Process/Methodology Model - Specific Project’s P/M Model - Information System built from its model Used at run timeUsed at design time worker manager outsiders process engineer

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata END 2-12