Spicy-stonehenge

From Scube-casestudies
Revision as of 10:10, 31 May 2012 by Chen (talk | contribs)
Jump to: navigation, search

Description

Spicy Stonehenge is an implementation of Apache Stonehenge [1] built on top of the Turmeric SOA platform [2]. Our goal with this project is to create a use case that researchers can use to validate their research and compare results by using a common platform.

Quick Overview

The Stonehenge system is composed of 5 web services, 1 web application and 2 databases.

The services are described as follows:

  • Business Service - Provides the business logic required for the web application to operate.
  • Configuration Service - Acts as a directory where references to all the instances of the web services are kept. Whenever the trader client wants to perform an action, it must first ask the configuration service for an endpoint.
  • Order Processor Service - Whenever a buy or sell order is made, the business service will interact with the Order Processing Service to make the order final.
  • Exchange Service - If a purchase is made in a currency different from that of the wallet used, it gets converted by the Exchange Service which uses real currency data from Google.
  • Quote Service - The quote service provides live quote information from Yahoo Finance. This service can be used directly to query the price of a certain stock symbol. It is also used indirectly whenever an order is placed as the Order Processing Service queries it to find the right price at which to place the order.

In this project, it’s common to see the abbreviations BS and OPS, these refer to the Business and Order Processing services respectively.

The databases run off an Apache Derby server and skeletons for them are also provided as part of this project. This database was not available as part of the original project and was built from scratch.

The web application is built using PHP and most of the code is reused from the original project. Some minor changes have been made to accommodate the new, Turmeric-powered web services.

Business Goals and Domain Assumptions

Business Goals and the Domain Assumptions for the current case study.

Business Goals

Table BG1. Business Goal ID
Field Description
UniqueID ID
Short Name
Type Business Goals.
Description
Rationale
Involved Stakeholders
Priority of accomplishment

Domain Analysis

Strategic Dependency Model and Context Diagram

Domain Model

Scenarios

The scenarios


Table S1: Scenario ID
Field Description
UniqueID ID
Short Name
Related To
Involved Actors
Detailed Operational Description
Problems and Challenges


Additional Material