Mobile PDF

A
Project Report
On
“MOBILE SHOP”
Submitted in partial fulfillment of the requirements for the award of degree

Post Graduate Diploma in Computer Application
From
Pt. Ravishankar Shukla University, Raipur (C.G.)
Year: 2018-19
Guide by: Submitted By:

Mr. Vikas Sharma vidya verma
(Dept.of computer science)
Submitted to
Agrasen Mahavidhyalay, purani basti , Raipur
Pt.RaviShankar Shukla University,Raipur(C.G)
CERTIFICATE OF APPROVAL
This is to certify that the project work entitled “Mobile shop” is carried out by
vidya verma, a student of PGDCA II Sem at Agarsen Mahavidyalaya Purani
Basti is here by approved as a credible work in the degree of Post Graduation
Diploma In Computer Application during the year 2018-19 From Pt.
Ravishankar Shukla University, Raipur (CG).
Mr.Vikas Sharma
H.O.D
(Dept. of Comp. Sci.)
CERTIFICATE
This is to certify that the project work entitled “Mobile shop” Submitted to
the Agarsen Mahavidyalaya by vidya verma,in partial fulfillment for the
requirement relating to nature and standard of the award of Post Graduation
Diploma In Computer Application degree by, Pt. Ravishankar Shukla
University, Raipur (CG) for the academic year
2018-19.This project work has been carried out under my guidance.
(Guide Name)
Mr. Vikas Sharma
Mr. Vaibhav Ingle
CERTIFICATE OF EVALUATION
This is to certify that the project work entitled “Mobile shop” is carried out by
vidya verma, a student of PGDCA II Semester at Agarsen Mahavidyalaya,
after proper evaluation and examination, is hereby approved as a credible
work in the discipline of computer science and is done in a satisfactory
manner for its acceptance as a requisite for the award of Post Graduation
Diploma In Computer Application II Semester during the year 2018-2019
from Pt. Ravishankar Shukla University, Raipur (CG)
Internal Examiner External Examiner

DECLARATION
This is to certify that the project work entitled “Mobile shop” which is
submitted by me in the partial fulfillment for the award of the degree of Post
Graduation Diploma In Computer Application, Agrasen Mahavidyalaya
Purani Basti, comprises the original work carried out by me. I further declare
that the work reported in this project has not been submitted and will not be
submitted, either in part or in full for the award of any other degree or
diploma in this institute or any other institute or University.
Place: Raipur vidya verma
Date: PGDCA II Semester
ACKNOWLEDGEMENT
This project is an inspiration, support, guidance, corporation and
facilities that were extended to us at their best and by person at all
levels. We were indebted to all of them.
We wish to acknowledgement our profound sense of gratitude to
the project guide Mr. Vikas Sharma for their remarkable guidance
and continued encouragement during the development of project. It
was a matter of great felicity and privilege for us to work under the
aegis. We would like to extend our special thanks to (Principal of-
Agrasen Mahavidyalaya Purani Basti) for boosting our confidence
when we were lacking so.
We offer our sincere thanks to Department staff members. Finally we
would also like to thank our entire classmate for their corporation and
support. We would like to pay our everlasting regards to our “Agrasen
Mahavidyalaya Purani Basti” Where this project gets completed.
MAIN REPORT
 OBJECTIVE AND SCOPE OF THE PROJECT

 THEORETICAL BACKGROUND
 DEFINITION OF PROBLEM
 SYSTEM ANALYSIS AND DESIGN
 SYSTEM PLANNING (PERT CHART)
 METHODOLOGY ADOPTED,SYSTEM IMPLEMENTATION &

DETAIL OF HARDWARE AND SOFTWARE USED
 SYSTEM MAINTENANCE AND EVALUATION
 COST AND BENEFIT ANALYSIS
 DETAILED LIFE CYCLE OF THE PROJECT
 ERD, DFD
 INPUT AND OUTPUT SCREEN DESIGN
 PROCESS INVOLVED
 METHODOLOGY USED FOR TESTING
 TEST REPORT
 USER/OPERATIONAL MANUAL-INCLUDING SECURITY
ASPECTS,ACCESS RIGHTS,BACK UP,CONTROLS ETC.
 CONCLUSION
 REFRENCES
OBJECTIVE & SCOPE OF THE PROJECT
This project is made for MOBILE SHOP;this software has been developed for
“MOBILE SHOP”. They wanted to have a system, which will take care of
maintenance of Login,MDIForm,add new mobile,stock,Report etc.. So they can
get whatever information about their problemsthey information to shop presently
their issue. They enter details in manual database. They want computerization of
their system planning.
There is no security; anybody can access any report and sensitive data, also
reports to find out themobile information related to mobile shop. This MOBILE
SHOPovercome the entire problem which they are facing currently, and making
complete of manual of mobile shop.
THEORITICAL BACKGROUND
FRONT END: VISUAL BASIC

Graphical interface user(GUIs) have revolution the microcomputer
industry. They demonstrate that the proverb “a picture is worth a thousand
words” hasn‟t lost its truth instead of the cryptic „c:> prompt that the DOS
users have long seen (and some have long feared), users are presented with a
desktop filled with icon .This provide a visual image of what the computer has to
offer.
Perhaps even more important in the long run then the look of Microsoft
Windows application is spend more time mastering to application and less
time worrying about what key strokes do what within menus and dialogue
boxes.
All this comes at a price, through Visual Basic, developing
windows application was much harder than developing application
programmers had to worry about too much such as what the mouse was doing,
where the user was inside the menu or what he or she was clicking or at a
given place. Developing a window application needed expert „c‟
Programmers, and they have trouble .Visual Basic has changed this situation.
Sophisticated Windows application can now be developed in the fraction of
time previously needed. Programming for windows has become fun (also least
most of the time).And we don‟t have to pay much of a performance
penalty application developed Visual Basic run quickly. This is not so is easy
that we can eliminate c or Assembly language programming for
windows, extending Visual Basic still requires tools that, at present, are available
only in these languages
INTRODUCTION TO VISUAL BASIC:
Microsoft Visual Basic is the quickest and easiest way to create application for
the Microsoft Windows operating system. The Visual Basic programming system
allows the user to create attractive and useful application that fully exploits the
Graphical User Interface(GUIs).
Recognize the action user‟s take events such as mouse movements
and button clicks. Visual Basic also comes with a menu design feature that makes
creating menus a snap.
Only after we design the interface dose anything like traditional
programming occur. Object in Visual Basic will recognize events like mouse
click, how the object respond to them depend upon the code we write. We shall
always need to write code in order to make controls responds to events. This
makes the Visual Basic programming fundamentally different from conversion
programming.
Programming in conversional programming Language run from
top, down. For lower programming language execution start from the first line
and moves with the flow if the program to different part as needed. A
Visual Basic programming works completely differently. The core of a Visual
Basic is a set of independent pieces of code that respond to event that occur in the
interface.
Using Visual Basic, user can create power full, full featured
application that exploits the key feature of the Microsoft Windows
application, including multiple document interface(MDI), object linking
and embedding (OLE), dynamic data exchange(DDE) Graphics and more. And
Visual Basic can be extended by adding custom control by calling procedure in
dynamic link libraries (DDL). The finished application is a true. Exe.file that uses
a run time DDL we can free distrust.
HOW TO DEVELOP A VISUAL BASIC APPLICATION
The first step in developing a Visual Basic application is to plan what the user
sees-in other, to design the screens Microsoft Windows application live in
windows that share on the user‟s screen, the application has menus, command
button, place to enter text, and so on, the objects are controls in Visual Basic.
What makes Visual Basic different from all other programming
tools for windows is the ease with
Which we can design the screen. We literally draw the user interface,
much like using a paint program in addition, when you are drawing the interface,
the command button, text boxes and other controls we have placed in a blank
window will automatically recognize the action users take-events such as design
feature that makes creating menus a snap.
Only after we design the interface dose anything like traditional
programming occur object in Visual Basic will recognize the events like mouse
click, how the objects respond to them depends upon the code we write. Will
always need to write the code in order to make controls responds to events. This
make Visual Basic programming fundamentally different from the conversional
programming.
CREATING VISUAL BASIC APPLICATION
There are three steps to creating application for windows in Visual Basic
1. create the interface
2. set properties
3. write the code
WHAT HAPPENS WHEN THE APPLICATION RUNNING
1. Visual Basic monitors the window and the control in each window can
recognize(mouse movement clicks, key strokes, and so on).
2. When Visual Basic defects an event, it examine the application to see it we
have written an event produce for event.
3. If we have written an event procedure, visual basic executes the code that
makes up the event procedure and goes back to step1.
4. If we have not written an event procedure, visual basic waits for the next
events and goes back to step1.
CONTROLS
A control is an object that you draw on a from to enable or enhance user

