Prototype Report Template Version 1.1. Prototype Report. Leamos. Team Number 7. Monty Shah Project Manager Life Cycle Planner

Transcription

1 Prototype Report Template Version 1.1 Prototype Report Leamos Team Number 7 Name Address Primary Role Secondary Role Monty Shah montysha@usc.edu Project Manager Life Cycle Planner David Wiggins dgwiggin@usc.edu IIV&V Off-campus Shaper Pragya Singh pragyasi@usc.edu System Architect Prototyper Shantanu Sirsamkar sirsamka@usc.edu Requirements Engineer Feasibility Analyst Suchita Doshi suchitad@usc.edu Prototyper Operational Concept Engineer Swapnil Savdekar savdekar@usc.edu Life Cycle Planner System Architect PRO_FCP_F11a_T07_V1.1 i

2 Version History Date Author Version Changes made Rationale 10/10/11 Suchita Doshi 14/10/11 Suchita Doshi 1.0 Original template Initial Prototype with the navigation flow and the prototypes with the description 1.1 Updated Sections 2 and 3 The mock ups are updated with more details with more screenshots. Updated after Evaluation PRO_FCP_F11a_T07_V1.1

3 Table of Contents Prototype Report...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures... v 1. Introduction Purpose of the prototype report Status of the prototype Navigation Flow Prototype... 4 PRO_FCP_F11a_T07_V1.1

4 Table of Tables Table 1 : Migration of Data... 4 Table 2: Sales website..9 PRO_FCP_F11a_T07_V1.1

5 Table of Figures Figure 1: Navigation flow... 3 Figure 2: Data Migration... Error! Bookmark not defined. Figure 3: Sales Website... 5 PRO_FCP_F11a_T07_V1.1

6 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_FCP_F11a_T07_V1.1 1

7 2. Navigation Flow PRO_FCP_F11a_T07_V1.1 2

8 Figure 1: Navigation Flow for Leamos Website PRO_FCP_F11a_T07_V1.1 3

9 3. Prototype 3.1 Data Migration: Table 1: Migration of data Description Related Capbility Pre-condition Post condition 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. Win condition 252 / Migration of database The admin/developer will open the program and set the connection string values in the configuration. Post execution of the program, data will be migrated from the old database to the new database. PRO_FCP_F11a_T07_V1.1 4

10 Figure 2.1: Code for data migration PRO_FCP_F11a_T07_V1.1 5

11 Figure 2.2: MySQL table before migration. PRO_FCP_F11a_T07_V1.1 6

12 Figure 2.3: SQL Table to be migrated to MySQL PRO_FCP_F11a_T07_V1.1 7

13 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 PRO_FCP_F11a_T07_V1.1 8

14 rows of another table in MySQL successfully. This would eliminate the pain of managing 2 databases for 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 Related Capbility Pre-condition Post condition 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. Win Condition 245 The user have selected the Become a Leamos Literacy Site on the home page of Leamos website 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 PRO_FCP_F11a_T07_V1.1 9

15 Figure 3(b): Sales website Mockup Figure 3(c): Sales website Mockup PRO_FCP_F11a_T07_V1.1 10

16 Figure 3(d): Sales website Mockup Figure 3(e): Sales website Mockup PRO_FCP_F11a_T07_V1.1 11

17 Figure 3(f): Sales website Mockup Figure 3(g): Sales website Mockup PRO_FCP_F11a_T07_V1.1 12

18 Figure 3(h): 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 deal will cost them. The user needs to click on any of the 3 icons to get more information. Figure 3(b) displays mock up of the page that would give the potential customer information on his deal 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 deal if he is outside the boundaries of Los Angeles county and an independent site. Figure 3(d) displays mock up of the page that would ask the partner or independent site user to enter the described details and send 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 send it to the database. Figure 3(f) displays mock up of the window that will allow the customer to make a payment selecting the options given therein. Figure 3(g) displays mock up of the screen that is validating the payment details of the user. Figure 3(h) displays mock up of the screen that shows the successful subscription of the product bought by the customer. PRO_FCP_F11a_T07_V1.1 13