Prototype Report. Leamos. Team Number 7

Transcription

1 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 Requirements sirsamka@usc.edu Sirsamkar Engineer Feasibility Analyst Suchita Doshi suchitad@usc.edu Prototyper Operational Concept Engineer Swapnil Savdekar savdekar@usc.edu Life Cycle Planner System Architect

2 Version History Date Author Version Changes made Rationale 10/10/11 Suchita Doshi, Shantanu Sirsamkar 1.0 Original template Initial Prototype with the navigation flow and the prototypes with the description 10/14/11 Suchita Doshi, Shantanu Sirsamkar 1.1 Updated Sections 2 and 3 The mock ups are updated with more details with more screenshots. Updated after Evaluation 10/18/11 Suchita Doshi, Shantanu Sirsamkar 1.2 Added prototype The prototype is required for managing students. Bug were also fixed 10/22/11 Shantanu Sirsamkar 1.3 Made changes to prototype mock ups Reduced the number of clicks in Sales web pages prototype and changes the migration prototype

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

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

5 Table of Figures Figure 1: Navigation flow 3 Figure 2: Data Migration 4 Figure 3: Sales Website 5 Figure 4: Manage Student Profile 6

6 Introduction 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. 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.

7 Navigation Flow Figure 1: Navigation Flow for Leamos Website

8 Prototype 3.1 Data Migration: Description Related Capability Pre-condition Post condition Table 1: Migration of data 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 (1 st week of November) 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.

9 Figure 2.1: Code for data migration

10 Figure 2.2: MySQL table before migration.

11 Figure 2.3: SQL Table to be migrated to MySQL

12 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

13 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: Description Related Capability Pre-condition Post condition Table 2: Sales Website 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

14 Figure 3(b): Sales website Mockup Figure 3(c): Sales website Mockup

15 Figure 3(d): Sales website Mockup Figure 3(e): Sales website Mockup

16 Figure 3(f): Sales website Mockup Figure 3(g): Sales website Mockup

17 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.

18 3.3 Managing Student Profile: Table 3: Managing Student Profile Description Related Capability Pre Condition Post Condition 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. WC 243 The admin must have logged into his account to access these web pages. The student profiles would have been added viewed edited or reports generated after access by admin. Figure 4(a): Manage Student Profile Mockup

19 Figure 4(b): Manage Student Profile Mockup

20 Figure 4(c): Manage Student Profile Mockup Figure 4(d): Manage Student Profile Mockup

21 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.