SALALE UNIVERSITY

COLLEGE OF NATURAL SCIENCE

DEPARTMENT OF COMPUTER SCIENCE
Project Title: Web Based School Management System In
Case Of Salale University Special Non-Boarding School.
No Name ID Number Email Address Phone
Number
1 DEME DEGO RU2333/14 [email protected] +2519030365
19
2 MAHDI BUSERI Advisor:
RU2341/14 - Mrs. Marta
[email protected] Legese (MSc).
+2519173959
om 59
3 OBSA SOLOMON
Submission
RT10099/16
Date: 23/05/2017 EC.
[email protected] +2519255084
m 45
 Introduction
 Established in 2013 E.C.
 part of Salale University.
 Dedicated to providing exceptional, high-quality education.
 Focus on academic excellence and make competitive student.
 320 students.
 Focus on natural science stream.
 Statement of the problem

 The manual system requires a long time to distribute information

for stakeholders.
 Record files of information may lose if the hard copies document
is destroyed.
 Lack of a centralized system for managing school activities.
 Redundant Information entered multiple times across different
forms or document
 The difficulty and time required to locate and access specific
information within a large volume of paper documents.
 Objective
General Objective
 The general objective of this project is to develop web-based
School Management System in case of Salale University Special
Non-Boarding School.
 Specific Objectives
 To Study and analysis problem of the existing system.

 To design, database architecture.

 To develop user friendly user interface.

 To implement the proposed system.

 To test the functionality of the system.
 To facilitates account management, report generate, mark, class
and subject management operation for specific stakeholder.
 Methodology
 Data Collection Methods
 Interviews: We Conducted with school director to identify
existing management system and identify associated
challenges.
 Observations: Team members physically observed the current
manual processes to understand inefficiencies and areas for
improvement.
 System design approach

 we selected object-oriented system UML for analysis and design

method.
 It is Standardized modeling language for system and software
development.
 To improved communication among stakeholders
 To enhanced understanding of system requirements
 To facilitates better system design and documentation
 Feasibility
 Faster processing times and reduced errors.
 The system is designed to be user-friendly, requiring minimal
training for staff and students.
 The system solve current challenges in student registration and
record management.
 The system adheres to university regulations and respects data
protection laws.
 Scope
 The system work for only slu special non boarding high school
 The system can Generate reports
 Secure storage and access control for sensitive information
 Class assignments, subject management, and mark entry.
 Access personal information, view marks, and schedules.
 Registration, updates, and delete.
 Existing system
 Current system is operate Paper-Based Processes Operations.
The operation perform manually is
 Student Registration.
 Report Generation.
 Class & Subject Management.
 Mark Recording etc.
Business rule (1) Business Rules
Business rule (1)
 It is describes the operations, policies, access rights and limitations of their
Business rule (1)activities.
day-to-day
Business
 rule (1)
BR1: - Only administrators can add new classes and subject, manage user
accounts (create, update, delete) for Teachers, Students, and the
Registrar's office.

 BR2: - the registrar's office can Register, Update, Search, Student also
view them.

 BR3: - Teachers can only view and insert marks for students in their
assigned classes. They cannot modify student accounts or class
information.
 Con’t…
 BR4: -Students can only view their own class schedules, subject

details, and marks. They cannot access or modify other students'

information.
 BR5: - All student records must include a unique student ID, name,

and contact information.

 BR6: - Marks enter by teachers must be within a valid range (e.g., 0-

100).
 BR7: -Users have valid contact example phone number.
 New system (2)
New System
 Functional Requirements:-
 User Management.
 Student Registration.
 Student Information Management.
 Mark Record and Management.
 Report Generation.
 Student Search.
 Class Assignment View.
 Con’t…
 Non-functional Requirements and Constraints:-
 Security: Role-based access via valid username/password.
 Performance: Fast response time with single-click actions.
 Usability: Attractive user interface and graphics.
 Maintenance: Easy and cost-effective system maintenance.
 Actors in the Proposed System

 Administrator: Manages all user accounts.

 Registrar Office: Manages student information.
 Teacher: Manages student marks
 student: Views own class, marks, and subjects.
 use case

,
 CRC
 Responsibilities:
Object actions.
 Collaborators:
Interacting objects.
 Purpose: Identify
objects & their
interactions.
 User Interface Prototyping
,
 Purpose and Goals of Design
Enhancing Efficiency: The design of the web-based
school management system (SMS) focuses on improving
student and administration effectiveness by:-
 Reduces manual tasks and errors.
 Provides easy access to all data or Centralization: .
 Features an intuitive and user-friendly interface.
 Maintainability: Built for easy updates and code reuse.
 Accessibility: Designed for all users, including system
admin and student.
 Current Software Architecture
 The school management system currently operates manually,
lacking accessibility.
 There is no established database architecture, leading to
inefficiencies.
 Reliance on paper-based processes increases the risk of errors
and data loss.
 Absence of a centralized system hampers effective data
management and retrieval.
 Proposed Software Architecture

 Two-Tier Architecture: The proposed system uses a two-tier

database architecture for enhanced performance and scalability.
 Data Security: Sensitive information, such as student marks and
personal data, is stored separately to protect against
unauthorized access.
 Ease of Maintenance: The architecture divides the system into
front-end and back-end, simplifying issue identification and
resolution.
 Increased Reliability: Ensures data availability and accessibility,
reducing system downtime and enhancing overall reliability.
 Subsystem Decomposition

 User Management Subsystem: Manages user registration,

and role-based access control for students, teachers, and
administrators.
 Student Information System: Handles student data
management, including registration, marks viewing, class
assignments, and password updates.
 Subject Management Subsystem: Facilitates the creation,
viewing, addition, and assignment of subjects.
 Reporting and Analytics Subsystem: Generates
performance reports to aid in monitoring and decision-making
 Component Diagram
A component diagram in UML illustrates the high-level structure
of a system or software application.
Depicts how various components or modular parts interact and
relate to one another.
Shows the organization of software parts and their dependencies
to ensure proper system operation.
Provides a high-level view of the system's architecture,
highlighting how components work together effectively.
 Deployment Diagram

A deployment diagram in UML illustrates the physical

deployment of software components (artifacts) on hardware
nodes.
 Shows the distribution of software components across various
hardware nodes or computing devices.
 Helps visualize how the system's software interacts with the
underlying hardware infrastructure.
 Provides insights into the system's architecture and resource
allocation, aiding in performance and scalability considerations
 Database Design (E-R Diagram) for Relational Database
E-R diagram is a visual representation of entities, their
attributes, and relationships within a relational database.
Helps to understand the structure and organization of the
database.
Main Components:
Entities: Represent objects or concepts that need data storage.
Attributes: Characteristics of entities providing additional
information. Depicted as ovals connected to their corresponding
entity rectangles.
Relationships: Define how entities are interconnected and
Represent associations or connections between different
entities.