interaction with an application. You add menu control to a form using windows.
All other controls appear the tools box and are placed on a form by double
clicking them or by clicking and then dragging them on a form.
Controls accept user input or display output. controls have properties
that define aspects of their appearance, such as position, size, colour and aspects
of their behaviour, such as how they respond to user input.
Controls can respond to events initiated by the user or
triggered by the system. For example you procedure that would load a file or
perform a calculate and then display the result.
Frame : provide a functional grouping and container for Other controls.
Grid : provide a matrix of spread sheet – typical whose Contents can be
manipulated in code. Grid a custom control supplied with Visual Basic.
Image : display a bit map, icon or metafile as graphic.
Label : display text which user can‟t change.
Line : display itself as a horizontal, vertical or a diagonal line .
List box : display a list from which user can select one or More items.
Menu : display a menu in a form.
Ole control : allow a programmer to create that can display and editing of data
from many different application for example, object created by, draw, graphics,
and spread sheet application can be edited with an application in which it was
created.
Picture box : display graph that are drawn with circle line and print method, or
that are loaded from bit map, icon or metafile can also act as a container form.
Other controls ?
Option button as part of a group of option button display multiple choices from
which the user can select only one.
Shape Display itself a variety of shapes including boxes, circles and
soon.
Text box Display text the user can edit.
Timer Enable you to run code at a specified time interval.
Horizontal Allow navigation through list or forms also
Scroll can indicate bar position in range.
The open database connectively (ODBC) facility makes the VISUAL BASIC
more powerful. It is user or connects to external database from the VISUAL
BASIC. The ODBC is used to connect to Microsoft SQL and ORACLE database
management system
.
DATA ACCESS SOURCE
VISUAL BASIC enables the programmer to manipulate the data and underlying
data structure of many types of database application. For example the
programmers can use Microsoft access to create and manage a database that his
VISUAL BASIC can manipulate. In the same way, he can create database in
visual basic that Microsoft access can manage. Visual basic also provides access
to several other popular database formats. There are three categories of database
that visual basic recognizes.
1. Microsoft Access – format database: there database files are manipulated with
visual basic or Microsoft Access. This is the visual basic native format it provide
the most flexibility and speed.
2.External database – this category includes database formats such as Dbase
III, Dbase IV, Microsoft FoxPro, Paradox. The programmer can create or
manipulate all of these database formats in VISUAL BASIC.
3. External ODBC database : this category includes Client / server database such
as Microsoft SQL Server And Oracle database management system. In the case
Of ODBC database, the programmer can pass SQL Commands directly to the
external server for process-ing.
ALTERNATIVES TO VISUAL BASIC DATA OBJECTS
Data objects are not the only means the programmer use to manipulate data from
the visual basic. He has access to following source:
 Sequentially, Random, and PRINT & PUT allow him to directly
manipulate these types of files.
 Visual Basic SQL Libraries (VBSQL) for Microsoft SQL Server VBSQL
provides a direct link to the C language application programming
interface(API) to DB-library function.
 You can use this API to communicate directly with Microsoft SQL Server.
 ODBC Libraries: It also possible to develop application that calls OBDC
API directly. Although this method is more complex to implement, it
provide a closer link between the application and the ODBC host than
using data objects.
ABOUT THE BACK-END
MICROSOFT ACCESS
All the business application need to store a large volume of data organized in a
format that simplifies retrieval. This is accomplished with Data Base
Management System (DBMS) , a machine for manipulating data with high level
details , such as how data are stored in a database , and free the programmer to
concentrate files or managing links over them.
There are several databases like dbase, Oracle, Sybase etc. Amongst small
database, MS ACCESS is more widely used. MS ACCESS which is a powerful
window base Relational Database Management System (RDBMS) that can be
used to create and maintain small database.
Index and Primary Key
Index is used to maintain the order of records. They are used uniquely
identify records. Primary key is gently a number or an ID or number i.e. unique
for unique records. That meets the primary key value cannot be repeated in the
table. MS ACCESS maintains the records in primary key order.
Relationship
Most of the time we would not pull the information in the table. More
fields and information in a table, more difficult to with. So the information is
divided into different table and then these tables are linked. Relationship helps
the deletion, updating and insertion.
Types of relationship
There are basically there types or relation
1. One to one 2. One to Many 3. Many to many.
DEFINITION OF PROBLEM
DEFINITION OF PROBLEM
Before a project can begin, there has to be a reason why it should take place.
You have to define the problem that the system is meant to be overcome.
This phase is called the 'Problem definition phase'.
Some formal effort is made to define exactly what is the problem.For example
the following statements may appear in the Problem Definition.
...The existing system cannot transfer data to the new invoice system ...
...Staff have to spend three hours loading information...
... New legislation insist that financial records are kept for this department
And so on.
Methods of defining a problem:
Interview employees about their issues with the current system

Analysing the total costs of the current system
Key external factors that may point towards developing a new system.
Performance of the existing system.
Once the problem definition stage is over, then if the decision is to carry on with
the project the next phase is the 'Feasibility Study'.
System Analysis And Design
SYSTEM ANALYSIS
System analysis is the process of gathering and interpreting facts, diagnosing

problems and using the information to recommend improvement to the system.
System analysis refers to the process of examining a business situation with the
intent of improving it through better procedures and methods. System analysis is
a management technique, which helps us in designing a new system or improving
an existing system.
The analysis model must achieve three primary objectives: -

1 The functions that the software is to perform must be defined.
2 The information domain of a problem must be represented and
understood.
3 The behaviour of the software (as a consequence of external events) must
IDENTIFICATION OF NEEDS:
The first step of system analysis process involves the identification of

