Modeling with SoaML: Service identification

Requirements Management Articles

The power of a service-oriented architecture (SOA) is in its ability to enable business agility through business process integration and reuse. SoaML (Service-Oriented Architecture Modeling Language) is an Object Management Group (OMG) standard that is intended to help realize the potential of SOA.

This article describes the business goals and objectives and the business processes implemented to meet those objectives, and then explains how to use the processes to identify business-relevant services necessary to fulfill the requirements that they represent.

The service architecture can realize use cases that capture information about the high-level functional and nonfunctional requirements for the business process from the perspectives of the key external stakeholders or actors. These use cases can be viewed in use case diagrams in Rational Requirements Composer or Rational Software Architect. This maintains the link between the service requirements contract, business processes, the business use case, and the business goals and objectives.

Whether you use business capabilities or service architectures, or both, to identify candidate services is a matter of personal preference. Business capability modeling is a straightforward way to decompose a business into competencies identifying the business capabilities and operations, and the relationships between capabilities needed to meet business objectives. Services architecture modeling provides a more formal way of specifying the participants and contracts governing their interactions. Both approaches can be used together. Use the approach most comfortable for you.

Read the full article on http://www.ibm.com/developerworks/rational/library/09/modelingwithsoaml-1/

software requirements group
Articles Knowledge

Reviewing Requirements for Testability

Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]

Read More
Requirements Management Articles
Articles Knowledge

User Stories for Both Requirements and Testing

User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, […]

Read More
Requirements Management Articles
Articles Knowledge

Understanding System Analysis Models

This article is an extract of the “Complete Systems Analysis” written by James and Suzanne Robertson. It explains the basics of analysis models and emphasize that the important thing to remember is that modeling tools are complementary. Each shows one aspect of the system. Together, they make a complete working model of the system.

Read More

Copyright © 2009-2021 Martinig & Associates