ElectionSystemCaseStudy
Kevin Brightwell edited this page Aug 26, 2015
·
1 revision
General
- Wiki Home
- FAQ Frequently asked questions
- Examples
- Presentations
- PhilosophyAndVision
- Best practices for using Umple
- Publications and theses
- Tutorials
- Installing Eclipse plugin
Developers
- Developer Setup
- UmpleOnline Setup
- Contribution Process
- Architecture
- Cheat sheet
- Umpleonline manual tests
- Planned development
- DraftManualPages
Server maintenance
External
Other
Clone this wiki locally
Introduction
This is currently under development.
This document walks through building an elections system using Umple. This case study is still under construction.
Targets
The case study covers building the election system using two languages:
- Java - The Java version is a stand-alone application. There is a controller for every use case. The controller calls data services if required to perform database operations.
- Php - The Php version needs some extra work using JavaScript, Ajax and HTML especially at front-end. Umple is used here to build services and domain objects. There is an entry page/link for every use case. This page is supported by JavaScript to communicate with the User and Ajax to communicate with the controller. The controller is a php file. This Php file is created outside Umple. The controller calls code from services to build the output in response to Ajax requests. Communications are made using JSON.
- Shared Features
- Domain objects are shared among the two applications.
- Both version use the same MySQL database (this can be replace by your own choice of database).