need. The system analyst (system engineer) meets with the customer & the end-
users (if different from the customer). Identification of need is the starting point
in the evolution of a computer-based system.
The need of the new system is those features or details that must be
incorporated to produced the improvements in the existing system. In other
words, they are theactivities or improvements that the new system must provide.
They are determined by comparing current performance with the objectives for
acceptable systems performance.
1 The analyst assists the customer on defining the goals of the system:
2 What information is to be consumed i.e. identifying inputs. What functions
and transformations are required?
3 What information will be produced i.e. identifying outputs.
Preliminary Investigation:
The first step in the system development life cycle is the preliminary
investigation to determine the feasibility of the system. In this kind of
investigation we evaluate project requests. In this we collect information that
helps the management to evaluate the merits of the project request and make
an informed judgment about the feasibility of the proposed project.
This investigation accomplished the objectives, which are as

follows:
1 Clarify and understand the project request.
2 Determine the size of the project.
3 Determine the technical and operational feasibility of alternative
approaches.
We gathered data through three primary methods:
1 Reviewing organization documents
2 On-site observations
3 Conducting interviews
 Reviewing organization documents:
We first learn about the organization involved in, or affected by the
project. In this project, very first We get to know how the department
works and who are the persons directly associated with distribution system.
As some other software was maintaining the proposed system, literature
relating to this system in the forms of various reports was available for
analysis.
On-site observations:
It is the process of recognizing and noting people, objects and occurrences
to obtain the information. The major objective of on site observation is to
get close as possible to real system. The information about the present
workflow, objects, people involved were gathered in this way. The
physical layout of current system, the location and movement of people
/staff were analyzed.
For collecting data, we did on-site observation. In this, we observe the
activities of system directly. Our purpose of on-site observation was to get
as chose as possible to the real system being studied. During on-site
observation, we see the office environment, work load of the system and
the users, methods of work and the facilities provided by the organization
to the users, which can help the developer to understand the processes and
procedures in development of new system.
PROBLEM ANALYSIS
A complete understanding of the software requirement is essential to the success
of software development efforts. The requirement analysis is a process of
requirement anticipation, requirement specification.
Requirement analysis is done in order to understand the problem, which the
software is to solve. The emphasis is on identifying what is needed from the
system and how the system will achieve its goals.
Requirement analysis provides the software designers with a representation of
information and function that can be translated to data, architectural and
procedural design. Finally, the requirement specificationprovides the developer
and the customer with the means to access quality once the software is built.
Software requirement analysis may be divided into 5 areas of effort:
 Problem recognition/definition.
 Evaluating and synthesis.
 Modelling.
 Specification.
 Review.
The following are the ways of requirement analysis:
 Structuring information.
 Data flow diagram and data dictionary.
Structured analysis
Proposed System
The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system. The
system provides proper security and reduces the manual work.
 Security of data.
 Ensure data accuracy’s.
 Proper control of the higher officials.
 Minimize manual data entry.
 Minimum time needed for the various processing.
 Greater efficiency.
 Better service.
 User friendliness and interactive.
 Minimum time required.

FEASIBILITY STUDY
Feasibility study is made to see if the project on completion will serve the
purpose of the organization for the amount of work, effort and the time that spend
on it. Feasibility study lets the developer foresee the future of the project and the
usefulness. A feasibility study of a system proposal is according to its
workability, which is the impact on the organization, ability to meet their user
needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.
The document provide the feasibility of the project that is being designed
and lists various areas that were considered very carefully during
the feasibility study of this project such as Technical, Economic and
Operational feasibilities. The following are its features:
A. TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The
assessment of this feasibility must be based on an outline design of the
system requirement in the terms of input, output, programs and procedures.
Having identified an outline system, the investigation must go on to
suggest the type of equipment, required method developing the system, of
running the system once it has been designed.
Technical issues raised during the investigation are:
 Does the existing technology sufficient for the suggested one?
 Can the system expand if developed?

The project should be developed such that the necessary functions and
performance are achieved within the constraints. The project is developed
within latest technology. Through the technology may become obsolete
after some period of time, due to the fact that never version of same
software supports older versions, the system may still be used. So there are
minimal constraints involved with this project. Thesystem has been
developed using Java the project is technically feasible for development.
B. ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. Criteria to
ensure that effort is concentrated on project, which will give best, return at
the earliest. One of the factors, which affect the development of a new
system, is the cost it would require.
The following are some of the important financial questions asked
during preliminary investigation:
 The costs conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
Since the system is developed as part of project work, there is no
manual cost to spend for the proposed system. Also all the resources are
already available, it give an indication of the system is economically
possible for development.
C. BEHAVIORAL FEASIBILITY
This includes the following questions:
 Is there sufficient support for the users?
The project would be beneficial because it satisfies the objectives when
developed and installed. All behavioral aspects are considered carefully
and conclude that the project is behaviorally feasible.
5.3 SYSTEM DESIGN
INTRODUCTION
The first step in phase of any engineered product, design is defined as the process
of applying various techniques and principles for the purpose of defining a
device, a process or a system in sufficient details to permit it to realize physically.
After the definition phase, in which software requirements are analyzed and
specified, software design first of three technique activity designing, coding and
testing in the development of the software.
The design activity is one of the main important phases, because in this activity
decision ultimately affecting the success of software implementation and its ease
of maintenance are made. The decisions have the final bearing upon
“RELIABILITY” and “MAINTAINABILITY” of the system.
Software design is conducted in two steps:
 Preliminary design.
 Detailed design.
PRELIMINARY DESIGN
Preliminary design is concerned with transformation of the requirements into data
and software architecture. Detailed design focuses on the refinements to the
architecture representations that lead to detailed “DATA STRUCTURE” and
“ALGORITHM” for the software.
SYSTEM DESIGN
In system design, the focus is on deciding which modules are needed for the
system; the specifications of these modules and how many modules should be
interconnected. Finally system design document is prepared.
DETAILED DESIGN
In detailed design, the internal design of the module, or how the specification of
the module can be satisfied is decided.
Some properties for a software system design are:

 Verifiability.
 Completeness.
 Consistency.
 Tractability.
Simplicity/understand ability
DATABASE DESIGN
A database is an organized mechanism that has the capability of storing

information through which a user can retrieve stored information in an effective
and efficient manner. The data is the purpose of any database and must be
protected.The database design is a two level process. In the first step, user
requirements are gathered together and a database is designed which will meet
these requirements as clearly as possible. This step is called Information Level
Design and it is taken independent of any individual DBMS.
In the second step, this Information level design is transferred into a design
for the specific DBMS that will be used to implement the system in question.
This step is called Physical Level Design, concerned with the characteristics of
the specific DBMS that will be used. A database design runs parallel with the
system design. The organization of the data in the database is aimed to achieve
the following two major objectives.
 Data Integrity
 Data independence
Normalization is the process of decomposing the attributes in an application,
which results in a set of tables with very simple structure. The purpose of
normalization is to make tables as simple as possible. Normalization is carried
out in this system for the following reasons.
 To structure the data so that there is no repetition of data , this helps in saving.
 To permit simple retrieval of data in response to query and report request.
 To simplify the maintenance of the data through updates, insertions, deletions.
 To reduce the need to restructure or reorganize data which new application
requirements arise.
RELATIONALDATABASEMANAGEMENT SYSTEM
(RDBMS):
A relational model represents the database as a collection of relations. Each
relation resembles a table of values or file of records. In formal relational model
terminology, a row is called a tuple, a column header is called an attribute and
the table is called a relation. A relational database consists of a collection of
tables, each of which is assigned a unique name. A row in a tale represents a set
of related values.
RELATIONS, DOMAINS & ATTRIBUTES:
 A table is a relation. The rows in a table are called tuples. A tuple is an
