RMP.

Turning data into clarity

All projectsAcademic / Software & Data

Helping Hand (Charity)

An undergraduate charity-management web project supported by a 51-page SRS, UML/ER modeling and Scrum teamwork.

HTMLCSSJavaScriptPHPMySQLUMLScrum
PROJECT TYPEAcademic / Software & Data
MY ROLEAcademic group collaboration across requirements
TOOLS & METHODSHTML · CSS · JavaScript
PROJECT OVERVIEW

The story behind the work

Helping Hand was a team project in the undergraduate Software Project I course. The concept was a web-based charity-management platform connecting people, donation opportunities and charitable organizations. The focus was on requirements analysis, thoughtful software architecture and a documented implementation rather than a commercial launch.

THE CHALLENGE

Make donation and charity-service workflows easier to specify, manage and use.

GOALS & SCOPE

What I set out to do

  • Design a clear process for online charity and donation activities.
  • Document functional requirements, stakeholders, risks and test scenarios.
  • Model the application’s core relationships and user interactions.
  • Consider donation transparency, secure payment processes and collaborative delivery.
PROCESS & IMPLEMENTATION

From raw data to a useful result

Worked on a 51-page SRS, requirements gathering, risk analysis, UML/ER models, test cases, Scrum planning and web interfaces.

  • Gathered requirements, analyzed risks and estimated project effort with the group.
  • Co-authored a 51-page Software Requirements Specification (SRS) describing the proposed product and its functions.
  • Created UML and Entity-Relationship diagrams to connect user behavior with the underlying data model.
  • Documented test cases and worked within a Scrum-based development approach.
  • Contributed to web interface development and documented payment security considerations, including PCI DSS-related requirements.
MY ROLE & RESPONSIBILITIES

What I contributed

Academic group collaboration across requirements, system design, documentation and frontend contributions.

  • Contributed to translating the initial charity-service problem into software requirements and acceptance-oriented documentation.
  • Participated in the UML/ER modeling, risk assessment, test planning and group work coordination.
  • Helped turn the requirements into a usable academic web interface.
RESULTS & FINDINGS

What the project delivered

  • The primary deliverable included a comprehensive 51-page SRS together with UML/ER design artifacts.
  • The team developed an academic web-based charity-management interface and associated project documentation.
  • The deliverables documented approaches to donation transparency, usability and payment security without a separately verified commercial impact measurement.
OUTCOME & CONTEXT

The project brought together software requirements engineering, documentation, Agile team collaboration and secure-payment design considerations. Its deliverables demonstrate the academic software-development process from requirements to interface implementation.

REFLECTION

Challenges & lessons

  • Connecting functional requirements and security considerations

Clear documentation helps a team build the right features.