Centralized Grading System
LCO Objectives Operational Concepts System Requirements System and Software Architecture Lifecycle Plan Feasibility Rationale
Operational Concepts Provide a centralized source to view and edit grades Enhance communication between student, parent, and teacher Automatic notifications Easy access to statistical information
System Requirements Three components: Web/Database Server Web based client (Students and parents) Client-side program (Teachers) Other requirements: Password protected accounts Account privileges
System and Software Architecture Web/Database Server Web server (IIS, Apche, etc.) Database server (SQL) Web based client (Students and parents) Java or.Net Client-side program (Teachers) Java or.Net
Lifecycle Plan 10 Backend Clients Beta Final May AprilJune
Feasibility Rationale Assumptions Student’s, teacher’s, and parent’s needs User participation Security Risks Team knowledge and experience Budget and Resources
Conclusion Centralized source for grading Three components Six to eight people Eight weeks to complete