1 / 55

JEP ONLINE PLATFORM Shreya Nigam Project Manager Reem Alfayez Requirement Engineer Rebecca Lin Feasibility Analyst W

TEAM 15. JEP ONLINE PLATFORM Shreya Nigam Project Manager Reem Alfayez Requirement Engineer Rebecca Lin Feasibility Analyst Wei Yan System Architect Wei-Ting Cheng Life Cycle Planner Ricardo Solano Operational Concept Engineer Nicholas Pecoraro IIV&V. Presentation Outline.

wyatt
Download Presentation

JEP ONLINE PLATFORM Shreya Nigam Project Manager Reem Alfayez Requirement Engineer Rebecca Lin Feasibility Analyst W

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TEAM 15 • JEP ONLINE PLATFORM • Shreya Nigam Project Manager • ReemAlfayez Requirement Engineer • Rebecca Lin Feasibility Analyst • Wei Yan System Architect • Wei-Ting Cheng Life Cycle Planner • Ricardo Solano Operational Concept Engineer • Nicholas Pecoraro IIV&V

  2. Presentation Outline • Remote Team Member(s): Team’s strong points & weak points (operational view and technical view) concerns & possible solutions • OCD: System purpose; shared vision; proposed new system; benefit-chain diagram; system boundary; desired capabilities and goals • Prototype: Most significant capabilities • Requirements: Most significant requirements and its priorities level • Architecture: Top-level physical and logical architecture; status of NDI/reuse choices • Life Cycle plan: Life cycle strategy; focus on Foundations phase; key stakeholder responsibilities; project plan, resource estimation • Feasibility Evidence: Business case; NDI analysis results; major risks; Personas • QFP: Traceability Matrix and summary; Quality Management Strategy; Defect Identification review type summary (what & how) by document section or UML, and current defect injection & removal matrix

  3. Remote Team Members

  4. Team Strong Points • Operationally • Committed Individuals • Active Listeners • Objective • Agile

  5. Team Strong Points • Technically • Experienced in a wide breadth of programming technologies

  6. Team Weak Points • Operationally • Schedules Differ • Communications • Lack of Experience in Roles

  7. Overall Project Evaluation Consideration • 24 Week Project from Planning to Delivery • Project scope has changed • Several Critical Stakeholders • No operational prototype

  8. Operational Concept Document

  9. Business Workflow

  10. Main Organizational goals -Facilitate communication across JEP students/staff/sites -centralize and organize JEP Information -Simplifyand Streamline existing paper processes -Increased learning from the JEP program

  11. Program Model

  12. Results Chain

  13. System Boundary and environment

  14. Element-Relationship Diagram

  15. Implications • -The elimination of the current, time-consuming attendance paperwork • -The need to hire a new system maintainer to take care of the system • -Replacement of inefficient manual e-mail method with an group e-mail capability provided by the site relations with students, or other relations in the database • -Students do not have to fill any attendance sheets anymore • -Students will access site information through JEPOP • Organizational • Operational

  16. PROTOTYPE

  17. Check-in • To record the current location of the student when he/she checks • This is will help in keeping the track of the student’s attendance • The current location will be compared to the site’s location and will send success(with message) or failure.

  18. Successful Check-in Check-in through phone Check-in through web

  19. Successful Check-in Check-in through phone Check-in through web

  20. 2. Site Information • Each student is able to see the site’s information they are assigned to • On the click of “Direction” button, the user will be directed to Google map for directions to the site My Site information through web

  21. My Site information through phone

  22. REQUIREMENTS

  23. Requirements

  24. Requirements

  25. Requirements

  26. ARCHITECTURE

  27. System Context Diagram

  28. User Cases Overview

  29. PS: If you are interested in any other user case, please refer to SSAD document or the UML model which can be downloaded in our team website.

  30. Current NDI Choice 100% 50% Routing Basic Map 0% 25% 0% 0% Places Street View Google Maps API Data Visualization Satellite

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

  32. LIFE CYCLE PLAN

  33. Estimated CSCI577a Effort : 7 team members at 12 hrs/week for 12 weeks • Estimated CSCI577b Effort : 7 team members at 12 hrs/week for 12 weeks • Total estimated effort : 13.26PM • Budget information: 0 • Project duration : 24 weeks • Component modules in your development project: • 1. Check_in • 2. Authentication • 3. Student management • 4. Document management • 5. Schedule component

  34. Project Plan

  35. COCOMO Estimation

  36. FEASIBILITY EVIDENCE

  37. Cost Analysis-Personnel Costs

  38. Cost Analysis-Hardware and Software Cost

  39. Benefit Analysis

  40. ROI Analysis

  41. NDI analysis results

  42. Major risk

  43. Personas – JEP participant - Tom • Attributes: • Helpful. • Forgetful • Have limited time Description: Tom is a CS major student who enjoys math and want to help children with their math homework Basic Demographic: Age: 20 Occupation: student Hometown: Los Angeles, CA Marital Status: Single. • Goals & Aspirations: • Be more organized and fulfill his assignment. User Scenario: Tom finished his CSIS 310 class. He knows that he must go to his JEP assignment, but he forget his paper schedule at home. He remembered that he should be in St. Agnes School, but when he arrived, he found that he went to the wrong school. Tom thinks that having his schedule online will save him time and effort • Information Sources: • Textbooks • Facebook

  44. Personas – JEP participant - Gary Basic Demographic: Age: 18 Occupation: student Hometown: China Marital Status: Single Description: Gary is a Chinese who came to America for his college degree. He wants to get an A grade in the history class, so he joined the JEP program to get extra credits. • Attributes: • Shy • Get lost easily • Use public transportation . Goals & Aspirations: - Having directions to the site User Scenario: Gary is not familiar with the local public transportation, since it is the first time he study aboard alone. This makes him get lost all the time and late for his JEP assignment. He wishes that he have an access to sites information and directions to get there. • Information Sources: • Daily Trojans

  45. Personas – JEP participant - Cindy Basic Demographic: Age: 22 Occupation: student Hometown: New York, NY Marital Status: Single. Description: Cindy is a student who participated in JEP program for one year. She lives far from both site assignments and JEP house. • Attributes: • Live far • Active. • Responsible. Goals & Aspirations: - Have a platform that allows JEP participants to submit attendance sheet online. User Scenario: Cindy have to spend one hour drive from her home to site assignment then half hour drive to JEP house to turn in the attendance sheet. She believe that if there is a way for JEP participant like her to turn in the attendance sheet more easily, it would save a lot of time. Information Sources: - Twitter

  46. Personas – JEP staff - Judy Basic Demographic: Age: 35 Occupation: JEP staff Hometown: Dallas, TX Marital Status: Married Description: Judy has working for JEP for 3 years, she is kind to every one and care about every one at every moment. • Attributes: • Care about every students • Check attendance Instantly User Scenario: Judy cares a lot about JEP students. When a student call and ask for site directions or a site assignment. She feels obligated to help them. However, sometimes she is not in JEP house, and she can not access the information from distance. She believes that having an online access to students and sites information anytime and anywhere will save her time. Students can also check their site by themselves. Goals & Aspirations: - A platform that allow her to check information and attendance of students every time she want. Information Sources: - Facebook

  47. Personas – Program assistant - James Basic Demographic: Age: 26 Occupation: Program assistant Hometown: Los Angeles, CA Marital Status: not married Description: Senior undergrad student who volunteered in JEP for two years . He wants to keep giving to JEP as it is improve his life. For that, he took this job even though it is a difficult one • Attributes: • Have limited time • Busy Goals & Aspirations: -Have a platform that allows program assistants to export student attendance sheets easily and ready for Blackboard to import. User Scenario: James spend his Friday spreading all the students attendance sheets to get his own student attendance sheets. Then He entered their attendance information to an excel sheet and imported them to the Blackboard. James believed that an electronic method will make his life more easier, so he can get out earlier on Friday to enjoy his time with his family. Information Sources: - Daily Trojans

  48. QUALITY FOCAL POINT

More Related