Professional Documents
Culture Documents
6025 - Computer Sales and Service System
6025 - Computer Sales and Service System
PROJECT REPORT ON
ROLL NO : 6025
NAME : R.M.VIZAL
CLASS : XI - A
PGT (CS)
TIRUPPUR DIST
TAMILNADU
SAINIK SCHOOL AMARAVATHINAGAR
CERTIFICATE
This is to certify that Cadet __R.M.VIZAL_____ Roll No: _6025 has successfully
completed the project Work entitled "COMPUTER SALES AND SERVICE SYSTEM." in
the subject Computer Science (083) laid down in the regulations of CBSE for the
Amaravathinagar on______________.
(PM Jigajinni)
PGT Comp Sci
Master IC
Examiner:
Name: _______________
Signature:
Date:
TABLE OF CONTENTS [ T O C ]
01 ACKNOWLEDGEMENT 04
02 INTRODUCTION 05
04 PROPOSED SYSTEM 06
07 FLOW CHART 15
08 SOURCE CODE 16
09 OUTPUT 18
10 TESTING 19
12 BIBLIOGRAPHY 23
ACKNOWLEDGEMENT
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.
Note :
• Allow the administrator to delete an enrollment, edit the name and course of a
candidate.
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.
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 outdated to rationalize your mistake. So, to keep pace with
time, to bring about the best result without malfunctioning and greater efficiency so to
replace the unending heaps of flies with a much sophisticated hard disk of the
computer.
One has to use the data management software. Software has been an ascent in
atomization various organisations. Many software products working are now 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 paper work has to be
done but now software product on 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 button.
Moreover, now it’s an age of computers of and automating such an organization gives
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.
PLANNING PHASE
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’ sjob 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.
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 alevel 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 MasterPlan.
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 scriptprograms during the development phase.
Program designs are c onstructed in various ways. Using a top-down approach,
designers first identify and link majorprogram 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:
• Identifying potential risks and defining mitigating design features.
• Performing a security risk assessment.
• Developing a conversion plan to migrate current data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and outputs.
• 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 byAgency 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
• Testing as a deployed system with end users working together with contract
personnel
• Operational testing by the end user alone performing all functions. Requirements
are traced throughout testing,a final Independent Verification & Validation
evaluation is performed and all documentation is reviewedand accepted prior to
acceptance of the system.
IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted by the
user. In this phase, the system is installed to support the intended business functions.
System performance is compared to performance objectives established during the
planning phase. Implementation includes user notification, user training, installation of
hardware, installation of software onto production computers, and integration of the
system into daily work processes. This phase continues until the system is operating in
production in accordance with the defined userrequirements.
Flow chart
START
5.exit “ “
If choice
==1:
PRINT”computer sales
INPUT “please enter yourname:”,cust_name
C1.EXECUTE(INSERT)
CONN.COMMIT()
If choice==
2:
PRINT”computer service”
Taking in values for name,phno,email,address and as
input
If a==1:
Inputs the values of customer name,cus_name,phone
no,phno1,sales boy or door delivary boy name,sa_name and
the customers problem,prob
IF a==2:
If a==3:
PRINT” sorry for the problem sire/madam we will ensure that this does
not happen next time. thankyou
Inserts the values into sb_prob table
IF choice==4:
IF choice==5:
STOP
SOURCE CODE
if choice==2:
print('')
print(' COMPUTER SERVICE')
print('')
name=str(input('please enter your name:'))
phno=int(input('please enter your phone number:'))
email=str(input('please enter your e-mail id:'))
address=str(input('please enter your residential address:'))
service=str(input('please enter the service you want:'))
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 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)
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.
SOFTWARE REQUIREMENTS:
• Windows OS
• Python
.
BIBLIOGRAPHY
***