A system lifecycle refers to the model that is used to construction, form, program, control and measure the procedure of developing an information system. This study describes the life rhythm for development of a little supermarket direction system ( SMS ) . It is based on the undertaking program of E-Qun Web-Studio ( EQ ) to plan a supermarket direction system for Ya Du Living supermarket ( YDL ) . The whole procedure of a simple additive development method will be discussed in this study.

Background

E-Qun Web-Studio is a service solution supplier to little and average endeavors. They provide marketing service, web designing, system design, package technology and other services ( E-Qun, 2009 ) .

Ya Du Living supermarket is a ready to hand supermarket located in Suzhou Industrial Park. It has a five-year history of manual entry. There are 4 employees in this supermarket, which are accountant, cashier, stock list director and purchaser. The proprietor decided to cut down the labor cost in day-to-day operation and found EQ to plan a supermarket direction system ( E-Qun, 2009 ) .

Introduction

Problems can be solved by systems. Systems attack is an organized manner to cover with jobs. In this dynamic universe, a broad assortment of system development methodological analysiss have evolved over the old ages, each model with its ain strengths and failings ( Paul, James & A ; Peter, 2004 ) . This study will concentrate on waterfall type through analyze the procedure of EQ ‘s supermarket direction system development.

SYSTEM LIFE CYCLE

System lifecycle is a structured procedure of developing and keeping systems. It lists all procedures and sub-processes required while developing a system. A combination of assorted activities in system development is referred as system development lifecycle ( Kaariainen and Valimaki, 2008 ) .

Fig. 1 Software development Lifecycle Phases:

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

1.1 SYSTEM STUDY

System development life rhythm starts from system survey. The system survey offprints in two stages. First, a study will assist the interior decorator to place the range of the system. Second, a deepness probe will assist the interior decorator understand user ‘s demands and jobs. By and large, a system proposal will transport out by analyst and offer to user to guarantee the content is right ( Steven & A ; Glenn, 2005 ) .

EQ defined YDL as a little sized supermarket. The proprietor of YDL wanted to cut down employee ( maintain two people at most ) , monthly study can be presented faster and set up a rank system.

1.2 FEASIBILITY STUDY

Based on system survey, feasibleness survey takes topographic point. The proposed system should be tested during this stage in four facets: workability, demand fittingness, effectual usage of resources and the cost effectivity ( Steven & A ; Glenn, 2005 ) . The chief aim of this stage is accomplishing the range.

To accomplish the range, EQ assumed the SMS have six chief maps, they are: gross revenues, coverage, goods telling, rank direction, expired offers and stock list direction. This proposed system merely needs two people, which are cashier and stock list director. Order goods and generate fiscal statement can be done by the system automatically. Therefore, a sub-system called rank direction was added into this SMS.

1.3 SYSTEM ANALYSIS

If a new system is decided to develop, the following stage is system analysis. It is a depth probe based initial probe and user demands. Detailed informations flow diagrams ( DFDs ) , informations lexicon, logical information constructions and illumination specifications should reflect user demands. Designation of informations shop, sub-dividing of complex procedure, and manual procedures besides should be included in system analysis ( Steven & A ; Glenn, 2005 ) .

EQ established its undertaking agenda, listed all major activities and undertakings in WBS ( Work Breakdown Structure ) , and the deliverables and mileposts were besides announced in the agenda.

Fig. 2 Undertaking Schedule ( Work Breakdown Structure ) :

Undertaking

Description

Duration

Assigned Role

Undertaking Input

End product

Requirements

Specify demands

General debut about the system

1 hebdomad

Management Team

Team affairs

A demands papers,

A architecture design papers

( system design papers ) ,

A object design papers,

A trial program,

A undertaking program.

System/subsystem, and demands overview

2 hebdomads

Documentation Team

Requirements evocation

General restraints, premises and dependences

2 hebdomads

Functional demands

2 hebdomads

External interface

1 hebdomad

Non-functional demands

1 hebdomad

Milestones R

5 paperss

Design

i?¬ Design the architecture of the system

System organisation design

1 hebdomad

Architecture Team

A architecture design papers

System beginning codification

Subsystem design

2 hebdomads

Architecture Team

Asystem design papers

Design the user interface

User interface design

2 hebdomads

User Interface Team

A object design papers

Milestones D

System beginning codification

Development

Design the specific objects of the system

Database and configure the waiter

1 hebdomad

Database Team

System beginning codification

System

User interface

Programing

3 hebdomads

User Interface Team

Layout design

3 hebdomads

User Interface Team

Design the specific objects of the system

Connection between subsystems

1 hebdomad

Control Team

Milestones De

The system that is available to utilize

Validation

Implement the system

Test the user interface

1 hebdomad

User Interface Team

System beginning codification

A papers about the jobs that the system still needs to be worked on

Test the database

1 hebdomad

Database Team

Measure the system

List the maps and jobs

1 hebdomad

Documentation Team

Milestones V

A papers about the jobs that the system still needs to be worked on

Development

Validate the system

Adapt the user interface

1 hebdomad

User Interface Team

A papers about the jobs that the system still needs to be worked on

Final system

Adapt the database

1 hebdomad

Database Team

Adapt and better the system

Recheck the whole system

1 hebdomad

Management Team

Documentation Team

Final system

A papers about the maps that the system can supply

Milestones E

Concluding system can be provided to client

Beginning: hypertext transfer protocol: //www.docin.com/p-41243574.html

Fig. 3 Undertaking Agenda

Beginning: hypertext transfer protocol: //www.docin.com/p-41243574.html

1.4 SYSTEM DESIGN

