← Projects & Case Studies← Projects & Case Studies
PORTFOLIO PROJECT·LIBRARY SYSTEMS
Library Management Portal
BACentric Capstone Project · Independent
An independent BA capstone project for BACentric certification — full requirements-to-wireframe delivery for an Online Library Management System, covering member management, catalogue search, book issuance and returns, and fine tracking.
My Role
Sole Business Analyst for this independent capstone project — owned requirements gathering, process mapping, and solution design end-to-end, from initial project brief through to wireframes and validation criteria.
Approach
- ▸Authored a Project Brief defining the problem statement, objectives, and scope for an Online Library Management System
- ▸Mapped As-Is and To-Be business processes to identify manual bottlenecks in book issuance, returns, and member management
- ▸Produced a combined As-Is & To-Be process flow document to visualise the transition from manual to system-based operations
- ▸Authored a Business Requirements Document (BRD) covering functional and non-functional requirements
- ▸Broke down requirements into Epics and User Stories for a phased delivery approach
- ▸Designed wireframes covering core library workflows — member registration, catalogue search, book issue/return, and fine management
- ▸Built a Validation Sheet defining test scenarios and acceptance criteria against the documented requirements
Component Library
Deliverables & Outcomes
- ▸Project Brief — problem statement, objectives, and scope definition
- ▸As-Is & To-Be Process Flow documentation
- ▸Business Requirements Document (BRD)
- ▸Epics & User Stories backlog
- ▸UI Wireframes covering core library management workflows
- ▸Validation Sheet — test scenarios and acceptance criteria
Key Takeaways
- ▸Mapping As-Is process pain points before defining To-Be workflows kept requirements grounded in real operational friction rather than assumed functionality
- ▸Breaking the BRD into Epics and User Stories made scope easier to sequence and validate incrementally
- ▸Building the validation sheet alongside the requirements — not after — surfaced ambiguous acceptance criteria early
Artifacts