Project CS
Project CS
Project CS
SCHOOL
KADRU, RANCHI
1
DAV KAPILDEV PUBLIC SCHOOL
KADRU, RANCHI
CERTIFICATE
This is to certify that ___________________ CBSE student Roll
No: _________________ has successfully completed the
project Work entitled “STUDENT REPORT MAKER”, in the
subject COMPUTER SCIENCE (083) laid down in the regulation
of CBSE for the purpose of Practical Examination in Class XII to
be held in DAV KAPILDEV PUBLIC SCHOOL, RANCHI on
______________.
__________________
(SK JHA)
PGT Comp Sci
MASTER IC
Examiner :
Name : ________________
Signature : ________________
Date : ________________
2
TABLE OF CONTENT
S NO. DESCRIPITION PAGE NO.
01 Acknowledgement 4
02 Objective of product 5
03 Proposed system 5
04 System development lifecycle SDLC 6
05 Phase of system development 8
lifecycle
06 Flow chart 9
07 System design 10
08 Features 12
09 Elaboration 14
10 Benefits 15
10 Conclusion 16
11 Source code 17
12 Output 24
13 Testing 25
14 Hardware and software 30
requirements
16 Bibliography 31
3
Acknowledgement
Apart from the heart 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 expressed deep sense of gratitude to almighty God for giving
me strength for the successful completion of this project.
I expressed my heartfelt gratitude to my parents for constant
encouragement while carrying out this project.
I gratefully acknowledge the contribution of individual who
contributed in bringing the project up to this level who continues to
look after me despite my flaws.
I express my deep sense of gratitude to the luminary, The
Principal, DAV Kapildev Public Ranchi, who has been continuously
motivating and extending their help hands to us.
I am overwhelmed to express my thanks to The
Administrative officer, DAV Kapildev Public Ranchi, for providing
me an infrastructure and moral support while carrying out this
project in the school.
4
Objective of product
purposes.
Proposed system
5
System development lifecycle
stakeholders.
6
3. Implementation: This phase involves developing the
system.
users.
development lifecycle:
7
Flow chart
8
System design
tier architecture:
The system will be designed as a three-tier
9
1. Presentation tier: The presentation tier will be responsible
user.
3. Data tier: The data tier will be responsible for storing and
10
professional-looking reports, especially when I was short
11
reports with ease. The idea behind the system is to
Features
Easy-to-use interface
Conclusion
12
The student report maker is a web-based application that
future.
13
The following pictures and diagrams illustrate the main
system
14
The student report maker system offers a number of
benefits, including:
organized.
process.
15
Conclusion
quickly.
16
Source Code:
import csv
def get_student_input():
marks = []
for i in range(5):
marks.append(mark)
def store_student_data(student_data):
17
with open("student_data.csv", "a", newline="") as
csvfile:
writer = csv.writer(csvfile)
writer.writerow(student_data)
def edit_student_data(name):
reader = csv.reader(csvfile)
students = list(reader)
for i in range(len(students)):
if students[i][0] == name:
marks = []
for j in range(5):
18
subject = input("Enter new subject name: ")
marks.append(mark)
students[i][1] = class_
students[i][2:] = marks
writer = csv.writer(csvfile)
writer.writerows(students)
def delete_student_data(name):
reader = csv.reader(csvfile)
19
students = list(reader)
for i in range(len(students)):
if students[i][0] == name:
del students[i]
break
writer = csv.writer(csvfile)
writer.writerows(students)
def show_student_data():
reader = csv.reader(csvfile)
20
for row in reader:
print(row)
def main():
while True:
print("Enter 5 to exit")
21
if choice == "1":
edit_student_data(name)
delete_student_data(name)
show_student_data()
break
else:
22
print("Invalid choice. Please try again.")
if __name__ == "__main__":
main()
23
Output:
24
Testing
25
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.
BLACKBOX TESTING
SPECIFICATION-BASED TESTING
26
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.
27
Types of white box testing:-
28
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:
29
HARDWARE AND SOFTWARE REQUIREMENTS
I.OPERATING SYSTEM : WINDOVWS 7 AND ABOVE
V. RAM : 512MB+
SOFTWARE REOUIREMENTS:
1. Windows OS
2. Python
30
Bibliography:
2.ChatGPT
3.Google Bard
4.Website: https://www.w3schools.com/
5.Website: https://www.wikipedia.org/
31