loading...
 This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Second IEEE International Symposium on Service-Oriented System Engineering (SOSE'06)
Formal incremental requirements specification of service-oriented automotive software systems
Shanghai, China
October 25-October 26
ISBN: 0-7695-2726-4
ASCII Text
x 
 
J. Hartmann, S. Rittmann, D. Wild, P. Scholz, "Formal incremental requirements specification of service-oriented automotive software systems," Service-Oriented System Engineering, IEEE International Workshop on, pp. 130-133, Second IEEE International Symposium on Service-Oriented System Engineering (SOSE'06), 2006.
 
 
BibTex
x
 
@article{ 10.1109/SOSE.2006.16,
author = {J. Hartmann and S. Rittmann and D. Wild and P. Scholz},
title = {Formal incremental requirements specification of service-oriented automotive software systems},
journal ={Service-Oriented System Engineering, IEEE International Workshop on},
volume = {0},
year = {2006},
isbn = {0-7695-2726-4},
pages = {130-133},
doi = {http://doi.ieeecomputersociety.org/10.1109/SOSE.2006.16},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - CONF
JO - Service-Oriented System Engineering, IEEE International Workshop on
TI - Formal incremental requirements specification of service-oriented automotive software systems
SN - 0-7695-2726-4
SP130
EP133
A1 - J. Hartmann,
A1 - S. Rittmann,
A1 - D. Wild,
A1 - P. Scholz,
PY - 2006
KW - null
VL - 0
JA - Service-Oriented System Engineering, IEEE International Workshop on
ER -
 
J. Hartmann, Technische Universit?t M?nchen, Germany
S. Rittmann, Technische Universit?t M?nchen, Germany
D. Wild, Technische Universit?t M?nchen, Germany
P. Scholz, Fachbereich f?r Informatik, Germany
In this paper, we introduce a simple but formal service description language (ForSeL) for modelbased requirements engineering.

The basic notion in ForSeL is a service representing a functional requirement. Each service describes a system "re"-action that is triggered by a set of input actions -- (but only) if an additional precondition holds. The functional part of a specification is then obtained by the combination of a finite number of services. We pay special attention to two kinds of preconditions which are often mixed up in practice: sufficient and necessary preconditions. Moreover, we present refinement concepts for services that enable a stepwise development of functional requirements.

Citation:
J. Hartmann, S. Rittmann, D. Wild, P. Scholz, "Formal incremental requirements specification of service-oriented automotive software systems," sose, pp.130-133, Second IEEE International Symposium on Service-Oriented System Engineering (SOSE'06), 2006
Usage of this product signifies your acceptance of the Terms of Use.