Project
Page
17-654: Analysis of
Software Artifacts
18-846: Dependability Analysis of Middleware
|
Team Name: TEAM 2
Team Members & Roles
Name
|
Email
|
Responsibilities
|
Myung Joo Ko (MSE)
|
mko1@andrew.cmu.edu
|
Requirements, Application, Database Design, Testing, Website
|
Cindy Jen (Senior, ECE)
|
cdj@andrew.cmu.edu
|
Requirements, Application, High Performance, Testing
|
Ryan Frenz (Masters, ECE)
|
rfrenzl@andrew.cmu.edu
|
Requirements, Application, Real Time, Testing
|
Vamshi Ambati (Research Scholar , ISRI)
|
vamshi@andrew.cmu.edu
|
Requirements, Application, Fault Tolerance, Testing
|
Project Title: Sales Inventory System
Baseline Application
Description:
Sales
Inventory tracking, selling and purchasing system in which employees can connect
to the company server to process sales orders, purchase orders and check and
update inventory status in real-time.
Configuration:
• Platform: Linux
• Middleware: EJB
• Language: Java
Third Party Software: MySQL, JBOSS
Baseline
Application Features:
Our
Baseline application would revolve around two main entities Employee and
Administrator. So we define the features of the system with respect to these
two entities as below.
•
V1.0 (Jan 23, 2004)
•
V2.0 (Feb 13, 2004)
Reliability
Requirements:
1)
Preserves status of the available employee connections in the event of Server
failure
2)
Preserves integrity of the database updates or notify user about the failure of
a server
3)
Any server crash would be handled automatically in lesser than 5 minutes.
High
performance Requirements:
1)
System will allow for 20 concurrent clients
2)
The backend database can handle about 1000 inventory items
3)
Systems can handle at least 5 concurrent transactions on different inventory
items
Real-time
Requirements:
1)
The result of a transaction is reflected in the system within 5 sec.
2)
Request search result is returned in about 3 sec.
3)
Salesperson can authenticate to server in less than 5 sec.
Baseline Application
Interfaces :
Requirements :
System
|
Use Cases
|
Acceptance Test Cases
|
Sales Order
|
|
|
|
|
view
|
Purchase Order
|
|
|
|
|
view
|
Inventory
|
|
|
|
|
view
|
User
|
|
|
|
|
view
|
Architecture :
Database Design :
Exception Handlings
Downloads
Version
|
Date
|
Download
|
Baseline End-to-end Demo
|
Feb 6, 2004
|
|
|
Baseline Application v1.0
|
Feb 13, 2004
|
testcases
|
sourcecode
|
|
Fault-Injector and Replication
Manager (Assignment#2)
|
Feb 17, 2004
|
testcases
|
sourcecode
|
Fault-Tolerant Baseline
Application
Measurement Charts
Client
|
Round Trip Time
|
Fault Free Case
|
Faulty Case
|
Single Client
|
|
|
|
20 Clients
|
|
|
|
Scenarios/Interactions
Requirements
Current Status
Downloads
Version
|
Date
|
Download
|
FT Baseline Application v1.0
|
March 22, 2004
|
|
|
Replication Manager
|
March 22, 2004
|
|
|
Measurement Data v1.0
|
March 31, 2004
|
|
|
Measurement Data v2.0
|
March 31, 2004
|
|
|
Real-Time Fault-Tolerant
Baseline Application
Measurement Charts
Client
|
Round Trip Time
|
Fault Free Case
|
Faulty Case
|
Single Client
|
|
|
|
20 Clients
|
|
|
|
Scenarios/Interactions
Current Status
Downloads
High-Performance Real-Time
Fault-Tolerant Baseline Application
Measurement Charts
F
Load
Balancing (view)
Scenarios/Interactions
Current Status
Downloads
Final Presentation (download PDF)