Debremarkos University

Technology College

Department of information

technology

Industrial Project Proposal

Title: Web based Mobile Shop and Inventory

System the case of Adugna mobile center

Debremarkos town.

Advisor name: Ms. Zebib

Group members are:-

1) Abere Balew 3) Gion yeshanew

1 | P a g e

2) Endawek Alemeneh 4) Ligaddis anley

April 2007 E.C

ContentsContents.............................................................2Chapter one..........................................................3

1. Introduction....................................................31.2. Background of the study........................................5

1.3. Statement of the problem.......................................61.4. Objective of this project......................................7

1.4.1. General objective........................................71.4.2. Specific objectives:.......................................7

1.5. Significance the system.....................................81.6. Scope of the project.........................................8

1.7. Limitation of the study........................................91.8 Methodology and tools.........................................9

1.8.1. Data collection methodology...............................91. 8.2. System development methodology.....................10

1. 8.3. Programming and data base tools.......................101.8.4 Software and hardware requirement tool.......................11

1.9. Feasibility analysis.......................................121.9.1. Economic feasibility....................................12

1.9.2. Technical feasibility.................................121.9.3. Operational feasibility................................13

2 | P a g e

1.10. Budget analysis..............................................131.11. Schedules....................................................14

2. 1.Current System................................................142.1.1 Problems encountered by the current system.................15

2.2 Functional requirements........................................162.3. Business rule identification................................18

Chapter Three....................................................193. Analysis......................................................19

3.1 Use case Diagrams............................................193.1.1 Actor Identification.........................................20

3.1.2 Use case Identification......................................203.1.3 Use Case Description.......................................21

3.2 Sequence diagram.............................................283.3 Activity Diagram...............................................32

3.4 Class Diagram..................................................37

3 | P a g e

Chapter one

1. Introduction

Electronic commerce or e-commerce refers to a wide

range of online business activities for products and

services. It also pertains to “any form of business

transaction in which the parties interact

electronically rather than by physical exchanges or

direct physical contact.”

One of the most profound changes currently transpiring

(emerging) in the world of business is the introduction

of electronic commerce. The impact of electronic

commerce (ecommerce, or EC) on procurement, shopping,

business collaboration, and customer services as well

as on delivery of various services is so dramatic that

almost every organization is affected. E-commerce is

changing all business functional areas and their

4 | P a g e

important tasks, ranging from advertising to paying

bills. The nature of competition is also drastically

changing, due to new online companies, new business

models, and the diversity of EC-related products and

services. EC provides unparalleled opportunities for

companies to expand worldwide at a small cost, to

increase market share, and to reduce costs. Nowadays,

peoples are using internet to communication,

collaboration, and many things that may be done online.

The entire project deals about online mobile

transaction system and store. Internet is changing the

way consumers shop and buys goods and services, and has

rapidly evolved into a global phenomenon. Many

companies have started using the Internet with the aim

of cutting marketing costs, thereby reducing the price

of their products and services in order to stay ahead

in highly competitive markets. Companies also use the

Internet to convey, communicate and disseminate

information, to sell the product, to take feedback and

also to conduct satisfaction surveys with customers.

Customers use the Internet not only to buy the mobile

product online, but also to compare prices, product

features and after sale service facilities they will5 | P a g e

receive if they purchase the product from a particular

store. Sales persons can visit web stores from

the comfort of their homes and shop as they sit in

front of the computer. Consumers buy a variety of

mobile items from online stores.

Apart from this Debremarkos city is in the highway of

development in technology. Many users are highly

becoming dependent on the mobile. The technological

advancement resulted mobile expansion all over the

town. The number of people who want to use cell phone

is also increasing in days. E-commerce, where

transactions are taken place online, becomes one of the

important issues in the world. Remotely located

customers have got access of the product anywhere. E-

commerce has also many advantages for both customers

and Sales persons to get profit as well as save

time. The technology has improved in times. Developed

countries started e-commerce for buying different goods

like clothes and other products. Even though e-

commerce has so many advantages, it does not expand as

expected due to high technological requirement and

skill. Developing countries has not started e-commerce

but in near future e-commerce would be one of market6 | P a g e

issue as internet technology reaches high level. As

mobile market is increasing in near future, e-commerce

would be the best solution for satisfying customers and

mobile retailers.

1.2. Background of the study

Adugna mobile center is one of the mobile shoppingcenter in Debremarkos city. It was established near

west of Debremarkos city bus station in 2004. The

mobile center purchases mobiles form s and retails to

