computer

project

Name – raj shekhar

Class-12
Sec-e
Roll no –40
Subject- computer
 Certificate

This is to certify that

Raj Shekhar Student in class
12 ‘e’ has completed the
Project titled
‘’student report marker ’’
During the academic year 2023-
2024 for computer practical
Examination submitted
satisfaction report as
compiled in the following pages
under the supervision

Teacher’s sign external sign

 Acknowledgement

I would like to take this opportunity

to thank my computer teacher mr.
rajiv sir as well as our school
principal mr. m.k Sinha who gave me
such an amazing opportunity to do
this wonderful project.
Also I wish to thank my parents &
friends who helped me a lot in
collecting data ,picture and
continuous help and support.
Finally I would wish to thank
everyone involved in this project
time.
 TaBLe OF cOnTenT
s nO. DescriPiTiOn PAGE
NO.
01 acknOwLeDgemenT 4
02 OBjecTive OF PrODucT 5
03 PrOPOseD sysTem 5
04 sysTemDeveLOPmenT LiFecycLe 6
sDLc
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
15 BiBLiOgraPhy 31
 OBjecTive OF PrODucT

The objective of this project is to develop a student report maker that

can help students to create professional looking reports quickly and
easily. The software should be easy to use and should provide a variety
of templates and features to help students create reports for a variety
of purposes.

PrOPOseD sysTem

The proposed system is a web-based student report maker. The system

will allow students to create reports by selecting a template and
entering the required information. The system will then generate a
professional-looking report that can be downloaded or printed.

The objective of this project is to develop a student report maker that

can help students to create professional looking reports quickly and
easily. The software should be easy to use and should provide a variety
of templates and features to help students create reports for a variety
of purposes.
 sysTem DeveLOPmenT LiFecycLe

the system development lifecycle (SDLC) is a framework for developing

information systems. The SDLC consists of the following phases:

1. Requirements gathering and analysis: This phase involves gathering

and analysing the requirements for the system. The requirements are
gathered from users and stakeholders.
2. System design: This phase involves designing the system architecture
and components. The design is based on the requirements gathered in
the previous phase.
3. Implementation: This phase involves developing the system
components and integrating them into a working system.
4. Testing: This phase involves testing the system to ensure that it meets
the requirements and is free of defects.
5. Deployment: This phase involves deploying the system to users.
 Phase OF sysTem DeveLOPmenT LiFecycLe:

The following diagram shows the phases of the system development

lifecycle:
 FLOw charT

The following flowchart shows the flow of the student report maker system:
 sysTem Design

The system will be designed as a three-tier architecture:

1. Presentation tier: The presentation tier will be responsible for

displaying the user interface and interacting with the user.

2. Application tier: The application tier will be responsible for processing

the user requests and generating the reports.

3. Data tier: The data tier will be responsible for storing and retrieving the
data required by the system.
Purpose and idea

The purpose of the student report maker is to help students to create

professional-looking reports quickly and easily. The idea for the system
came from my own experience as a student. I often found it difficult to
create

professional-looking reports, especially when I was short on time. I

wanted to develop a system that would make it easier for students to
create reports, so that they could focus on their studies
 sysTem Design

The system will be designed as a three-tier architecture:

1. Presentation tier: The presentation tier will be responsible for displaying

the user interface and interacting with the user.
2. Application tier: The application tier will be responsible for processing the
user requests and generating the reports.
3. Data tier: The data tier will be responsible for storing and retrieving the
data required by the system.

The purpose of the student report maker is to help students to create

professional-looking reports quickly and easily. The idea for the system came
from my own experience as a student. I often found it difficult to create

professional-looking reports, especially when I was short on time. I wanted to

develop a system that would make it easier for students to create reports, so
that they could focus on their studies.
 PurPOse anD iDea

The purpose of the student report maker system is to help students to

create professional and well-formatted project reports with ease. The
idea behind the system is to provide students with a variety of features
to help them create customized reports, without the need to have any
knowledge of coding or design.

FeaTures
The student report maker will have the following features:

• A variety of templates for different types of reports

• Easy-to-use interface

• Ability to add and remove sections from reports

• Ability to add images, charts, and graphs to reports

