Integrating Service Specifications at Different Levels of Abstraction

Rittmann, Sabine; Fleischmann, Andreas; Hartmann, Jochen; Pfaller, Christian; Rappl, Martin; Wild, Doris

doi:10.1109/sose.2005.18

Cited by 4 publications

(2 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…S.Rittmann et al propose a methodology for a stepwise re¿nement of service speci¿ca-tions on different levels of abstraction [13]. The B method is applied to SOA for service veri¿cation [15].…”

Section: ) Speci¿cation-based Testing Techniquementioning

confidence: 99%

Service-oriented modeling using the SOFL formal engineering method

Miao

Liu

2009

2009 IEEE Asia-Pacific Services Computing Conference (APSCC)

View full text Add to dashboard Cite

Service-oriented computing advocates the development of new software or services on the basis of existing services. This paradigm shows a great potential of achieving high productivity and low cost, but it faces a challenge in ef¿ciently and correctly using existing services in producing a new application and ensuring its reliability. Building a formal model using a formal speci¿cation language allows the developer to thoroughly understand what existing services are needed for the new application, but how to construct the model so that it can effectively facilitate the developer to recognize the appropriate services still remains an open problem. In this paper, we describe an approach to applying the SOFL formal engineering method to the modeling of a service-oriented system by means of a case study. In particular, we focus on the issue of how to apply the SOFL three-step modeling approach to the construction of a formal speci¿cation for a service-based system, exploring the general principle and speci¿c techniques for reusing existing services in developing a system model.

show abstract

Section: ) Speci¿cation-based Testing Techniquementioning

confidence: 99%

Service-oriented modeling using the SOFL formal engineering method

Miao

Liu

2009

2009 IEEE Asia-Pacific Services Computing Conference (APSCC)

View full text Add to dashboard Cite

show abstract

“…Users include not only drivers and passengers but also the people in a garage and maintenance staff, perhaps even the people in the production and many more. We call this the functionality level (see [28]). …”

Section: Functionality Level -Users Viewmentioning

confidence: 99%

Automotive software engineering

Broy¹

2003

25th International Conference on Software Engineering, 2003. Proceedings.

View full text Add to dashboard Cite

The amount of software in cars grows exponentially. Driving forces of this development are cheaper and more powerful hardware and the demand for innovations by new functions. The rapid increase of software and software based functionality brings various challenges (see [21], [23], [25], [26]) for the automotive industries, for their organization, key competencies, processes, methods, tools, models, product structures, division of work, logistics, maintenance, and long term strategies. From a software engineering perspective, the automotive industry is an ideal and fascinating application domain for advanced techniques. Although the automotive industry may adopt general results and solutions from the software engineering body of knowledge gained in other domains, the specific constraints and domain specific requirements in the automotive industry ask for individual solutions and bring various challenges for automotive software engineering. In cars we find literally all interesting problems and challenging issues of software and systems engineering.

show abstract