1 / 81

Efficient Attendance Tracking System for Girls On The Run LA

This project aims to develop a new system for Girls On The Run LA that allows for better attendance monitoring, reduced paperwork, and improved program quality. The team highlights their strong points, weak points, concerns, and possible solutions. They also discuss the system's purpose, shared vision, proposed new system, and its benefits. The architecture, capabilities, requirements, and functionality are also presented. The team discusses the technical concerns and risks associated with the project and proposes solutions. Additionally, the project's system context diagram, artifacts, use cases, and the top-level physical and logical architecture are described.

niemi
Download Presentation

Efficient Attendance Tracking System for Girls On The Run LA

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. Team15-GOTRLA Girls On The Run Los Angeles

  2. Team-15 • Deepak Earayil: Project Manager & System/Software Architect • AnkithNagarle :Prototyper & Operational Concept Engineer • Aayush Jain : Feasibility Analyst & Project Manager • Presha Thakkar : Life Cycle Planner & Requirements Engineer • NidhiBaheti :Operational Concept Engineer & Prototyper • SuhaniVyas :Requirements Engineer & Feasibility Analyst • AnushilaDey : System/Software Architect & Life Cycle Planner • Elaine Lo :Shaper and Quality Analyst

  3. Remote Team MemberTeam’s strong points & weak points (operational view and technical view) concerns & possible solutions; S/P Engineer observations Elaine Lo

  4. Strong and Weak Points • Strong points • Operational view: hardworking, team members have a good understanding of foundations for project • Technical view: quick learners • Weak points • Operational view: scheduling/time management, communication • Technical view: lack of experience

  5. Concern and Risk • Technical concern • Lack of Experience working with the tools and languages used for developing this system • 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 • 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. • 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.

  6. OCDSystem purpose; shared vision; proposed new system; benefit-chain diagram; system boundary; core capabilities, constraints and goals NidhiBaheti

  7. System Purpose • Establish a better Attendance Tracking system. • Enables better monitoring of the program leading to improved program quality.

  8. System Boundary Diagram

  9. Element Relationship Diagram

  10. Desired Capability Goals

  11. Organizational Goals 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.

  12. Win-Win Agreements Agreed Win conditions in each category SuhaniVyas

  13. Capability Requirements *Admin hold all the privileges that program staff holds.

  14. Project Requirements

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

  16. Level Of Service Requirements

  17. Prototype/ Product Demo Most significant capabilities, NDI/NCS integration AnkithNagarle

  18. User Interface Mock Ups

  19. Mobile App If successful : Roster Selection Login

  20. Mobile App Select Week & Session Attendance

  21. Website : Login

  22. Website : Login • Two types of users use the website. • ADMIN : Admin gets the access to all the modules which consists of : • Class : It consists of two sub modules : • Class • Girls • Attendance • Volunteer • User • STAFF : Staff gets access to all the modules of Admin except User Module.

  23. Website : Home

  24. Website : View Class

  25. Website : Add Class

  26. Website : View Girls

  27. Website : Add Girls

  28. Website : View Attendance

  29. Website : Export Attendance

  30. Website : View Volunteers

  31. Website : Add Volunteer

  32. Website : View User

  33. Website : Add User

  34. Functional Prototype

  35. Functional Prototype • 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.

  36. Web Server : User Module – User List

  37. Web Server : Create User Form

  38. Web Server : User Information Preview

  39. Mobile App:Home Page

  40. Mobile App Menu Option

  41. Mobile App : School List Page

  42. Mobile App :Roster page

  43. ArchitectureTop-level physical and logical architecture Presha Thakkar

  44. System Context Diagram

  45. Artifacts

  46. Use Case : Admin

  47. Use Case : Program Staff

  48. Use Case : Volunteer

More Related