ordered set of n elements. Columns are referred to as attributes. Relationships
have been set between every table in the database. This ensures both
Referential and Entity Relationship Integrity. A domain D is a set of atomic
values. A common method of specifying a domain is to specify a data type from
which the data values forming the domain are drawn. It is also useful to specify
a name for the domain to help in interpreting its values. Every value in a relation
is atomic, that is not decomposable.
 RELATIONSHIPS:
Table relationships are established using Key. The two main keys of prime
importance are Primary Key & Foreign Key. Entity Integrity and Referential
Integrity Relationships can be established with these keys. Entity Integrity
enforces that no Primary Key can have null values. Referential Integrity enforces
that no Primary Key can have null values.
 Referential Integrity for each distinct Foreign Key value, there must exist
a matching Primary Key value in the same domain. Other key are Super Key and
Candidate Keys.
 Relationships have been set between every table in the database. This
ensures both Referential and Entity Relationship Integrity.
NORMALIZATION:
As the name implies, it denoted putting things in the normal form. The
application developer via normalization tries to achieve a sensible organization
of data into proper tables and columns and where names can be easily correlated
to the data by the user. Normalization eliminates repeating groups at data and
thereby avoids data redundancy which proves to be a great burden on the
computer resources. These includes:
 Normalize the data.

 Choose proper names for the tables and columns.
 Choose the proper name for the data.
First Normal Form:

The First Normal Form states that the domain of an attribute must include only
atomic values and that the value of any attribute in a tuple must be a single value
from the domain of that attribute. In other words 1NF disallows “relations within
relations” or “relations as attribute values within tuples”. The only attribute
values permitted by 1NF are single atomic or indivisible values.
The first step is to put the data into First Normal Form. This can be donor by
moving data into separate tables where the data is of similar type in each table.
Each table is given a Primary Key or Foreign Key as per requirement of the
project. In this we form new relations for each nonatomic attribute or nested
relation. This eliminated repeating groups of data. A relation is said to be in first
normal form if only if it satisfies the constraints that contain the primary key
only.
Second Normal Form:
According to Second Normal Form, For relations where primary key contains
multiple attributes, no nonkey attribute should be functionally dependent on a
part of the primary key.
In this we decompose and setup a new relation for each partial key with its
dependent attributes. Make sure to keep a relation with the original primary key
and any attributes that are fully functionally dependent on it. This step helps in
taking out data that is only dependant on apart of the key.
A relation is said to be in second normal form if and only if it satisfies all the
first normal form conditions for the primary key and every non-primary key
attributes of the relation is fully dependent on its primary key alone.
Third Normal Form:
According to Third Normal Form, Relation should not have a nonkey attribute
functionally determined by another nonkey attribute or by a set ofnonkey
attributes. That is, there should be no transitive dependency on the primary key.In
this we decompose and set up relation that includes the nonkey attributes that
functionally determines other nonkey attributes. This step is taken to get rid of
anything that does not depend entirely on the Primary Key.
A relation is said to be in third normal form if only if it is in second normal
form and more over the non key attributes of the relation should not be depend
on other non key attribute.
The collection of data is usually referred to a database. The database contains the
information about one particular enterprise. Database system of data involves
both the definition of the structure of information, processing and mechanism for
manipulation of the information. In addition the database system provides for the
safety of information stored in the database despite system crashes or attempts of
unauthorized access.
It includes two topics: -
Table Structure
Relationship between Tables
METHODOLOGY USED FOR TESTING
TESTING
Introduction:
In software development project errors can be injected at any stage during
development. For each stage different techniques for detecting and eliminating
errors is followed. The code developed during the coding activity likely to have
some requirement errors and design errors, in addition to the error introduced
during the coding activity. Hence testing performs a very crucial role for quality
assurance and for ensuring reliability for the software.
During testing the, the program to be tested is executed with a set of test cases,
and the output of the program is evaluated to determine if the is performing
expected. Due to this approach the dynamic testing can only ascertain the
presence of errors in the program, the exact nature of the error is not usually
decided by testing. Testing performs the first step in determining the errors in a
program. The success of testing depends on the test case.
Incremental Testing
Testing large system is a complex activity, and like any other activity it has to be
broken into smaller activities. Due to this, for a project incrementaltesting is
generally performed, in which components of and subsystems of the systems are
tested separately before integrating them to from the system testing.
Unit Testing
Unit testing is normally considered as an adjunct to the coding step. After source
level code has been developed, reviewed, and verified for correct syntax, unit
testing begins. A review of design information provides guidance for establishing
test cases that are likely to uncover errors in each of the categories.
Integration Testing
A question arrives that if all modules have been tested then what will happen
when they work together. The problem is of putting them together i.e.
interfacing. Data can be loosed across an interface, one, module can have an
inadvertent, adverse affect on another. Some functions when combine may not
produce the desire major function.
Regression Testing
Each time new module is added as a part of integration testing, them software
changes. New data flow paths are established. New I/O may occur and new
control logic is invoked. Regression testing is the re-execution of some subsets of
tests that have already been conducted to ensure that changes have not
propagated side effects.
TABLE STRUCTURE
In the System, there are total 9 tables to be used under one database file for
storing data. Tables names are listed below:-
Following tables are created:-
 Question Table
 Students Table
 Data Dictionary
Brief descriptions of above 6 tables are as follow:-Project“Shoe Billing
System"
PERT CHART
PERT
Complex projects require a series of activities, some of which must be
performed sequentially and others that can be performed in parallel with other
activities. This collection of series and parallel tasks can be modeled as a
network.
In 1957 the Critical Path Method (CPM) was developed as a network model for
project management. CPM is a deterministic method that uses a fixed time
estimate for each activity. While CPM is easy to understand and use, it does not
consider the time variations that can have a great impact on the completion time
of a complex project.
The Program Evaluation and Review Technique (PERT) is a network model that
allows for randomness in activity completion times. PERT was developed in the
late 1950's for the U.S. Navy's Polaris project having thousands of contractors. It
has the potential to reduce both the time and cost required to complete a project
The Network Diagram

In a project, an activity is a task that must be performed and an event is a
milestone marking the completion of one or more activities. Before an activity
can begin, all of its predecessor activities must be completed. Project network
models represent activities and milestones by arcs and nodes. PERT originally
was an activity on arc network, in which the activities are represented on the
lines and milestones on the nodes. Over time, some people began to use PERT as
an activity on node network. For this discussion, we will use the original form of
activity on arc.
The PERT chart may have multiple pages with many sub-tasks. The following
is a very simple example of a PERT diagram:
PERT CHART
The milestones generally are numbered so that the ending node of an activity
has a higher number than the beginning node. Incrementing the numbers by 10
allows for new ones to be inserted without modifying the numbering of the entire
diagram. The activities in the above diagram are labeled with letters along with
the expected time required to complete the activity.
Steps in the PERT Planning Process

PERT planning involves the following steps:
1. Identify the specific activities and milestones.
2. Determine the proper sequence of the activities.
3. Construct a network diagram.
4. Estimate the time required for each activity.
5. Determine the critical path.
6. Update the PERT chart as the project progresses.
1. Identify Activities and Milestones

The activities are the tasks required to complete the project. The milestones
are the events marking the beginning and end of one or more activities. It is
helpful to list the tasks in a table that in later steps can be expanded to include
information on sequence and duration.
2. Determine Activity Sequence

