Project Thor Part 2: Assumptions and Business Requirements

In Part 1 of this series I described the problem we're trying to solve with Project Thor. In this part I'll go through the assumptions and business requirements.

Assumptions

1. Users will have a smart phone capable of supporting the Microsoft Tag Applet
2. Users will have an active internet connection to their mobile device
3. Users accessing the Thor Service will have an account on the source Exchange infrastructure
4. Users will have a browser on their mobile device capable of supporting Java Script

Business Requirements

1. Users will create unique Microsoft Tags for each resources to be access via Project Thor’s Services
2. The recognition and processing of these tags will be done by the Microsoft Tag Smart Phone Applet
3. The content returned to the smart phones as part of the Tag resolution process will supported on all Smart Phone OS’s supported by Microsoft Tag (Browser Neutral)
4. When the user is redirected to the Thor Service, they will be prompted for UserID, Password and Domain account and given the option to remember this for future requests
5. The user will be provided with the current schedule for the resource requested in a visually pleasing format
6. The user should have the ability to “book” the resource from the Thor UI.
7. The Booking feature must be configurable to allow a different account than that of the resource to be the target of the request (Conference room schedules may not be monitor but be schedule via a common email like MNConferenceRooms)
8. The Thor Service must be configurable to allow the modification of the Exchange Services URL

In the next part of this series I'll walk through our technical requirements.

Stay tuned...

(P.S. sorry for the odd formatting, Ning is a little limited when it comes to formatting one's blog posts)