• Ability to download or print reports

 Conclusion

The student report maker is a web-based application that will

help students to create professional-looking reports quickly
and easily. The system will provide a variety of templates and
features to help students create reports for a variety of
purposes. The system is currently under development and is
expected to be released in the near future.
 Elaboration with pictures and diagrams:

The following pictures and diagrams illustrate the main components of the student
report maker system:
 Benefits of using the student report maker
system

The student report maker system offers a number of benefits, including:

• Improved student productivity: The system can help students to create reports
more quickly and easily, freeing up their time to focus on their studies.
• Increased student confidence: The system can help students to create
professional-looking reports that they can be proud of.
• Improved student grades: Teachers are more likely to give higher grades to
reports that are well-written and wellorganized.
• Reduced teacher workload: The system can help teachers to reduce their
workload by automating the grading process.

Conclusion
The student report maker is a web-based application that can help
students to create professional-looking reports quickly.

Source Code: import csv

def get_student_input():
name = input("Enter student name: ")
class_ = input("Enter student class: ")
marks = [] for i in range(5):
subject = input("Enter subject name: ")
mark = int(input("Enter mark: "))
marks.append(mark)

return name, class_, marks def

store_student_data(student_data): with
open("student_data.csv", "a", newline="")
as csvfile:
writer = csv.writer(csvfile)
writer.writerow(student_data) def edit_student_data(name):
with open("student_data.csv", "r", newline="") as csvfile:
reader = csv.reader(csvfile)
students = list(reader)

for i in range(len(students)):
if students[i][0] == name:
class_ = input("Enter new student class: ")
marks = []
for j in range(5):
subject = input("Enter new subject name: ")
mark = int(input("Enter new mark: "))
marks.append(mark)

students[i][1] = class_
students[i][2:] = marks

with open("student_data.csv", "w", newline="") as csvfile:

writer = csv.writer(csvfile) writer.writerows(students) def
delete_student_data(name): with
open("student_data.csv", "r", newline="") as csvfile:
reader = csv.reader(csvfile)
students = list(reader)
 for i in range(len(students)):
if students[i][0] == name:
del students[i]
break

with open("student_data.csv", "w", newline="") as csvfile:

writer = csv.writer(csvfile) writer.writerows(students)
def show_student_data(): with open("student_data.csv", "r", newline="") as csvfile:
reader = csv.reader(csvfile)
for row in reader:
print(row)
def main():
while True:
print("Enter 1 to add student data")
print("Enter 2 to edit student data")
print("Enter 3 to delete student data")
print("Enter 4 to show stored student data")
print("Enter 5 to exit")

choice = input("Enter your choice: ")

if choice == "1":
name, class_, marks = get_student_input()
store_student_data([name, class_, *marks])
elif choice == "2":
name = input("Enter student name to edit: ")
edit_student_data(name)
 elif choice == "3":

name = input("Enter student name to delete: ")

delete_student_data(name)
elif choice == "4":
show_student_data()
elif choice == "5":
break
else:
print("Invalid choice. Please try again.")

if __name__ == "__main__":
main()
Output:
 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 thatit 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.

BLACKBOX 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 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. 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

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 testingmethods
• 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
 HARDWARE AND SOFTWARE REQUIREMENTS

I.OPERATING SYSTEM : WINDOVWS 7 AND ABOVE

Il. PROCESSOR : PENTIUM(ANY) OR AMD (3800+- 4200+ DUALCORE)
II. MOTHERBOARD: 845 OR 915,995 FOR
PENTIUM OR MSI
V. RAM : 512MB+
V. Hard disk : SATA 40 GB OR ABOVE
VI. CD/DVD rlw multi drive combo:(If back up required)
VIL. FLOPPY DRIVE 1.44 MB : (If back up required)
VIll. MONITOR 14.1 or 15 -17 inch
IX Key board and mouse
X Printer : (if print is required-[Hard copy])

SOFTWARE REOUIREMENTS:
1. Windows OS
2. Python
 Bibliography

1.In computer science with Python class. 12 by Sumita Arora.

2.ChatGPT
3.Google Bard
4.Website: https://www.w3schools.com/
5.Website: https://www.wikipedia.org/