This step may be combined with the activity identification step since the
activity sequence is evident for some tasks. Other tasks may require more
analysis to determine the exact order in which they must be performed.
3. Construct the Network Diagram

Using the activity sequence information, a network diagram can be drawn
showing the sequence of the serial and parallel activities. For the original
activity-on-arc model, the activities are depicted by arrowed lines and milestones
are depicted by circles or "bubbles".
If done manually, several drafts may be required to correctly portray the

relationships among activities. Software packages simplify this step by
automatically converting tabular activity information into a network diagram.
4. Estimate Activity Times

Weeks are a commonly used unit of time for activity completion, but any
consistent unit of time can be used.
A distinguishing feature of PERT is its ability to deal with uncertainty in activity

completion times. For each activity, the model usually includes three time
estimates:
 Optimistic time - generally the shortest time in which the activity

can be completed. It is common practice to specify optimistic times to be
three standard deviations from the mean so that there is approximately a
1% chance that the activity will be completed within the optimistic time.
 Most likely time - the completion time having the highest
probability. Note that this time is different from the expected time.
 Pessimistic time - the longest time that an activity might require.
Three standard deviations from the mean is commonly used for the
pessimistic time.
PERT assumes a beta probability distribution for the time estimates. For a beta
distribution, the expected time for each activity can be approximated using the
following weighted average:
Expected time = ( Optimistic + 4 x Most likely + Pessimistic ) / 6
This expected time may be displayed on the network diagram.
To calculate the variance for each activity completion time, if three standard
deviation times were selected for the optimistic and pessimistic times, then there
are six standard deviations between them, so the variance is given by:
[ ( Pessimistic - Optimistic ) / 6 ]2
5. Determine the Critical Path

The critical path is determined by adding the times for the activities in each
sequence and determining the longest path in the project. The critical path
determines the total calendar time required for the project. If activities outside the
critical path speed up or slow down (within limits), the total project time does not
change. The amount of time that a non-critical path activity can be delayed
without delaying the project is referred to as slack time.
If the critical path is not immediately obvious, it may be helpful to determine the
following four quantities for each activity:
 ES - Earliest Start time

 EF - Earliest Finish time
 LS - Latest Start time
 LF - Latest Finish time
These times are calculated using the expected time for the relevant activities.
The earliest start and finish times of each activity are determined by working
forward through the network and determining the earliest time at which an
activity can start and finish considering its predecessor activities. The latest start
and finish times are the latest times that an activity can start and finish without
delaying the project. LS and LF are found by working backward through the
network. The difference in the latest and earliest finish of each activity is that
activity's slack. The critical path then is the path through the network in which
none of the activities have slack.
The variance in the project completion time can be calculated by summing the
variances in the completion times of the activities in the critical path. Given this
variance, one can calculate the probability that the project will be completed by a
certain date assuming a normal probability distribution for the critical path. The
normal distribution assumption holds if the number of activities in the path is
large enough for the central limit theorem to be applied.
Since the critical path determines the completion date of the project, the
project can be accelerated by adding the resources required to decrease the time
for the activities in the critical path. Such a shortening of the project sometimes is
referred to as project crashing.
6. Update as Project Progresses

Make adjustments in the PERT chart as the project progresses. As the project
unfolds, the estimated times can be replaced with actual times. In cases where
there are delays, additional resources may be needed to stay on schedule and the
PERT chart may be modified to reflect the new situation.
Benefits of PERT
PERT is useful because it provides the following information:
 Expected project completion time.

 Probability of completion before a specified date.
 The critical path activities that directly impact the completion time.
 The activities that have slack time and that can lend resources to
critical path activities.
 Activity start and end dates.
Limitations
The following are some of PERT's weaknesses:
 The activity time estimates are somewhat subjective and depend on

judgement. In cases where there is little experience in performing an
activity, the numbers may be only a guess. In other cases, if the person or
group performing the activity estimates the time there may be bias in the
estimate.
 Even if the activity times are well-estimated, PERT assumes a beta
distribution for these time estimates, but the actual distribution may be
different.
 Even if the beta distribution assumption holds, PERT assumes that the
probability distribution of the project completion time is the same as the
that of the critical path. Because other paths can become the critical path if
their associated activities are delayed, PERT consistently underestimates
the expected project completion time.
The underestimation of the project completion time due to alternate paths

becoming critical is perhaps the most serious of these issues. To overcome to
eliminate this optimistic bias in the expected project completion tim
Methodology Adopted, System
Implementation & Detail of
Hardware & Software used
Methodology Adopted
Project management in the modern sense began in the early 1950s, driven by
businesses that realised the benefits of organising work around projects, and the
critical need to communicate and co-ordinate work across departments and
professions.
Project management is no small task. It has a definite beginning and end, and
is not a continuous process. Project management uses various tools to measure
progress and track project tasks. Projects need ad-hoc resources, as opposed to
businesses that have dedicated full-time positions.
Project management methodologies consist of four to five process groups, and
a control system. Regardless of the methodology or terminology used, project
management uses the same basic processes. Process groups typically include:
1. Initiation
2. Planning and Design
3. Execution
4. Monitoring and Controlling
5. Closing
1. Initiation
All projects start with an idea for a product, service, or other desirable outcome.
The initiation process group determines the nature and scope of the project. If this
stage is not performed well, it is unlikely the project will be successful in meeting
the businesses needs. The key project controls needed, are an understanding of
the business environment and making sure all necessary controls are incorporated
into the project. Any deficiencies should be reported and a recommendation made
to fix them.
The first project document is the project charter, which includes:
 Business case
 Scope and deliverables
 Objectives
 Resources needed
 Milestone plan and timeline
 Cost estimate
 Risks and issues
 Dependencies
The charter answers the basic question, "What are we trying to do?"
2. Planning and Design
After initiation, the project is planned to an appropriate level of detail. The main
purpose is to plan time, cost and resources adequately to estimate the work
needed and to manage risk effectively during project execution. This is recorded
in the project management plan. As with the initiation process group, a failure to
plan adequately lessens the project's chances of success.
Project planning includes:
 Developing the scope statement

 Developing the schedule (Gantt chart)
 Developing the budget
 Selecting the team
 Creating a work breakdown structure
 Identifying deliverables
 Risk planning
 Communication planning
This information forms the project contract, used to gain formal approval to
begin work.
3. Execution
Execution consists of the processes used to complete the work defined in the
project management plan, to accomplish the project's objectives. The execution
process involves co-ordinating people and resources, as well as integrating and
performing the activities of the project. The deliverables are produced as outputs
from the processes performed as defined in the project management plan.
4. Monitoring and Controlling
The monitoring and controlling process group involves managing and tracking
the project, so potential problems can be identified quickly and corrective action
taken. To do this the project management plan is used. Monitoring and
controlling includes:
 Measuring the ongoing project activities (where are we, against where we
should be?)
 Monitoring the project variables (cost, effort, scope) against the project
