22682362
Md.SAKIR ANSARI
Md.SAKIR ANSARI 22682347
SCHOOL
MANAGMENT SYSTEM
BRL DAV
Md.SAKIR ANSARI
XII 'A'
4
21
OUTPUTS 22
MYSQL DATABASE 29
32
PROJECT ON SCHOOL MANAGEMENT SYSTEM
INTRODUCTION
The SCHOOL. Management System s a software used to register
oneself for a course in our SSA Computer Institute.
Note :
• Allow the user to input their number, name, desired course
• Allow the administrator to delete an enrollment, edit the name and course of a
candidate.
• Allows the user to see the details.
OBJECTIVES OF THE PROJECT
The objective of this project is to let the students apply the programming
knowledge into a real- world situation/problem and exposed the students how
programming skills helps in developing a good software.
• Write programs utilizing modern software tools.
• Apply object oriented programming principles effectively when developing small
to medium sized projects.
• Write effective procedural code to solve small to medium sized problems.
• Students will demonstrate a breadth of knowledge in computer science, as
exemplified in the areas of systems, theory and software development.
• Students will demonstrate ability to conduct a research or applied Computer
Science project, requiring writing and presentation skills which exemplify
scholarly style in computer science.
HARDWARE AND SOFTWARE REQUIREMENTS
I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE
II. PROCESSOR : PENTIUM(ANY) OR AMD
ATHALON(3800+- 4200+ DUAL CORE)
III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI
K9MM-V VIA K8M800+8237R PLUS CHIPSET
FOR AMD ATHALON
IV. RAM : 512MB+
V. Hard disk : SATA 40 GB OR ABOVE
VI. CD/DVD r/w multi drive combo: (If back up required)
VII. FLOPPY DRIVE 1.44 MB : (If Backup required)
VIII. MONITOR 14.1 or 15 -17 inch
IX. Key board and mouse
X. Printer : (if print is required – [Hard copy]
SOFTWARE REQUIREMENTS:
• Windows OS
• Python
.
INSTALLATION PROCESS
1. Install “python-3.4.0” in your device (if you do not
have Python).
2. Install “My SQL” in your device (if you do not have
My SQL).
3. Run the file “cims_create_database.py” in your PC to
create a database
4. Run the file “cims_create_table” in your PC to create
a table.
5. Run the file “cims_menu.py” in your PC to work on
our management system.
6. For further more details on how to use our software,
please read “Project - Class 11 - Computer Institute
Management System Project”.
PROGRAMMING:----
#SCHOOL managment SYSTEM
#CONNECT DATABASE
import mysql.connector as a
passwd=str(input("DATABASE PASSWORD:"))
con=a.connect(host="localhost",user="root",
passwd='BOXapple957012:::',auth_plugin="m
ysql_native_password")
#SELECT DATA IF EXIST
c=con.cursor()
c.execute("show databases")
dl=c.fetchall()
dl2=[]
for i in dl:
dl2.append(i[0])
if 'myschllll' in dl2:
sql="use myschllll"
c.execute(sql)
#CREATE DATABASE IF
DOES NOT EXIST
else:
sql1="create database myschllll"
c.execute(sql1)
sql2="use myschllll"
c.execute(sql2)
sql3="""create table students(Name
varchar(50),Registration varchar(50),Class
varchar(10),Rollnumber integer,Date
varchar(30))"""
c.execute(sql3)
sql4="""Create Table Fees(Name
varchar(20),Registration varchar(25),Fee
varchar(8), Date varchar(20),Phone
varchar(12))"""
c.execute (sql4)
sql5="""Create table Bills(Detail
varchar(20),cost integer,Date varchar(20))"""
c.execute(sql5)
sql6="""Create table Teacher(Name
varchar(100),Work varchar(20),salary
varchar(20))"""
c.execute(sql6)
con.commit()
#SYSTEM PASSWORD LOGIN
def signin():
print("\n")
print(" .......^^^^^^ Welcome DELHI
international school[D.I.S]^^^^^................")
print("\n")
p=input("system password:")
if p == "dis111":
options()
else:
signin()
#PROJECT WORKING OPTIONS
def options():
print(""" -DELHI INTERNATUONAL
SCHOOL-
............................................
1. add student 5.Display
students
2. pay fees 6.Dislplay Fees
3. add bill 7. Display Bills
4. add teacher 8. Display
Teachers
............................................
""")
choice=input("Select option:")
while True:
if(choice=='1'):
Addstudent()
elif(choice=='2'):
PayFees()
elif(choice=='3'):
Addbill()
elif(choice=='4'):
AddTeacher()
elif(choice=='5'):
Displaystudents()
elif(choice=='6'):
DFees()
elif(choice=='7'):
dBills()
elif(choice=='8'):
dTeachers()
else:
print("Enter Again........")
options()
def Addstudent():
n=input("Name:")
r=input("Registration:")
c=input("Class:")
rn=input("Roll Number:")
d=input("Date:")
data=(n,r,c,rn,d)
sql='insert into Students
values(%s,%s,%s,%s,%s)'
c=con.cursor()
c.execute(sql,data)
con.commit()
print("Data inserted successfully")
options()
def PayFees():
n=input("Name:")
r=input("Registration:")
f=input("Fee:")
d=input("Date:")
p=input("Phone:")
data=(n,r,f,d,p)
sql='insert into Fees
values(%s,%s,%s,%s,%s)'
c=con.cursor()
c.execute(sql,data)
con.commit()
print("Data inserted successfully")
options()
def Addbill():
dt=input("Detail:")
c=input("Cost:")
d=input("Date:")
data=(dt,c,d)
sql='insert into Bills values(%s,%s,%s)'
c=con.cursor()
c.execute(sql,data)
con.commit()
print("Data inserted successfully")
options()
def AddTeacher():
n=input("Name:")
w=input("Work:")
s=input("salary:")
data=(n,w,s)
sql='insert into Teacher values(%s,%s,%s)'
c=con.cursor()
c.execute(sql,data)
con.commit()
print("Data inserted successfully")
options()
def Displaystudents():
cl=input("class:")
sql='select*from students'
c=con.cursor()
c.execute(sql)
d=c.fetchall()
for i in d:
if i[2]==cl:
print("Name:",i[0],"Registration:",i[1],"Class:",
i[2],"Roll Number:",i[3],"Date",i[4])
print("..................................................")
options()
def DFees():
sd=input("Date:")
sql='select*from Fees'
c=con.cursor()
c.execute(sql)
d=c.fetchall()
for i in d:
if i[3]==sd:
print("Name:",i[0],"Registration",i[1],"Fee:",i[
2],"Date:",i[3],"Phone:",i[4])
print(".................................................")
options()
def dBills():
#sd=input("Date:")
d=input("date")
sql='select*from Bills'
c=con.cursor()
c.execute(sql)
d=c.fetchall()
for i in d:
print("Detail:",i[0],"cost:",i[1],"Date:",i[2])
print("........................................")
options()
def dTeachers():
sql='select*from Teacher'
c=con.cursor()
c.execute(sql)
d=c.fetchall()
for i in d:
print("Name:",i[0],"work:",i[1],"salary:",i[2])
print(".....................................")
options()
signin()
----------------------------END-------------------------------
OUTPUTS:-
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
The systems development life cycle is a project management technique that
divides complex projects into smaller, more easily managed segments or phases.
Segmenting projects allows managers to verify the successful completion of project
phases before allocating resources to subsequent phases.
Software development projects typically include initiation, planning, design,
development, testing, implementation, and maintenance phases. However, the phases
may be divided differently depending on the organization involved.
For example, initial project activities might be designated as request,
requirements-definition, and planning phases, or initiation, concept-development, and
planning phases. End users of the system under development should be involved in
reviewing the output of each phase to ensure the system is being built to deliver the
needed functionality.
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.
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, andDevelop 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.
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.
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. 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
ADVANTAGES 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, and/or (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.
CODE COMPLETENESS EVALUATION
White box testing methods can also be used to evaluate the completeness of a
test suite that was created with black box testing methods. This allows the software
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.
Two common forms of code coverage are:
• Function Coverage: Which reports on functions executed and
• Statement Coverage: Which reports on the number of lines executed to
complete the test.
They both return coverage metric, measured as a percentage
BIBLIOGRAPHY
• Computer science With Python - Class XI By : Sumita Arora
• A Project Report On Computer Institute Management System (CIMS)
By : Praveen M Jigajinni
• Website: https://www.w3resource.com
• https://en.wikipedia.org/
***
