Prototype Report Version 3.0

Prototype Report Version 3.0 Prototype Report

Leamos

Team Number 7

Secondary Name Email Address Primary Role Role Monty Shah [email protected] Project Manager Life Cycle Planner David Wiggins [email protected] IIV&V Off-campus Shaper Pragya Singh [email protected] System Architect Prototyper Shantanu Requirements [email protected] Feasibility Analyst Sirsamkar Engineer Operational Suchita Doshi [email protected] Prototyper Concept Engineer Swapnil Savdekar [email protected] Life Cycle Planner System Architect

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0

Version History

Date Author Version Changes made Rationale 10/10/11 Suchita 1.0 ● Initial Prototype with the Doshi, ● Original template navigation flow and the Shantanu prototypes with the description Sirsamkar

10/14/11 Suchita 1.1 ● Updated Sections 2 and 3 ● The mock ups are updated with Doshi, more details with more Shantanu screenshots. Sirsamkar ● Updated after Evaluation

10/18/11 Suchita 1.2 ● Added prototype ● The prototype is required for Doshi, managing students. Shantanu ● Bug were also fixed Sirsamkar

10/22/11 Shantanu 1.3 ● Made changes to prototype mock ● Reduced the number of clicks in Sirsamkar ups Sales web pages prototype and changes the migration prototype

11/06/11 Shantanu 1.4 ● Section numbers added ● Section number as described in ● Table of contents, Table of figures the table of contents has been Sirsamkar changed added correctly ● Bugs fixed 11/20/11 Shantanu 3.0 ● Notes Added ● Prototype development in Sirsamkar progress. Notes added for Draft DCP Submission

Table of Contents Prototype Report...... 1 Version History...... 2 Table of Tables...... 6 Table of Figures...... 7 1. Introduction...... 8 2. Navigation Flow...... 9 3. Prototype...... 10

Table of Tables

Table 1: Migration of Data 4 Table 2: Sales Website 9 Table 3: Manage Student Profile 14

Table of Figures

Figure 1: Data Migration 4

Figure 2: Sales Website 5

Figure 3: Manage Student Profile 6

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0 1.Introduction

1.1 Purpose of the prototype report

The prototype report is a report that provides the prototypes developed and documented for the Leamos ™ (Centro Latino Organization) as well as understandability of the navigation flow of the system. This report would provide the details of project through screenshots, diagrams and description for the same. It would also provide in detail of how the system would behave and function with the help of the prototypes designed. This would fetch the response from the client on prototypes which would help the system to get a better shape. It helps us to mitigate the risks.

1.2 Status of the prototype

The prototypes have been created based on the initial requirements from clients. These include the Migration of data and creating the sales website. New prototypes will be added as and when required.

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0 2.Navigation Flow

Figure 1: Navigation Flow for Leamos Website

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0 3.Prototype

3.1 Data Migration:

Table 1: Migration of data Description This screenshot is useful for migrating data from SQL to MySQL database. First we create a connection with the old database – SQL and then we create a connection with the new database –MySQL. Then we get all the rows of the related table and we insert the same into the new database. Finally we close the connection to the old database and the new database. Please note that based on the current observation, this seems to be a simple data migration. We are awaiting the client to share the existing schemas. Once the schemas have been shared we will get to know if there are any tricky scenarios and the prototype will be updated as required. The client is awaiting the schema from their development team. This should be available to us in a couple of weeks (last week of November) Related Win condition 252 / Migration of database Capability Pre-condition The admin/developer will open the program and set the connection string values in the configuration. Post condition Post execution of the program, data will be migrated from the old database to the new database.

Figure 2.1: Code for data migration

Figure 2.2: MySQL table before migration.

Figure 2.3: SQL Table to be migrated to MySQL

Figure 2.4: MySQL Table with the migrated data

Details:

The figure 2.1 displays a code which migrates the data, currently in MS SQL (table 2.3) to MySQL (for before migration refer table 2.2, for data after migration refer to table 2.4. The code demonstrates an example of how all the rows of one table in MS SQL are fed into the rows of another table in MySQL successfully. This would eliminate the pain of managing 2 databases for

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0 the client by migrating the data. This piece of code is a sample code, taking in some sample values in MS SQL and successfully migrating them to MySQL database.

3.2 Sales Website: Table 2: Sales Website Description In the following mock ups, we demonstrate a sequence flow of how a user can buy Leamos licenses as a user or as an organization online, through a third party merchant system. Client has requested certain specific UI for the Sales Website. We have completed UI to some extent and will completely display the functional prototype before ARB.

Related Win Condition 245 Capability Pre-condition The user have selected the Become a Leamos Literacy Site on the home page of Leamos website Post condition Post execution of the program, user will be provided with the License(s) with a username and password on completion of the payment.

Figure 3(a): Sales website Mockup

Figure 3(b): Sales website Mockup

Figure 3(c): Sales website Mockup

Figure 3(d): Sales website Mockup

Figure 3(e): Sales website Mockup

Figure 3(f): Sales website Mockup

Figure 3(g): Sales website Mockup

Details:

The above screenshots provides a brief overview of how the website would look when an organization wants to buy courses or wants to become an independent user or an independent site with Leamos.

Figure 3(a) displays the mock up of the 1st page from which the process of payment will start. There are 3 icons as described. The function of these icons is to give a more detailed idea of how much the purchase will cost them. The user needs to click on any of the 3 icons to move further.

Figure 3(b) displays mock up of the page that would give the potential customer information on his purchase if he is inside the boundaries of Los Angeles County.

Figure 3(c) displays mock up of the page that would give the potential customer about the information on his purchase if he is outside the boundaries of Los Angeles County and an independent site.

Figure 3(d) displays mockup of the page that would ask the partner or independent site user to enter the described details and store it to the database.

Figure 3(e) displays mock up of the page that would ask the individual user to enter the described details and store it to the database.

Figure 3(f) displays that the customer is being re-directed to the Course Merchant payment gateway for further processing.

Figure 3(g) displays mockup of the screen that shows the successful subscription of the product bought by the customer.

PRO_DCP_F11a_T07_V3.0 11/20/11 Prototype Report Version 3.0 3.3 Managing Student Profile:

Table 3: Managing Student Profile

Description Following are the mock ups for displaying how an administrator can manage the student profiles. The operations include adding a student profile, viewing student profile, editing student profile and generating a report on student profiles. All mock ups include relevant details respective to their operation. Client has requested certain specific UI for the Sales Website. We have completed UI to some extent and will completely display the functional prototype before ARB.

Related WC 243 Capability

Pre Condition The admin must have logged into his account to access these web pages.

Post Condition The student profiles would have been added viewed edited or reports generated after access by admin.

Figure 4(a): Manage Student Profile Mockup

Figure 4(b): Manage Student Profile Mockup

Figure 4(c): Manage Student Profile Mockup

Figure 4(d): Manage Student Profile Mockup

Figure 4(e): Manage Student Profile Mockup

Details:

Figure 4(a): Displays the simple login screen for the user who will manage the student profiles.

Figure 4(b): Displays the screen after login where by default it shows the screen to Add student profile with their relevant details.

Figure 4(c): Displays the screen for the tab to View student profile details.

Figure 4(d): Displays the screen for the tab to edit student profile details.

Figure 4(e): Displays the screen for the tab to Generate Report about students and their progress. Also the admin can search the name of the student whose report he wants to see.

PRO_DCP_F11a_T07_V3.0 11/20/11