sasa event — Software Requirements Specification (SRS)
Table of Contents
- 1 Document Information
- 2 Project Overview
- 3 User Requirements
- 4 Detailed Feature Requirements
- 5 Technical Requirements
- 6 External Dependencies
- 7 Release Planning
- 8 Risks Assumptions
- 9 Market Specific Considerations
- 10 Sign Off
- 11 Additional Context
1 Document Information
| Field | Value |
|---|---|
| Project Name | sasa event |
| Version | 0.1 |
| Date | 2025-08-07 |
| Project Manager | TBD |
| Tech Lead | TBD |
| Qa Lead | Tester |
| Platforms | ['Android', 'iOS'] |
| Document Status | Draft |
2 Project Overview
2.1 What Are We Building
2.1.1 System Function
A mobile application for users to discover, interact with, and manage attendance for events.
2.1.2 Users
- Event Attendee
2.1.3 Problem Solved
The application aims to provide a centralized platform for event discovery and management, which is currently hampered by critical issues such as inability to add events, faulty ticket payment systems, and login failures.
2.1.4 Key Success Metric
Increase the Overall Quality Percentage from 44.4% to over 95% by resolving all major defects.
2.2 Scope
2.2.1 In Scope
- User authentication via phone number and email.
- Event discovery and viewing upcoming event lists.
- Viewing event details.
- Ticket payment functionality.
- User profile management.
- Notification feature.
- Language selection.
- Dark mode support.
- RSVP to events.
2.2.2 Out Of Scope
- Adding new events by users (feature is missing).
- Wishlist feature (dependent on adding events).
- Ticket purchasing (dependent on adding events).
3 User Requirements
3.1 Authentication User Management
| Feature Code | I Want To | So That I Can | Priority | Notes |
|---|---|---|---|---|
| FT-AUTH-LOGIN-PHONE | Log in successfully using my phone number | Access the application's features. | Must | This functionality is currently passing on both Android and iOS. |
| FT-AUTH-LOGIN-EMAIL | Log in successfully using my email and password | Access the application's features. | Must | This is a critical failure point. 'Couldn't login with an email' (Bug ID 010). It fails on both Android and iOS. |
| FT-AUTH-LOGOUT | Log out of the application | Securely end my session. | Must | This functionality is currently passing on both Android and iOS. |
3.2 Core Business Features
| Feature Code | I Want To | So That I Can | Priority | Notes |
|---|---|---|---|---|
| FT-EVENT-VIEW-LIST | View a list of upcoming events | Discover what is happening. | Must | This functionality is currently passing on both Android and iOS. |
| FT-EVENT-VIEW-DETAILS | View the full details of a specific event | Get all the necessary information like description, location, and host. | Must | This passes on Android but causes the app to crash on iOS ('Sasa event crashed'). |
| FT-EVENT-ADD | Add a new event to the platform | Share it with other users. | Must | Critical missing feature. 'There is no feature for adding an event' (Bug ID 001). This prevents core functionality. |
| FT-TICKET-PAY | Pay for an event ticket | Secure my attendance. | Must | Major failure. The payment screen shows 'coming soon' on Android. Also reported as 'Payment problem with cash method' (Bug ID 004). |
3.3 Additional Features
| Feature Code | I Want To | So That I Can | Priority | Notes |
|---|---|---|---|---|
| FT-PROFILE-VIEW | View my user profile information | Check my details like name and mobile number. | Should | This functionality is currently passing on both Android and iOS. |
| FT-EVENT-RSVP | RSVP to an event | Indicate my intention to attend. | Should | This feature is not runnable. On Android, the button is missing. On iOS, it causes the app to crash. |
| FT-UI-DARKMODE | Change the app to dark mode | Use the app comfortably in low-light conditions. | Should | Fails on both platforms. Not all screens change to dark, and some words aren't visible (Bug ID 008). |
| FT-UI-LANGUAGE | Change the application language | Use the app in my preferred language. | Should | Fails or is not runnable. On Android, it shows a grey screen. On iOS, not all words change (Bug ID 011). |
| FT-APP-NOTIFICATIONS | View notifications | Stay updated on event-related news. | Should | Major failure. The notification button does not work on either platform (Bug ID 005). |
4 Detailed Feature Requirements
4.1 Ft Auth Login Email
4.1.1 Priority
Must Have
4.1.2 User Story
As a user with a valid email and password, I want to log in to the app so I can access its features.
4.1.3 Preconditions
A user with a valid email and password exists.
4.1.4 Postconditions
The user is successfully logged in and redirected to the dashboard or event list.
4.1.5 Test Cases
| Id | Description | Weight |
|---|---|---|
| AUTH-TC-001 | Failed login with valid email and password. | High |
4.2 Ft Event Add
4.2.1 Priority
Must Have
4.2.2 User Story
As a user, I want to post an event so that other users can see it.
4.2.3 Preconditions
The user is successfully logged in.
4.2.4 Postconditions
The new event is posted and visible to other users.
4.2.5 Test Cases
| Id | Description | Weight |
|---|---|---|
| EVENT-TC-001 | Could not post an event as it is posted through Sasa Chat app. | High |
4.3 Ft Ticket Pay
4.3.1 Priority
Must Have
4.3.2 User Story
As a user, I want to complete a ticket payment so I can attend an event.
4.3.3 Preconditions
The user is viewing an upcoming event.
4.3.4 Postconditions
The user is directed to a secure payment gateway, completes the transaction, and receives a confirmation and ticket.
4.3.5 Test Cases
| Id | Description | Weight |
|---|---|---|
| EVENT-TC-005 | Ticket payment screen displayed 'coming soon'. | High |
4.4 Ft Event View Details
4.4.1 Priority
Must Have
4.4.2 User Story
As a user, I want to tap on an event to see its details without the app crashing.
4.4.3 Preconditions
An active event exists in the app.
4.4.4 Postconditions
The event details page is displayed, showing full information.
4.4.5 Test Cases
| Id | Description | Weight |
|---|---|---|
| EVENT-TC-003 | The app keeps crushing and closing completely. | High |
5 Technical Requirements
5.1 Performance Standards
| Requirement | Target | How To Test |
|---|---|---|
| App Stability | Zero crashes during core user flows (viewing events, navigation). | Execute test cases for event management and navigation on iOS. |
| App load | ≤ 3s | Stopwatch on target devices |
5.2 Platform Requirements
| Platform | Minimum Version | Target Version | Notes |
|---|---|---|---|
| Android | Android 9 (API 28) | Latest | Testing was performed on an AQUOS sense3 plus. |
| iOS | iOS 14 | Latest | Testing was performed on an iPhone 11 plain. |
5.3 Security Privacy
| Requirement | Must Have | Implementation |
|---|---|---|
| User data encryption | True | AES-256 at rest; TLS 1.2+ in transit |
| Privacy Policy and Terms of Use | True | The content of the privacy policy and terms of use must match the app's functionality (Bug ID 007). |
6 External Dependencies
6.1 Third Party Services
| Service | What It Does | Criticality | Backup Plan |
|---|---|---|---|
| Payment Gateway | Processes ticket payments. | Critical | The feature is not yet implemented. A provider needs to be selected and integrated. |
| Sasa Chat app | Currently the only way to post an event. | High | Implement a native event creation feature within the 'sasa event' app. |
7 Release Planning
7.1 Development Phases
| Phase | Features Included | Timeline | Success Criteria |
|---|---|---|---|
| Phase 1 (Critical Fixes) | ['FT-AUTH-LOGIN-EMAIL (fix)', 'FT-EVENT-ADD (implement)', 'FT-TICKET-PAY (implement)', 'FT-EVENT-VIEW-DETAILS (iOS crash fix)', 'FT-APP-NOTIFICATIONS (fix)'] | 4 weeks | All 'Must' priority features are functional and pass testing on both Android and iOS. Overall Quality score > 80%. |
| Phase 2 (Should Fixes & UI Polish) | ['FT-EVENT-RSVP (implement/fix)', 'FT-UI-DARKMODE (fix)', 'FT-UI-LANGUAGE (fix)', 'Fix all minor bugs (002, 006, 007, 009, 011)'] | 4 weeks | All features are fully functional. No critical or major bugs remain. Overall Quality score > 95%. |
7.2 Release Checklist
- All Must-Haves complete and functional
- No critical bugs as identified in the report
- Performance baselines met (especially no crashes on iOS)
- Payment gateway successfully integrated and tested
- Privacy policy and terms of use content verified
8 Risks Assumptions
8.1 Risks
| Risk | Probability | Impact | Mitigation |
|---|---|---|---|
| Inability to implement a native event-adding feature, making the app dependent on 'Sasa Chat app'. | High | High | Prioritize the development of a native event creation module. |
| Payment gateway integration is complex and causes delays. | Medium | High | Begin research and selection of a payment provider early; allocate sufficient development and testing time. |
| Persistent stability issues on iOS lead to a poor user experience and negative reviews. | High | High | Allocate dedicated iOS development resources to specifically address and resolve all identified crashes. |
8.2 Assumptions
- The 'Sasa Chat app' dependency for adding events is a temporary workaround and not a long-term solution.
- Users expect standard features like dark mode and language switching to work correctly.
- The target users have access to digital payment methods.
9 Market Specific Considerations
9.1 Primary Market
- General
9.2 Target Demographics
- Users looking for local events
9.3 Payment Preferences
| Preference | Value |
|---|---|
| Mobile Money | TBD |
| Cash | TBD |
| Cards | TBD |
10 Sign Off
10.1 Approval
| Role | Name | Signature | Date |
|---|---|---|---|
10.2 Document History
| Version | Date | Changes Made | Changed By |
|---|---|---|---|
| 0.1 | 2025-08-07 | Initial draft created from testing report. | Gemini System Designer |
11 Additional Context
11.1 Success Metrics
11.1.1 Customer Acquisition
1,000 active users within 3 months of relaunch.
11.1.2 Partner Signups
N/A
11.1.3 Daily Orders
50 successful ticket transactions per day within 3 months.
11.1.4 Customer Satisfaction
≥ 4.0-star rating on app stores.
11.1.5 Order Success Rate
≥ 98% successful payment transactions.
11.1.6 Average Delivery Time
N/A