Prototype Report

Construction Meeting Minutes Application

Team number 6

1. Pradeep Muruganandam - Prototyper and Quality Focal Point2. Dennis Evans - System Architect, Project Manager3. Pavan Lingambudhi Seshadri Vasan - Requirements Engineer 4. Sideok You - Feasibility Analyst 5. Shengyi Chen - Operational Concept Engineer6. Nguyen Tran - IIV & V 7. Qichen Gu - Life Cycle Planner

10/15/2015

Version HistoryDate Author Version Changes made Rationale

10/14/15 PM 1.0 • Original for CSCI577a; Tailored from ICSM OCD Template • To fit CS577a course content

10/15/15 PM 1.1 • Added images and other community feats

• To add more benefit chain and deign new systems.

10/15/15 PM 1.2 • Added new details about the changed prototype

Fixed the suggestions given by client and the changes told by Faculty.

Table of ContentsPrototype Report 1Version History 2Table of Contents 4Table of Tables 5Table of Figures 61.Introduction 12.Navigation Flow 23.Prototype 33.1. Login Page 43.2 Dashboard Page 63.3 New Meeting Page 73.4 New Task Page 83.5 Notification 9

Table of TablesPrototype Report 1Version History 2Table of Contents 4Table of Tables 5Table of Figures 6Table 1: Mobile App Login Page 4Table 2: Dashboard Page 6Table 3: New Meeting Page 7Table 4: New Task Page 8Table 5: Notification 9

Table of FiguresPrototype Report 1Version History 2Table of Contents 4Table of Tables 5Table of Figures 6Figure 1: Navigation Flow of the Prototype System 2Figure 2: Mobile App - Login Page Prototype 5 Figure 3 - Mobile App - Dashboard Page Prototype 7Figure 4 - Mobile App - New Meeting Page Prototype 8 Figure 5 - Mobile App - New Task Page Prototype 9Figure 6 - Mobile App - Notification Prototype 10

1. IntroductionPrototype Report: A prototype is an early sample, a working model or small release of a product built to test a con-cept or process and get feedback from user about it.

It gives the client an idea about how the application is going to look when it is developed. It also gives the development team an opportunity to experiment on new technology stack by develop-ing a working sample to see the compatibility and usability for the given use case.

Eg. A new database technology, a new device driver compatibility, a cloud solution could all be factors for compatibility issues. So, a prototype of a working model using them could be benefi-cial to understand the working of the technology as well as a good reusable module code for the software during development. This report details the progress we have made with respect to the Prototype. We can do incre-mental prototyping to steer clear of bigger problems in the product in later stages of develop-ment. So, we keep track of the changes we make in the Prototypes soon after getting feedback from client and maintain it up to date.

Current status:

Week 5: A. UI Prototypes - Using Balsamiq - For Manager view, tasks, and another prototype for Notifi-

cations.B. Working sample Google App Engine Storage Prototype - To see compatibility of the cloud

app deployment and storage for the use case.

To be tracked and updated in coming weeks……

1

2. Naviga- tion Flow

Figure 1: Navigation Flow of the Prototype System

2

Construction Meeting Minutes

App

Login

Manager / Supervisor View

Notifications

Create Meeting

View Dash-board

Create Fol-low Up Meet-

ing

View Meeting

View/Up-date Min-

utes

Create Project

Edit Meet-ing

Publish MeetingSearch Min-

utes

View Meeting

3. PrototypeTop Risks associated with our project:

• Clean usable User InterfaceA. Our critical-success stakeholders need the most usable and easier User Interface so

that it has to have not only intuitive looking, but also direct understanding how to use it.

B. A prototype using a prototyping tool, which has support for designing mobile UI would be of good help to collect user feedback and incorporate those changes into our UI design when we develop the application.

• A proper data storage and retrieval mechanism that works for mobile applications seamlessly.

A. Clients need to have a storage for maintaining or saving their data into database. In addition, clients need to retrieve data anywhere through their mobile devices.

B. Our developer team lacks experience storing data on a cloud server from mobile ap-plications.

C. A prototype for showing how data could be stored, retrieved on a solution on the cloud, could get us some good idea about using familiar cloud solution tools for our use case.

Prototypes:

• A Clean usable UI => Developed using BalsamiqA. Cost: low cost and high quality(providing free trial)B. It provides tools for designing and developing useful User ExperienceC. It provides sketch function that we can easily draw the app design(called Mockup)

provides lots of UI components & icons(comminuted generated) gives options to add external mockups and own images.

D. The tool is easy to learn for even non-technical people.E. Options to drag and drop icons and elements.F. Created template can be reused for other mockups.G. Helps us collect valuable feedback from end users without designing a real UI.

We have 2 UI prototypes -• The main prototype which shows the Dashboard, meeting creation, task creation,

view meeting. • One prototype for the user ( contractor / manager ) for viewing notifications and us-

ing the App. Link to Prototype : https://www.youtube.com/watch?v=3dBCVt40bPg

Link to Notification Prototype : https://www.youtube.com/watch?v=kZiKFVD49vI

3

3.1. Login PageTable 1: Mobile App Login Page

Description This screenshot shows the Mobile App’s login page to authenticate the users and give the right kind of view, privileges for different stakeholders based on their role.

Related Capa-bility

CR-1 User ManagementWC_3516, WC_3513

Pre-condition Clicking on the Construction Meeting Minutes App icon in the Home Screen takes the user to this screen.

Post condition The user’s credentials are checked and if correct, user is taken to the Dashboard page.

Figure 2: Mobile App - Login Page Prototype

4

3.2 Dashboard PageTable 2: Dashboard Page

Description This screenshot shows the different meeting topics the manager has. There is an option to create a new meeting or click on any meeting to view details about it.

Related Capa-bility

CR-2 - Meeting Minutes Management.

Pre-condition Login by using the right credentials.

Post condition The user's actions can be either the viewing of meeting details or creation of new meeting.

Figure 3 - Mobile App - Dashboard Page Prototype

3.3 New Meeting Page

5

Table 3: New Meeting Page

Description This screenshot shows the page which lets you create a new meeting to add to the list of different meeting topics the manager has. It asks meeting details, and people involved to create the meeting.

Related Capa-bility

CR-2 - Meeting Minutes Management.

Pre-condition Clicking on the New Meeting button icon in the Dashboard takes the user to this screen.

Post condition Meeting is added if all the needed details are present in the fields and people involved are notified.

Figure 4 - Mobile App - New Meeting Page Prototype

3.4 New Task Page

6

Table 4: New Task Page

Description This screenshot shows the page which lets you create a new task to add to the a specific meeting topics the manager chooses. It asks task details, completion date and people involved to create the task.

Related Capa-bility

CR-2 - Meeting Minutes Management.

Pre-condition Clicking on the New Task button icon in Meeting task list takes the user to this screen.

Post condition Task is added if all the needed details are present in the fields and members involved notified.

Figure 5 - Mobile App - New Task Page Prototype

3.5 Notification Table 5: Notification

Description This screenshot shows the notification window coming up on the Home Screen of the phone. Users have the option to choose to view the update or choose to

7

Dismiss it.

Related Capa-bility

CR-3 - Notifications

Pre-condition Have the application installed in the Phone.

Post condition User can choose to see the notifications regarding the meeting task or choose to ignore it.

8

Figure 6 - Mobile App - Notification Prototype

9