management plan and the project baseline (where should we be?)
 Identifying corrective actions to address risks and issues (how can we get
back on track?)
 Managing changes using our change control process (what is the impact of
this change?)
The monitoring and controlling process group ends once the project has
achieved its goals and objectives as detailed in the project contract. A project
may be stopped before completion for various reasons, including changes in the
business, lack of resources or higher priorities.
5. Closing
Project closing is an important part of project management, sometimes
overlooked. A project that is not closed will continue to consume resources.
Closing a project means finishing all activities across all process groups,
splitting up the project team, and signing off the project with the customer.
At this point it is important to know how well the project has performed. This
is done using the project closure report. It communicates how well the project has
performed against its original business case, quality measures, cost, duration and
tolerances.
Rather than leave valuable project experiences locked in peoples heads, it's a
good idea to complete and publish a lessons learned report. This is used to pass
on valuable learning that can be applied to future projects.
Project Control
Project control is that part of a project that keeps it on-track, on-time and within
budget. Project control begins early in the project with planning, and ends late in
the project with post-implementation review.
Projects should be assessed for the right level of control needed: too much
control is time-consuming, too little control is risky. If project control is not
carried out correctly, the cost to the business should be clarified in terms of
errors, fixes and added costs.
Typical elements of project control are:
 Overall business strategy
 Standards for new systems
 Project management policies
 Change management
 Quality control
SYSTEM SPECIFICATION
HARDWARE REQUIREMENTS
Processor : X86 Compatible processor

with 1.7 GHz Clock speed
RAM : 512 MB or more
Hard disk : 20 GB or more
Monitor : VGA/SVGA
Keyboard : 104 Keys
Mouse : 2 buttons/ 3 buttons
SOFTWARE REQUIREMENTS
Operating System : Windows 2000/XP

Front end : Visual Basic 6.0
Back end : MS ACCESS
SYSTEM EVALUTION
& MAINTANANCE
SYSTEM EVALUATION
During system testing, the system is used experimentally to ensure that the
software does not fail. In other words, we can say that, it will run according to its
specifications and in the way user expects. Special test data are inputs for
processing, and the results examined. A limited number of users may be allowed
to use the system,
So those, analyst can see whether to use it in unforeseen ways. It is desirable to
discover any surprises before the organization implements the system and
depends on it.
Implementation is the process of having systems personnel check out and put
new equipment into use, train users, install the new application and construct any
files of data needed to use it. This phase is less creative than system design.
Depending on the size of the organization that will be involved in using the
application and the risk involved in its use, system developers may choose to test
the
Operation in only one area of the firm with only one or two persons. Sometimes,
they will run both old and new system in parallel way to compare the results.
Evaluation of the system is performed to identify its strength and weaknesses.
The actual evaluation can occur along any one of the following dimensions:
Operational Evaluation:
Assessment of the manner in which the system functions.
Organizational Impact:
Identification and measurement of benefits to the organization in
such areas as financial concerns, Operational efficiency and competitive impact.
User Manager Asses:
Evaluation of the attitudes of senior manager and user within the
organization, as well as end users.
Development Performance:
Evaluation of the development process in accordance with such
yardsticks as overall development time and effort, conformance to budgets and
their standards and other project management criteria.
SYSTEM MAINTENANCE
Maintenance is necessary to eliminate errors in the working system during its

working life and to tune the system to any variations in its working environment.
Often small system deficiencies are found, as a system is brought into operation
and changes are made to remove
them. System planners must always plan for resource availability to carry out
these maintenance functions. The importance of maintenance is to continue to
bring the new system to standards.
Like any system, there is an ageing process in software that requires periodic
maintenance of hardware and software. If the new information is inconsistent
with design specification, then changes
Have to be made. Hardware also requires periodic maintenance to be in tune
with design specifications.
COST / BENEFIT
ANALYSIS
Cost/Benefit Analysis
Cost/benefit analysis is performed to ascertain, whether the costs in the system
match with the benefits it will provide. The various kinds of costs incurred in the
development and implementation of the system include:
 Hardware Costs incurred in purchase of hardware, i.e. computer and its
peripherals.
 Personnel Costs include the salaries of the EDP staff, as well as the perks of
personnel involved in the development of the system.
 Facility Costs include expenses incurred in the preparation of the physical

site. This includes flooring, wiring, lighting, etc.
 Operating costs include all costs associated with the day to day operations of
the system.
 Supply costs include variable costs that increase with increased use of paper,
ribbon, disks, etc.
The system is also expected to provide benefits. The first task is to identify each
benefit and then assign a monetary value to it for cost/benefit analysis. Benefits
may be tangible or intangible, fixed or variable, direct or indirect.
Since cost plays quite an important role in deciding the new system, it must be
identified and estimated properly. Costs vary by type and consist of various
distinct elements. Benefits are also of different types and can be grouped on the
basis of advantages they provide to the management .The benefits of a project
include four types:
I. Cost-Saving benefits
II. Cost-avoidance benefits
III. Improved-service-level benefit
IV. IV. Improved-information benefits
Cost-Saving benefits lead to reduction in administrative and operational costs. A
reduction in the size of the clerical, staff used in the support of an administrative
activity is an example of a cost saving benefit.
Cost-avoidance benefits are those, which eliminate future administrating and

operational costs. No need to hire additional staff in future to handle an
administrative activity is an example of cost-avoidance benefit.
Improved-service-level benefits are those, where the performance of a system is

improved by a new computer-based method.
Improved-information-benefit is where computer based methods lead to better

information for decision-making. For example, a system that reports the most-
improved fifty customers as measured by an increase in sales is an improved-
information. This information makes it easier to provide better service to major
customers.
CATEGORIES OF COSTS AND BENEFITS
The costs associated with the system are expenses, outlays or losses arising from
development and using a system. But the benefits are the advantages received
from installing and using this system.
Costs and Benefits can be classified as follows:
a) Tangible or intangible
b) Fixed or variable
c) Direct or indirect
TANGIBLE OR INTANGIBLE
Tangibility refers to the ease with which costs or benefits can be measured. An
outlay of cash for any specific item or activity is referred to as a tangible cost.
Costs that are known to exist but their financial value cannot be exactly
measured, are referred to as an intangible costs.
DIRECT OR INDIRECT COSTS AND BENEFIT
Direct costs are those which are directly associated with a system. They are
applied directly to the operator.Indirect costs are not directly associated with a
specific activityIn the system. They are often referred to as overhead expenses.
FIXED OR VARIABLE COSTS AND BENEFITS
Fixed costs are considered as sunk costs. Once encountered, They will not occur
Variable costs are incurred on a regular basis.
DETAILED LIFE SYCLE OF PROJECT

Systems development life-cycle
The SDLC is a process used by a systems analyst to develop an information
system, including requirements, validation, training, and user (stakeholder)
ownership. Any SDLC should result in a high quality system that meets or
exceeds customer expectations, reaches completion within time and cost
estimates, works effectively and efficiently in the current and planned
Information Technologyinfrastructure, and is inexpensive to maintain and cost-
effective to enhance.[2] Computer systems are complex and often (especially with
the recent rise of service-oriented architecture) link multiple traditional systems
potentially supplied by different software vendors. To manage this level of
complexity, a number of SDLC models or methodologies have been created, such
as "waterfall"; "spiral"; "Agile software development"; "rapid prototyping";
"incremental"; and "synchronize and stabilize".
SDLC models can be described along a spectrum of agile to iterative to

