Formal incremental requirements specification of service-oriented automotive software systems

Hartmann, Jochen; Rittmann, Sabine; Wild, Doris; Scholz, Peter

doi:10.1109/sose.2006.16

Cited by 9 publications

(7 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Though most service description techniques are intended for describing the functional requirements of services [5], [16], [28], [29], [35] ; there are a considerable number of approached that aim in giving emphasis to the non-functional requirements too [18], [21].…”

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

“…ForSel (Formal Service description language) is a typical example of such efforts. ForSel describes services by describing the necessary functionalities in terms of finite or infinite reactions [5]. Using calculus of communication systems (CCS) to model behavior of services is also another approach discovered for describing services [33].…”

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

“…For instance, in order to describe services developed for reactive systems, a method named Formal Service description is proposed in [5]. This approach specifies services as a composition of precondition, triggering event and the system reaction.…”

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

“…The same is true in the newly Service Oriented Computing (SOC) paradigm, where one of the consequences, associated with this lack of appropriate RE techniques, is the absence of accurate service descriptions 1 , which will affect other SOC activities like service discovery and service composition [5], [6].…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Systematic Literature Review on Service Description Methods

Teka

Condori-Fernández

Sapkota

2012

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

Abstract. [Context and Motivation]As a result of recent trends in enhancing Service Oriented Requirement Engineering activities, a number of service description methods have been proposed for describing services. The availability of different service description methods can give developers a range of options to choose from so that they can have an appropriate description method that fits best their services. [Question/problem] But there is neither holistic information on service description methods nor a clear understanding of the strengths and weaknesses of each service description method. The aim of this paper is to identify problems of service descriptions that have been researched so far, and the techniques or methods available to tackle these problems. [Principle ideas/results] Thus, to gather this relevant information available in the literature, a systematic review was conducted. A total of 191 articles were examined, of which 24 articles focus on service description related concepts. The results show that, despite the recent efforts in describing the nonfunctional requirements of services through approaches like semantic annotations and policy attachments, there is still a lot to do in enhancing the description of quality aspects of services. Furthermore, this study reveals that a negligible effort is given to the description of consumer oriented services.[Contribution] This paper identifies and analyzes the current service description methods that exist in the literature and explains the pros and cons inherent to these methods

show abstract

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

Section: Functional Vs Non Functional Requirements Description Methodsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Systematic Literature Review on Service Description Methods

Teka

Condori-Fernández

Sapkota

2012

Requirements Engineering: Foundation for Software Quality

View full text Add to dashboard Cite

show abstract

“…The Aspect-Oriented Requirements Engineering (AORE) methodology models the collaboration between several embedded systems in terms of aspects involved [9]. Formal Service description Language (ForSeL) models each functional requirement as a service which holds actions, input triggers and preconditions to be met [10]. EAST-ADL2 is an architecture description language specifically dedicated to automotive systems.…”

Section: Introductionmentioning

confidence: 99%

Using SysML Modeling to Accurately Represent Automotive Safety Requirements

Gulias

Torreblanca

Aguilar

et al. 2016

2016 4th International Conference in Software Engineering Research and Innovation (CONISOFT)

View full text Add to dashboard Cite

Nowadays, software development innovations are heavily found in electronic control units for the automotive sector. Software in this sector has grown considerably, though, the number of vehicle recalls because of software defects has grown accordingly. Because of this situation, different proposals arise in the various phases of the software development life cycle which aim to prevent these defects. In this article, we focus on the automotive requirements section and present, based on ISO standard 26262 and the SysML modeling language, a guide to effective requirement writing, specification and modeling.

show abstract

System Modeling and Simulation

Wasson¹

2005

System Analysis, Design, and Development

View full text Add to dashboard Cite

Formal incremental requirements specification of service-oriented automotive software systems

Cited by 9 publications

References 3 publications

A Systematic Literature Review on Service Description Methods

A Systematic Literature Review on Service Description Methods

Using SysML Modeling to Accurately Represent Automotive Safety Requirements

System Modeling and Simulation

Contact Info

Product

Resources

About