Ayoola lateef
Bu/23c/eng/9442
1. Identify Stakeholder Groups & Key Requirements
Stakeholders:
• Admin: System setup, access control, reporting.
• Donor: View donation history, update profile, make donations.
• Project Manager: Allocate donations, track project funding.
• Finance Staff: Monitor funds, generate financial reports.
• IT Staff: System maintenance, user support.
Key Requirements:
•Secure login & role-based access.
•Track donations with donor info and timestamps.
•Link donations to specific projects.
•Generate real-time and historical reports.
•Profile management for donors.
•Dashboard for project funding status.
2. Create Personas
•Admin (Amaka, 38): NGO administrator, tech-savvy, needs overview and control.
•Donor (Chidi, 45): Businessman, wants transparency and easy donation tracking.
•Project Manager (Ngozi, 33): Oversees health projects, needs quick access to funding data.
⸻
3. SRS Excerpt
Problem Definition:
Current manual tracking of donors, donations, and project funding leads to inefficiency and errors. A centralized digital system is
needed.
Scope:
The system will manage donor records, track donations, assign funds to projects, and support reporting and user role management.
Requirements List (sample):
•FR1: System shall allow donors to register and login.
• FR2: Admin shall view all donor and donation data.
• FR3: System shall link donations to projects.
• NFR1: System must be available 99.9% uptime.
• NFR2: Data should be encrypted at rest and in transit.
4. ER Diagram (Entities & Relationships)
.
⸻
5. Class Diagram
6. Access Control Model
Role View Donations Manage Projects View Reports Edit Profiles
Donor Own only Own only
Project Manager
Admin
Finance Staff
7. UI Wireframes Suggestions
Donor Profile Page:
• Profile Picture
• Name, Email, Phone
• “Edit Profile” button
• Recent donations list
Donation History Page:
• Table with: Date, Amount, Project, Status
• Filters: by date, project
• Download receipt button
