CS Project 5

STUDENT MANAGEMENT SYSTEM PAGE NO.
: 01
INTRODUCTION
NIRMALA ENG. HR. SEC. SCHOOL (CBSE) DEPT OF COMPUTER SCIENCE 2022-2023
STUDENT MANAGEMENT SYSTEM PAGE NO. : 02
INTRODUCTION
1.1 ABOUT THE PROJECT
"KAUN BANEGA CROREPATI" This project is a brain game for the students
for utilising their free time in the game. The Game is for only the enjoying and
entertainment purpose. It is for taking some general knowledge for future
purpose. This game can give many hard questions and many easy questions
you can also try this game. This game is also for wining a little moment of
your life.
` 1.2. ADVANTAGES AND DISADVANTAGES
 ADVANTAGES:
1. INCREASES VOCABULARY– More enhancements in player’s vocabulary, it

becomes easier to express thoughts and opinions without hesitating,
especially for students.
2. IMPROVES SPELLING – This game improves language skills as well

improves spelling skills overall.
3. ENHANCES COGNITIVE SKILLS – The process of thought and analysis

must run at the same time thus effectively enhancing cognitive skills.
4. POSITIVE APPROACH – As the game starts with a greeting message, it

creates a positivity in the mind of player.
 DISADVANTAGES
1. TOO BASIC – The design of the game is very simple but it does produces
good results.
2. ISOLATED VOCABULARY – The game makes the player to guess only
those words given in coded directory.
3. UNCERTAINITY – There is no control of developer over choice of word given

to player.
1.3. PROBLEM DEFINITION
Computer programs are written to solve problems posed by humankind. Prior

to writing a program, one has to understand the description of the problem to
solve. This description can be very precise or vague, but nevertheless, it is
necessary/present.
While creating the source-code of this project in python, we generally
designed the whole structure of the program at initial and then went on to
problem analysis and definition.
Generally, we face problems regarding making our logics and the output of
this program suitable at one place. Later, creating questions over this project
and its source code somehow helped us to achieve our plan.
Posing such questions compels us to define the problems very precisely and
once we get sure regarding the problem entails, we must write down a list of
specifications.
1.4 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.
1. Write programs utilizing modern software tools.
2. Apply object oriented programming principles effectively when developing

small to medium sized projects
3. Write effective procedural code to solve small to medium sized problems.
4. 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.
1.5 SCOPE OF THE PROJECT
The scope of this project is to put our basic knowledge about python into actions by
using for loop, if else statement etc. We decided to go beyond our knowledge and try
features and learn vast areas of applying our knowledge.
LITERATURE SURVEY
LITERATURE SURVEY
 HISTORY OF PYTHON
• Python laid its foundation in the late 1980s.
• The implementation of python was started in the December 1989 by Guido Van
Rossum at CWI in Netherland.
• In February 1991, Van Rossum published that code (labeled version 0.9.0) to alt
sources.
• In 1994, Python 1.0 was released with new features like : lambda, map, filter and
reduce.
• Python 2.0 added new features like list comprehensions, garbage collection
system.
• On 3 December 2008, Python 3.0 (also called “Py3k”) was released. It was
designed to rectify fundamental flaw of the language flaw = fault.
• ABC programming language is said to be the predecessor of Python language
which was capable of exception handling and interfacing with Amoeba Operating
System.
• Python is influenced by following programming languages:
1. ABC language
2. Modula
 FEATURES OF PYTHON
Python provides lots of features that are listed below:

EASY TO LEARN AND USE: Python is easy to learn and use. It is developer’s
friendly and high level programming language.
1) EXPRESSIVE LANGUAGE: Python language is more expressive means

that it is more understandable and readable.
2) UNIQUE STYLES: Python is an interpreted language i.e. interpreted
executes the code line by line at a time. This makes debugging easy and
thus, suitable for beginners.
3) GROSS – PLATFORM LANGUAGE: Python can run equally on
different platforms such as windows, Linux, UNIX and Macintosh etc. So,
we can say that python is a portable language.
4) FREE AND OPEN SOURCE: Python language is freely available at

official web address (https://www.python.org/). The source code is also
available. Therefore it is open source.
5) OBJECT- ORIENTED LANGUAGE: Python supports object oriented
language and concepts of class and objects come into existence.
6) EXTENSIBLE: It implies that other languages such as C/C++ can be used
to compile that code and thus it can be used further in our provides rich set
of module and functions for rapid applications development
7) LARGE STANTARD LIBRARY: Python has a large and broad library
and provides rich set of modules and functions for rapid application
development.
8) GUI PROGRAMMING SUPPORT: Graphical user interfaces can be
developed using python.
9) INTEGRATED: It can be easily integrated with languages like C/C++,

Java, etc.
 BENEFITS OF PYTHON
1. Deep learning
2. Machine learning
3. Predictive analytics
4. Advanced analytics
5. Academic scientific research
6. Exploration and Data analysis
7. Data science
8. Statistics
9. Memory intensive and computation intensive tasks.
 LIMITATIONS
Python is not a good choice for:
• Memory intensive and computation intensive tasks.
• Embedded system where processor has limited capacity.
• For graphical intensive 3D game that takes up a lot of CPU.
• Application that demanded concurrency and parallelism.
• Developing mobile apps.
Interpreted languages and is slow compared to C/C++ or Java.
System Development
Strategy
STUDENT MANAGEMENT SYSTEM PAGE NO. :
010
SYSTEM DEVELOPMENT STRATEGY

3.1. SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)
In systems engineering, information systems and software engineering, the

systems development life cycle (SDLC), also referred to as the applications
development life-cycle, is a process for planning, creating, testing, and
developing an information system. The systems development lifecycle concept
applies to a range of hardware and software configurations, as a system can be
composed of hardware only, software only, or a combination of both. There are
usually six stages in this cycle: analysis, design, development and testing,
implementation, documentation, and evaluation.
SDLC can be described along a spectrum of agile to iterative to sequential
methodologies. Agile methodologies, such as XP and Scrum, focus on
lightweight processes which allow for rapid changes (without necessarily
following the pattern of SDLC approach) along the development cycle. Iterative
methodologies, such as Rational Unified Process and dynamic systems
development method, focus on limited project scope and expanding or
improving products by multiple iterations. Sequential or big-design-up-front
(BDUF) models, such as waterfall, focus on complete and correct planning to
guide large projects and risks to successful and predictable results. [Citation
needed] Other models, such as anamorphic development, tend to focus on a
form of development that is guided by project scope and adaptive iteration of
feature development.
In project management a project can be defined both with a project life cycle (PLC)
and an SDLC, during which slightly different activities occur. According to Taylor
(2004),”the project life cycle encompasses all the activities of the project, while the
systems development life cycle focuses on realizing the product requirement SDLC is
used during the development of an IT project, it describes the different stages
involved in the project from the drawing board, through the completion of the project.
The SDLC is not a methodology per se, but rather a description of the phases in
the cycle of a software application. These phase (broadly speaking) are
011
investigating, analysis, design, build, test, implement, and maintenance and
support.
All software development methodologies (such as the more commonly known

waterfall and scrum methodologies) follow the SDLC phases but the method of
doing that varies vastly between methodologies. In the Scrum methodologies,
for example, one could say a single user stories goes through all the phases of
the SDLC within a single two-week sprint. Contrast this to the waterfall
methodologies, as another examples, where every business requirement
(recorded in the analysis phase of the SDLC in a document called the Business
Requirements Specifications) is translated into feature/functional descriptions
(recorded in the design phase in a document called the Functional Specification)
which are then all build in one go as a collection of solution features typically
over a period of three to nine months, or more.
These methodologies are obviously quiet different approaches, yet they both
contain the SDLC phases in which a requirements is born, then travels through
the life cycle phases ending in the final phase of maintenance and support, after-
which (typically) the whole life cycle starts again for a subsequent version of the
software application.
STRENGTH AND WEAKNESSES OF SDLC
STRENGTHS WEAKNESSES
Control Increased development time
Monitor large projects Increased development cost
Detailed steps Systems must be defined up front
Evaluate costs and completion targets Rigidity
Documentation Hard to estimate costs, project overruns
Well defined user input User input is sometimes limited
Ease of maintenance Little parallelism
Development and design standards Automation of documentation and standards is

limited
012
Tolerates changes in MIS of staffing Does not tolerate changes in requirements
Projects canned early on the result in little or no

value
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE:

1. System Analysis
2. Analysis
3. Design
4. Environments
5. Testing
6. Training and Transition
7. Operations and maintenance
8. Evaluation
3.2. WATERFALL MODEL
This project has been carried out using WATERFALL MODEL.
013
The waterfall model is a breakdown of project activities into linear sequential
phases, where each phase depends on the deliverables of the previous one and
corresponds to a specialization of tasks. The approach is typical for certain areas
of engineering design. In software development, it tends to be among the less
iterative and flexible approaches, as progress flows in largely one direction

(“downwards” like a waterfall) through the phases of conception, initiation,
analysis, design, construction, testing, development and maintenance.
The waterfall development model originated in the manufacturing and
construction industries; where the highly structured physical environments mean
that design changes became prohibitively expensive much sooner in the
development process. When first adopted for software development, there were
no recognized alternatives for knowledge-based creative work.
The following illustration is a representation of the different phases of the
waterfall Model.
The sequential phases in Waterfall model are –
1. Requirement Gathering and analysis –All possible requirements of the

system to be developed are captured in this phase and documented in a
requirement specification document
014
2. System Design – The requirement specifications from first phase are
studied in this phase and the system design is prepared. This system design
helps in specifying hardware and system requirements and helps in defining
the overall system architecture.
3. Implementation− With inputs from the system design, the system is first
development in small programs called units, which are integrated in the next
phase. Each unit is developed and tested for its functionality, which is
referred to as Unit Testing.
4. Integration and Testing – All the units developed in the implementation
phase are integrated into a system after testing of each unit. Post integrating
the entire system is tested for any faults failures.
5. Deployment of System – Once the functional and non-functional testing

is done; the product is developed in the customer environment or released
into the market.
Maintenance – There are some issues which come up in the client environment. To
fix those issues, patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the customer
environment. All these phases are cascaded to each other in which progress is seen as
flowing steadily downwards (like a waterfall) through the phases. The next phase is
started only after the defined set of goals are achieved for previous phase and it is
signed off, so the name “Waterfall Model”.
3.3 HARDWARE AND SOFTWARE REQUIREMENTS
I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD
ATHALON(3800+- 4200+
DUALCORE)
III. MOTHERBOARD 0R MSI : 1.845 OR 915,995 FOR PENTIUM
K9MM-V VIAK8M800+8237R PLUS
CHIPSET FOR AMD ATHALON
IV. RAM : 1GB+
015
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
Key board and mouse
X. Printer : (if print is required – [Hard copy])
3.4 SOFTWARE REQUIREMENTS:
I. Windows OS
II. Python
016
SYSTEM ANALYSIS
017
SYSTEM ANALYSIS
4.1. EXISTING SYSTEM
 We have gathered all information of Kaun Banega Crorepati game by

playing the game ourselves.
 Today, besides playing word games with pen and paper, people can also
make use of software games like Kaun Banega Crorepati .
4.2. DRAWBACK(S) OF EXISTING SYSTEM
 Time-Consuming
 Great chances of system hang-up
 Server Problems
4.3. NEED FOR PROPOSED SYSTEM
 To Make the System Time-Efficient.
 To Reduce the Chances of glitch.
 To Provide the Flexibility to the Users.
4.4. PROPOSED SYSTEM
Software has been an ascent in atomization various organizations. Many software

products working are now in market, which have helped in making the organizations
work easier and efficiently.
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 computer of and automating such an organization gives
the better look.
018
SYSTEM DESIGN
019
SYSTEM DESIGN
5.1. DATA-FLOW DIAGRAM
A data-flow diagram (DFD) is a way of representing a flow of a data of a

process or a system (usually an information system). The DFD also provides
information about the outputs and inputs of each entity and the process itself. A
data-flow diagram has no control flow, there are no decision rules and no loops.
Specific operations based on the data can be represented by a flowchart.
There are several notations for displaying data-flow diagrams. The notation
presented above was described in 1979 by Tom De Marco as part of Structured
Analysis.
For each data flow, at least one of the endpoints (source and/or destination) must
exist in a process. The refined representation of a process can be done in another
data-flow diagram, which subdivides this process into sub-processes.
The data-flow diagrams is part of the structured-analysis modeling tools. When
using UML, the activity diagram typically takes over the role of the data-flow
diagram. A special from of data-flow plan is a site-oriented data-flow plan.
Data-flow diagrams can be regarded as inverted Petri nets, because places in
such networks correspond to the semantics of data memories. Analogously, the
semantics of transitions from Petri nits and data flows and functions from data-
flow diagrams should be considered equivalent.
 DFD COMPONENTS:-
DFD consists of processes, flow, warehouses, and terminator, There are several
ways to view these DFD components.
1. Process: The process (functions, transformation)is part of a system that
transforms inputs to outputs. The symbol of a system that transformation
inputs to output. The symbol of s process is a circle, an oval, a rectangle
or a rectangle with rounded corners (according to the type of notation).
The process is named in one word, a short sentence, or a phrase that is
clearly to express its essence.
020
2. Data Flow: Data flow (flow, dataflow) shows the transfer of
information (sometimes also material) from one part of the system to
another. The symbol of the flow is the arrow. The flow should have a
name that determines what information (or what material) is being
moves. Exceptions are flows where it is clear what information is
transferred through the entitles that are linked to these flows. Material
shifts are modelled in systems that are not merely informative. Flow
should only transmit one type of information (material). The arrow
shows the flow direction (it can also be be-directional if the information
to/from the entity is logically dependent – e.g. question and answers).
Flows link processes, warehouses and terminators.
3. Warehouse: The warehouse (data stores, file, and database) is used to
store data for later use. The symbol in the DFD Notation. The name of
the warehouse is a plural noun (e.g. orders)- it derives from the input and
output streams of the warehouse. The warehouse does not have to be just
a data file, for examples, a folder with documents, a filing cabinets, and
optical discs. Therefore, viewing the warehouse in DFD is independent
of implementation. The flow from the warehouse usually represents the
reading of the data stored in the warehouse, and the flow to the
warehouse usually expresses data entry or updating (sometimes also
deleting data). Warehouse is represented by two parallel lines between
which the memory mane is located (it can be modelled as a UML buffer
node).
4. Terminator: The Terminator is an external entity that communicates
with the system and stands outside of the system. It can be , for example,
various organisations (e.g. a bank), groups of people (e.g. customers),
authorities (e.g. a tax office) or a department (e.g. a human-resource
department) of the same organisation, which does not belong to the
model system. The terminator may be another system with which the
modelled system communicates.
021
FLOW CHART
1.REGISTER
2.LOGIN
IF N=1 IF N =2
PROGRAM PROGRAM
INSERTS FETCHES
DATA IN THE DATA FROM
DATABASE DATABASE
MENU IS DISPLAYED
1 CHOOSE THE COORECT
OPTION
2.IF TRUE IT
3.CONTINUES
4 IF FALSE IT QUITS
5 AND YOU HAVE TO RESTART THE
GAME
IF TRUE IF FALSE
IT CONTINUES IT QUITS THE GAME AND YOU HAVE
TO RESTART THE GAME
022
TESTING
023
TESTING
Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service under
test, 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
024
that for a given input, the output value (or behavior), 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.
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
025
IMPLEMENTATION
026
Source code
import random
import time
for i in range(80):
print("*",end="")
time.sleep(0)
print()
print("\t\t\t Welcome to")
print("\t\t\tKaun Banega Crorepati")
for i in range(80):
print("*",end="")
time.sleep(0)
print()
a=input("\tEnter Your Name - ")
for i in range(80):
print("*",end="")
time.sleep(0)
print()
print("\n\t\tOK ",a," Let's Start The Game")
time.sleep(1)
questions=["Who is The Prime Minister of India","In Which Country Area 51 is
Located","Which one is the largest Continent in the world","What is the Latest
Version of Windows Since 2019","Which One of These Is not a Software
Company","How Many MB Makes 1 GB","Facebook Was Firstly Developed
By","Founder of Apple is","_________ is one of The Founder of Google","BIGG
BOSS season 13 Starts in ____ & ends in _____","Apple's Laptop is Also Known
as","First Apple Computer is Known as","Joystick is used For","____________ is
used to Encrypt Drives in Computer"]
answer=["Narendra Modi","United States","Asia","Windows
10","Honda","1024","Mark Zuckenberg","Steve Jobs","Larry Page","2019 -
2020","Macbook","Mactonish","Playing Games","Bitlocker"]
wronganswers=[["Amit Shah","Aditya Nath Yogi","Abhishek Jangdey"],
["India","Africa","Iraq"],["South Africa","North America","Europe"],["Windows
027
7","Windows 8","Windows 11"],["Oracle","Microsoft","Google"],
["10024","1004","2024"],["Bill Gates","Larry Page","Anish Bhardwaj"],["Rupesh
Sidar","Charles Babbage","Sundar Pichai"],["Larry Hensberg","Sunder Pichai","Bill
Gates"],["2020 - 2021","Not Starts Now","2018 - 2019"],
["ThinBook","Notebook","ChromeBook"],["Apple v.1","Apple Computer","Appbook"],
["Giving output command","Shutting down Computer","Log off Computer"],
["KeyGuard","Windows Secure","No Software like this"]]
attempquestion=[]
count=1
amount=0
while True:
while True:
selectquestion=random.choice(questions)
if selectquestion in attempquestion:
pass
elif selectquestion not in attempquestion:
attempquestion.append(selectquestion)
questionindex=questions.index(selectquestion)
correctanswer=answer[questionindex]
break
optionslist=[]
inoptionlist=[]
optioncount=1
while optioncount<4:
optionselection=random.choice(wronganswers[questionindex])
if optionselection in inoptionlist:
pass
elif optionselection not in inoptionlist:
optionslist.append(optionselection)
inoptionlist.append(optionselection)
optioncount+=1
optionslist.append(correctanswer)
alreadydisplay=[]
optiontodisplay=[]
a1=True
while a1:
a=random.choice(optionslist)
if a in alreadydisplay:
028
pass
else:
alreadydisplay.append(a)
optiontodisplay.append(a)
a1=not True
a1=True
while a1:
b=random.choice(optionslist)
if b in alreadydisplay:
pass
else:
alreadydisplay.append(b)
optiontodisplay.append(b)
a1=not True
a1=True
while a1:
c=random.choice(optionslist)
if c in alreadydisplay:
pass
else:
alreadydisplay.append(c)
optiontodisplay.append(c)
a1=not True
a1=True
while a1:
d=random.choice(optionslist)
if d in alreadydisplay:
pass
else:
alreadydisplay.append(d)
optiontodisplay.append(d)
a1=not True
right_answer=""
if correctanswer==a:
right_answer="a"
elif correctanswer==b:
right_answer="b"
elif correctanswer==c:
029
right_answer="c"
elif correctanswer==d:
right_answer="d"
print("--------------------------------------------------------------------------------------------")
print("\t\t\tAmount Win - ",amount)
print("--------------------------------------------------------------------------------------------")
time.sleep(1)
print("\n\t\tQuestion ",count," on your Screen")
print("--------------------------------------------------------------------------------------------")
time.sleep(1)
print(" | Question - ",selectquestion)
print("--------------------------------------------------------------------------------------------")
print("\t-----------------------------------------------------------------------------")
time.sleep(1)
print("\t| A. ",a)
print("\t-----------------------------------------------------------------------------")
time.sleep(1)
print("\t| B. ",b)
print("\t-----------------------------------------------------------------------------")
time.sleep(1)
print("\t| C. ",c)
print("\t-----------------------------------------------------------------------------")
time.sleep(1)
print("\t| D. ",d)
print("\t-----------------------------------------------------------------------------")
useranswer=input("\t\tEnter Correct Option\t or \t press Q to quit.\n\t\t\t...").lower()
if useranswer==right_answer:
if count==1:
amount=1000
elif count==2:
amount=2000
elif count==3:
amount=5000
elif count==4:
amount=10000
elif count==5:
amount=40000
elif count==6:
030
amount=80000
elif count==7:
amount=160000
elif count==8:
amount=320000
elif count==9:
amount=640000
elif count==10:
amount=1500000
print("\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n")
print("*********************************************************************************")
print("\t\t\t \\\\\\\\\\ Congratulations! //////////")
print("\t\t\t|||||||||| You Won The Game ||||||||||")
print("*********************************************************************************")
print("\n\n\t\t You Won Rs. ",amount)
print()
break
print("\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n")
print("*********************************************************************************")
print("\t\t\t \\\\\\\\\\ Congratulations! //////////")
print("\t\t\t|||||||||| Right Answer ||||||||||")
print("*********************************************************************************")
count+=1
elif useranswer=="q":
print("\n\n\t\t You Won Rs. ",amount)
break
else:
print("*********************************************************************************")
print("*********************************************************************************")
print("\t\t\tWrong Answer")
print("*********************************************************************************")
print("*********************************************************************************")
print("\n\n\t\t \tYou Won Rs. ",amount)
print("*********************************************************************************")
print("*********************************************************************************")
break
## Abhishek Ku.Jangdey,Rupesh Sidar,Anish Bhardwaj
031
SNAPSHOTS
OUTPUT
MAIN PAGE
032
033
CONCLUSION
034
CONCLUSION
The conclusion of this project KBC is a traditional game, typically played with
options. It’s possible, however, to play category KBC rather than answering
options the player might guess the answers. You’ll be writing a program to
play a “KAUN BANEGA CROREPATI” version of KBC as shown above. You’ll
also be doing same statistical analysis of the words used in the KBC game
035
FUTURE ENHANACEMENT
036
FUTURE ENHANACEMENT
The project has a very vast scope in future. The project can be
implemented on intranet in future. Project can be updated in near
future as and when requirement for the same arises, as it is very
flexible in terms of expansion. With the proposed software of
database Space Manager ready and fully functional the client is
now able to manage and hence run the entire work in a much
better, accurate and error free manner. The following are the future
scope for the project.
037
BIBLIOGRAPHY
038
BIBLIOGRAPHY
1. WEBSITES
1. www.google.com
2. www.myschoolr.com
2. Books
1. Computer Science with python, Sumita Arora
2. Computer Science, NCERT
3. Others
1. Teacher’ Guidance, Mr. Vikash Kumar Sahu
********************

CS Project 5

Uploaded by

Copyright:

Available Formats

You might also like

CS Project 5

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CS Project 5

Uploaded by

Copyright:

Available Formats

STUDENT MANAGEMENT SYSTEM PAGE NO.

1.1 ABOUT THE PROJECT

1. INCREASES VOCABULARY– More enhancements in player’s vocabulary, it

2. IMPROVES SPELLING – This game improves language skills as well

3. ENHANCES COGNITIVE SKILLS – The process of thought and analysis

4. POSITIVE APPROACH – As the game starts with a greeting message, it

3. UNCERTAINITY – There is no control of developer over choice of word given

Computer programs are written to solve problems posed by humankind. Prior

1.4 OBJECTIVES OF THE PROJECT

1. Write programs utilizing modern software tools.

2. Apply object oriented programming principles effectively when developing

1.5 SCOPE OF THE PROJECT

• Python laid its foundation in the late 1980s.

Python provides lots of features that are listed below:

1) EXPRESSIVE LANGUAGE: Python language is more expressive means

4) FREE AND OPEN SOURCE: Python language is freely available at

9) INTEGRATED: It can be easily integrated with languages like C/C++,

5. Academic scientific research

6. Exploration and Data analysis

9. Memory intensive and computation intensive tasks.

Python is not a good choice for:

• Memory intensive and computation intensive tasks.

• Embedded system where processor has limited capacity.

• For graphical intensive 3D game that takes up a lot of CPU.

• Application that demanded concurrency and parallelism.

• Developing mobile apps.

Interpreted languages and is slow compared to C/C++ or Java.

SYSTEM DEVELOPMENT STRATEGY

In systems engineering, information systems and software engineering, the

All software development methodologies (such as the more commonly known

STRENGTH AND WEAKNESSES OF SDLC

Control Increased development time

Monitor large projects Increased development cost

Detailed steps Systems must be defined up front

Evaluate costs and completion targets Rigidity

Documentation Hard to estimate costs, project overruns

Well defined user input User input is sometimes limited

Ease of maintenance Little parallelism

Development and design standards Automation of documentation and standards is

Projects canned early on the result in little or no

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE:

6. Training and Transition

7. Operations and maintenance

3.2. WATERFALL MODEL

This project has been carried out using WATERFALL MODEL.

iterative and flexible approaches, as progress flows in largely one direction

The sequential phases in Waterfall model are –

1. Requirement Gathering and analysis –All possible requirements of the

5. Deployment of System – Once the functional and non-functional testing

3.3 HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOWS 7 AND ABOVE

IV. RAM : 1GB+

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

Key board and mouse

X. Printer : (if print is required – [Hard copy])