customers with appropriate price and in different

models.

The shop has many customers at locally place. But there

is no mechanism of accessing the shop from far area.

Peoples also have not awareness about the shop. This

manual process makes hard to bring profit. Automation

the system will make the shop profitable due its

accuracy, reliability, efficiency. So this Adugna

mobile center should have mechanism of selling phones

Online that is why the project would like to develop

online application for adverting and selling online.

The project will create a powerful E-Commerce business.

One other important feature will be included in the

7 | P a g e

project is the stock inventory system; this will create

for the seller easily know the transaction and be

profitable. For that matter, the shop should build a

website that will facilitate sells incase of

advertising, storing and commit transaction through

online. Most of its manual transaction systems should

be automated.

1.3. Statement of the problem

Due to the manual transaction and retailing service it

has many problems inside. Most series problems are:-

There is no inventory management mechanism.

The existing system works manually

Is time consuming

Not effective and efficient

Inconsistency is the major problem.

Not coordinated that make ambiguous to select

mobile models with respect to customer need. To

address thus and like problems there is a need of

developing automated system.

8 | P a g e

1.4. Objective of this project

1.4.1. General objective

As far as concerned, the project wants to build an

efficient a viable e-market system where most business

activities take place through online.

1.4.2. Specific objectives:

Having above general objective, highlighting sub

activities which would target the general objective is

necessary. Thus are:-

To create inventory management systems

To create online adverts so that customers willhave knowledge of mobile type, model, price and thecompany information.

Delivery products at anywhere of the world.

To reduce user time cost in searching the mobileand related information.

To expand user choices in selecting appropriatemobile.

To create online purchase orders and commitstransaction through available bank branches.

In make profit.

9 | P a g e

1.5. Significance the system

After accomplishing these general and specific

objectives, the system will have the following

important advantages thus are:-

Improve the continuity and efficiency of services.

Creates faster, efficient and accurate data

processing.

Increase sales and profit.

Will reduce both customer and Sales

person time costs.

Makes customer mobile search robust.

Easy expanding market.

Will reduce employ work load which reduces paper

work.

Will create user satisfaction by giving comments

through online.

Makes easy to generate reports

1.6. Scope of the project

The scope of the study is as follows.

10 | P a g e

View products, feedback, and customer.

Purchase order.

Add stock, customer, feedback

Update record

Delete stock, order, feedback

Add sales report

1.7. Limitation of the study

Even though the system to be proposed has best

powerful abilities in accomplishing online business

transaction it has the following limitations.

The system does not have electronic card, visa

card and smart card electronic payment

mechanisms.

1.8 Methodology and tools

1.8.1. Data collection methodology

Observation

By inspection what people do or by obtain

relatively objective measures of how workers

can do or by seeing the customers at market

place.

11 | P a g e

Interview Technique

Interview is also best technique of acquiring

information related to market case through

preparing open ended and closed ended question

to customers and employs.

Document Analysis .it is tried to discover all

written documents about the organizational areas

relevant to the project.

1. 8.2. System development methodology

This project is developing by the object oriented

programming (OOP)

It is clear and modified in class models and object

oriented

It uses methods and functions easily.

The program must inherit in different functions and

methods.

Support the polymorphism in the programming factor.

1. 8.3. Programming and data base tools

1. 8.3.1 Programming tools: html and css are in client

side. And in Server side programming tools php. Php is

one of the most popular server side scripting languages

12 | P a g e

running today. It is used for creating dynamic

webpage’s that interact with the user offering

customized information. Php offers many advantages; it

is fast, stable, secure, easy to use .php technology

enables rapid development of web-based applications

that are server and platform-independent. There are

many reasons to love php.

Cost: Open source

Usability: is human-friendly language.

Ease of Use: php is easy to learn compared to many

other scripting languages.

Embedded: php can be easily fixed directly into,

HTML. Css and xml

Compatibility: php is platform independent.

1.8.3.2 Database tools: MySql.

MySql is one of the most popular databases which can

easily integrate with php.

1.8.4 Software and hardware requirement tool

There are some of software and hardware requirements of

the online mobile shopping.

Soft ware requirement

13 | P a g e

Edrawmax to draw UML diagrams.

Window -7 and 8

CSS (cascading style sheet): display HTML elements.

HTML (Hyper Text Markup Language): it has good

interactive interface.

Microsoft Power Point 2007: for presentation of the

project.

Microsoft office word 2007(library-office writer):

for writing documentation and for submit the

documentation.

Hardware requirement

