Peter McIntyre

Overview of the WSA500 programming assignment in the Fall 2013 semester.

.

Link to specifications document 1, for work due on November 8.

Link to specifications document 2, for work due on November 15.

Link to specifications document 3, for work due on November 22.

Link to specifications document 4, for work due on November 29.

.

Idea and overview

Gather data that will be used in a future ‘campus locations directions/finder’ app.

How this web service will be used

A mobile device (running iOS) will have an app that will enable an ‘editor’ to gather data about ‘spaces’ and ‘openings’ in the SEQ and TEL buildings on campus. (You do not have to write the app in this web services course. You can test your work with Fiddler or an HttpClient instance.) The data will describe and locate the space or opening.

A ‘space’ is a classroom, corridor, office, or any other area in the building.

An ‘opening’ joins two spaces. Often it’s a doorway, but it doesn’t have to be. (For example, when two corridors meet, there’s usually no doorway.)

As noted above, an ‘editor’ will be able to add (and edit) data. Anonymous users will be able to view some data, but will not be able to make changes.

How to get started 

Create a new project, named “Locations”. If you wish, you can create it as a new and clean app, or you can use a ‘template’ app as a foundation.

Next, think about the problem that you’re trying to solve.

Then, begin creating the app domain data model classes. Study the “Class diagram” below. Create some test data in the store initializer.

Finally, for the Building entity, write code for the view models, repository, and controller. This work is due on Friday, November 8.

.

Class diagram

Click to open the diagram full-size in a new tab/window:

.

Due dates

The following table briefly describes the due dates.

Due date	Complete these tasks	Marks
Fri Nov 8, 1:30pm	App domain model classes Store initializer, adds these objects: two buildings (TEL, SEQ) two spaces (one classroom, one corridor) one opening (between the two spaces) Building entity support, includes: view model classes repository controller (for get-all and get-one only) Deployed on an Azure web site	5
Fri Nov 15, 1:30pm	Space entity support, includes: view model classes repository controller (for get, post, put, delete) photo (update, and deliver) Deployed on an Azure web site	5
Fri Nov 22, 1:30pm	Opening entity support, includes: view model classes repository controller (for get, post, put, delete) Deployed on an Azure web site	5
Fri Nov 29, 1:30pm	All done and tested Deployed on an Azure web site	15

.

.

.

.

.

.

.

.