Object-Process Methodology: A Hidden Secret for SOA Service Design
We design and develop a software system to answer the specific needs of stakeholders. As software engineers, it is our very first job to document their needs. This initial document of requirements is only the beginning of the development of the software system. There are many stakeholders involved i...
Gespeichert in:
1. Verfasser: | |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | We design and develop a software system to answer the specific needs of stakeholders. As software engineers, it is our very first job to document their needs. This initial document of requirements is only the beginning of the development of the software system. There are many stakeholders involved in designing complex systems, each of them holding only part of the needs-based information required for system design. As software engineers, it is our prime job to extract data on all of the needs and knowledge from all of the involved stakeholders and implement this knowledge in the system design. This paper presents a software engineering methodology, called Object-Process Methodology or OPM. It is a complete system engineering, architecting, and system lifecycle modeling approach that can be used by the software engineering community to achieve the desired results for stakeholders expeditiously and as accurately as possible. |
---|---|
ISSN: | 2376-1164 |
DOI: | 10.1109/AMS.2009.36 |