Mobile PDF
Mobile PDF
Mobile PDF
Project Report
On
“MOBILE SHOP”
Year: 2018-19
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)
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
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.
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
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.
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.
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 ...
... New legislation insist that financial records are kept for this department
And so on.
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 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.
IDENTIFICATION OF NEEDS:
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.
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 soft- ware 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
Greater efficiency.
Better service.
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
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
The document provide the feasibility of the project that is being designed
and lists various areas that were considered very carefully during
A. TECHNICAL FEASIBILITY
The system must be evaluated from the technical point of view first. The
B. ECONOMIC FEASIBILITY
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
manual cost to spend for the proposed system. Also all the resources are
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.
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.
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:
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 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.
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:
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
If the critical path is not immediately obvious, it may be helpful to determine the
following four quantities for each activity:
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.
Benefits of PERT
PERT is useful because it provides the following information:
Limitations
The following are some of PERT's weaknesses:
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:
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
Monitor : VGA/SVGA
SOFTWARE REQUIREMENTS
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
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.
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.
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.
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.
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".
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 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.
Integration and testing: Brings all the pieces together into a special testing
environment, then checks for errors, bugs and interoperability.
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
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.
Item name
product
Customer
number
price Bill
Selling
weight item
Dealer product
selling
stock
weight
code
Item name
Mobile shop quantity
amount
Dealer date
name
weight
INPUT AND OUTPUT DESIGN
System 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.
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
End Sub
End Sub
End Sub
End Sub
End Sub
End Sub
End Sub
INFORMATION FORM
Option Explicit
Option Explicit
End Sub
End Sub
End Sub
MDI FORM
End Sub
Private Sub MNUSALE_Click()
Form2.Show
End Sub
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
End Sub
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
End Sub
End Sub
End Sub
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
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.
• Greater efficiency.
• Better service.