System design is the most important stage in system development lifecycle. By and large, the design progresss in two phases: general design and elaborate design. In general design procedure, the characteristics of the system will be specified ; costs and benefits of these characteristics will be estimated. In elaborate design phase, computing machine oriented work starts at first. Structure design becomes the bluish print of system solution to those jobs mentioned in system analysis stage. Furthermore, the scheduling linguistic communication, the platform, input, end product and processing specifications will decided in item in this phase ( Steven & A ; Glenn, 2005 ) .

Several tools and techniques used for planing are ( Steven & A ; Glenn, 2005 ) :

Flow chart

Data flow diagram ( DFDs )

Data lexicon

Structured English

Decision tabular array

Decision tree

Based on the range of this supermarket and proposed system, EQ used C/S theoretical account as development theoretical account. The beginning codification were written in JAVA,

Server hardware and package environment:

“ Hardware: IBM System x3200 M2. The x3200 M2 offers the latest quad-core Intel Xeon processor ( up to 3.16 GHz/12MB/1333MHz ) , 4 GB memory ( DDR II 800MHz ) , enlargement slots ( 2 PCI ( 32-bit/33 MHz ) ,2 PCI-Express ( x8, x1 ) , Remote Supervisor Adapter II ) , 4.0TB SATA HDDs difficult thrust.

Software: Microsoft Windows Server 2008, MySQL Cluster 7.0, Avast! Anti-virus Server 4.8.1091, JDK 6 Update 16 with NetBeans 6.7.1 ” ( E-Qun, 2009 ) .

Fig. 4 System Structure:

Beginning: hypertext transfer protocol: //www.docin.com/p-41243717.html

Fig. 5 Hardware/Software Mapping

Beginning: hypertext transfer protocol: //www.docin.com/p-41243717.html

1.5 CODING & A ; Testing

After planing, the whole system should change over into computing machine understanding linguistic communication. The coder uses computing machine understanding linguistic communication to compose plans to organize the information motions and command the full procedure in the system ( Steven & A ; Glenn, 2005 ) .

Before implementing the whole system, a trial tally is done to take all bugs and step the stableness of the system ( CMS, 2009 ) . First, single units of the system should be tested. Any uncertainness occurrence must be recorded and debugged. Then, in conformity with trial program, a given set of trial informations will set into the system. The end products of the trial tally should be analyzed. If there ‘s any end product did non fit the expected end product, the mistakes in the peculiar plan or system should be identified and fixed and farther trial should be done until the end products match the expected consequences ( Parkin, 1997 ) .

Modular development technique was used in this cryptography and proving stage. EQ divided the coders in two squad, database squad and user interface squad. Each squad focal point on their ain country.

Fig. 6 Database:

& lt ; Bar codification, Product name, Unit, monetary value, Number, Total sum, Date of input and etc. & gt ;

Beginning: hypertext transfer protocol: //www.equn.net/product_1.asp

Fig. 7 User Interface of the System:

& lt ; Product, Price ticket, Inventory sheet, Gross saless enquiries, Gross saless, Reminder, Member direction, etc. & gt ; Source: hypertext transfer protocol: //www.equn.net/product_1.asp

1.6 Execution

During execution stage, the system is loaded onto the user ‘s computing machine. Then, user preparation starts. By and large four subjects will be introduced to users: executing of the bundle, informations input, informations processing and coverage. After users are trained, computerized working begins at following two schemes ( operational ) : parallel tally or pilot tally. Parallel tally means in a certain period, both systems ( i.e. manual and computerized system ) are executed in analogue. Pilot tally means the new system installs in parts. Some parts executed foremost and ran in a defined period. Other parts will be implemented merely if the consequences satisfied the expected consequences ( New York State Office, 2009 ) .

After five yearss preparation, two employees from YDL had mastered the operational accomplishments. In the ulterior month, manual working and computerized working were running in analogue to avoid the possible failure of system.

1.7 Care

Care means error rectification and ascent during the system ‘s working life. Because of there ever have some mistakes found in the system, system reappraisal is necessary to observe and rectify these mistakes. In add-on, from system reappraisal, the developer can cognize the full capablenesss of the system, required alterations and the extra demands. If a important alteration demands to be executed, a new undertaking has to be set up and continue through all the life rhythm stages ( New York State Office, 2009 ) .

Presently, EQ ‘s supermarket direction system is running in YDL. The supermarket had reduced 2 members. About 500 people were registered as members. Furthermore, the proprietor of YDL wants to turn his concern to chain-store operations. EQ has started to measure this undertaking.

Discussion

Harmonizing to Paul Davidson et Al. ( 2003 ) , waterfall theoretical account fits the state of affairss where most appropriate that undertaking has clear objects and solutions, the demands are comprehensive and stable and etc. In this instance, the lifecycle of this supermarket direction system shows that E-Qun Web-Studio used waterfall method. This model type is additive:

Those deliverables and mileposts were mensurable. The whole undertaking was divided into stages ; emphasized on planning, clip direction, mark day of the months and system execution at one clip ; maintained control of undertaking through utilizing extended paperss such as undertaking program, trial program, etc.

Decision

To sum up, the lifecycle for information system development is chiefly make up of eight facets. They are system survey, feasibleness survey, system analysis, system design, cryptography, proving, execution and care. Linear type is the simplest model to develop the system ( Paul et al. 2003 ) . In little information system, if the system is non highly complex, demands are stable and can be identified easy, undertaking squad is less experient and project agenda is unambiguous, it is strongly recommended that this undertaking uses waterfall method as the develop methodological analysis ( Paul et al. , 2004 ) .