Since its establishment in 2018, Modern Schools has sought a comprehensive school portal to automate and manage business processes. With over 500 students, 20 teachers, a school principal, an accountant, a secretary, a registrar, and two cleaning employees, Modern Schools now requires a state-of-the-art software system to streamline operations and improve efficiency.
The project involves developing an analysis and design model for this new system, aimed at automating processes such as student registration, class scheduling, assignments, messages, payments, salary receipts, grades publication, warnings, and teaching materials distribution.
With the challenges posed by the COVID-19 pandemic, the need for a modern school portal has become critical. This portal will facilitate:
- Communication between teachers and students.
- Assignment submissions and feedback.
- Viewing and managing schedules, grades, and warnings.
- Automated payment systems and payroll management.
The portal will remain relevant in face-to-face school scenarios, enhancing the overall teaching and learning experience.
- User Requirements: Develop and write a list of 7-9 comprehensive and core user requirements.
- System Requirements: Write detailed system requirements based on user requirements.
- Effort & Cost Estimation: Provide a rough estimate of project cost and effort.
- Scenario Analysis: Identify four or five key business scenarios, including normal, alternative, and error flows. Each group member writes one scenario.
- Actors and Use Case Diagram: Identify actors and use cases, then draw an overall use case diagram with actors' roles and semantic descriptions.
- Use Case Description: Write a detailed description of four or five key use cases. Each group member writes one use case.
- Instance Activity Diagrams: Create an activity diagram for each key use case to represent the workflow.
- System Class Modeling: Identify and describe system analysis classes, and create a detailed class diagram.
- System Sequence Modeling: Each group member writes one sequence diagram for their respective use case.
- System Design Goals: Define at least three design goals, including two general goals (e.g., low coupling, high cohesion) and one system-specific goal (e.g., performance in processing speed).
- System Component Design: Create a component diagram that aligns with the design goals.
- System Deployment Design: Develop a deployment diagram mapping software components to hardware nodes.
- Student and teacher registration.
- Collecting and managing student information (e.g., personal, parental, medical, and academic details).
- Assigning classes and schedules for teachers.
- Payment collection and reminders.
- Managing discounts and payroll for employees.
- Monitoring student grades, attendance, warnings, and complaints.
- Overseeing teacher performance and attendance.
- Viewing schedules and publishing materials (PDF, Word, etc.).
- Sending assignments and messages.
- Publishing grades and feedback.
- Viewing schedules, assignments, messages, grades, warnings, and payments.
- Low Coupling: Ensure minimal dependencies between system modules.
- High Cohesion: Maintain a strong focus within each module.
- Performance: Optimize for high processing speed.
- Use Case Diagram: Visual representation of actors and use cases.
- Class Diagram: Detailed model of system classes and their relationships.
- Activity Diagrams: Workflows for key use cases.
- Component Diagram: Software component structure.
- Deployment Diagram: Hardware and software mapping.
A detailed breakdown of project effort and cost will be included in the project documentation.
This project is a collaborative effort by the team, with each member contributing to specific tasks outlined in the project phases.