Service-oriented modeling framework

Service-Oriented Modeling is a software development practice that employs disciplines and a universal language to provide tactical and strategic solutions to enterprise problems. Service-Oriented Modeling takes an anthropomorphic view to the modeling process by striving to create models that can be understood by individuals with diverse levels of business and technical understanding. The Service-Oriented Modeling paradigm advocates taking a holistic view of the Analysis, Design, and Architecture of all 'Software Entities' in an Organization. Service-Oriented Modeling encourages viewing Software Entities as 'Assets' [service-oriented assets] , and refers to these assets collectively as 'Services'.

The Service-Oriented Modeling methodology includes a modeling language that can be employed by both the 'Problem Domain Organization' [the Business] , and 'Solution Domain Organization' [the Information Technology Department] , whose unique perspectives typically influence the 'Service' development life-cycle strategy and the Projects implemented using that strategy.

The Service-Oriented Modeling paradigm is based upon the following vision:
* Introduce a state-of-the-art and holistic modeling language that can facilitate an SOA implementation
* Introduce advanced service life cycle concepts and processes that can be employed to manage service-oriented projects
* Enable business and IT personnel to equally partner in service-oriented modeling efforts and to represent their unique perspectives

The Service-Oriented Modeling practice employs the following disciplines that are widely utilized during service-oriented development life cycle:

* "Service-Oriented Conceptualization"
* "Service-Oriented Discovery and Analysis"
* "Service-Oriented Business Integration"
* "Service-Oriented Design"
* "Service-Oriented Conceptual Architecture"
* "Service-Oriented Logical Architecture"

Service-Oriented Modeling Framework

The Service-Oriented Modeling Framework (SOMF) is simply a work structure. It is a high-level map depicting the various components that contribute to a successfulservice-oriented modeling approach (see image).

It illustrates the major elements that identify the “what todo” aspects of a service development scheme. These are the modeling pillars that will enable practitioners to craft an effective project plan and to identify the milestones of a service-oriented initiative—either a small or large-scale business or a technological venture.

The provided image thumb (on the right hand side) depicts the four sections of the modeling framework that identify the general direction and the corresponding units of work that make up a service-oriented modeling strategy: practices, environments, disciplines, and artifacts. Remember, these elements uncover the context of a modeling occupation and do not necessarily describe the process or the sequence of activities needed to fulfill modeling goals. These should be ironed out during the project plan--the service-oriented development life cycle strategy--that typically sets initiative boundaries, timeframe, responsibilities and accountabilities, and achievable project milestones.

References

* cite web
last = Bell
first = Michael
year = 2008
url = http://www.amazon.com/Service-Oriented-Modeling-Service-Analysis-Architecture/dp/0470141115/ref=pd_bbs_2
title = Service-Oriented Modeling: Service Analysis, Design, and Architecture
publisher = Wiley

* cite web
last = Zhang Et Al.
first = Tao
year = 2006
url = http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4032288
title =A Modeling Framework for Service-Oriented Architecture
publisher = IEEE

ee also

Service-Oriented Modeling