32 and more GB for data storage

CD-RW 700MB

128 to 512 KB RAM

Printer for printing.

Computer

mouse

keyboard

1.9. Feasibility analysis

A feasibility study is a test of system proposal

according to its workability, impact on the

14 | P a g e

organization, ability to meet user needs and effective

use of resources.

1.9.1. Economic feasibility

Economic analysis is the most frequently used method

for comparing the cost with the benefit or income that

is expected from proposed system.

In the economical feasibility, the development cost in

creating the system is evaluated against the ultimate

benefit derived from the new systems. Financial

benefits must equal or exceed the costs. This project

is technically feasible because of many advantages.

After the project is delivered to the user it would

make profit for the market.

1.9.2. Technical feasibility

Includes the following:-

Does the necessary technology exist to do what is

suggested?

Do the proposed equipments have the technical

capacity to hold the data required to use the new

system?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy,15 | P a g e

reliability, ease of access and data security?

The system that have been answering the entire

above question it is said to be technically

feasible. This project is technically feasible

since it can be accomplished with the available

technology.

1.9.3. Operational feasibility

People are inherently resistant to change and

computer has known to facilitate change.

An estimate should be made of how strong a reaction

the user staff likely to have towards the

developments of computerized system.

Nowadays most people have become familiar to the

internet. This makes the project operationally

feasible which can be accomplished with a single

click. For this reason this system is operationally

feasible.

1.10. Budget analysis

No.

Expense category Amount

1 Equipment and installation 1000

16 | P a g e

2 software 1000

3 laptop 15000

4 Travel 500

5 Total 175000

1.11. Schedules

NO_ Task Name Start Finish Duration

November

December

January

1 proposal 01//07

20/09/07

6day

2 analysis 21/4/07

01/10/07

1week 6day

3 design 020/4/07

26/10/07

6day

4 implementation

17/11/07

15/12/07

6day

5 Final paper

17/5/07

20/51207

1week5day

6 defense 27/12/07

17 | P a g e

Chapter two

Overview of proposed system

2. 1.Current System

Adugna mobile center is manual based retailer shop in

Debremarkos city. It does not handle customer

information in a computerized system.

It is almost a paper work system that induces latency

in the transaction which takes time. The project aims

at solving problems of the existing system.

2.1.1 Problems encountered by the current system

The existing system is not effective.

It is time consuming.

The current system works manually.

The user has no choice regard to that makes

difficult for the customer to select appropriate

mobile model.

Report handling is weak and slow.

Hard to get speedy service.

To compile the report is time consuming.

It is not possible to get efficient information

about sell information.

18 | P a g e

Increases workload of the Sales person

because of manual systems.

2.2 proposed system

The main purpose of the proposed system is to improve

the Adugna mobile e-commerce where transaction is

possible via internet. This system is a web based

system that can improve overall activities/services.

The system is a multi-user environment that supports

customers to search mobiles, and make orders to buy

mobiles. The above problems should be eliminated using

the proposed system.

In general the proposed system will be described as

follows; regarding:-

Performance:-

It is easy to use (user friendly).

Fast and reliable.

Speed:-

It will let the buyer to access the information

being needed more quickly.

Give service to many users at any time.

19 | P a g e

Cost:-

It minimizes cost

Reduces consumption of resources to maintain

regular communication time.

The proposed system should fulfill the following

requirements. A Requirement is any function,

constraint, or property that the system must provide,

meet, or satisfy in order to fulfill its purpose. In

doing this there may be functional and non functional

requirements as follows.

2.2 Functional requirements

Functional requirements are observable tasks or

processes that must be performed by the system. For

example, functional requirements of the designed system

are must easy and more accessible for a user in the

internet. In short it is an action of the system.

Functional requirements that must be included in our

system are:

View products.

Purchase orders.

Sign up and login

Add stock,customer

20 | P a g e

Give and view feedback

Update record

Delete feedback

Delete stock, order

Confirm order

21 | P a g e

2.3 Non functional requirement

Non-functional requirements define how a system is

supposed to be. Non-functional requirements are often

called qualities of a system. Some examples of non-

functional requirements are:

Accessibility requirement The accessibility degree

of this system can be in two directions. First one

is for the Sales person who works in the

shop who will view purchase orders and available

stock. In the other side are customers who search

for , available mobile model and order product. The

system is easily accessible everywhere in the

internet.

Efficiency requirements: With the web based mobile

shop, the retailer would be able to process data

faster when they retrieve information about sell

information.

Reliability requirements

