Joint Educational Project
ONLINE PLATFORM
Shreya Nigam
Reem Alfayez
Rebecca Lin
Wei Yan
Wei-Ting Cheng
Nicholas Pecoraro
Project Manager/Prototyper
Requirement Engineer
Feasibility Analyst
System Architect
Life Cycle Planner
IIV&V
1
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




Development environments set up
Setting up test servers
Acceptance Test cases identified
Database Schema finalization in progress
4
Testing Plan





Unit Tests
Integration Tests
Regression Tests
System Tests
Alpha Tests
5
Testing Topology
6
Test Cases
Test Case ID
Description
TC-01
Receive Msg Upon Checkin
TC-02
View Volunteer’s Site Info
TC-03
Get Directions to Site
TC-04
View JEP Docs
TC-05
View Schedule
TC-06
Export Checkin Info
TC-07
Browse Volunteer Info
TC-08
Manage JEP Docs
TC-09
Set Msg for Volunteers
TC-10
Edit Msg for Volunteers
TC-11
Login
TC-12
Logout
TC-13
Search Volunteer Info
TC-14
Add User Role
TC-15
Edit User Role
TC-16
Delete User Role
TC-17
Add Site
TC-18
Edit Site
TC-19
Delete Site
7
System Test Plan
Date
02/28
03/07
03/14
Test Case
TC-11, TC-12
TC-14, TC-15, TC-16,
TC-01
Log in/out, Manage users,
Checkin
TC-17, TC-18, TC-19,
TC-02
Manage Sites
TC-13, TC-07
Description
Search/Browse Users
8
System Test Plan (Post-CCD)
Date
04/11
Test Case
TC-04, TC-08,
TC-03, TC-06,
TC-05
Description
Manage 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
Capability Goals
OC_1 receive custom message upon check-in
OC_2 Unique User accounts (JEP PAs, Administrators,
Volunteers)
OC_3 Geo-Location Check-In
OC_4 Access to Site information (Map, contact,
description)
OC_5 Organize and access PDF Documents (reflective
questions)
Level of Service
Goals
Desired Acceptance Priority
level
level
Level
Geo-location
30ft
tolerance
Check-in Time 5s
System
99%
Availability
Priority Level
Must Have
Must Have
Must Have
Must Have
Must Have
Referred WinWin
Agreements
50ft
High
WC_2610
15s
95%
Med
Med
WC_2610
WC_2610
14
15
16
System Context Diagram
Artifacts and Information Diagram
18
Process Diagram
20
21
Hardware Component Class Diagram
22
Software Component Class Diagram
23
Deployment Diagram
24
User Interface Class Diagram
Login and Role Management Class Diagram
26
Check-in Class Diagram
27
Document Management Class Diagram
28
Site Management Diagram
29
Message Management Class Diagram
30
Volunteer Class Diagram
31
Login Sequence Diagram
32
Check-in Sequence Diagram
33
Current NDI Choice
100%
Basic Map
50%
0%
Street View
Satellite
0%
Routing
25%
Google Maps API
0%
Places
Data Visualization
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
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)
38
39
40
Date
Role
Responsibility
Location
04/14/14
Developer
professor
PTR ARB will allowed professors and TAs to evaluate whether
the product is ready to release or not.
SAL
04/21/14
Developer
client
Deploy the product in JEP
JEP house
04/22/14
Developer
Alpha test
Leavy
04/24/14
Developer
Clients
Release beta test to client and user.
JEP house
04/24/14
Developer
Client
Training and deliver all document.
JEP house
04/27/14
Client
Release the client and user feedback
JEP house
04/28/14
Client
Developer
Professor
Operational Commitment Review for Initial Operational
Capability
SAL
05/05/14
Client
Client evaluation
SAL
41
Risk Exposure
Risks
Accuracy of the location for
check-in. The checks ins are used
for attendance and incorrect data
can cause problem.
The project may not finish on
schedule because clients asked for
earlier schedule for testing phase
The misunderstanding of the
terms that our clients was using.
Risk Mitigations
Potential
Magnitude
Probability
Loss
Risk
Exposure
7
7
49
6
8
48
7
6
42
Speak to the client that this feature
should only be available for mobile
phones
Reschedule the development phase
Clarify terms during meeting and
email to make sure we are in the same
page.

Iteration 1
1.
Unit test pass
2.
Integration test pass
3.
System test pass
4.
Peer reviewed
5.
Remaining hours for task set to zero and task closed
6.
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
9
0.934
9
0.934
8
0.896
2785 As a user I can log in.
As an admin, I can add users(admins, and PA) to the system by adding their USC ID, and selecting their role(Admin,
2819 PA)
As an admin, I can add site information including Name,Dress Code,No School,Early Dismissal,Image,Office
2823 Location,Office Location,Address,Principal Name,Coordinator's info(First Name,Last Name ,e-mail,Office Location)
As a JEP volunteer, I can log in and find my site information including location, description, and site times that I am
2645 supposed to go there.
8
0.871
9
0.855
2786 As a user, I can log out.
As a JEP volunteer, I can check-in my geo location on through the website either from my phone or pc, to confirm
2609 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
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
As an admin, I can edit site information Name,Dress Code,No School,Early Dismissal,Image,Office Location,Office
2824 Location,Address,Principal Name,Coordinator's info(First Name,Last Name ,e-mail,Office Location)
6
0.7
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
5 0.647
2832 As an admin, I can delete users'(admins, and PA) roles in the system.
As a JEP staff(PA,Admin), I can edit the message that students will get when they checked_in by setting the message start date,
2833 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
(4 submissions)
Actual Weekly Hours
Worked
mins
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 Reporting
Hours Worked vs. Hours Planned
180
160
Hours Planned: 144
140
120
100
Hours
80
Hours Worked
60
40
20
0
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17
Week
48
Metrics Reporting
Defect Data
Found Via
Defect Sources
Requirements
Design
Documents
Peer Review
0
0
5
Sanity Check
6
1
0
ARB
0
0
4
49