Iqra University Islamabad

Department of Computer & Technology

(CSC351/SEN351) Software Engineering

BS (CS)

Assignment No.1

School Management System

Submitted by:

Student 1
Ck-FA20-110024
Student 2
Ck-FA20-110021
Student 3
Ck-FA20-110052

Submission Date:
07 – April – 2023
Use Case Diagram

Detail Use Case

Feature Name (School Management System Generally use for every School)

Use Case Name (Example: Withdraw Cash)

Use Case ID: UC-001: Manage Student Information

UC-002: Manage Teacher Information
UC-003: Manage Parent Information
UC-004: Manage Course Information
UC-005: Enroll Students in Courses
UC-006: View Student Attendance
UC-007: Manage Student Grades
UC-008: Generate Student Reports
UC-009: Manage Teacher Schedule
UC-010: Manage School Resources (e.g. classrooms, textbooks, etc.)
UC-011: Manage School Finances
UC-012: Generate School Reports (e.g. financial, student performance, etc.)
UC-013: Manage User Accounts (e.g. administrators, teachers, students,
parents, etc.)
UC-014: Communicate with Parents and Students (e.g. messaging,
announcements, etc.)
UC-015: Monitor Student Progress and Performance.
Use Case Name: UC-001: Manage Student Information - This use case involves creating,
updating, and deleting student records, as well as viewing and searching for
student information.

UC-002: Manage Teacher Information - This use case involves creating,

 updating, and deleting teacher records, as well as viewing and searching for
teacher information.

UC-003: Manage Parent Information - This use case involves creating,

updating, and deleting parent records, as well as viewing and searching for
parent information.

UC-004: Manage Course Information - This use case involves creating,

updating, and deleting course records, as well as viewing and searching for
course information.

UC-005: Enroll Students in Courses - This use case involves enrolling students
in courses, updating enrollment records, and dropping students from courses.

UC-006: View Student Attendance - This use case involves recording and
viewing student attendance information.

UC-007: Manage Student Grades - This use case involves recording and
updating student grades, as well as calculating overall grades and GPA.

UC-008: Generate Student Reports - This use case involves generating and
printing student reports, such as report cards and transcripts.

UC-009: Manage Teacher Schedule - This use case involves creating and
updating teacher schedules, as well as assigning teachers to courses.

UC-010: Manage School Resources - This use case involves managing school
resources, such as classrooms, textbooks, and equipment.

UC-011: Manage School Finances - This use case involves managing school
finances, such as budgeting, billing, and accounting.

UC-012: Generate School Reports - This use case involves generating and
printing school reports, such as financial reports and student performance
reports.

UC-013: Manage User Accounts - This use case involves creating, updating, and
deleting user accounts for administrators, teachers, students, and parents.

UC-014: Communicate with Parents and Students - This use case involves
sending and receiving messages and announcements to and from parents and
students.

UC-015: Monitor Student Progress and Performance - This use case involves
tracking and analyzing student performance data to identify areas for
improvement and provide support as needed.
Actors: 1. Administrator - An administrator is responsible for managing the
system, creating and managing user accounts, and setting system
configurations.
 2. Teacher - A teacher is responsible for managing courses, recording
attendance, entering grades, and communicating with students and
parents.

3. Student - A student is the primary beneficiary of the system and

interacts with it to view course schedules, access course materials,
check grades, and receive notifications.

4. Parent - A parent is an interested party in the student's performance

and interacts with the system to view course schedules, access course
materials, check grades, and receive notifications.

5. Staff - Staff members may include school secretaries, librarians,

custodians, and other personnel who use the system to perform tasks
related to their job responsibilities.

6. External stakeholders - External stakeholders may include government

agencies, regulatory bodies, or accrediting organizations that interact
with the system to review school performance data, audit financial
records, or enforce regulations.
Preconditions: 1. The system is installed and running on a server or cloud-based platform
accessible to authorized users.

2. The user is authenticated and authorized to access the system based on

their role and privileges.

3. Student, teacher, and course records are already created and available
in the system.

4. Course schedules and class rosters are already created and available in
the system.

5. Attendance and grade recording policies and procedures are already

defined and communicated to users.

6. School resources, such as classrooms, textbooks, and equipment, are

already assigned and available in the system.

7. Financial data, such as budgets, invoices, and receipts, are already

entered and available in the system.

8. The system is up to date with the latest security patches and updates to
ensure the safety and integrity of user data.

9. The system is designed and developed to meet the regulatory and

compliance requirements of the school's jurisdiction.

10. The system has adequate resources and capacity to handle the
expected workload and usage patterns.
Post conditions: 1. Student, teacher, and course records are updated and accurate in the
 system.

2. Course schedules and class rosters are updated and accurate in the
system.

3. Attendance and grade records are updated and accurate in the system.

4. Student reports, such as report cards and transcripts, are generated

and available for distribution.

5. School resources, such as classrooms, textbooks, and equipment, are

properly assigned and utilized.

6. Financial data, such as budgets, invoices, and receipts, are accurately

recorded and reported.

7. User accounts are properly managed and maintained in the system.

8. Communication with parents and students is timely and effective,

enhancing their engagement and satisfaction.

9. Student progress and performance data are analyzed and acted upon
to improve student outcomes.

10. The system is continuously monitored, maintained, and improved to

ensure its reliability, availability, and security.
Normal Flow: 1. The user logs in to the system using their username and password.

2. The user selects the appropriate menu option based on their role and
intended action.