The system must perform accurately towards customer

request. For example, when the customer orders

product he/she should get the required mobile at

time of delivery. The system is intended to do so.

22 | P a g e

Security issues This issue encompasses measures

taken throughout the applications life cycle to

prevent exceptions in the security policy of the

system through flows in the design, development,

and maintenance of application. In general to make

the system asset safe, the system will follow a

role based security which means the access level

and privilege for each users of system is

predefined by the system administrator. The end

user of the system most of the time will be asked

for authorization login.

Usability requirements

This system must be designed with user-friendly

and easy to use by the staff so that the user can

perform their job nicely. It must have a clear

instruction to guide user through the system.

Besides that, the description of error message

should be clear. Looking this proposed system is

designed user-friendly.

Delivery requirements

The whole system is estimate to be done around 6

months time and the documentation will be done in

2 months. The full system will be delivers in a 23 | P a g e

softcopy method while the documentation will be

delivers in hardcopy and softcopy.

2.3. Business rule identification

All customers should be abided by the following

business rules.

Thus are:

Every user should have username and password

Each mobile product has 6 month warranty.

Chapter Three

3. Analysis

The analysis   defines the requirements of the system,

independent of how these requirements will be

accomplished. This phase defines the problem that the

customer is trying to solve. The deliverable result at

the end of this phase is a requirement document.

Ideally, this document states in a clear and precise

fashion what is to be built. This analysis represents

the ``what'' phase. The requirement document tries to

capture the requirements from the customer's

perspective by defining goals and interactions at a

level removed from the implementation details. The

24 | P a g e

analysis of the system may be expressed intermesh of

uml diagrams like use case, class, component, activity

diagrams like below.

3.1 Use case Diagrams

Use case is a structure for documenting the functional

requirements for a system, usually involving software,

whether that is new or being changed. Each use case

provides a set of scenarios that convey how the system

should interact with a human user or another system, to

achieve a specific business goal. Use cases typically

avoid technical jargon, preferring instead the language

of the end-user or Domain expert. Use cases are often

co-authored by requirements engineers and stakeholders.

3.1.1 Actor IdentificationActors:-actor is an external entity that interacts with

the system. An actor can be human or external system.

It is someone and something that exchange information

with the system. The actors are

Customers

Administrator

Sales person

25 | P a g e

3.1.2 Use case Identification

Use case is a structure for documenting the

functional requirements for a system, usually

involving software, whether that is new or being

changed. Each use case provides a set of scenarios

that convey how the system should interact with a

human user or another system, to achieve a specific

business goal. Use cases typically avoid technical

jargon, preferring instead the language of the end-

user or Domain expert. Use cases are often co-

authored by requirements engineers and stakeholders.

The use cases are:

Login

Add stock, category, customer

Purchase order

Check payment

Generate report

View stock, category, customer, feedback

View customer orders

Delete stock, feedback, customer

26 | P a g e

3.1.3 Use Case Description

Id 1Name Add stock, categoryActor AdministratorDescriptio

n

Administrator of the system adds

stock, and category.Preconditi Login to the system

27 | P a g e

onPost

condition

Administrator adds stock and category

Detail.Basic

course

Of action

1.Click login button

2.Fill user details

3.Click add button

Alternativ

e course

of action

If error occurs,

A1: the system displays you have not

added message

A2: administrator should re-enter

stock detail.

A3:the use case continues at step 1.

Id 2Name View stockActor Administrator, Salesperson, CustomerDescripti

on

Users of the system views stock

detail.Precondit

ion

Login to the system

Post

condition

Users view stock and .

Basic 4.Click login button

28 | P a g e

course of

action

5.Fill user details

6.Click view button

7.End of use case

Alternati

ve course

of action

If error occurs,

The system will not display stock

detail. Actors should try it again.

Id 3Name customer registrationActor customerDescripti

on

Customers register themselves for the

need of order purchases. Precondit

ion

Access to the system

Post

condition

The customers views success message

for the registrationBasic

course of

action

1.Click sign in button

2.Click registration button

3.Fill the required information

4.Click submit button

5.End of use case

29 | P a g e

Alternati

ve course

of action

If error occurs,

1)Either he/she should re-enter his

detail or

2)Write feedback to the system to get

solution.

After that he/she can proceed

correctly.

30 | P a g e

Id 4

Name Order stock

Actor customer

Description Customer access to the system for purchasing mobiles after him/her viewsavailable stock, and quantity of stock.

Pre-condition

Login to the system

Post-condition