sequential. Agile methodologies, such as XP and Scrum, focus on lightweight
processes which allow for rapid changes 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 iterations 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
requirements".[4]
History
The systems life cycle (SLC) is a methodology used to describe the process for
building information systems, intended to develop information systems in a very
deliberate, structured and methodical way, reiterating each stage of the life cycle.
The systems development life cycle, according to Elliott & Strachan & Radford
(2004), "originated in the 1960s,to develop large scale functional business
systems in an age of large scale business conglomerates. Information systems
activities revolved around heavy data processing and number crunching routines".
Several systems development frameworks have been partly based on SDLC, such
as the structured systems analysis and design method (SSADM) produced for the
UK government Office of Government Commerce in the 1980s. Ever since,
according to Elliott (2004), "the traditional life cycle approaches to systems
development have been increasingly replaced with alternative approaches and
frameworks, which attempted to overcome some of the inherent deficiencies of
the traditional SDLC".
Systems development phases
This section needs additional citations for verification. Please help improve this
article by adding citations to reliable sources. Unsourced material may be
challenged and removed. (September 2010)
The System Development Life Cycle framework provides a sequence of activities

for system designers and developers to follow. It consists of a set of steps or
phases in which each phase of the SDLC uses the results of the previous one.
Model of the Systems Development Life Cycle
The systems development life cycle (SDLC), or software development life cycle
in systems engineering, information systems and software engineering, is a
process of creating or altering information systems, and the models and
methodologies that people use to develop these systems.
In software engineering the SDLC concept underpins many kinds of software

development methodologies. These methodologies form the framework for
planning and controlling the creation of an information system[1]: the software
development process.
 Project planning, feasibility study: Establishes a high-level view of the

intended project and determines its goals.
 Systems analysis, requirements definition: Defines project goals into

defined functions and operation of the intended application. Analyzes end-
user information needs.
 Systems design: Describes desired features and operations in detail, including

screen layouts, business rules, process diagrams, pseudocode and other
documentation.
 Implementation: The real code is written here.
 Integration and testing: Brings all the pieces together into a special testing
environment, then checks for errors, bugs and interoperability.
 Acceptance, installation, deployment: The final stage of initial

development, where the software is put into production and runs actual
business.
 Maintenance: What happens during the rest of the software's life: changes,
correction, additions, moves to a different computing platform and more.
This, the least glamorous and perhaps most important step of all, goes on
seemingly forever.
In the following example (see picture) these stage of the systems development
life cycle are divided in ten steps from definition to creation and modification of
IT work products
WATER FALL MODEL
The waterfall model is a popular version of the systems development life cycle
model for software engineering. Often considered the classic approach to the
systems development life cycle, the waterfall model describes a development
method that is linear and sequential. Waterfall development has distinct goals for
each phase of development. Imagine a waterfall on the cliff of a steep mountain.
Once the water has flowed over the edge of the cliff and has begun its journey
down the side of the mountain, it cannot turn back. It is the same with waterfall
development. Once a phase of development is completed, the development
proceeds to the next phase and there is no turning back.
The advantage of waterfall development is that it allows for

departmentalization and managerial control. A schedule can be set with deadlines
for each stage of development and a product can proceed through the
development process like a car in a carwash, and
ER DIGRAM
Item name
product
Customer
number
price Bill
Selling
weight item
Dealer product
selling
stock
weight
code
time Dealer price
Item name
Mobile shop quantity
amount
Dealer date
name
weight
INPUT AND OUTPUT DESIGN
System Design
System Designing is a most challenging

Task. System design refers to the technical specification applied for
Implementing the system design involves.
INPUT/OUTPUT FILE AND PROCESSING DESIGN
The Firststep for designing is to determine in what formal outputs are presented.
The Second step is to collect input data and design the database file to meet the
requirement of the proposed outputs.
The processing phase is developed through program construction and testing

including a list of programs and explaining a global picture of the entire system.
Lastly, we can say that system design is the detail study of various operations
performed by the system inside and outside and also their relationships.
LOGIN FORM
INTRODUCTION FORM
MDI FORM
ADD MOBILEFORM
SALE INFORMATION FORM
CUSTOMER REPOT FORM
CODING
LOGIN FORM
Private Sub Timer1_Timer()

WELL.ForeColor = RGB(Rnd * 255, Rnd * 255, Rnd * 255)
If WELL.Left< 0 Then WELL.Left = 11000
WELL.Left = WELL.Left - 50
'WELL.Top = WELL.Top + 35
'If WELL.Top> 5900 Then WELL.Top = -40
End Sub
Private Sub CMDCANCEL_Click()

End
End Sub
Private Sub CMDOK_Click()

If Text1 = "MOBILE" Then
frmSplash.Show
Unload Me
Else
MsgBox "INVALID PASSWORD PLEASE TRY AGAIN!"
Text2 = ""
Text2.SetFocus
End If
Else
MsgBox "INVALID USER NAME PLEASE TRY AGAIN"
Text1 = ""
Text1.SetFocus
End If
End Sub

End Sub

End
End Sub

frmSplash.Show
Unload Me
Else
Text2 = ""
Text2.SetFocus
End If
Else
Text1 = ""
Text1.SetFocus
End If
End Sub

End Sub

End
End Sub

frmSplash.Show
Unload Me
Else
Text2 = ""
Text2.SetFocus
End If
Else
Text1 = ""
Text1.SetFocus
End If
Private Sub MNUADDMOBILE_Click()

Form7.Show
End Sub
Private Sub MNUCHANGE_Click()

Form6.Show
End Sub
Private Sub MNUCUSTOMER_Click()

DataReport1.Show
End Sub
Private Sub MNUDELETE_Click()

Form5.Show
End Sub
Private Sub MNUDELETEMOBILE_Click()

Form1.Show
End Sub
Private Sub MNUEXIT_Click()

Unload Me
End
End Sub
Private Sub MNUSALE_Click()

Form2.Show
End Sub
Private Sub MNUSALES_Click()
DataReport2.Show
End Sub
Private Sub MNUSEARCH_Click()

Form3.Show
End Sub
Private Sub MNUUPDATE_Click()

Form4.Show
End Sub
Private Sub SALES_Click()

DataReport2.Show
End Sub

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub

Unload Me
End
End Sub

Form2.Show
End Sub
DataReport2.Show
End Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End Sub
End Sub
INFORMATION FORM
Option Explicit
Private Sub Form_KeyPress(KeyAscii As Integer)

Unload Me
End Sub
Private Sub Form_Load()

lblVersion.Caption = "Version "&App.Major& "." &App.Minor& "."
&App.Revision
' lblProductName.Caption = App.Title
End Sub
Private Sub Frame1_Click()

MDIForm1.Show
Unload Me
End Sub

frmSplash.Timer1.Interval = frmSplash.Timer1.Interval + 1
If Timer1.Interval > 80 Then
Timer1.Enabled = True
MDIForm1.Show
Unload Me
End If
End Sub
Label1.Caption = Date + Time
End Sub

lblCompanyProduct.ForeColor = RGB(Rnd * 225, Rnd * 225, Rnd * 225)
End Sub
Option Explicit

Unload Me
End Sub

&App.Revision
End Sub

MDIForm1.Show
Unload Me
End Sub

MDIForm1.Show
Unload Me
End If
End Sub

End Sub

End Sub
Option Explicit

Unload Me
End Sub
&App.Revision
End Sub

MDIForm1.Show
Unload Me
End Sub

MDIForm1.Show
Unload Me
End If
End Sub

End Sub

End Sub
Option Explicit

Unload Me
End Sub

&App.Revision
End Sub

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub

Unload Me
End
End Sub