3. The user navigates to the relevant screen or form to enter or view data.

4. The user enters the required data, such as student, teacher, or course
information.

5. The system validates the entered data to ensure its accuracy and
completeness.

6. The user saves the entered data to the system.

7. The system confirms the successful saving of the data and updates the
relevant records.

8. The user views the updated data to confirm its accuracy.

9. The user navigates to other screens or forms to perform other actions,

such as recording attendance or grades, generating reports, or
communicating with parents and students.
 10. The user logs out of the system when finished using it.

Note: This normal flow is a general example and may vary based on the specific
use case and system design.
Alternative 1. The user logs in to the system using their username and password.
Flows:
2. The user selects the appropriate menu option based on their role and
intended action.

3. The user navigates to the relevant screen or form to enter or view data.

4. The user enters the required data, such as student, teacher, or course
information.

5. The system identifies an error in the entered data, such as an incorrect

date or missing required fields.

6. The system displays an error message to the user, indicating the error
and providing guidance on how to correct it.

7. The user corrects the error and resubmits the data to the system.

8. The system validates the corrected data and confirms its successful
saving.

9. The user views the updated data to confirm its accuracy.

10. The user navigates to other screens or forms to perform other actions,
such as recording attendance or grades, generating reports, or
communicating with parents and students.

Note: This alternative flow is a general example and may vary based on the
specific use case and system design. Other types of alternative flows may
include exceptions, errors, or unexpected events that require deviation from
the normal flow.

[Alternative 1. The user logs in to the system using their username and password.
Flow 1 – Not in
Network] 2. The user selects the appropriate menu option based on their role and
intended action.

3. The user navigates to the relevant screen or form to enter or view data.

4. The user enters the required data, such as student, teacher, or course
information.

5. The system attempts to save the entered data to the database but
 encounters a network connectivity issue.

6. The system displays an error message to the user, indicating that the
data cannot be saved at the moment due to a network error.

7. The system prompts the user to try again later or to save a local copy of
the data to be uploaded later.

8. The user selects the appropriate option based on their preference and
the urgency of the task.

9. If the user decides to save a local copy of the data, the system saves the
data to a local cache or file for later synchronization with the database.

10. The user logs out of the system.

Note: This alternative flow is a general example and may vary based on the
specific use case and system design. Other types of network connectivity issues
may include intermittent connections, slow connections, or server downtimes
that may affect the normal flow of the system.

Exceptions: 1. The user logs in to the system using their username and password.

2. The user selects the appropriate menu option based on their role and
intended action.

3. The user navigates to the relevant screen or form to enter or view data.

4. The user enters the required data, such as student, teacher, or course
information.

5. The system identifies an unexpected error, such as a database

corruption or system malfunction.

6. The system displays an error message to the user, indicating that the
action cannot be completed due to an unexpected error.

7. The system logs the error and notifies the system administrator or
technical support team to investigate and resolve the issue.

8. The user is prompted to retry the action later or to select an alternative

action.

9. If the user chooses to retry the action later, the system saves the
entered data and prompts the user to try again at a later time.

10. The user selects an alternative action, such as generating a report or

communicating with a colleague.

Note: This exception flow is a general example and may vary based on the
 specific use case and system design. Other types of exceptions may include
system crashes, data loss, or security breaches that require special handling
and attention.
Includes: 1. The user logs in to the system using their username and password.

2. The system validates the user's credentials and grants them access to
the appropriate features and data based on their role.

3. The user selects the appropriate menu option to generate a report on

student attendance.

4. The system displays the report generation screen, which includes

options for selecting the date range, student group, and output format.

5. The user selects the desired options and clicks on the "Generate
Report" button.

6. The system retrieves the necessary data from the database and formats
it according to the selected output format.

7. The system includes a feature that allows the user to preview the
report before downloading or printing it.

8. The user reviews the preview and verifies the accuracy of the data.

9. The user clicks on the "Download" or "Print" button to save or print the
report.

10. The system updates the user's report generation history and logs the
action for audit purposes.

Note: This includes flow is a general example and may vary based on the
specific use case and system design. Other types of includes may include
common functions, such as user authentication, data validation, or error
handling, that are used across multiple features and screens of the system.
Quality 1. Performance: The system should be able to handle a large number of
Requirements users and data entries without significant delays or crashes. The
response time for common user actions, such as logging in, retrieving
data, or generating reports, should be less than a few seconds.

2. Security: The system should ensure the confidentiality, integrity, and

availability of the data stored in the database. The user authentication
and access control mechanisms should prevent unauthorized access or
 modification of the data. The system should also have backup and
disaster recovery procedures to minimize the risk of data loss or
corruption.

3. Usability: The system should be intuitive and user-friendly, even for

users with limited technical skills or experience. The navigation and
user interface should be consistent and easy to understand. The system
should also provide clear and informative error messages to guide users
in case of mistakes or exceptions.

4. Reliability: The system should be reliable and available 24/7, with

minimal downtime or maintenance windows. The system should also
have mechanisms to detect and recover from errors or failures, such as
system crashes, network interruptions, or data corruption.

5. Scalability: The system should be able to handle future growth and

expansion of the school or district. The system should have the capacity
to store and process larger amounts of data, support more users and
roles, and integrate with new technologies or systems as needed.

Note: These quality requirements are a general example and may vary based
on the specific use case and system design. Other types of quality
requirements may include compatibility, maintainability, portability, or
regulatory compliance.

The End 