For BSIS programmes the capstone usually solves a real business problem with a working system. The grading rubric typically rewards alignment with industry practice and clear documentation of the SDLC.
BSIS Capstone Anchors
Anchor
What Panel Looks For
Real beneficiary
Named, endorsed, accessible
Working system
Deployed (even on staging), demoable
SDLC documentation
Each phase has an artefact
Quality assurance
At minimum, ISO 25010 acceptance survey
Business impact
Quantified or strongly evidenced
Common BSIS Project Types
Type
Example
Internal operations
Attendance, inventory, queueing
Customer-facing
Online ordering, reservation, loyalty
Decision support
Sales dashboard, predictive maintenance
Compliance
Document tracker, audit trail
Public good
Barangay services, school records
What Differentiates A Top BSIS Capstone
Element
Adequate
Top-grade
Beneficiary
One name on the endorsement
Active partnership, joint co-design sessions
Requirements
Listed
Traceability matrix to objectives
Testing
Some test cases
Full test plan, automation where possible
Deployment
Localhost demo
Staging environment with the beneficiary
Documentation
User manual
User + maintenance + admin manuals, plus an architecture document
Risks To Manage
Beneficiary loses interest mid-project (most common cause of capstone failure).
Scope creep from well-meaning beneficiary requests.
Discussion
Loading…