Requirements for service architecture modeling

The development of large and complex software intensive systems, among other issues, means various stakeholders related to software architecture modeling. Various stakeholders concern different aspects of software development, e.g. management, testing, component engineering or product marketing. Therefore, fluent communication between various stakeholders may become a difficult and confusing issue in software development. This paper introduces the requirements for service architecture modeling. The requirements include definitions of four viewpoints at two levels of abstraction. The rationale for two levels and four viewpoints required in service architecture modeling are introduced first. In addition, this paper also defines the viewpoints by means of concerns, stakeholders and artifacts. This paper also maps the service architecture description approach to the OMG’s model driven architecture approach. The service architecture modeling approach introduced here improves communication among different stakeholders and increases reusability of higher-level architecture descriptions.