1 / 12

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata

SPE-RFI Response Part 2 by Nihon Unisys. Needs for Software Development Model 1999.2.17. Hiromichi Iwata (Hiromichi.Iwata@unisys.co.jp) Information Technologies & Services Nihon Unisys, Ltd. (tel)+81-3-5546-7104 (fax)+81-3-5546-7848. 2-01. SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata.

lexi
Download Presentation

SPE-RFI-R ： FEB.1999 ： NUL-ITD-Iwata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SPE-RFI Response Part 2 by Nihon Unisys. Needs for Software Development Model 1999.2.17. Hiromichi Iwata (Hiromichi.Iwata@unisys.co.jp) Information Technologies & Services Nihon Unisys, Ltd. (tel)+81-3-5546-7104 (fax)+81-3-5546-7848 2-01 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

  2. 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 3 -----------> 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. 2-02 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

  3. 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 2-03 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

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

  5. 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. 2-05 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

  6. 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 2-06 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

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

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

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

  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 ? 2-10 SPE-RFI-R：FEB.1999：NUL-ITD-Iwata

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

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

More Related