Harnessing rCOS for Tool Support—The CoCoME Experience - Formal Methods and Hybrid Real-Time Systems - page 106

Bank

CashdeskGUI

Sale

Ruby

Java

Java

Tomcat+Tuscany Java SCA+JRuby

P

Local Method Call

PostgreSQL

JVM

Local Method Call

Cashdesk

Store

Java

Tuscany Java SCA

JVM

Ruby

reference

service

Tomcat+Tuscany Java SCA+JRuby

PostgreSQL

JVM

Fig. 15. SCA based Implementation

component description. The component implementation can be coded with re-
spect to the component function features and the corresponding rCOS class
design. We have implemented a prototype CoCoME system that contains six
different distributed applications. The system components and their implemen-
tation and running information included in the sale process are shown in Fig.
15. The bold black rectangles represent the independent applications that can
be deployed and run on different machines. The Bank and Store components are
published as Web services, whose WSDL method description can be generated
from the method definitions in rCOS component description, and the SOAP pro-
tocol binding on HTTP is used for the communications between applications. In
addition, the Bank and Store components currently will create a new component
instance for handling each client request.
During the development process, from the rCOS design, the most appropriate
implementation technology can be used for different components, such as the
Ruby language for the Store component, and we can also build the application
based on the generated Java implementation from the rCOS design. The im-
plementation only took two days. This process also corresponds to the spirits
of Agile Software Development (Extreme Programming and Adaptive Software
Development) [27].

4 Enhance Industrial Tool Support: MasterCraft

MasterCraft [31] is developed by TRDCC to support ecient development of
software system. In MasterCraft, different activities at different stages of de-
velopment are performed by project participants in different roles. We see this
distinction as very important, as it allows us to define at which point in the
development process should various models (or informally called artifacts )be
produced , and different kinds of manipulation , analysis , checking and verification
be performed, with different tools. We make the particular roles responsible for
assuring the correctness of the resulting software system.