CS DEVENDRA SINGH RAO - Creating UPSC Forms
CS DEVENDRA SINGH RAO - Creating UPSC Forms
PROJECT REPORT ON
ROLL NO :
CLASS : XII A
PGT (CS)
1
PM SHRI KENDRIYA VIDYALAYA CHITTORGARH
CERTIFICATE
INFORMATION SYSTEM in the subject Computer Science (083) laid down in the
(Rajendra Shakyawal)
PGT Comp Sci
External Examiner:
Name: _______________
Signature:
2
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 22
09 OUTPUT 29
10 TESTING 31
12 BIBLIOGRAPHY 34
3
ACKNOWLEDGEMENT
Apart from the efforts of me, the success of any project depends largely on the
encouragement and guidelines of many others. I take this opportunity to express my
gratitude to the people who have been instrumental in the successful completion of this
project.
I express deep sense of gratitude to almighty God for giving me strength for the
successful completion of the project.
My sincere thanks to Mr. Rajendra Shakyawal,, PGT CS, A guide, Mentor all the
above a friend, who critically reviewed my project and helped in solving each and every
problem, occurred during implementation of the project.
The guidance and support received from all the members who contributed and
who are contributing to this project, was vital for the success of the project. I am grateful
for their constant support and help.
XII A
4
PROJECT ON UPSC REGISTRATION INFORMATION SYSTEM
INTRODUCTION
This programme helps the users to add a UPSC registration details of particular student,
after feeding information this programme automatically generates a registration Number
and displays it. The user can use the registration number to view their registered details.
This programme can be used only if the Login ID and the Password is correct by doing
so we enforce security and restriction of unauthorised access.
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
projects.
5
PROPOSED SYSTEM
Today one cannot afford to rely on the fallible human beings of be really wants to
stand against today’s merciless competition where not to wise saying “to err is human”
no longer valid, it’s out-dated to rationalize your mistake. So, to keep pace with time, to
bring about the best result without malfunctioning and greater efficiency so to replace the
unending heaps of flies with a much sophisticated hard disk of the computer.
One has to use the data management software. Software has been an ascent in
atomization various organisations. Many software products working are now in markets,
which have helped in making the organizations work easier and efficiently. Data
management initially had to maintain a lot of ledgers and a lot of paperwork has to be
done but now software producton this organization has made their work faster and
easier. Now only this software has to be loaded on the computer and work can be done.
This prevents a lot of time and money. The work becomes fully automated and
any information regarding the organization can be obtained by clicking the button.
Moreover, now it’s an age of computers of and automating such an organization gives
6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
7
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE
INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies a need or an opportunity.
8
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.
9
PICTORIAL REPRESENTATION OF SDLC:
PLANNING PHASE
10
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.
REQUIREMENTSANALYSIS 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.
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,
11
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:
12
DEVELOPMENT PHASE
13
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.
14
FLOW CHART FOR LOGIN TABLE
START
conn=sql.connect(host='local
host',user='root',passwd='co
mputer',database='UPSC')
c1=conn.cursor()
us=input("user")
pa=input("pass")
conn.commit()
STOP
15
FLOW CHART FOR REGISTRATION TABLE
START
conn=sql.connect(host='localhost',user='root'
,passwd='computer',database='UPSC')
c1=conn.cursor()
STOP
16
FLOW CHART FOR VIEWING OR ADDING DETAILS
START
conn=sql.connect(host='localhost',user
='root',passwd='computer',database='
UPSC')
c1=conn.cursor()
dat=c1.fetchall()
if FALSE
(user,passw
d) in dat:
TRUE
print("$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ UPSC
REGISTARATION$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$")
print("1:ADD DETAILS")
print("2:VIEW DETAILS")
print("3:QUIT")
17
FALSE if
ch==1:
TRUE
c1.execute("select * from registration_information")
v_data=c1.fetchall()
v_count=len(v_data)
v_reg_no=(v_count+1)
v_ea=input("Enter the examination applied--")
v_yr=input("Enter the year--")
v_name=input("Enter your name--")
v_gen=input("Enter your gender--")
v_dob=input("Enter your date of birth--")
v_f_na=input("Enter you father name--")
v_m_na=input("Enter your mother name--")
v_nat=input("Enter your nationality--")
v_mar_st=input("Enter your marital staus--")
v_comm=input("Enter your community--")
v_min=input("Do you belong to minority--")
v_add1=input("Enter address line1--")
v_add2=input("Enter address line2--")
v_add3=input("Enter address line3--")
v_dist=input("Enter your district--")
v_state=input("Enter your state--")
v_pin=input("Enter your pin code--")
v_pho=input("Enter your phone number--")
v_mob=input("Enter your mobile number--")
v_ema=input("Enter your mail ID--")
v_edu=input("Enter your education qualification--")
print(v_sql)
c1.execute(v_sql)
conn.commit()
FALSE elif
ch==2
TRUE
c1.execute(v_ch)
data=c1.fetchone()
print('\n')
print("Registration no--",data[26])
print("Nationality --",data[7])
print("Marital status--",data[8])
print("Community--",data[9])
print("Minority --",data[10])
print("District --",data[14])
print("State --",data[15])
print("Phone no --",data[17])
print("Mobile no--",data[18])
print("Education_qualification--",data[20])
print("Aadhar no --",data[0])
print("Preferance --",data[21])
FALSE elif
ch==3
20
TRUE
print("QUITTING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")
else : FALSE
TRUE
STOP
21
SOURCE CODE
conn=sql.connect(host='localhost',user='root',passwd='computer',d
atabase='UPSC')
#if conn.is_connected():
#print('connected sucessfully')
c1=conn.cursor()
varchar(11),date_of_birth varchar(10),nationality
varchar(15),marital_status varchar(10),community
22
#creating login info
conn=sql.connect(host='localhost',user='root',passwd='computer',d
atabase='UPSC')
#if conn.is_connected():
#print('connected sucessfully')
c1=conn.cursor()
#print(v_sql)
#c1.execute(v_sql)
us=input("user")
pa=input("pass")
print(v_sq)
c1.execute(v_sq)
conn.commit()
23
# for getting info, showing info
conn=sql.connect(host='localhost',user='root',passwd='computer',d
atabase='UPSC')
#if conn.is_connected():
#print('connected sucessfully')
c1=conn.cursor()
dat=c1.fetchall()
if (user,passwd) in dat:
print("$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ UPSC
REGISTARATION$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$")
print("1:ADD DETAILS")
print("2:VIEW DETAILS")
print("3:QUIT")
if ch==1:
v_data=c1.fetchall()
v_count=len(v_data)
v_reg_no=(v_count+1)
24
v_yr=input("Enter the year--")
25
v_stu_sa=input("Whether Student of Sainik/Military
School--")
("+v_aadh+","+"'"+v_f_na+"'"+","+"'"+v_m_na+"','"+v_ea+"',"+v_yr+
",'"+v_gen+"','"+v_dob+"','"+v_nat+"','"+v_mar_st+"','"+v_comm+"'
,'"+v_min+"','"+v_add1+"','"+v_add2+"','"+v_add3+"','"+v_dist+"',
'"+v_state+"',"+v_pin+","+v_pho+","+v_mob+",'"+v_ema+"','"+v_edu+
"','"+v_pre+"','"+v_p_f+"','"+v_stu_sa+"','"+v_son_mil+"','"+v_na
me+"',"+str(v_reg_no)+")")
print(v_sql)
number is--",v_reg_no)
c1.execute(v_sql)
conn.commit()
elif ch==2:
print('\n')
reg_no="+str(reg))
c1.execute(v_ch)
data=c1.fetchone()
print('\n',"registration no--",data[26],'\n')
26
print("Name --",data[25],'\n')
print("Nationality --",data[7],'\n')
print("Marital status--",data[8],'\n')
print("Community--",data[9],'\n')
print("Minority --",data[10],'\n')
print("District --",data[14],'\n')
print("State --",data[15],'\n')
print("Phone no --",data[17],'\n')
print("Mobile no--",data[18],'\n')
print("Education_qualification--",data[20],'\n')
print("Aadhar no --",data[0],'\n')
print("Preferance --",data[21],'\n')
",data[23],'\n')
miltary school--",data[24],'\n')
27
elif ch==3:
print("QUITTING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")
else :
28
OUTPUT
# adding details
29
#Viewing detail
30
TESTING
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.
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
31
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
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 a black box tester writes many test cases to
check something that can be tested by only one test case, and/or 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, 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)
32
HARDWARE AND SOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. MySQL
33
BIBLIOGRAPHY
3. Website: https://www.w3resource.com
***
34