Cs Project
Cs Project
One of the core advantages of this system is its ability to streamline the
entire process of managing student records, thus reducing manual effort and
minimizing the risk of data entry errors. The MySQL database ensures that all
records are stored securely and can be retrieved quickly when needed, with
each transaction being committed to the database for data integrity. In
1
addition, the system has built-in safeguards for data security, ensuring that
unauthorized access is prevented.
2
INTRODUCTION
3
Delete) operations, empowering the administrator to efficiently handle
student records without needing to rely on manual processes.
4
EXISTING SYSTEM
5
PROPOSED SYSTEM
6
SYSTEM REQUIREMENTS
SOFTWARE:
- Python 3.x
- MySQL Server
HARDWARE:
- RAM: 4 GB or higher
7
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
8
development should be involved in reviewing the output of each phase to
ensure the system is being built to deliver the needed functionality.
INITIATION PHASE
9
● 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.
10
● 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.
11
PLANNING PHASE
12
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 the functional and 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 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
13
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
14
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.
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.
15
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 staffs assess
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
● 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 prior to acceptance of the system.
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.
16
OPERATIONS AND MAINTENANCE PHASE:
The system operation is ongoing. 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 reenter 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.
17
CODING
import sys
con = mcon.connect(host="localhost",port="3306",user="root",passwd="root")
mycursor = con.cursor()
if con.is_connected():
mycursor.execute("use LOC")
#print(Q)
#mycursor.execute(Q)
con.commit()
18
at = 1
while at <= 3:
at += 1
status = 'A'
mycursor.execute("select * from user where uname = '{}' and upwd = '{}' and
ustatus = '{}'".format(uid,pwd,status))
data = mycursor.fetchone()
count = mycursor.rowcount
#print(count)
if count == 1:
print("Login Successfully.")
#--------------------------*CHOICES*-----------------------------
while True:
19
print("Input 'I' for Insertion a New Record.")
#--------------------------*TABLE CREATION*-----------------------------
if ch == 'I' or ch == 'i':
reg_num int(20) primary key, loc_sr_num integer NOT NULL, yr_pass_xi int(5)
NOT NULL,\
20
sub_1 char(15),sub_2 char(15) NOT NULL,sub_3 char(15) NOT NULL,\
exam_of_equi_exam_passed char(20),board_of_equi_exam_passed
char(20),single_child char(5),\
#print(ins)
mycursor.execute(ins)
#--------------------------*INSERTION OF RECORDS*-----------------------------
print("Insertion Operation.")
21
ecat = input("Enter student's exam_cat: ")
22
intsub3 = input("Enter name of internal grade subject3: ")
mother_name,father_name,gender,category1,minority,PwD_status,mob_num,emai
l_id,\
aadhar_num,sub_1,sub_2,sub_3,sub_4,sub_5,add_sub_6,int_grade_sub1,int_grade_s
ub2,int_grade_sub3,\
annual_income,roll_num_of_equi_exam_passed,exam_of_equi_exam_passed,board_
of_equi_exam_passed,\
23
'{}','{}','{}','{}','{}','{}','{}',{},'{}',{},'{}','{}','{}','{}','{}','{}','{}','{}','{}',{},\
{},'{}','{}','{}','{}',{},'{}')\
".format(reg,locsr,yrpassc11,ecat,cname,mname,fname,gender,cat,minor,pwdis,m
num,email,ad_num,s1,s2,s3,s4,s5,s6,intsub1,intsub2,intsub3,aninc,eexrnum,eexam,
eexboard,sch,mgcr,adm_num,adm_date)
mycursor.execute(q)
con.commit()
#--------------------------*UPDATION*-----------------------------
print("Updation of Record.")
24
mycursor.execute(qry)
con.commit()
#--------------------------*DELETION*-----------------------------
print("Removal of Record.")
mycursor.execute(qry)
con.commit()
#--------------------------*SEARCHING*-----------------------------
print("Searching Operation.")
25
qry = "select * from students where reg_num = {} ".format(reg)
#print(qry)
mycursor.execute(qry)
data = mycursor.fetchone()
count = mycursor.rowcount
print(row)
#--------------------------*DISPLAY*-----------------------------
mycursor.execute(qry)
data = mycursor.fetchall()
count = mycursor.rowcount
26
print("{0:<9s}{1:<9s}{2:<9s}{3:<9s}{4:<9s}{5:<9s}{6:<9s}{7:<9s}{8:<9s}
{9:<9s}".format('Sl.No','Name','MName','FName','Subject1','Subject2','Subject3','Sub
ject4','Subject5','Subject6'))
print("_____________________________________________________________________________
____________")
print("{0:<9s}{1:<9s}{2:<9s}{3:<9s}{4:<9s}{5:<9s}{6:<9s}{7:<9s}
{8:<9s}
{9:<9s}".format(str(row[1]),row[4],row[5],row[6],row[14],row[15],row[16],row[1
7],row[18],row[19]))
print("Exiting Program.")
sys.exit(0)
else:
else:
print("Login Failed")
if at !=4:
print("Try Again")
27
else:
28
1.Table created successfully.
29
STRUCTURE OF THE TABLE
30
2. Insertion of record:
31
3. Updating record:
32
4. Deleting a record:
5. Searching a record:
33
6. Display all Records:
34
35
7. Exit:
RECORDS:
36
CONCLUSION
37
The Student Management System Using Python and MySQL provides a
robust solution for managing student data in an educational institution. By
transitioning from a manual system to a digital database-driven solution, the
institution can ensure data accuracy, improve administrative efficiency, and
safeguard student records from unauthorized access or loss. Future
enhancements could include a graphical user interface (GUI), remote access
features, and more complex data analysis functionalities to further streamline
administrative tasks.
38
BIBLIOGRAPHY
39