MAJOR PROJECT REPORT ON PIZZA MANAGEMENT SYSTEM WITH “VISUAL BASIC” SUBMITED AS PROJECT OF BACHELOR OF COMPUTER APPLICATION Study center at Computer Career Institute Brahmanand Nagar Colony Durgakund,Varanasi STUDY CENTER CODE (S195) SUBMITED BY: Shashank Singh
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
MAJOR PROJECT REPORT ONPIZZA MANAGEMENT SYSTEM WITH
“VISUAL BASIC”
SUBMITED AS PROJECT OFBACHELOR OF COMPUTER APPLICATION
Study center at
Computer Career InstituteBrahmanand Nagar Colony
Durgakund,VaranasiSTUDY CENTER CODE (S195)
SUBMITED BY: Shashank SinghGUIDED BY:- Mr. Satish TiwariEnroll NO. 721951050064 ROLL NO: 18044Session :- 2007-2010
ANALYSIS AND DESIGN
The design of the information system produces the
details that state how a system will meet requirements identified
during system analysis. System specialists often refer to this stage as
logical design, in contrast to the process of developing program
software, which is referred to as physical design.
System analysis begins the process by identifying
reports, the requirements and output needed by the system. Then the
specific data on each are pinpointed. Usually, designers’ sketch the
form of display as they expect from the system. This can also be
done on paper of on the computer display with the help of the
automated system tools available.
The system design also describes the data to be input,
calculated of stored. Individual data items and calculations
procedures are written in detail. The procedures tell bow to process
the data and produce the output. Designers are responsible for
providing programmers with complete and clearly outlined software
specifications.
As programming starts, designers are able to answer
questions, clarify fuzzy areas and handle problems that comfort the
programmers when using the design specifications. As the software
is to be designed in Access DBMS; the concept of the database is
must of quality designing. It will be designing of the database,
designing, designing the forms. Designing of reports, designing of
data loader.
DESIGN OBJECTIVES:-
The following goals were dept in mind while
designing the new system;
To reduce the mutual word required to be done in
the existing system.
To avoid errors inherent works and hence make
the outputs consistent and correct.
To improve the management of permanent
information to the company be keeping it in properly structured
tables and to provide facilities to update this information as
efficiently ad possible.
To make the system completely menu-driven and
hence user –friendly. This was necessary so that even non-
programmers could use the system effectively and system could act
as catalyst in achieving objectives.
To make the system compatible i.e. it should “fit
in” the total, integrated system.
To make the system in such a way that reduced
future maintenance and enhancement times and efforts.
To make the system reliable, understandable and
cost effective.
DESIGN OVERVIEW
The design stage takes the final specification of the
system from analysis stages and finds the best way of fulfilling them,
given the technical environment and pervious decisions on required
level of automation.
The system design is carried out in two phases:
1. Architectural design (High level design)
2. Detailed design (Low Level Design)
HIGH LEVEL DESIGN
The high-level design maps the business system
described in the program requirement specification to logical data
structure. It involves:-
Identifying the entities: All the entities related to
module were identified, checked and consolidated.
Identifying the relations: The relationship between
entities, within and outside the system was identified.
Attributes definition: The pertaining to the entities
was designed and their field characteristics were specified.
Normalization: The entities were normalized. After
first and second normalization was achieved for all entities of
system.
Interface: interfacing with other system was done and
attributes related to external entities were identified.
Once the entities and their attributes were defined,
ENTITY REALTIONSHIP DIAGRAM was drawn.
LOW LEVEL DESIGN
The low-level design maps the logical model of the
system to a physical
Database design.
Default database design: this utility creates column and constraints
definitions from the design stage of business system development. the
application system, fautions, tables and column must already exit in
CASE * Dictionary before being referenced.
User preference: based on user preferences like block
name, validation of primary keys, layouts of blocks, layout of fields,
creating titles of blocks, mandatory input field prompts etc. were
incorporated here.
BACK END
BENEFITS OF COMPUTERIZATION
There are lot of difficulties and bottlenecks in the current manual system.
After the computerization of registration of the student. The problem can
be removed to a great extent, for example:-
1. Response time will be reduced i.e. time taken to
complete any inquiry will be reduced resulting in reduced waiting time.
2. The workload of the staff is currently more, it will be
reduced.
3. Improved user satisfaction.
4. Easy access of record.
5. Security and secrecy of records.
Objectives of the proposed system
The function of student record management system is an
essential part of any college. The objective of this system is to keep
track, records & maintain strict control over proper maintenance and
security of students’ records. This system is designed with the purpose,
that it should be useful to the keeping student’s records management
system of a college.
BIBLIOGRAPHY
1. “DATABASE PROGRAMMING WITH VISUAL BASIC 6.0”.
By TECHAMEDIA
2. “MASTERING IN VISUAL BASIC.” By AVANGELOUS PETROUSOS
3. “VISUAL BASIC 6” By GARY CORNELL
4. “MICROSOFT ACCESS 2003” By BPB PUBLICATIONS
5. “SYSTEM ANALYSIS AND DESIGN Vol. (I & II)”
By LEE
6. “SYSTEM ANALYSIS AND DESIGN” By ELIAS M. AWAD
7. “SOFTWARE ENGINEERING” By PRESSMAN
CONCLUSION
Based upon the above analysis of present project we can work out
through three major conclusions regards to:
1. Merits of Student record management system.
2. Limitations of student record management system.
3. Scope of further study.
MERITS:
The following are few positive points in favor of proposed student
record management system in contrast with the existing traditional
system of working:
(A) Less time consumed.
(B) Less paper work is involved.
(C) Increase in overall efficiency.
(D) Lesser costs are involved.
(E) The overall wording becomes Easy & Economical.
LIMITATIONS:
(A) Computer cannot replace human judgment & Decision-
making.
(B) Higher costs are associated with computer related
applications.
(C) Any, even a minor, mistake or flow in computer operational
process might cost human life.
SCOPE:
As the requirements of speedy processing of daily transaction is
becoming the basic need for every area business. Therefore every
body is adapting computer technology for his or her business.
CONTENTS
1. INTRODUCTION
2. PROJECT PROFILE
3. VARIOUS DEVELOPMENTS
A.SYSTEM ANALYSIS.
B.FEASIBILETY STUDY
C.DESIGN
D.IMPLEMENTATION
E. TESTING
F. MAINTAINENCE
4. FORMS AND TABLES
A. Main Form
B. MAIN MENU FORM
D Bill Managment
E. Pizza detail
5. ER DIAGRAM
6. DATA FLOW DIAGRAM
7. BIBLIOGRAPHY
Cost Benefit Analysis
Risk Management
Risk management is an emerging area that aims to address the
problem of identifying and managing the risk associated with the
software project. The basic motivation of having this is to avoid
heavy losses or disasters. It is very important particularly of large
project. The project has no major hazards associated with is. The
only risk has are the cost band schedule risks. Although analysis can
easily is done regarding the schedule risk involved. Risk
management is the area that tries to ensure that the impact of risk on
cost quality and schedule.
Like in booking system cost and quality is major risk prone area. it
minimizes the impact of risk. Project management generally does it,
risk assessment is and activity that must be undertaken during project
planning, and this involves identifying the risk occurs in system,
analyzing them and prioritizing them on the analysis due to the
nature of the software uncertainties are most near the beginning of
the project and remain throughout the project so risk assessment
should be done throughout the project. At the high software level,
risk is divided into three categories these are:-
Cost risk is the risk that is associated with the budgeted outlays
for the project and its impact on the project the system should
be economical. if the cost is going beyond the limit expected
then project is nit good.
Performance risk is the possibility that the system is not giving
all the benefits expected form it or will not perform according
to the requirement here performance includes quality.
Schedule risk associated with the project schedule or the ability of
the project to achieve the specified milestone. The goal of risk
assessment is to prioritizing so that risk management easily focuses
attention and resources on the more risk items. The main aim of risk
paining is to enumerate the risk items and specify how to handle it.
Otherwise it creates the problem in the last in term of cost, quality
and schedule.
DESIGN DECISION
The system bas been decided to be developed on visual basic 6.0
using various products like FORMS. REPORTS.
MICROSOFT ACCESS 2003 RDBMS has been chosen since the
system has the following requirements and it caters all:
1. Large databases and space management control
ACCESS supports the largest of database, potentially. Hundreds
of gigabytes in size. It stores the data in the form of tables making
optimal use of the available storage. To make efficient use of
expensive hardware devices, it allows full control of space usages.
2. Many concurrent database users
ACCESS supports large number concurrent users
executing a verity of database application operating on the data.
3. High transaction processing performance
ACCESS maintains the preceding feature with a
high degree of overall system performance database users do not
suffer from slow processing performance.
4. Controlled availability
ACCESS RXBMS can selectively control the
availability of data, at the databases level and sub-databases level.
E.g. an administrator can disallow use of specific applications so
that applicant’s data can reload, without affecting others
applications.
DETAILED SYSTEM INVESTIGATION
At the heart of the system analysis does a detailed understand
of all-important facets of the business area under investigation?
For this reason the process of acquainting this information is often
called as detailed investigation analysis warding closely with
employees, manager and proprietor must study the business
process to answer these questions:
1. What is being done?
2. How is being done?
3. How frequently does it occur?
4. How is the volume of work?
5. Hoe well is the task being performed?
6. Does any problem exit?
7. If a problem exits, what is the underlying cause?
8. If a problem exits, what is the underlying cause?
9. And what is the solution of the problem?
To answer these questions, system
analysts talk to variety of persons together details about the
business and their opinions of why things happens as they do and
their ideas for changing the process. Questionnaires are used to
collect this information.
Detailed investigations also require the study of manual and
reports actual observation of work activates, and sometime,
collection of sample forms and documents to fully understand the
process.
As a detailed are gathered, the
analysts study the requirements data to identify features the new
system should have, including both the information the system
should produce and operational features such as processing
controls, response times and input and out methods.
HARDWARE CONFIGURATION
The hardware used for the development of software was
Pentium IV based are as follows:-
C P U Chip : Intel Pentium
Main Memory: 128 MB
Cache Memory: 256 KB
Hard Disk: 40 GB
Floppy Disk: 1.44 MB
SOFTWARE CONFIGURATION
Operating System: Windows 98/ME/XP
Database: MS Access 2002
Application Development Tools: Visual Basic 6.0
IMPLEMENTATION
After the user has certified the system, it comes to the stage of
implementation. it involves many issues like preparation for the
changeover to the new system and then the actual change over.
Preparation of site and installation and facilities, training of staff,
preparation of data file etc. are the various steps involved which
might require the involvement of the system analyst, the user as
well as operational staff.
After all the preparation of the system implementation is
completed, comes the stage of actual change this involves the
usages of the system, which has been developed and thoroughly
tested. There are different approaches, which might be followed in
this change over.
Direct over
Parallel running
Pilot running
Direct changeover in this method old system is scrapped of
with drawn the moment new one is put into user like in creditor
leader of changeover would man manual record keeping like
maintaining ledger and day book is stopped and converted into the
data file which is them stored and is directly handled through the
new computerized system this could lead to some problem if the
new system does not behave as expected. This may be the result of
some unforeseen situation which had not been taken care of during
the system analyses and design phase, in such situation there is no
manual system remain to get back upon, the user may be put to
serious problem in such, we may follow a procedure of running
both system for some times as parallel running.
Parallel running is the method of submitting a new system to
final acceptance test, in which data is processed using both the old
and new system simultaneously. in which manual system like
ledger cashbook, daybook and the related data files of computer
system are running parallel. The result of two system are compared
and any discrepancies examined to see whether the system is at
fault this is a better method but is has some drawbacks like extra
cost, because the user staff will have to work with to system i.e. old
and new.
They will have to do extra work also in cross the result when
they are busy in learning new procedures.
Pilot running is an alternative to parallel running and consist
of the allocation of the certain amount of work to be performed by
the computer while the remainder is done by the old method. The
amount of work performed on the computer is gradually increased
until the changeover is complete and old system is discontinued.
From the entire above pilot running is better than all because
it provides the facilities of both fast accesses processing affecting
the cost. In which half of the work is done manually and half is
done with computerized and then compared the two. Then convert
them slowly to new system. This will save cost, time and the
problem arises during direct changeover.
INTRODUCTION
The project development is not an easy job.
Every aspect of the ‘software design’ project should
be well analyzed and data should be in a very
structured manner. Duplicity of the data should be
avoided, to the point and descriptive fields should be
taken. I have put my best efforts to computerize the
process of Academic System and other relevant
details for ready reference to the best of my
information about this. It is a very comprehensive
and complicated job, which involves many persons;
whatever I have analyzed is detailed portion of record
entries.
The main outcome is shown through the help of
different reports. Various reports that are made in the
project are:-
List of products
List of Pizza detail
MAINTENANCE
The goal of the system development project is to produce
software which is easy to maintain because during the life of
software the maintenance cost generally exceed the development
cost one possible reason of exceeding cost is that the developer
frequently develop the software, install it, and than hand it over
to different set of people called maintainers. But the maintainer
usually don’t even belong to the organization that develop
software so first of all we have to give proper training to staff
about the system and teach them how to handle it, operate it and
what to do in saturation when it is not performing well or the
delivery of the system.
once the system has been settled down and been running
for some years then responsibility handed to the trained
maintainer during maintenance the system analyst has to check
that weather system performed according to the started objective
or not during maintenance we have to keep eyes on the
functioning of new system like addition of record, showing and
payment entry etc, and check whether it is performing well
according to required specified.
This is on going exercise after the system has been
implemented. The read life is not static its requirements or
objectives are keep changing. so the system has to keep on
carrying out changing and modification into the system this is a
stage normally called system maintenance. The maintenance the
testing depend on the design and coding to make testing and
maintenance easier.
But the maintainer usually don’t even belong to the
organization that develop software so first of all we have to give
proper training to staff about the system and teach them how to
handle it, operate it and what to do in saturation when it is not
performing well or the delivery of the system.
MS ACCESS
Using Microsoft Access, you can manage all your
information from a single datable file. Within the file divide
your data into separate storage container called tables, view, add
and update table data using online forms, find and retrieve the
data you want using queries, and analyze or print data in a
specific layout using reports.
To store your data, create one table for each type of
information you that you specify, including data from multiple
tables, create a query. A query can also update or elate multiple
records at the same time and perform built-in or custom
calculation on your data.
To easily view and change directly in a table, create a form
when you a form Microsoft Access retrieve the data from one
or more tables. And displays it on screen using the layout you
choose in the form wizard or using a layout that you created
from scratch.
To analyze your data or present it a certain way in print,
create report. For example, you might print one report that
group’s data and calculates total, and another report with
different data formatted for printing mailing tables.
ABOUT MS ACCESS 2002: A relational database .The
Access as a database is the easiest and simplest.
Some of its features are as follows:-
FEATURES:-
First Access is obviously a database application. Database
allows you to collect any type of information for storage and
later searching and retrieval.
Access excels at being able to collect information. Through
the use of either a datasheet view or a custom form. The
datasheet view provides a spreadsheet similar to Microsoft
Excel. You can create custom forms that can look like all other
Windows applications and use these together and retrieve
information.
You can also create custom reports for printing and
exporting the information stored in the database.
Second Access is desktop database. This means Access is
designed to be used on a desktop computer. You can place an
Access file on a network server and share the database with
other user on the network. It is not however a true client server
database the Access is a fire stored on hard drive, not a running
application.
Client / server are term describe two different computers,
which communicate with one another in a short master slave
relationship. One computer the server provides data and other
services for multiple other computers, the clients. The fact that
Access is not a client / server database might seem like a
disadvantage, but it realty is not When Access is used in proper
Environment, it has distinct advantages over client / server
database. First and Foremost, it is very easy to administer.
There are not a lot of complications settings or network
security issue to muddy the waters. You also do not need a very
powerful system to run Access 2002. So if you need a database
which only few people can access at a time then Access 2002 is
the perfect choice.
Finally the Access 2002 is a relational database. Relational
database is one of the most versatile types of database ever
developed. In relational data, you can define relationships can
then be used to perform complex searches and to produce
detailed reports.
OBJECTIVES
The Project management is the application of planning
organizing and control concepts to critical one-of-a kind
projects. Management projects require top management
commitment, active- Participation and long –range plan. The
fundamental objective of a project work is to demonstrate how
tedious manual work using the computer capabilities can easily
do.
The main objective of my project is that it shows the critical
jobs in the object schedule, explains the relationships between
jobs, and generates reports and schedules as needed.
Specifically, it does the following:-
1. Determine the jobs that require quick and secure
Process to compile the computerized booking.
1. 2. Determines the jobs, which save time that can be
Delayed without it..
3. Maintains a schedule in sequence is preferred.
4. Maintains requirements and information.
5. Keeps track of important deadlines and significant aspects
throughout the project.
6. Investigates trade offs between work cost and time.
7. Changes the aspects of a job and immediately shows the
impact performance on the overall project.
8. Allows sorting and rearranging jobs in the schedule and rep
E - R DIAGRAM
PHONE ADDRESS
NAME
Customer
Order Delivary
Pizza Cost
Order no NAME RECIPIT NO
(The E-R Diagram of Pizza managment System)
C ontext Diagram
CUSTOMER
REQUEST RESPONSE
PIZZA MANAGEMENT
SYSTEM
UPDATION QUERIES SOLVED
DATABASE
(Context Diagram)
D EBUGGING
Once errors are identified, it is necessary to first identify
the precise the location of the error and then to fix them, in this
section, we will summarize the important approaches that are
available to identify the error locations.
DEBUGGING APPROACHES
BRUTE FORCE METHOD:-
In this approach, the program
is loaded with print statements to print the intermediate values
with the hope that some of the printed values will help to identify
the statement in error.
BACKTRACKING:-
This is also a fairly common approach.
In this approach, beginning from the statement at which an error
symptom has been observed, the source is traced backwards until
the error is discovered.
CAUSE ELIMINATION METHOD:-
In this approach, a list
of causes which could possible have contributed to the error
symptom is developed and tests are conducted to eliminated to the
error symptom is developed and tests are conducted to each cause.
A related technique of identification of the error from the error
symptom is the software fault tree analysis.
IMPLEMENTATION:-
After completion of about test plan
successfully the system is ready to implement for which it has
been made.
Implementation is a thing to convert any system design into
operational form using several implementation tools.
Implementation of that system acquire compatible environment
for this system as defines above.
Successful implementation needs to teach the user how to operate
the system by user manual.
Preliminary Investigation
The first step in the system development life cycle is the
preliminary investigation to determine the feasibility of the
system. The purpose of the preliminary investigation is to
evaluate project requests. it is not a design study nor does it
include the collection of details to describe to business system in
all respect. Rather, it is the collecting of information that helps
committee members to evaluate the merits of project request and
make one informed.
Analysis working on the preliminary investigation should
accomplish the following objectives.
o Clarify and understand the project request
o Determine the size of the project.
o Assess costs and benefits of alternative
approaches.
o Report the findings to management with
recommendations outlining the acceptance or
rejection of the proposal.
Conducting the Investigation
The data that the analysis collect during preliminary
investigations are gathered through three preliminary methods:
reviewing organization documents, on-site observations and
conducting interviews.
Reviewing Organization Documents
The analysis conducting the investigation first learnt about
the organization involved in or affected by the project. For
example, to review an inventory systems proposal means
knowing first how.
Conducing Interviews
Written documents and the on-site observation tell the
analysis how system should operate, but they may not include
enough details to allow a decision to be made about the merits
of a details to allow a decision to be made about the merits of a
system proposal, nor do they present user views about current
operations. Analysis use interviews to learn these details.
Interviews allow analysis to learn more about the nature of the
project and the reason of submitting it. Interview view should
provide details that further explain the project and show
whether assistance is merited economically, operationally
technically.
PRESENT SYSTEM
The existing system depends upon manual operations
that are all records were kept in simple files and thus the
data is maintained, but, any small mistake may lead to a
big problem.
For example:-
For example ,for the proper maintenance of the
registration information , several reports i.e. List of Names
Address dept wise and ready reference of functions a
constant check on this data is required , because of the
reason that without this , proper and lengthy record can’t
be maintained .
This may also lead to some accuracy problems in
various data files.
Project Monitoring Plan
Cost schedule milestone graph
A cost schedule graph represents the planned cost of
different milestones. It also shows the actual of achieving the
milestone gained by so far. By having the planned cost verses
milestone and actual cost verses milestone on the same graph the
progress of the project easily.
In the following the x-axis of the graph is time, where the
month in the project schedule are marked the y-axis represent
the cost in dollars or PMs. The two carves are drawn one curves
is the panned cist and planned schedule in which the project plan
is completed. The second curve represents the actual cost and
actual schedule and the actual achievement of milestone are
marked. Thus for each milestone the point representing the time
when the milestone are actually achieved and the actual cost of
achieving are marked for example milestone graph of creditor
are given below.
In this project cost is estimated to be $100k different
milestones are identified and curves are drawn with this
milestone.
The milestone in this graph is PDR, CDR, module 1
completion, module 2 completion, integration testing and
acceptance testing. For each of these milestones some budgets
are allocated based on the estimates the planned budget is shown
by dotted line and the actual expenditure are shown by bold line.
This chart shows that only two milestones are achieved, PDR,
SDR, and through the project are in budget when PDR was
completed, it is now slightly over budget.
This type of graph helps system designer had programmer in
risk management in cost and benefit plan. It tells us clearly that
whether the proposed system are in budget of going out budget
this also helps us in checking economical feasibility if the
project is going beyond the going beyond the expected budget
and not giving enough benefited as expected than is not good.
The two carves are drawn one curves is the panned cist
and planned schedule in which the project plan is completed.
The second curve represents the actual cost and actual
schedule and the actual achievement of milestone are
marked.
PROJECT PROFILE
Name of the Institute Computer Career Institute,
Varanasi
Address of the Institute: B-34/130-12-1, Bramhanand
(Kabeer Nagar), Durgakund
Varanasi (U.P)-221005
Name of Software: Pizza Management System
Platform Used: Win 98/Win 2000/XP
Language Used: Visual Basic 6.0
Database Used: MS ACCESS 2002
Project Guide: Mr. Satish Tiwari
PROJECT SELECTION
Software selection is a critical aspect of system
development .Although, reliable software is a desirable
goal; limited progress has been made towards improving it
in the last decades. Software is classified for controlling
computer operations and application software for solving
user oriented problems. In general, software allows
concurrence of operation, resource and information
sharing, multiplexed operation. It has grown by leaps and
bounds, especially, since the birth of microcomputers.
In the world of HI-TECH, where everything is moving
around information Technology, this whole world has
become a global village. I would certainly not like to be
left behind in this competitive world. So keeping this in
view , I have joined this course , and as a part of our
curriculum , I have prepared this project . To select a
project is not an easy task . As nightly said-“Good start is a
half way to success “. So I discussed many projects to
work on. Then, I came across this project.
Encouraged by the demand of computers in this
competitive world, I am promoted to take up this
project .After getting permission; I started working on this
project. After discussing every feature of this project with
the concerned guide and teacher. I am quite confident to
work on this project.
Although, reliable software is a desirable
goal; limited progress has been made towards improving
it in the last decades. Software is classified for
controlling computer operations and application
software for solving user oriented problems. In general,
software allows concurrence of operation, resource and
information sharing, multiplexed operation.
PROPOSED SYSTEM
After going through the through study. it is found that given
project is feasible with respect to technical, social economical,
operational and legal aspects. A system is technically feasible, if
it can be designed and implemented within the limitations of the
available resources like funds, manpower, hardware, software
etc. The proposed system is technically feasible as the existing
staff can be trained to operate the computerized system and costs
involved are reasonable considering the benefits and future
aspects.
The proposed system is economically feasible if the benefits
obtained in the long run compensate, rather than overdo the costs
incurred in designing and implementing. in this case benefits
outweigh the costs. which make the systems economically
feasible.
The system will be socially feasible the workload of staff
will reduce and same staff can work on highly efficient
computerized system after getting training. The system must be
socially feasible from the public point of view, as the system
will offer better services to them.
The availability of the required hardware, system software
and technical manpower makes the system operationally
feasible.
The computerized system will offer high level of record,
which makes the system legally feasible.
A system is technically feasible, if it can be designed and
implemented within the limitations of the available resources
like funds, manpower, hardware, software etc. The proposed
system is technically feasible as the existing staff can be trained
to operate the computerized system and costs involved are
reasonable considering the benefits and future aspects.
RESEARCH DESIGN
Research design is the plain for the study that will lead to the most
economical method for collection of required and their analysis. If the
proposal is property designed most of the unnecessary labor in
collecting non-essential data will be saves.
Exploratory
descriptive
experimental
The present system is exploratory in nature for it seeds to discover
the ideas.
SAMPLE DESIGN
In most of research studies, the amount of the
word is always limited by shortage of time and resources. Within
these limitations, the samples size of past eight months (i.e.-
MAY) is taken for present study.
DATA COLLECTION METHOD
In fact, the data collection is basic step and of
vital importance on which success of failure study depends.
ANALYSIS AND INTERPRETATION OF DATA
The data collection in the aforesaid manner bas been tabulated in
condensed form to draw meaning results. The different techniques are
adopted to analyze the data. An attempt has also been made to prepare
report on the basis of test data.
All the data and material is arranged through
internal resources and last pare of the project consist of conclusions
draw from the report, a brief summary and recommendations and giving
final touch to the report by starting annexes and bibliography.
SOFTWARE QUALITY ASSURANCE PLAN
To ensure that the new system provides high quality final product,
some quality control activities must be performed throughout
development this is because correcting errors in final stages are very
costly. Especially when they originated in early stage the purpose of
software quality assurance plan specify all the activity that are
needed to check the quality of each product it takes the board new of
quality, it is not only interested in the quality of out put but also of
the intermediate product. Because if the requirement and design are
of good quality then the software propose also of good quality. To
check the correctness of the product quality assurance plan use two
processes called verification and validation.
Verification it is the process of determining whether or not the
product phase of the software development fulfill the specification
established during the previous phase this activity include testing
review and proving.
Validation is the process of evaluating software at the end of the
software to ensure compliance with the software requirement.
Testing is the common example of validation.
For this we have to make a software quality assurance table. The
purpose of this document is to decide the quality assurance for the
maintaining the creditor’s ledger. For this purpose all the validation
are check with fake data so that user get the desired output quality
assured certificate is given to this software on the basis of factors i.e.
product operation, transition and revision. These factors include the
following activity i.e. maintainability correctness, reliability,
testability etc this software assure the software cannot be transfer
from one hardware configuration to another system. Cannot be
coupled with other system these factors are easily explained with the
help of quality assurance table.
System Development Life Cycle
Stage key Question Result
1. Recognition of need Preliminary survey /initial
investigation
2. .Feasibility study Evaluation of existing system and
procedures analysis alternative candidate system cost
estimates.
3. Analysis evaluation of present system data collection.
4. Design general design specification detailed design
THE IS TO CERTIFY THAT PROJECT ENTITLED COMPUTER CAREER INSTITUTE EMBODIES THE ORIGINAL WORK DONE BY SHASHANK SINGH IN PARTIAL FULFILLMENT OF THEIR COURSE REQUIREMENT AT THE COMPUTER CAREER INSTITUTE , BRAHMANAND NAGAR COLONY DUGAKUND, VARANASI.
…………………… ..……..………...MR. HEMANT KUMAR CHAUDHARY MR. RAJKUMAR PAL
(EXECUTIVE DIRECTOR) (H.O.D)
C ONCLUSION
This project has been a rewarding experience in more ways than
one. Firstly we have gained an insight into working of the Computer Centre
Automation System. This represents a typical real-word situation.
Secondly, in order to generate the final reports, all the steps of database
designing had to be meticulously following, this has strengthen our
understanding of database design, which we have used in back-end. This
project has been of tremendous help in improving our knowledge of Visual
Basic, which is one of the most efficient tools for designing user interfaces.
The project also introduced us to the concept of database connectivity.
Initially, there were problems with validations, but with the guidance of our
teachers, we were able to important the validations.
Finally, we can appreciate the power of a dbms like MS Access in
managing data and that of Visual Basic in developing easy to handle yet
very efficient user interface. We are now confident of handing such real-life