SYST36367 - Iteration 1: Prototype

This page summarizes the requirements for this deliverable. Please read this page and the corresponding rubric carefully!

Though this deliverable is due in Week 13 of the course, it is strongly recommended that you begin work on it immediately (Week 10)
as it will require a considerable amount of research, collaboration and discussion to produce a quality result.

Deliverable Requirements

In this deliverable, you are to prototype key elements of your capstone project including:

1. Design Document Feedback

List the changes you made to your user interface based on the feedback from your customer and faculty and how these changes will benefit users

2. User Interface Prototype

Provide access instructions and a URL link to the website where your User Interface Prototype is hosted. This prototype should leverage the Storyboards and Wireframes from your Design Document (Deliverable 3) and incorporate the design feedback described above. The prototype should represent the application in its final form with images, titles, logos, navigation bar, footers, etc. It should model desired workflows accurately, use appropriate controls and be aesthetically pleasing. Also, the pages should provide working links between one another as per the final system.

3. Proof of Concept Prototype

Implement a "Proof of Concept" prototype for the Login use case based on the architecture you describe in the previous deliverable. If you deviate from that architecture, include a modified architecture diagram in this section.

4. Project Technical Risks

Describe two or three technical risks (issues) that you discovered while implementing the Login use case that could jeopardize the project's success

5. Customer Sign Off

Attach the Customer Sign Off form which has been fully completed by your customer.

Submission Requirements

All model diagrams must be created using standard UML notation, unless otherwise noted. The report must include a cover page with the Client’s name, application name, and team members. A table of contents must be provided, with each page numbered with a header and footer. Update he word .docx (_teamname_CapstoneProjectDocument) you have been using and upload it to your team’s SLATE dropbox for this deliverable. Host the UI and login as you specify and provide URL by updating the word .docx The document should look professional and make appropriate use of diagrams, lists, images, tables, graphs and graphics to assist the reader.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License