Smart tickets

Smart Tickets USIU Project Team

  • Project Manager: George Kamanu

  • UI/UX Designer: Francis Chianu

  • Product Owner: Chantal Pande

  • Quality Assurance Tester: Samson Onyancha

  • Software Developers:

    • Front-End: Sharon Kairu

    • Back-End: Melvin Ngugi, Josiah Mbao

  • Scrum Master: Stephen Kamau

Project Overview

/

/

Table of Contents

  1. Project Goals and Objectives

  2. Problem Definition

  3. User Requirements

  4. Agile Project Management

  5. System Design

  6. Collaborative and Slack Usage

  7. Documentation and Reporting

Problem Definition

USIU faces significant inefficiencies in managing event tickets due to outdated manual processes, which lead to prolonged queues, ticket fraud, and challenges in tracking attendance. Currently, there exists no centralized platform that allows students and event organizers to efficiently create, buy, and validate event tickets. The proposed solution is an online ticketing system explicitly designed for USIU, digitizing the ticketing process to ensure secure transactions, effective ticket distribution, and easy verification through QR codes.

Project Goals and Objectives

  1. Enhance Accessibility and Efficiency:

    • Develop a centralized platform for students and event organizers to create, purchase, and verify tickets easily.

  2. Improve Security and Fraud Prevention:

    • Implement QR code-based ticketing to prevent fake tickets and unauthorized access.

  3. Optimize Event Management and Tracking:

    • Provide organizers with real-time analytics concerning ticket sales, attendance, and user engagement.

User Requirements

Functional Requirements

  • User Authentication & Management:

    • Registration and login via university credentials for users.

    • Event organizers can manage events.

    • Students can browse and purchase tickets.

  • Event Creation & Management:

    • Organizers can create, modify, and delete events with relevant details like date, time, location, and ticket pricing.

    • Ability to set ticket limits for events.

  • Ticket Purchasing & Payment Integration:

    • Users can select and buy tickets.

    • Integration with payment gateways (mobile payments, credit/debit cards).

    • Receipt of a digital ticket with a unique QR code following successful purchase.

Functional Requirements Continued

  • QR Code Ticket Verification:

    • Each ticket has a unique QR code for scanning by event staff to validate entry, preventing duplicate or expired tickets.

  • User Dashboard:

    • Users can view their purchased tickets; organizers can track sales and event stats.

  • Notifications & Alerts:

    • Ticket purchase confirmations sent via email/SMS.

    • Alerts about event reminders and updates sent to ticket holders.

Non-Functional Requirements

  1. Scalability:

    • System must handle multiple simultaneous users without performance lag.

  2. Security:

    • Implementation of user authentication, encrypted transactions, and secure QR code generation.

  3. Reliability:

    • Minimal downtime, ensuring constant system availability.

  4. Usability:

    • User-friendly interface catering to both students and event organizers.

  5. Performance:

    • Fast loading times and quick QR code validations.

  6. Maintainability:

    • Well-structured codebase to enable easy updates and new feature integration.

  7. Cross-Browser Compatibility:

    • Web app functionality across all modern web browsers.

User Stories

  • User Experience:

    • View purchased tickets to verify bookings.

    • Receive updates and reminders for events.

    • Secure login using university credentials.

  • Event Organizer Experience:

    • Ability to track ticket purchases for analytical purposes.

    • Add events after proper verification.

Personas

Primary User: University Student

  • Activities include logging in, searching for events, purchasing tickets, and receiving notifications.

Organizer: University Event Coordinator

  • Responsibilities include creating and updating event information, tracking ticket sales for statistics.

Admin: IT Admin/University Staff

  • Tasks comprise event verification and system access management.

Agile Project Management

Scrum Practices

  1. Stand-ups:

    • Regular stand-up meetings to discuss progress held on Tuesdays and Thursdays.

  2. Sprint Planning:

    • Two sessions held to establish objectives and address issues for upcoming sprints.

  3. Reviews:

    • Conducted after two completed sprints for feedback and quality improvement.

  4. Retrospectives:

    • One meeting held to reflect on performance and identify areas for process improvement.

System Design

User Views

  • User Login, Home, Purchase, Personal Ticket QR Code View - Prototype Link available.

Admin Views

  • Events Management, Registry, Event Creation and Update Views.

Diagrams

Use Case Diagrams

  • Student actions include: Register, Log In, View Events, Make Payments, View Purchased Tickets, Scan Tickets.

Sequence Diagrams

  • Detailed steps of user login, event viewing, payment processing, and ticket retrieval.

Data Flow Diagrams

  • Level 0 and Level 1 diagrams illustrating user interactions and system database activities.

Entity Relationship Diagram

  • Diagram detailing relationships between Users, Notifications, Tickets, Payments, and Events.

Collaborative Tools

Using Slack

  • Active communication during Scrum, task division, and monitoring resources such as Slack, WhatsApp, Jira.

Documentation and Reporting

Project Documentation Overview

  1. Process Definition:

    • Steps of user authentication, event management, ticket purchasing, and more.

  2. Tools and Technologies:

    • Frontend: HTML, CSS; Backend: Python, Flask; Database: Google Cloud; Payments: Mobile money, credit/debit cards; Collaboration: Slack, GitHub, Jira.

  3. Risk Management:

    • Identifying risks associated with payment failures, security threats, and mitigations.

  4. Lessons Learned:

    • Agile methodology advantages, user feedback incorporation, and automated testing benefits.

  5. Version Control Practices:

    • GitHub usage with structured branching and consistent commit messaging.

Conclusion

The Smart Tickets documentation provides a well-rounded approach to the development and management of the ticketing system at USIU. This framework enhances the project’s ability to adapt, securely manage ticketing processes, and facilitate seamless communication and coordination among team members.