1

Joint Educational Project

ONLINE PLATFORM

Shreya Nigam Project Manager/PrototyperReem Alfayez Requirement EngineerRebecca Lin Feasibility AnalystWei Yan System ArchitectWei-Ting Cheng Life Cycle PlannerNicholas Pecoraro IIV&V

TEAM 15

Team Strong Points

Dedicated to meeting deadlines Strong Background in SQL Learn new technologies rapidly

2

Team Weak Points

• Domain Vernacular• Time Constraints• Lack of Unit Testing Experience

3

Overall Project Evaluation

4

Development environments set up Setting up test servers Acceptance Test cases identified Database Schema finalization in progress

Testing Plan

5

Unit Tests Integration Tests Regression Tests System Tests Alpha Tests

Testing Topology

6

Test Cases

7

Test Case ID DescriptionTC-01 Receive Msg Upon CheckinTC-02 View Volunteer’s Site InfoTC-03 Get Directions to SiteTC-04 View JEP DocsTC-05 View ScheduleTC-06 Export Checkin InfoTC-07 Browse Volunteer InfoTC-08 Manage JEP DocsTC-09 Set Msg for VolunteersTC-10 Edit Msg for VolunteersTC-11 LoginTC-12 LogoutTC-13 Search Volunteer InfoTC-14 Add User RoleTC-15 Edit User RoleTC-16 Delete User RoleTC-17 Add SiteTC-18 Edit SiteTC-19 Delete Site

System Test Plan

Date Test Case Description

02/28TC-11, TC-12 

TC-14, TC-15, TC-16, TC-01

Log in/out, Manage users, Checkin

03/07 TC-17, TC-18, TC-19, TC-02 Manage Sites

03/14 TC-13, TC-07 Search/Browse Users

8

System Test Plan (Post-CCD)

Date Test Case Description

04/11TC-04, TC-08, TC-03, TC-06,

TC-05Manage Docs, Directions, Export

Checkin, View Schedule

9

Acceptance Test

Value-Based Final Test Before Transitioning System End-to-End Test ( est. 3 days) All Test Cases Must Pass

10

11

Operational Concept Document

System Boundary

System Purpose and goalsCapability Goals Priority Level

OC_1 receive custom message upon check-in Must HaveOC_2 Unique User accounts (JEP PAs, Administrators, Volunteers)

Must Have

OC_3 Geo-Location Check-In Must HaveOC_4 Access to Site information (Map, contact, description)

Must Have

OC_5 Organize and access PDF Documents (reflective questions)

Must Have

   Level of Service

GoalsDesired

levelAcceptanc

e levelPriority Level

Referred WinWin Agreements

Geo-location tolerance

30ft 50ft High WC_2610

Check-in Time 5s 15s Med WC_2610System Availability

99% 95% Med WC_2610

14

Prototype

15

16

ARCHITECTURE

System Context Diagram

18

Artifacts and Information Diagram

Process Diagram

20

21

22

Hardware Component Class Diagram

23

Software Com

ponent Class Diagram

24

Deployment Diagram

User Interface Class D

iagram

26

Login and Role Management Class Diagram

27

Check-in Class Diagram

28

Document Management Class Diagram

29

Site Managem

ent Diagram

30

Message Management Class Diagram

31

Volunteer Class Diagram

32

Login Sequence Diagram

33

Check-in Sequence Diagram

Current NDI Choice

Basic Map Routing

Street View Places

Data VisualizationSatellite

Google Maps API

100%

0%

0%

50%

25%

0%

Why Google Map API? Free License can meet our requirement. We do not need to buy the Business License.

The Google Maps APIs let us embed Google Maps in our web pages or mobile apps easily. We can refer to Google Maps JavaScript API v3 which provides lots of code examples.The API even provides specific interface for different browse and operation system.

Why MySQL?

The leaders of web rely on MySQL. Twitter, Facebook, LinkedIn, Youtube, yahoo! and Paypal

SQL based database. All our team members have experienced with SQL—based database.

MySQL offers great reliability and ease of use. It is free, and comes with free documentation as well as thousands of programmers that share their code that relates to communicating with a MySQL databse.

37

Life Cycle Plan

38

Roles of team members

Name First role Second role

Wei Yan Developer Tester

Shreya Nigam Project Manager Developer

Wei-ting Cheng Life Cycle Planner Developer

Reem Alfayez Requirement Engineer Developer

Rebecca Lin Developer Tester

Nicholas Pecoraro IIV&V Quality Focal Point

