NEW - Hyn PJT Upsc
NEW - Hyn PJT Upsc
NEW - Hyn PJT Upsc
NAME : P.HASMITHA
CLASS : XII
PGT (CS)
1
CERTIFICATE
INFORMATION SYSTEM in the subject Computer Science (083) laid down in the
(Geetanjali B K)
PGT Comp Sci
Examiner:
Name: _______________
Signature:
2
TABLE OF CONTENTS
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 05
07 FLOW CHART 14
08 SOURCE CODE 20
09 OUTPUT 26
10 TESTING 28
12 BIBLIOGRAPHY 31
ACKNOWLEDGEMENT
3
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.
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.
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.
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
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
5
efficiency so to replace the unending heaps of flies with a much sophisticated
One has to use the data management software. Software has been an ascent 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 production 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
6
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
7
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:
8
The ITPR must be approved by the State CIO before the project can move
forward.
PLANNING PHASE
9
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.
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,
10
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 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:
11
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.
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:
12
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 as a deployed system with end users working together with contract
personnel
13
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.
START
conn=sql.connect(host='local
host',user='root',passwd='co
mputer',database='UPSC')
c1=conn.cursor()
us=input("user")
pa=input("pass")
14
c1.execute("insert into login_info
values('"+us+"','"+pa+"')")
conn.commit()
STOP
START
conn=sql.connect(host='localhost',user='root'
,passwd='computer',database='UPSC')
c1=conn.cursor()
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: 16
TRUE
print("$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ UPSC
REGISTARATION$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$")
print("1:ADD DETAILS")
print("2:VIEW DETAILS")
print("3:QUIT")
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--")
17
v_pho=input("Enter your phone number--")
v_mob=input("Enter your mobile number--")
v_ema=input("Enter your mail ID--")
v_pre=input("Enter your preferance--")
print(v_sql)
c1.execute(v_sql)
conn.commit()
FALSE
elif
ch==2 18
:
TRUE
c1.execute(v_ch)
data=c1.fetchone()
print('\n')
print("Registration no--",data[26])
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])
TRUE
print("QUITTING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!")
else : FALSE
TRUE
STOP
SOURCE CODE
#creating registration table
conn=sql.connect(host='localhost',user='root',passwd='computer
',database='UPSC')
20
#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
(3),aadhar_no bigint)")
conn=sql.connect(host='localhost',user='root',passwd='computer
',database='UPSC')
#if conn.is_connected():
#print('connected sucessfully')
c1=conn.cursor()
#print(v_sql)
#c1.execute(v_sql)
21
us=input("user")
pa=input("pass")
print(v_sq)
c1.execute(v_sq)
conn.commit()
conn=sql.connect(host='localhost',user='root',passwd='computer
',database='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:
22
c1.execute("select * from
registration_information")
v_data=c1.fetchall()
v_count=len(v_data)
v_reg_no=(v_count+1)
23
v_edu=input("Enter your education
qualification--")
School--")
values
("+v_aadh+","+"'"+v_f_na+"'"+","+"'"+v_m_na+"','"+v_ea+"',"+v_
yr+",'"+v_gen+"','"+v_dob+"','"+v_nat+"','"+v_mar_st+"','"+v_c
omm+"','"+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_name+"',"+str(v_reg_no)+")")
print(v_sql)
number is--",v_reg_no)
c1.execute(v_sql)
conn.commit()
elif ch==2:
print('\n')
24
reg=int(input("Enter the registartion number"))
where reg_no="+str(reg))
c1.execute(v_ch)
data=c1.fetchone()
print('\n',"registration no--",data[26],'\n')
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')
25
print("Education_qualification--",data[20],'\n')
print("Aadhar no --",data[0],'\n')
print("Preferance --",data[21],'\n')
miltary school--",data[24],'\n')
elif ch==3:
print("QUITTING!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!)
else :
OUTPUT
# adding details
26
#Viewing detail
27
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
28
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.
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
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.
29
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.
30
I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
III. MySQL
BIBLIOGRAPHY
31
By : Geethanjali B K
3. Website: https://www.w3resource.com
***
32