Server Requests
From CSSEMediaWiki
(Difference between revisions)
| Line 1: | Line 1: | ||
| − | = | + | = My Project = |
== Background == | == Background == | ||
| Line 26: | Line 26: | ||
*apply & learn better OO techniques | *apply & learn better OO techniques | ||
| − | = | + | = Design Study + |
| + | |||
| + | == Deliverables == | ||
*Classes that model the different request types | *Classes that model the different request types | ||
*Classes that allow requests to be sent over the network | *Classes that allow requests to be sent over the network | ||
Revision as of 08:20, 28 July 2010
Contents |
My Project
Background
My design study is related to my part time job, where I am developing an application that can retrieve and plot data from a device that monitors air quality. The application is connected to a back end server where certain data is stored.
User operations that require communication with the server roughly include:
- Requesting help (and that the user be contacted)
- Electronically registering a device
- Calibrating a device - data about the calibration process is uploaded
Additionally, server communication is needed when the application:
- Authenticates with the server
- Pings the server to ensure network connectivity
My goal here is to create a design for the application side server interface framework. HTTPS POST requests are to be used to transfer data to the server.
Requirements
As this is a just a part of the app, the requirements are largely self imposed & generic:
- something that works
- is as nicely designed as practical
- is as easy to understand and maintain as practical
- is flexible so that new server requests can be added without much hassle
And not to forget:
- apply & learn better OO techniques
= Design Study +
Deliverables
- Classes that model the different request types
- Classes that allow requests to be sent over the network
