Formal incremental requirements specification of service-oriented automotive software systems

Author(s):  
J. Hartmann ◽  
S. Rittmann ◽  
D. Wild ◽  
P. Scholz
Author(s):  
Jaroslac Král ◽  
Michal Žemlicka

Service-oriented software systems (SOSS) are becoming the leading paradigm of software engineering. The crucial elements of the requirements specification of SOSSs are discussed as well as the relation between the requirements specification and the architecture of SOSS. It is preferable to understand service orientation not to be limited to Web services and Internet only. It is shown that there are several variants of SOSS having different application domains, different user properties, different development processes, and different software engineering properties. The conditions implying advantageous user properties of SOSS are presented. The conditions are user-oriented interfaces of services, the application of peer-to-peer philosophy, and the combination of different technologies of communication between services (seemingly the obsolete ones inclusive), and autonomy of the services. These conditions imply excellent software engineering properties of SOSSs as well. Service orientation promises to open the way to the software as a proper engineering product.


Author(s):  
Jaroslav Kral ◽  
Michal Zemlicka

Service-oriented software systems (SOSS) are becoming the leading paradigm of software engineering. The crucial elements of the requirements specification of SOSSs are discussed as well as the relation between the requirements specification and the architecture of SOSS. It is preferable to understand service orientation not to be limited to Web services and Internet only. It is shown that there are several variants of SOSS having different application domains, different user properties, different development processes, and different software engineering properties. The conditions implying advantageous user properties of SOSS are presented. The conditions are user-oriented interfaces of services, the application of peer-to-peer philosophy, and the combination of different technologies of communication between services (seemingly the obsolete ones inclusive), and autonomy of the services. These conditions imply excellent software engineering properties of SOSSs as well. Service orientation promises to open the way to the software as a proper engineering product.


2008 ◽  
pp. 462-476
Author(s):  
Jaroslav Kral ◽  
Michal Zemlicka

Service-oriented software systems (SOSS) are becoming the leading paradigm of software engineering. The crucial elements of the requirements specification of SOSSs are discussed as well as the relation between the requirements specification and the architecture of SOSS. It is preferable to understand service orientation not to be limited to Web services and Internet only. It is shown that there are several variants of SOSS having different application domains, different user properties, different development processes, and different software engineering properties. The conditions implying advantageous user properties of SOSS are presented. The conditions are user-oriented interfaces of services, the application of peer-to-peer philosophy, and the combination of different technologies of communication between services (seemingly the obsolete ones inclusive), and autonomy of the services. These conditions imply excellent software engineering properties of SOSSs as well. Service orientation promises to open the way to the software as a proper engineering product.


Author(s):  
Mario Trapp ◽  
Soeren Kemmann ◽  
Ralf Kalmar ◽  
Christian Denger

2010 ◽  
Vol 20-23 ◽  
pp. 992-997 ◽  
Author(s):  
Qing Wu ◽  
Shi Ying ◽  
You Cong Ni ◽  
Hua Cui

Service-oriented software systems are inherently complex and have to cope with an increasing number of exceptional conditions in order to meet the system’s dynamic requirements. This work proposes an architecture framework which has exception handling capability. This framework ensures the credibility of service-oriented software, during the architectural stage, by adding exception handling-related architecture elements and modeling exception handling process. It allows a clear separation of concerns between the business function and the exception handling unit, using reflection mechanism. It plays an important guiding role for achieving reliable service-oriented system.


2021 ◽  
Vol 2083 (3) ◽  
pp. 032095
Author(s):  
Zhimin Ni ◽  
Fan Zhao

Abstract For the existing service-oriented software single, favors business processing, cannot guarantee the software business processing into the development of software. When the operator encounters operational problems, software failure problems and other problems related to software operation and operation, software development technicians to provide technical support to ensure the software’s business processing functions. This study will move away from dependence on other software and provide technical support to business software operators accurately and in a timely manner to effectively solve the problems that operators may encounter.


2009 ◽  
Vol 50 ◽  
Author(s):  
Jérémy Besson ◽  
Albertas Čaplinskas

In the last decade the component technologies have evolved from object-oriented to serviceoriented ones. Services are seen as utilities based on a pay-for-use model. This model requires providing and guaranteeinga certain Quality of Service (QoS). However, QoS and even a service itself can be defined and understood in many different ways. It is by far not obvious which of these approaches and in what extent they should be used when developing service-oriented software systems. This paper analyzes the notion of QoS namely from this point of view.


Sign in / Sign up

Export Citation Format

Share Document