TOPIC - SCHOOL MANAGEMENT SYSTEM

I ABINASH ROUT SCIENCE. I

“ School
Introduction
The School Management System is a computerized solution
designed to help educational institutions manage day-to-day
administrative tasks efficiently. By integrating Python with
SQL, the system offers a user-friendly interface to handle
student information, class assignments, and overall school
management.

Objectives
The objective of this project is to let the students apply
the programming knowledge into a real-world
situation/problem and exposed the students ow
programming skills helps in developing a good
software.
1. To develop a system that allows easy management of
student data through Python and MySQL .
2. To implement CRUD (Create, Read, Update, Delete)
operations for managing school data effectively.
3. To ensure data security and improve the
efficiency of school management processes.
4. Apply object oriented programming principles
effectively when developing small to medium sized
projects.
1
Proposed System
The proposed School Management System automates
school administrative tasks such as managing student
and class records. It provides a user-friendly
interface for adding, viewing, updating, and deleting
student and class information.

Using Python for the interface and MySQL as the

database, the system ensures data is securely stored
and efficiently managed. The system supports full
CRUD operations, allowing users to manage records
easily. This solution simplifies school administration,
making it more efficient and reducing manual effort.

The School Management System aims to simplify

school administration and improve the overall
efficiency of managing records and daily tasks in
educational institutions.

2
System Development
Life Cycle (SDLC)
The System Development Life Cycle (SDLC) for the
School Management System involves several key
phases. First, requirements were gathered to
understand the need for managing student and class
data. Next, the system was designed using Python for
the interface and MySQL for the backend. During
implementation, CRUD operations were integrated,
allowing the system to add, view, update, and delete
records. The system was then thoroughly tested to
ensure functionality. After deployment on school
computers, the system is maintained for updates or
bug fixes as needed, ensuring long-term reliability and
efficiency.

3
Phases Of System Development
Life Cycle Initiation Phase
The Initiation Phase begins when a business sponsor identifies
a need or an opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business
accomplishments of the organization or a deficiency related to a
business need.
Identify significant assumptions and constraints on solutions to that
need.
Recommend the exploration of alternative concepts and methods to
satisfy the need including questioning the need for technology, i.e., will
a change in the business process offer a solution?
Assure executive business and executive technical sponsorship. The
Sponsor designates a Project Manager and the business need is
documented in a Concept Proposal. The Concept Proposal includes
information about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful Concept Proposal
results in a Project Management Charter which outlines the authority of
the project manager to begin the project.
Careful oversight is required to ensure projects support strategic
business objectives and resources are effectively implemented into an
organization's enterprise architecture. The initiation phase begins
when an opportunity to add, improve, or correct a system is identified
and formally requested through the presentation of a business case.
The business case should, at a minimum, describe a proposal’s
purpose, identify expected benefits, and explain how the proposed
system supports one of the organization’s business strategies. The
business case should also identify alternative solutions and detail as
many informational, functional, and network requirements as
possible. 4
System Concept
Development Phase
The System Concept Development Phase begins after a
business need or opportunity is validated by the
Agency/Organization Program Leadership and the
Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness of the alternatives.

Identify system interfaces.
Identify basic functional and data requirements to satisfy the
business
need.
Establish system boundaries; identify goals, objectives, critical
success factors, and performance measures.
Evaluate costs and benefits of alternative approaches to
satisfy the basic functional requirements
Assess project risks
Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a concept of
operations. This phase explores potential technical solutions within
the context of the business need.
It may include several trade-off decisions such as the decision to use
COTS software products as opposed to developing custom software or
reusing software components, or the decision to use an incremental
delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System Boundary
Document serves as an important reference document to support the
Information Technology Project Request (ITPR) process.
The ITPR must be approved by the State CIO before the project can
move forward.
5
 Pictorial Representation
Of SDLC

Planning Phase
The planning phase is the most critical step in completing development,
acquisition, and maintenance projects. Careful planning, particularly in the early
stages of a project, is necessary to coordinate activities and manage project risks
effectively. The depth and formality of project plans should be commensurate
with the characteristics and risks of a given project. Project plans refine the
information gathered during the initiation phase by further identifying the specific
activities
and resources required to complete a project.

