Remote Team Member Teams strong points & weak points
(operational view and technical view) concerns & possible
solutions; S/P Engineer observations Elaine Lo
Slide 4
Strong and Weak Points Strong points o Operational view:
hardworking, team members have a good understanding of foundations
for project o Technical view: quick learners Weak points o
Operational view: scheduling/time management, communication o
Technical view: lack of experience
Slide 5
Concern and Risk Technical concern o Lack of Experience working
with the tools and languages used for developing this system o
Solution: Evaluate pros and cons of the different tools and come to
an agreement on what we think would work best/meet all the win-win
conditions Risk o The database of new set of students at the
beginning of the school year. Can lead to duplicate data if data is
not properly analyzed. o Solution: We need to have discussion with
the Client to decide on the possibility of occurrence of this
issue. Can have check boxes next to each row with a select all
option and delete button once this issue is resolved.
Slide 6
OCD System purpose; shared vision; proposed new system;
benefit-chain diagram; system boundary; core capabilities,
constraints and goals Nidhi Baheti
Slide 7
System Purpose Establish a better Attendance Tracking system.
Enables better monitoring of the program leading to improved
program quality.
Slide 8
Slide 9
System Boundary Diagram
Slide 10
Slide 11
Element Relationship Diagram
Slide 12
Desired Capability Goals Capability GoalsPriority Goals OC-1
Modifying girls data: The system is capable of adding/editing and
deleting girls data. Must have OC-2 Modifying volunteer coachs
data: The system is capable of adding/editing and deleting data of
volunteer coaches. Must have OC-3 Modifying Program staffs data:
The system is capable of adding/editing and deleting program staff
data. Must have OC-4 Class Management: The system is capable of
Adding/Editing and Deleting classes. Must have OC-5 Attendance
Tracking: The system shall provide the methods to check-in the
girls and store the attendance data. Must have
Slide 13
Organizational Goals OG-1: Improved Attendance Monitoring OG-2:
Reduced Paperwork for attendance OG-3: Better tracking of program
quality OG-4: Increased support to teams having issues.
Slide 14
Win-Win Agreements Agreed Win conditions in each category
Suhani Vyas
Slide 15
Capability Requirements IDRequirement Win condition(s)
Priority* CR-1 Admin can add/Update/Delete program staff in the
database WC_3277 Must have CR-2 Program Staff can Add/Update/Delete
Classes, Girls and Volunteer in the database. WC_3269,WC
_3270,WC_327 1 Must have CR-3 Volunteer Coaches can View/Access the
class roster on the mobile app to Check-in the girls attendance.
WC_3268 Must have CR-4 User of the website and application can
Reset/Update the password. WC_3425 Must have *Admin hold all the
privileges that program staff holds.
Slide 16
Project Requirements IDRequirement Win condition(s) Priority
PR- 1 System shall be accessible via Desktop and Mobile device (
iOS and Android) WC_3279Must have PR- 2 The maximum budget of the
client is $750. WC_3266Must have
Slide 17
Project Requirements Tools and Languages : Web Server:
Language: PHP Framework: Symfony Mobile Application: Language:
HTML, CSS, Javascript Tool: PhoneGap Platform: iOS and Android
Database Server : MySQL Server
Slide 18
Level Of Service Requirements IDRequirementWin condition( s)
Priority LOS-1 Reliability: The system shall be down for no more
than 3 to 5 hours a month and preferably not after the school
hours. WC_3280Must have LOS-2 Usability: The system shall be easy
and intuitive to use. WC_3281Can have LOS-3 Maintainability: The
system shall be easily monitored and maintained WC_3478Must
have
Slide 19
Prototype/ Product Demo Most significant capabilities, NDI/NCS
integration Ankith Nagarle
Slide 20
User Interface Mock Ups
Slide 21
Mobile App Login If successful : Roster Selection
Slide 22
Mobile App Attendance Select Week & Session
Slide 23
Website : Login
Slide 24
Two types of users use the website. o ADMIN : Admin gets the
access to all the modules which consists of : Class : It consists
of two sub modules : Class Girls Attendance Volunteer User o STAFF
: Staff gets access to all the modules of Admin except User
Module.
Slide 25
Website : Home
Slide 26
Website : View Class
Slide 27
Website : Add Class
Slide 28
Website : View Girls
Slide 29
Website : Add Girls
Slide 30
Website : View Attendance
Slide 31
Website : Export Attendance
Slide 32
Website : View Volunteers
Slide 33
Website : Add Volunteer
Slide 34
Website : View User
Slide 35
Website : Add User
Slide 36
Functional Prototype
Slide 37
We have set up the development environment required for the
project. We have started with the Functional prototype of the Web
Interface and the Non Functional prototype of Mobile
application.
Slide 38
Web Server : User Module User List
Slide 39
Web Server : Create User Form
Slide 40
Web Server : User Information Preview
Slide 41
Mobile App: Home Page
Slide 42
Mobile App Menu Option
Slide 43
Mobile App : School List Page
Slide 44
Mobile App : Roster page
Slide 45
Architecture Top-level physical and logical architecture Presha
Thakkar
Slide 46
System Context Diagram
Slide 47
Artifacts
Slide 48
Use Case : Admin
Slide 49
Use Case : Program Staff
Slide 50
Use Case : Volunteer
Slide 51
Integrated Use Case
Slide 52
Life Cycle Plan Life cycle strategy; Focus on Development phase
& transition increment; Key stakeholder responsibilities;
Project plan; Resource estimation Anushilla Dey
Slide 53
LIFE CYCLE STRATEGY Purpose of LCP Status of LCP Assumptions
Duration Personnel Resources
RESOURCES AND COINCOMO SYSTEM o GOTRLA SUB-SYSTEM o MOBILE
APPLICATION Attendance Management o WEB APPLICATION Attendance
Tracking Class Calendar Class Management Student Management
Volunteer Management
Slide 57
SCALE DRIVERS DRIVERVALUERATIONALE PRECEDENTNESS (PREC) HIGHThe
team is developing such a project for the first time. But, such
projects have been developed in the past by other developers.
DEVELOPMENT FLEXIBILITY (FLEX) HIGHThe client has given us complete
flexibility over the development platform RISK RESOLUTION (RESL)
NOMINALMost of the risks have been identified and corresponding
risk mitigation plans have been made TEAM COHESION (TEAM)
NOMINALThe team members are working with each other for the first
time. PROCESS MATURITY (PMAT) NOMINALICSM Principles and guidelines
are followed strictly by the development team.
Slide 58
COST DRIVERS DRIVER VIEW ROSTER RECORD ATTENDA NCE EXPORT
ATTENDA NCE MONITOR ATTENDA NCE SCHEDUL E CLASSES VOLUNTEE R
MANAGEM ENT CREATE A NEW CLASS ADD A NEW STUDENT ADD A NEW VOLUNTE
ER RELYNOMINAL DATALOW DOCUNOMINAL CPLXNOMINAL RUSENOMINAL
TIMENOMINAL STORNOMINALHIGHNOMINAL PVOLLOWNOMINALLOW
Slide 59
COST DRIVERS DRIVERVIEW ROSTER RECORD ATTENDA NCE EXPORT
ATTENDA NCE MONITOR ATTENDA NCE SCHEDUL E CLASSES VOLUNTEE R
MANAGEM ENT CREATE A NEW CLASS ADD A NEW STUDENT ADD A NEW VOLUNTE
ER ACAPNOMINAL APEXNOMINAL PCAPNOMINAL PLEXNOMINAL LTEXNOMINAL
PCONLOW TOOLNOMINALHIGHNOMINAL SITEVERY HIGH
Slide 60
Mobile Application Overview
Slide 61
Web Application Overview
Slide 62
GOTRLA Overview
Slide 63
Feasibility Evidence NDI/NCS alternatives, NDI/NCS evaluation
& analysis results; Business case (beginnings, including
benefits analysis); Major Risks; Capability and LOS feasibility
evidence; 5 Personas Aayush Jain
Slide 64
INTRODUCTION Purpose of FED Status of FED o Process Feasibility
Analysis o Risk Assessment o NDI/NCS Feasibility Analysis o
Business Case Analysis
Slide 65
PROCESS FEASIBILITY ANALYSIS Criteria for Process Feasibility
Analysis o Critical on compatibility o Internet Connection
independence o Need high level of services/performances o Need high
security
Slide 66
RISK ASSESSMENT Risks Risk Exposure Risk Mitigations Potential
Magnitude Probability LossRisk Exposure Clients Requirements:
Incorrect understanding about the requirements of the client. 2510
Have more client interactions to understand the requirements of the
client and document those requirements well. Clients Current
Technology: Limited knowledge about working of the RacePlanner
system in the existing system of the client. 2510 Race Planner is
not included in the current system. This would be taken as an
evolutionary measure in future. Project Management: Lack of
coordination amongst team mates 177 Decide proper time to meet
according to the schedule of all the team mates.
Slide 67
NDI/NCS FEASIBILITY ANALYSIS Candidate NDI/NCS Components
NDI/NCS features o PhoneGap supports hybrid application development
o PhoneGap uses existing technologies such as HTML/CSS o Symphony
provides access control o Symphony supports scalability of
application
Slide 68
FEASIBILITY EVIDENCE Level of Service Feasibility o LOS-1: The
system shall be down for no more than 3 to 5 hours a month and
preferably not after school hours o LOS-2: The system should be
easy and intuitive to use Capability Feasibility o CR-1: Monitor
Attendance of girls and coaches o CR-2: Export Attendance from Web
Server
Slide 69
BUSINESS CASE ANALYSIS Assumptions : Every camp will have at
least two coaches with smartphone. Paper based attendance
monitoring system is the reason for low program quality. The
program quality will improve by using this application and having
real time data. Stakeholders Initiatives Value
PropositionsBeneficiaries -GOTRLA staff -Coaches -CSCI577a Team15
-Maintainers -Develop a mobile application and a web server for new
participants check-in system. -Provide training to the program
staff to use the new system. -Record the attendance of the girls
and the coaches. -Monitor the attendance of the girls and coaches
in each roster. Improved attendance monitoring. Improved volunteer
support. More efficient processes for volunteer and staff
communication. -Volunteer Coaches - Program Staff - Program
Participants CostsBenefits -Annual apple store membership cost.
-Web Server hosting cost. -Need to hire a maintainer.
-Time/manpower spent on creating the system. -Have real time data
on attendances. -Reduce the paper work done by the program staff.
-Increased number of girls registering for the program.
BENEFIT ANALYSIS Current activities & resources used%
ReduceTime Saved (Hours/Year) Program Monitoring Program Staff
(3hrs/week * 52 weeks) 66%102 Total102 Year Cost (in terms of time
saved) Benefit (Effort Saved) Cumulative Cost Cumulative Benefit
ROI 20141560 0 2015172102328102-0.68 2016189102517204-0.60
2017208102725306-0.58 ROI ANALYSIS
Slide 72
Quality Focal Point Traceability Matrix and summary; Defect
Identification review type summary (what & how) by document
section or UML, and current defect injection & removal matrix;
Quality Management Strategy Elaine Lo
Defect Injection & Removal Matrix DefectDefect Description
Date InjectedDate Removed Program Business Model Incorrect modeling
of the business flow 9/19/149/21/14 SSADMissing some use case
scenarios 10/13/14 Test CasesDiscuss how to handle rainy day cases
10/13/14
Acceptance Test cases Sunny day scenario o Web Interface TC-01:
User permissions TC-02: Add/remove data to the database via website
from point of view of admin and staff TC-03: Add/remove data to the
database via application from point of view of a coach TC-05:
Previewing how the reports will look o Mobile Interface: TC-04:
Saving the attendance as a coach
Slide 79
Acceptance Test cases Rainy day cases o TC-06: Multiple coaches
record attendance o TC-07: Attendance is recorded but then a girl
shows up late o TC-08: Attendance is recorded but then a girl
leaves early o TC-09: Error handling o TC-10: Handling the web/mob
application events when the internet service is not available.
Slide 80
Suggestions and Questions? Things done right & Issues to
address
