Professional Documents
Culture Documents
PROJECT REPORT ON
Conducted by
Central Board of Secondary Education
ROLL NO :
NAME :
CLASS : XII A
1
SAINIK SCHOOL GOPALGANJ
CERTIFICATE
This is to certify that Cadet __________________ Roll No: ____________
has successfully completed the project Work entitled COMPUTER SALES AND
SERVICE in the subject Computer Science (083) laid down in the regulations of
(Manish Kumar)
PGT Comp Sci
Teacher IC
Examiner:
Signature:
Name: _______________
2
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT
02 INTRODUCTION
08 SOURCE CODE
09 OUTPUT
12 BIBLIOGRAPHY
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 HOSTEL MANAGEMENT
INTRODUCTION
the students such as his\her roll number , in department they belong to , etc. These
information can be stored in the data and can be verified whenever we want.this
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
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
One has to use the data management software. Software has been an ascent
markets, which have helped in making the organizations work easier and efficiently.
Data management initially hadto maintain a lot of ledgers and a lot of paperwork has
to be done but now software producton this organization has made their work
fasterand easier. Now only this software has to beloaded on the computer and work
can be done.
This prevents a lot of time and money. Thework becomes fully automated and
any information regarding the organization can beobtained by clicking the button.
6
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
SDLC Activities
Communication
This is the first step where the user initiates the request for a desired software
product. He contacts the service provider and tries to negotiate the terms. He
submits his request to the service providing organization in writing.
Requirement Gathering
7
This step onwards the software development team works to carry on the project.
The team holds discussions with various stakeholders from problem domain and
tries to bring out as much information as possible on their requirements. The
requirements are contemplated and segregated into user requirements, system
requirements and functional requirements. The requirements are collected using a
number of practices as given -
Feasibility Study
After requirement gathering, the team comes up with a rough plan of software
process. At this step the team analyzes if a software can be made to fulfill all
requirements of the user and if there is any possibility of software being no more
useful. It is found out, if the project is financially, practically and technologically
feasible for the organization to take up. There are many algorithms available, which
help the developers to conclude the feasibility of a software project.
System Analysis
At this step the developers decide a roadmap of their plan and try to bring up the
best software model suitable for the project. System analysis includes
Understanding of software product limitations, learning system related problems or
changes to be done in existing systems beforehand, identifying and addressing the
impact of project on organization and personnel etc. The project team analyzes the
scope of the project and plans the schedule and resources accordingly.
Software Design
Next step is to bring down whole knowledge of requirements and analysis on the
desk and design the software product. The inputs from users and information
gathered in requirement gathering phase are the inputs of this step. The output of
this step comes in the form of two designs; logical design and physical design.
Engineers produce meta-data and data dictionaries, logical diagrams, data-flow
diagrams and in some cases pseudo codes.
Coding
Testing
8
testing is done while coding by the developers and thorough testing is conducted by
testing experts at various levels of code such as module testing, program testing,
product testing, in-house testing and testing the product at user’s end. Early
discovery of errors and their remedy is the key to reliable software.
Integration
Software may need to be integrated with the libraries, databases and other
program(s). This stage of SDLC is involved in the integration of software with outer
world entities.
Implementation
This means installing the software on user machines. At times, software needs
post-installation configurations at user end. Software is tested for portability and
adaptability and integration related issues are solved during implementation.
This phase confirms the software operation in terms of more efficiency and less
errors. If required, the users are trained on, or aided with the documentation on how
to operate the software and how to keep the software operational. The software is
maintained timely by updating the code according to the changes taking place in
user end environment or technology. This phase may face challenges from hidden
bugs and real-world unidentified problems.
Disposition
As time elapses, the software may decline on the performance front. It may go
completely obsolete or may need intense upgradation. Hence a pressing need to
eliminate a major portion of the system arises. This phase includes archiving data
and required software components, closing down the system, planning disposition
activity and terminating system at appropriate end-of-system time.
9
FLOWCHART
start
CHOICE=INT(I
NPUT(“ENTER
THE
CHOICE”))
IF
CHOICE==
1:
10
print(abc)
Elif
Choice==2;
mysql="select*from
hostel_management where
roll_no={}".format(roll_no)
print("roll_no:",data[0][0])
print("name:",data[0][1])
print("address:",data[0][2])
print("room_no:",data[0][3])
print("dept:",data[0][4])
print("fees:",data[0][5])
11
elif
choice==2:
print("1.COMPUTER")
print("2.BIO")
print("3.TECH")
print("4.PHYSICS")
print("5.ECO")
print("6.ENG")
department=input("ENTER YOUR
DEPARTMENT")
c1.execute(mysql)
data=c1.fetchall()
12
elif
choice==4:
print("your fees
is:",data[0][1])
else
print("QUITTING!!!!!!!!!")
stop
13
SOURCE CODE
c1=conn.cursor()
#c1.execute("create table hostel_management(roll_no int
primary key,name varchar(20),address varchar(100),room_no
int,dept varchar(15),fees int,bal int)
print(" 4.EXIT")
choice=int(input('ENTER YOUR CHOICE'))
if choice==1:
v_roll=input("ENTER YOUR ROLL NUMBER")
v_name=input("ENTER YOUR NAME")
v_add=input("ENTER YOUR ADDRESS")
v_room_no=input("ENTER YOUR ROOM NUMBER")
v_dept=input("ENTER YOUR DEPARTMENT")
v_fees=input("ENTER YOUR FEES")
v_bal=input("ENTER YOUR BALANCE")
14
mysql="select*from hostel_management where
roll_no={}".format(roll_no)
c1.execute(mysql)
data=c1.fetchall()
print("roll_no:",data[0][0])
print("name:",data[0][1])
print("address:",data[0][2])
print("room_no:",data[0][3])
print("dept:",data[0][4])
print("fees:",data[0][5])
print("bal:",data[0][6])
elif choice==2:
print("AVAILABLE DEPARTMENTS AS FOLLOWS")
print("1.COMPUTER")
print("2.BIO")
print("3.TECH")
print("4.PHYSICS")
print("5.ECO")
print("6.ENG")
department=input("ENTER YOUR DEPARTMENT")
mysql="select*from fees where
department='{}'".format(department)
c1.execute(mysql)
data=c1.fetchall()
print("your fees is:",data[0][1])
else:
print("QUITTING!!!!!!!!!")
15
16
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.
17
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
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, 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)
18
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.
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.
19
HARDWARE AND SOFTWARE REQUIREMENTS
SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
BIBLIOGRAPHY
20