Service Views: a Coherent View Model of the SOA in the Enterprise

Ibrahim, Dayang Hanani Abang; Mišić, Vojislav B.

doi:10.1109/scc.2006.91

Cited by 6 publications

(3 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Both the RiSE process and SOMA present a well-structured and focused template for the architecture documentation. This characteristic seems appropriated, since serviceoriented architectures should be well documented using different views in order to address the concerns of the different stakeholders involved in the project and the quality attributes of the SOA (Ibrahim and Misie, 2006).…”

Section: Architecture Documentation Activitymentioning

confidence: 99%

“…Figure 5.14 shows the inputs, outputs, tasks and roles of the architecture specification activity. The architectural views that can be produced to represent the concerns of the stakeholders involved in the project, and the quality attributes of the SO-PLA are presented next (Kruchten, 1995;Ibrahim and Misie, 2006 activities are represented in their respective layer. Figure 5.15 depicts a layer view example with some services categorized.…”

Section: Checklistmentioning

confidence: 99%

See 1 more Smart Citation

SOPLE-DE: An Approach to Design Service-Oriented Product Line Architectures

Medeiros

Almeida

Meira

2010

Software Product Lines: Going Beyond

View full text Add to dashboard Cite

educational support to get here. Next, I would like to thank CNPq for the financial support, which helped me to live in Recife during my master degree. Without this support, I could not spend my time researching and trying to do my best to complete this dissertation on time. The results of this dissertation could not be achieved without the support of the Reuse in Software Engineering (RiSE) group. My gratitude to the RiSE members for their patience during the experiment, seminars, presentations, and discussions about my work. Some key researchers in the software reuse area offered valuable feedback for this work. My gratitude to John McGregor and Sholom Cohen for their suggestions during our discussions that improved the quality of my work. Finally, I would like to thank my great family, friends, and my wonderful girlfriend. Especially, my parents that always stood by me with everything I needed during my life, and my girlfriend for her patience and comprehension. v

show abstract

Section: Architecture Documentation Activitymentioning

confidence: 99%

Section: Checklistmentioning

confidence: 99%

SOPLE-DE: An Approach to Design Service-Oriented Product Line Architectures

Medeiros

Almeida

Meira

2010

Software Product Lines: Going Beyond

View full text Add to dashboard Cite

show abstract

“…The maintainer needs details for all the views related to Module viewtype (regarding decomposition, generalization, uses and layers) and almost all from Component-andconnector viewtype (shared data, communicatingprocesses, peer-to-peer and client-server). Another model, dedicated to service oriented systems and called Service Views (Ibrahim, 2006), considers the maintenance staff as part of the category "production support". It defines a special group of quality attributes dedicated to maintenance, which are important for the service providers and crosscut eight specific views.…”

Section: Evolution Laws and Modelsmentioning

confidence: 99%

Evolvability in Service Oriented Systems

Ioniţă¹,

Litoiu²

2010

Proceedings of the 5th International Conference on Software and Data Technologies

View full text Add to dashboard Cite

The paper investigates the evolution and maintenance of service oriented systems deployed in SOA and cloud infrastructures. It analyzes the challenges entailed by the frequent modifications of business environments, discussing their causes, grasping the evolution points in service architectures, studying classifications of human actors involved across the whole life cycle, as well as pointing out possible risks and difficulties encountered in the process of change. Based on the lessons learned in our study, four pillars for improving service evolvability are identified: orientation towards the users, increasing the level of abstraction, supporting automation and enabling adaptivity through feedback loops.

show abstract

Applying View Models in SOA: A Case Study

Ioniţă

Florea

2010

Lecture Notes in Electrical Engineering

View full text Add to dashboard Cite

Service Views: a Coherent View Model of the SOA in the Enterprise

Cited by 6 publications

References 7 publications

SOPLE-DE: An Approach to Design Service-Oriented Product Line Architectures

SOPLE-DE: An Approach to Design Service-Oriented Product Line Architectures

Evolvability in Service Oriented Systems

Applying View Models in SOA: A Case Study

Contact Info

Product

Resources

About