A critical part of a project manager’s job is to coordinate discussions between

user, audit, security, design, development, and network personnel to identify and
document as many functional, security, and network requirements as possible.
During this phase, a plan is developed that documents the approach to be used
and includes a discussion of methods, tools, tasks, resources, project schedules,
and user input. Personnel assignments, costs, project schedule, and target dates
are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality
assurance planning, concept of operations, system security, verification
and validation, and systems engineering management planning.
6
Requirements Analysis Phase
This phase formally defines the detailed functional
user requirements using high-level requirements
identified in the Initiation, System Concept, and
Planning phases. It also delineates the requirements
in terms of data, system performance, security, and
maintainability requirements for the system. The
requirements are defined in this phase to a level of
detail sufficient for systems design to proceed. They
need to be measurable, testable, and relate to the
business need or opportunity identified in the
Initiation Phase. The requirements that will be used
to determine acceptance of the system are captured
in the Test and Evaluation Master Plan.
The purposes of this phase are to:
Further define and refine functional and
the data
requirements and document them in the Requirements
Document.
Complete business process reengineering of the
functions to be supported (i.e., verify what information
drives the business process, what information is
generated, who generates it, where does the information
go, and who processes it).
Develop detailed data and process models (system
inputs, outputs, and the process.
Develop the test and evaluation requirements that will
be
used to determine acceptable
7 system performance.
Design Phase
The design phase involves converting the informational, functional, and network
requirements identified during the initiation and planning phases into unified design
specifications that developers use to script programs during the development phase.
Program designs are constructed in various ways. Using a top-down approach,
designers first identify and link major program components and interfaces, then
expand design layouts as they identify and link smaller subsystems and connections.
Using a bottom-up approach, designers first identify and link minor program
components and interfaces, then expand design layouts as they identify and link larger
systems and connections. Contemporary design techniques often use prototyping tools
that build mock-up designs of items such as application screens, database layouts, and
system architectures. End users, designers, developers, database managers, and
network administrators should review and refine the prototyped designs in an iterative
process until they agree on an acceptable design. Audit, security, and quality assurance
personnel should be involved in the review and approval process. During this phase, the
system is designed to satisfy the functional requirements identified in the previous
phase. Since problems in the design phase could be very expensive to solve in the later
stage of the software development, a variety of elements are considered in the design
to mitigate risk. These include:

Identifying potential risks and defining mitigating design features.

Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new system.
Determining the operating environment.
Defining major subsystems and their inputs and outputs.
Allocating processes to resources.
Preparing detailed logic specifications for each software module. The result is
a draft System Design Document which captures the preliminary design for the
system.
Everything requiring user input or approval is documented and reviewed by
the user. Once these documents have been approved by the Agency CIO and
Business Sponsor, the final System Design Document is created to serve as the
Critical/Detailed Design for the system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business requirements.
Concurrent with the development of the system design, the Agency Project
Manager begins development of the Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.
8
Development Phase
The development phase involves converting design specifications into
executable programs. Effective development standards include
requirements that programmers and other project participants discuss
design specifications before programming begins. The procedures help
ensure programmers clearly understand program designs and functional
requirements. Programmers use various techniques to develop computer
programs. The large transaction oriented programs associated with
financial institutions have traditionally been developed using procedural
programming techniques. Procedural programming involves the line-by-
line scripting of logical instructions that are combined to form a program.
Effective completion of the previous stages is a key factor in the success
of the Development phase.
The Development phase consists of:
Translating the detailed requirements and design into system
components.
Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.
Integration And Test Phase
Subsystem integration, system, security, and user acceptance testing is
conducted during the integration and test phase. The user, with those
responsible for quality assurance, validates that the functional requirements, as
defined in the functional requirements document, are satisfied by the
developed or modified system. OIT Security staff assesses the system security
and issue a security certification and accreditation prior to
installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly supported by

end users prior to acceptance of the system.
Testing as a deployed system with end users working together with contract
personnel.
Operational testing by the end user alone performing all functions.
Requirements are traced throughout testing, a final Independent Verification &
Validation evaluation is performed and all documentation is reviewed and
accepted.

9
Implementation Phase
This phase is initiated after the system has been tested and
accepted by the user. In this phase, the system is installed
to support the intended business functions. System
performance is compared to performance objectives
established during the planning phase. Implementation
includes user notification, user training, installation of
hardware, installation of software onto production
computers, and integration of the system into daily work
processes. This phase continues until the system is
operating in production in accordance with the defined
user requirements
Operations And Maintenance Phase
The system operation is on-going. The system is monitored for
continued performance in accordance with user requirements and
needed system modifications are incorporated. Operations continue as
long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified,
the system may re-enter the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive
information.
Conduct periodic assessments of the system to
ensure the
functional requirements continue to be satisfied.
Determine when the system needs to be modernized,
replaced, or retired.
10
Source Code

11
12
Output Screens

13
14
 Testing
Software Testing is an empirical investigation conducted to provide stakeholders
with information about the quality of the product or service under test[1] , with
respect to the context in which it is intended to operate. Software Testing also
provides an objective, independent view of the software to allow the business to
appreciate and understand the risks at implementation of the software. Test
techniques include, but are not limited to, the process of executing a program or
application with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that a software
program/application/product meets the business and technical requirements
that guided its design and development, so that it works as expected and can be
implemented with the same characteristics. Software Testing, depending on the
testing method employed, can be implemented at any time in the development
process, however the most test effort is employed after the requirements have
been defined and coding process has been completed.
Testing Methods
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing
test cases.
Black Box Testing
Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs
testing, fuzz testing, model-based testing, traceability matrix,
exploratory testing and specification-based testing.
Specification-Based Testing
Specification-based testing aims to test the functionality of software
according to the applicable requirements.[16] Thus, the tester inputs data
into, and only sees the output from, the test object. This level of testing
usually requires thorough test cases to be provided to the tester, who then
can simply verify that for a given input, the output value (or behaviour),
either "is" or "is not" the same as the expected value specified in the test
case. Specification-based testing is necessary, but it is insufficient to guard
against certain risks 15
 Advantage And Disadvantages
The black box tester has no "bonds" with the code, and a tester's
perception is very simple: a code must have bugs. Using the
principle, "Ask and you shall receive," black box testers find bugs
where programmers don't. But, on the other hand, black box
testing has been said to be "like a walk in a dark labyrinth without
a flashlight," because the tester doesn't know how the software
being tested was actually constructed.
That's why there are situations when
1.a black box tester writes many test cases to check something that can be
tested by only one test case.
2. some parts of the back end are not tested at all. Therefore, black box
testing has the advantage of "an unaffiliated opinion," on the one hand,
and the disadvantage of "blind exploring," on the other.
White Box Testing
White box testing, by contrast to black box testing, is when the tester
has access to the internal data structures and algorithms (and the code
that implement these)

Types of white box testing:-

The following types of white box testing exist:
API testing - Testing of the application using Public and Private APIs.
Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements in
the program to be executed at least once.
fault injection methods.
mutation testing methods.
static testing - White box testing includes all static testing.

16
 Hardware And Software
Requirements
HARDWARE
I. OPERATING
WINDOWS 7 AND ABOVE
SYSTEM
PENTIUM(ANY) OR AMD
II .PROCESSOR ATHALON(3800+-
4200+DUALCORE
1.8495 OR 915,995 FOR PENTIUM
OR MSI
III. MOTHERBOARD K9MM-V VIAK8M800+8237R
PLUS CHIPSET FOR AMD
ATHALON
IV. RAM 512MB+

V. HARD DISK SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive
(if black up required)
combo
VII. FLOPPY DRIVE
(if backup required)
1.44MB
VIII. PRINTER (if print is required-[Hard copy])

SOFTWARE
i. Windows OS
ii. Python
17
18