Form2.Show
End Sub

DataReport2.Show
End Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End Sub

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub

Unload Me
End
End Sub

Form2.Show
End Sub

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub
Unload Me
End
End Sub

Form2.Show
End Sub

DataReport2.Show
End Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End Sub
DataReport2.Show
End Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End Sub
MDIForm1.Show
Unload Me
End Sub

MDIForm1.Show
Unload Me
End If
End Sub

End Sub

End Sub
MDI FORM

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub

Unload Me
End
End Sub
Form2.Show
End Sub

Form7.Show
End Sub

Form6.Show
End Sub

DataReport1.Show
End Sub

Form5.Show
End Sub

Form1.Show
End Sub

Unload Me
End
End Sub
Private Sub CMDADD_Click()
Dim mid As Integer
Adodc1.Recordset.MoveLast
mid = Adodc1.Recordset.Fields("MOBILE ID").Value
Adodc1.Recordset.AddNew
Text1.Text = mid + 1
Text1.SetFocus
End Sub
Private Sub CMDEXIT_Click()

Unload Me
End Sub
Private Sub CMDFIND_Click()

Dim N As Integer
N = Val(InputBox("ENTER mobileid ", "SEARCH..."))
Adodc1.Recordset.MoveFirst
Adodc1.Recordset.Find ("mobileid = " & N & " ")
End Sub
Private Sub CMDFIRST_Click()

End Sub
Private Sub CMDLAST_Click()

End Sub
Private Sub CMDNEXT_Click()

If Adodc1.Recordset.EOF Then
Else
Adodc1.Recordset.MoveNext
End If
End Sub
Private Sub CMDPREV_Click()

If Adodc1.Recordset.BOF Then
Else
Adodc1.Recordset.MovePrevious
End If
End Sub
Private Sub CMDREFRESH_Click()

Adodc1.Refresh
End Sub
Private Sub CMDUPDATE_Click()

Adodc1.Recordset.Update
End Sub
Private Sub Command9_Click()

CommonDialog1.ShowPrinter
End Sub

Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source="
&App.Path& "\mobile.mdb;Persist Security Info=False"
Adodc1.RecordSource = "SELECT * FROM mobile"
Set Text1.DataSource = Adodc1
Text1.DataField = "mobile id"
Text2.DataField = "mobile set"
Text3.DataField = "model no"
Text4.DataField = "date of launching"
Text5.DataField = "qty of mobile"
Text6.DataField = "price"
Text7.DataField = "feature"
Text8.DataField = "colors"
Set DataGrid1.DataSource = Adodc1
End Sub
Dim mid As Integer
Text1.SetFocus
End Sub

Unload Me
End Sub

Dim N As Integer
End Sub

End Sub

End Sub

Else
End If
End Sub

Else
End If
End Sub

Adodc1.Refresh
End Sub

End Sub

End Sub

End Sub

Form2.Show
End Sub

DataReport2.Show
End Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End SubEnd Sub

Form3.Show
End Sub

Form4.Show
End Sub

DataReport2.Show
End Sub
ADD MOBILE FORM

Dim mid As Integer
Text1.SetFocus
End Sub

Unload Me
End Sub

Dim N As Integer
End Sub

End Sub

End Sub

Else
End If
End Sub

Else
End If
End Sub

Adodc1.Refresh
End Sub
End Sub

End Sub

End Sub
Dim mid As Integer
Text1.SetFocus
End Sub

Unload Me
End Sub

Dim N As Integer
ADVANTAGES OF THE PROPOSED
SYSTEM
The system is very simple in design and to implement. The system requires very
low system resources and the system will work in almost all configurations. It has
got following features
• Security of data.
• Ensure data accuracy‟s.
• Proper control of the higher officials.
• Reduce the damages of the machines.
• Minimize manual data entry.
• Minimum time needed for the various processing.
• Greater efficiency.
• Better service.
• User friendliness and interactive.
Minimum time required.

LIMITATION
This software is basically designed to maintain general information of the
MOBILE SHOP. There is some limitation of this software.
• Searching of record not at a high level.
• Interface is not well designed.
• Database Security is not considered.
• It is not accessible for multiuser environment.
• It is not tested to fulfill various software engineering approaches.
• Data can also be accessed by an unauthorized person.
• Like any system, there is an ageing process in software that requires

periodic maintenance of hardware and software.
CONCLUSION
Due to efficiency and Performance today computer are introduced in all the
department. Our Project “MOBILE SHOP”is done to give a better
computerized work in.MOBILE SHOP.This software is mainydevelope
formaintenance of Login,MDIForm,add new mobile,stock,Report etc..and all the
updation ,changes,add,remove is also done through system . This software is like
other software this is also user friendly all the work is done user friendly but if
any user don‟t know the userid and password then he/she is not able to open this
software.

Mobile PDF

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Mobile PDF

Diunggah oleh

Hak Cipta:

Format Tersedia

A

Submitted in partial fulfillment of the requirements for the award of degree

Guide by: Submitted By:

Internal Examiner External Examiner

 OBJECTIVE AND SCOPE OF THE PROJECT

 METHODOLOGY ADOPTED,SYSTEM IMPLEMENTATION &

FRONT END: VISUAL BASIC

INTRODUCTION TO VISUAL BASIC:

HOW TO DEVELOP A VISUAL BASIC APPLICATION

A control is an object that you draw on a from to enable or enhance user

ALTERNATIVES TO VISUAL BASIC DATA OBJECTS

This phase is called the 'Problem definition phase'.

...Staff have to spend three hours loading information...

Methods of defining a problem:

Interview employees about their issues with the current system

System analysis is the process of gathering and interpreting facts, diagnosing

The analysis model must achieve three primary objectives: -

The first step of system analysis process involves the identification of

This investigation accomplished the objectives, which are as

The aim of proposed system is to develop a system of improved facilities. The

 Proper control of the higher officials.

 Minimize manual data entry.

 Minimum time needed for the various processing.

 User friendliness and interactive.

 Minimum time required.

usefulness. A feasibility study of a system proposal is according to its

normally goes through a feasibility study before it is approved for development.

the feasibility study of this project such as Technical, Economic and

Operational feasibilities. The following are its features:

assessment of this feasibility must be based on an outline design of the

system requirement in the terms of input, output, programs and procedures.

Having identified an outline system, the investigation must go on to

suggest the type of equipment, required method developing the system, of

running the system once it has been designed.

Technical issues raised during the investigation are:

 Does the existing technology sufficient for the suggested one?

 Can the system expand if developed?

minimal constraints involved with this project. Thesystem has been

developed using Java the project is technically feasible for development.

The developing system must be justified by cost and benefit. Criteria to

system, is the cost it would require.

The following are some of the important financial questions asked

during preliminary investigation:

 The costs conduct a full system investigation.

 The cost of the hardware and software.

 The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no

already available, it give an indication of the system is economically

possible for development.

5.3 SYSTEM DESIGN

Some properties for a software system design are:

A database is an organized mechanism that has the capability of storing

 Normalize the data.

First Normal Form:

The Network Diagram

Steps in the PERT Planning Process

1. Identify Activities and Milestones

2. Determine Activity Sequence

3. Construct the Network Diagram

If done manually, several drafts may be required to correctly portray the

4. Estimate Activity Times

A distinguishing feature of PERT is its ability to deal with uncertainty in activity

 Optimistic time - generally the shortest time in which the activity