Ricardo Solano(leave)    

39

First iteration

40

Second iteration

41

Date Role Responsibility Location04/14/14 Developer

professorPTR ARB will allowed professors and TAs to evaluate whether the product is ready to release or not.

SAL

04/21/14 Developerclient

Deploy the product in JEP JEP house

04/22/14 Developer Alpha test Leavy

04/24/14 DeveloperClients

Release beta test to client and user. JEP house

04/24/14 DeveloperClient

Training and deliver all document. JEP house

04/27/14 Client Release the client and user feedback JEP house04/28/14 Client

DeveloperProfessor

Operational Commitment Review for Initial Operational Capability

SAL

05/05/14 Client Client evaluation SAL

Feasibility Evidence

Major risk

Risks

Risk Exposure

Risk MitigationsPotential

MagnitudeProbability

LossRisk

Exposure

Accuracy of the location forcheck-in. The checks ins are usedfor attendance and incorrect datacan cause problem.

7 7 49Speak to the client that this featureshould only be available for mobilephones

The project may not finish onschedule because clients asked for earlier schedule for testing phase 6 8 48 Reschedule the development phase

The misunderstanding of theterms that our clients was using. 7 6 42

Clarify terms during meeting andemail to make sure we are in the samepage.

Iteration 1

Definition of done

1. Unit test pass2. Integration test pass3. System test pass4. Peer reviewed5. Remaining hours for task set to zero and task closed6. The components have covered all the requirements

Biz value Weight WC Description

8 0.949 2610 As a program assistant, I can export my students successful check-ins information which includes(date,time,and site)

9 0.921 2785 As a user I can log in.

9 0.934 2819As an admin, I can add users(admins, and PA) to the system by adding their USC ID, and selecting their role(Admin, PA)

9 0.934 2823As an admin, I can add site information including Name,Dress Code,No School,Early Dismissal,Image,Office Location,Office Location,Address,Principal Name,Coordinator's info(First Name,Last Name ,e-mail,Office Location)

8 0.896 2645As a JEP volunteer, I can log in and find my site information including location, description, and site times that I am supposed to go there.

8 0.871 2786 As a user, I can log out.

9 0.855 2609As a JEP volunteer, I can check-in my geo location on through the website either from my phone or pc, to confirm my attendance at a school or volunteer site.

8 0.855 2784 As JEP PA, I can browse my student information

9 0.855 2787 As a user, I can view the proper website view based on my role after I logged in

9 0.855 2794 As JEP Admin, I can search student view and their infromation

Traceability matrix

7 0.82 2789 As a JEP staff(PA,Admin), I can set the message that students will get when they checked_in

8 0.783 2643 As a JEP volunteer, I can see maps to and from community sites and USC.

6 0.745 2651 As a JEP volunteer, I get a message when I check in

6 0.7 2824As an admin, I can edit site information Name,Dress Code,No School,Early Dismissal,Image,Office Location,Office Location,Address,Principal Name,Coordinator's info(First Name,Last Name ,e-mail,Office Location)

8 0.686 2820 As an admin, I can edit users'(admins, and PA) roles in the system.

5 0.662 2781 As a JEP volunteer, I can view a list of all JEP documents.

5 0.647 2825 As an admin, I can delete a site.

5 0.647 2832 As an admin, I can delete users'(admins, and PA) roles in the system.

5 0.647 2833As a JEP staff(PA,Admin), I can edit the message that students will get when they checked_in by setting the message start date, end date, and content.

5 0.618 2782 As a program assistant , I can upload JEP important pdf documents

As of 12-6-13 V3.0

Traceability matrix

(4 submissions)

minsActual Weekly Hours Worked Planned Weekly Hours Week

2100 35 144 3

3920 65.33333333 144 4

4170 69.5 144 5

5870 97.83333333 144 6

9832 163.8666667 144 7

1396 23.26666667 144 8

1225 20.41666667 144 9

3025 50.41666667 144 10

2280 38 144 11

3533 58.88333333 144 12

3235 53.91666667 144 13

890 14.83333333 144 14

1975 32.91666667 144 15

2540 42.33333333 144 16

Metrics

48

Metrics Reporting

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 170

20

40

60

80

100

120

140

160

180

Hours Planned: 144

Hours Worked vs. Hours Planned

Hours Worked

Week

Hours

49

Metrics ReportingDefect Data

Found Via Defect Sources

Requirements Design Documents

Peer Review 0 0 5

Sanity Check 6 1 0

ARB 0 0 4