Add purchase and finish payment.

Basic course of action

1.Click on login button2.View stock available3.Add purchase requirement4.Purchase mobile5.End of use case

Alternativecourse of action

If error occurs.

1.System displays incorrect data entry

2.Users should try it again at step1.

Id 5Name Give Feed back

31 | P a g e

Actor customerDescripti

on

The customer logins to the system and

gives feed backPrecondit

ion

Login to the system

Post

condition

Give feedback successfully then logged

out successfulBasic

course of

action

1.Login to the system

2.Click submit feedback button

3.Write feedback

4.Click submit button

5.End of use case

Alternati

ve course

of action

If A: the feedback is empty the system

requests you to fill againA1: the system displays the feedback

empty message.

A2: actors must look and fix those

errors.

A3:the use case continues at step 1

32 | P a g e

id 6

Name View order

Actor Administrator, sales person

Description Administrator or sales person views order detail

Pre-condition

Login to the system

Post condition

View order successfully.

Basic course of action

1.Login to the system2.Browse order detail 3.View order4.End of use case

Alternativecourse of action

If the information is not correct data

The system fill again message

33 | P a g e

Id 7

Name Check payment

Actor Administrator, Sales person

Description

Administrator, shop retailer checks payments.

Pre-condition

Login to the system

Post condition

Check payment successfully

Basic course of action

1.Click on login button2.Fill user id3.Click check payment button4.View payment5.End of use case

Alternative course of action

If the information is not correct data

The system fill again message

34 | P a g e

Id 8Name Add reportActor Sales personDescripti

on

The actor generate report

Precondit

ion

Login the system

Post

condition

Generate report

Basic

course of

action

1.Click login icon

2.Inter user id

3.Deliver product

4.End of use case

Alternati

ve course

of action

A: If the information is invalid go

againA1: the system displays error

message.

A2: actors must look and fix those

errors.

A3: The use case continues at step

1.

35 | P a g e

3.2

Sequence diagramA sequence diagram is an interaction diagram that

details how operations are carried out: what messages

are sent and when. Sequence diagrams are organized

according to time. The time progresses as you go down

the page. The objects involved in the operation are

36 | P a g e

Id 9

Name View feed backActor AdministratorDescripti

on

Administrator view feedback

Precondit

ion

Login to the system

Post

condition

administrator successfully view

feedbackBasic

course of

action

1.Click login button

2.Fill user id

3.Click view feedback

4.End of use case

Alternati

ve course

of action

If error occurs,

The system displays try again

message.

listed from left to right according to when they take

part in the message sequence.

37 | P a g e

38 | P a g e

39 | P a g e

40 | P a g e

3.3 Activity DiagramActivity diagrams show the work flow from a start point

to the finish point detailing the many decision paths

that exist in the progression of events contained in

the activity. They may be used to detail situations

where parallel processing may occur in the execution of

some activities. Activity diagrams are useful for

business modeling where they are used for detailing the41 | P a g e

processes involved in business activities. An

individual activity may be manual or automated and

often represents the action needed to move an object

between states. Further each activity is the

responsibility of particular organizational unit. In

activity diagrams, you use activity nodes and activity

edges to model the flow of control and data between

actions. Activity diagrams are helpful in the

following phases of a project:

Before starting a project, you can create activity

diagrams to model the most important work flows.

During the requirements phase, you can create

activity diagrams to illustrate the flow of events

that the use cases describe. During the analysis

and design phases, you can use activity diagrams to

help define the behavior of operations. In our case

the main activity diagrams for each use case is as

follows.

42 | P a g e

43 | P a g e

44 | P a g e

45 | P a g e

3.4 Class Diagram

A class diagram is an illustration of the relationships

and source cod e dependencies among classes in the

Unified Modeling Language (UML). In this context, a

class defines the methods and variables in an object,

46 | P a g e

which is a specific entity in a program or the unit of

code representing that entity. Class diagrams are

useful in all forms of object-oriented programming

(OOP). The concept is several years old but has been

refined as OOP modeling paradigms have evolved.

In a class diagram, the classes are arranged in groups

that share common characteristics. A class diagram

resembles a flowchart in which classes are portrayed as

boxes, each box having three rectangles inside. The top

rectangle contains the name of the class; the middle

rectangle contains the attributes of the class; the

lower rectangle contains the methods, also called

operations, of the class. Lines, which may have arrows

at one or both ends, connect the boxes. These lines

define the relationships, also called associations,

between the classes.

47 | P a g e

48 | P a g e