Chapter One o Me Dad PLC

AKSUM UNIVERSITY
COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTING TECHNOLOGY
PROGRAM OF INFORMATION TECHNOLOGY
PROJECT PROPOSAL
PROJECT TITLE: - ONLINE EQUIPMENT BUYING AND SELLING
FOR OMEDAD PLC.
GROUP MEMBERS
ID NO
1) DANAIT MESSELE
AKUR/2620/04
2) FREWEINI TESFAY
AKUR/2639 /04
3) ZEMBABA H/SELASSIE
AKUR/2751
Submitted Date: Nov 3, 2014

ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.
Page 1
Contents
CHAPTER ONE
1.
Introduction
1.1
Background of the organization
1.2
Statement of the problem
1.3 Objective of the Project

1.3.1 General objective
1.3.2 Specific objectives
1.4 Scope and limitation of the project
1.4.1 Scope of the project
1.4.2 Limitation of the project
1.5 Purpose of the project
1.6 Methodology
1.6.1 Data gathering techniques
1.6.2 Design Methodology
1.6.3 Implementation methodology
1.6.4 Testing Methodology
CHAPTER TWO
2.
Requirement Analysis Description
2.1 Overview of existing system

2.1.1 Activities of the system
2.1.2 Problem with the existing system
2.1.3 Business rule
2.2 Over view of the proposed system
2.2.1 Functional requirement
2.2.2 Non-Functional Requirement
2.2.3 System requirement (hardware and software requirement)
2.2.4 Constraint
2.2.5 Assumptions
CHAPTER THREE
3.
System Modeling
3.1
Use case model
3.1.1
Actor Specification

Page 2
3.1.2 Use case diagram

3.1.3 Use case Description
3.2
Sequence diagram
3.3
Class diagram
CHAPTER FOUR
4.
System Design
4.1
Design goal
4.2 System decomposition

4.3 System architecture
4.4 Deployment Diagram
4.5 Persistent diagrams
4.6 Access Control and Security

Page 3
CHAPTER ONE
1. Introduction
According to Omedad plc in Ethiopia information or newsletter, it has been always
providing a full sales service, which is fully manual especially at Aksum branch other
than that situated in Addis Ababa. Omedad plc. will automate to process more than the
current sales service and number of customer to meet the ever increasing of demand of
customers for buying or getting services. Omedad plc has plan to give higher level of
Selling services in enabling customer to buy what they need the material from the local
branch.
In order to achieve its plans, objectives and to facilitate the service it gives to the
customers the company uses manual system. The current selling system also carried out
manually. There is no Database that offers away to track records of customer and good
sold.
1.1
Background of the organization
Omedad plc is one of the services Provider Corporation in Ethiopia it was

established in 1970 with the capital of 2 million birr. At that time Omedad plc was
engaged in a wide range of service provide activity and advertisement of the product. The
Corporation served the country with the full power of services. Omedad plc has been full
service provider and they continue to add product and service to meet their customer
needs including Aksum branch it has 22 branches throughout the country.
Aksum branch is one of the branches situated in Tigray regional state and it was opened
or established in 2001 E.C with the capital of 10 million birr.
The branch together with the head office and districts facilitate the operation of
provide the service by extending various quality type of equipment with guaranty. It
helps the economic sectors and organizations to accomplish their organizational
objective as whole. Above all, the branch has been playing a great role in enhancing the
demand of customers to buy the equipment they need.
Omedad plc in Aksum branch currently provides the following service to the customer:ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.
Page 4
1.2
Office Equipment
General stationary
Spare parts and consumable
Domestic Appliances
Cutlery and kitchen utensils
House hold and office Furniture
Sports and camping goods
Consumer Electronics
Reliable and prompt Technical service
Statement of the problem
Perceived problem that leads to the investigation can actually turn out to be symptom of a
problem which needs solution as a group member we observed along queue and waiting to much
to observe which is not the problem by itself the problem could be manual record keeping of
goods sold to the customer and customer record for credit selling which may take time. Currently
the branch of Omedad plc service is fully carried out manually. As a result:
Difficult to know daily and weekly selling equipment and the
amount of money.
Delay of daily total selling data.
There is no way of providing any service without extensive paper
work and time.
Customer devotes much time to be served or to buy equipment.
There is less security because of manually operation.
They delay in payment handling because it is paid by physically
going to the organization.
There is data redundancy in the existing Omedad plc.
Difficult in summarizing the transaction performed in the existing
system.
Above all the current system of Aksum branch cannot attract the customer and better services to
the customer need.
Page 5
1.3 Objective of the Project

1.3.1 General objective
The general objective of the project is to change the manual Omedad plc to the web based
Omedad plc.
1.3.2 Specific objectives

The specific objectives that will enable us to achieve the general objective are:
Allowing customers to search the equipment efficiently.

Making the money transaction securely.
Allow to increase the performance of storage capacity.
Making the employers to take a lot of different orders at the same time
perfectly.
Making to decrease the number of employees in the company.
To browse the wanted information easily.
Allowing customer to use their time effectively.
1.4 Scope and limitation of the project

1.4.1 Scope of the project
The extent to which the problem can be treated by volume is wide, since it covers
full service that Omedad provide to the customer like reliable and prompt Technical
service, Free training, advice cutlery kitchen utensils cluttering equipment furniture,
office equipment ,Domestic Appliance and etc., which are all fully manual currently that
needs automation. In fact automating all sub systems takes much time and cost. Hence,
the team member limited the scope of the project to the following functionality.
The
system
register
the
new
customer who is currently need the equipment.
The system record goods or materials with
The system displays the price of good which
The system shall be checking the availability
their fixed cost.

are sold.
of equipment
Page 6
The system shall be adding new equipment
The system shall be deleted unwanted
to the data base.

information and update.
The system should have an administrative
Payment handling using virtual bank.

Generate report
Searching the Omedad plc items
feedback
account.
1.4.2 Limitation of the project

It does not include actual payment from actual bank.
1.5 Purpose of the project

Omedad plc. Is a business organization which provides goods and services for profit
and also its well known within the customer by providing quality and the most guaranty
equipments Studying the problem with the existing systems that may result in to improve
the information system has great advantage for the customer of Omedad plc of Aksum
branch in particular. It means that while conducting the project, it is amid at improving
the performance of the branch by which users the system benefit. The project that will
lead to the development of new system after deeply identify the problem of the existing
system will be expected to benefit both Omedad and the customer.
So by using this web application mainly the service will be provided: To reduce work load for the Aksum Omedad plc.
Improves the quality of internal operations as well as services given to customers
of Omedad plc.
To enhance the security of Omedad plc.
To enhance data accuracy in the Omedad plc.
To decrease data losing in the company.
To reduce energy for the customers.
Page 7
1.6 Methodology
1.6.1 Data gathering techniques
The method of data collecting for identification of requirements can be: Interview: We use this technique to make an interview with staff
members including the branch manager and the customers, and we collect the data
using different methods of questionnaires such as mailed questionnaires and paper
questionnaires.
Document analysis: we use this technique to make an analysis on
the existing Omedad plc.
Observation: we use this technique to observe the existing system
functionalities or activities. This is done by going to the Omedad plc. And observe
all the operations of the organization.
1.6.2 Design Methodology

In this project, we are going to utilize the object oriented development approach for
system modeling for the following reasons:
Simplicity of implementation
Reusability of code
Efficiency of modeling the real world
Ease of adopting changes at any level.
A tool we will use during system analysis and design is:Universal Modeling Language (UML) that is provided in Microsoft Project and Microsoft
visual studio. Furthermore, because we are taking the project as a course, the process model to be
used is the Waterfall process model; which is a sequential design process, in which progress is
seen as flowing steadily downward
1.6.3 Implementation methodology
Hardware tools
Processor: x86 compatible processor

RAM: 512 MB or greater
Hard Disk: 20 GB or greater
Monitor: VGA/SVGA
Keyboard: 104 keys standard
Mouse: 2/3 button. Optical/ Mechanical
Software tools of the project

Page 8
WAMP server:-used to write PHP code

MS word: - used to write documentation
Visual paradigm: - to draw UMLdiagram
Windows 8: operating system that is used to deploy the project or used to run the
software.
1.6.4 Testing Methodology

Our group members use those methods in order to test our system such as:.
1.6.4.1 Unit Testing

The unit testing is performed to test the validity of the individual units. This is done
in the coding phase with the interactive testing. Thus it itself constitutes a majority of
functionality test for each logical unit. For example we will test the system functionality
by testing one functionality like testing for the registration form after develops the
registration form.
1.6.4.2 Integrity Testing

When all the development of all the units or modules is completed and integrated the
integrity test phase is started. In this phase the interface between the modules are tested.
This phase basically verifies whether inter module exchange of information and events
are as per required system behavior. For example we will test the system functionality by
integrated two or more functionalities like testing registration and payment handling
form.
1.6.4.3 System Testing:

The system testing phase incorporates the performance stress testing so as to meet
the product criteria with respect to the desired bench marks. This is necessary test for
highly data intensive product. Here there are two testing methods:
Alpha testing: we will test the proposed system by enter a sample
with in our group members.
Beta testing: we will test the proposed system by entering sample
data with the customers or Omedad plc. Organization.

Page 9
CHAPTER TWO
2. Requirement Analysis Description
2.1 Overview of existing system
The existing system of Aksum omedad corporation has been working its activity fully
manual way. The corporation organizes the customers equipment based on types of equipment.
Omedad plc provides complete services for all equipment and goods sold by it. Omedad runs its
business to make profit through adequate collection and selling of customer electronics
equipment of the organization.
The company imports qualified goods from outside our country and selling to their customers.
There are a lot of equipments to sell for different organizations: For governmental office
Example: - fax, printer, furniture and etc.
For private sector
Example: - domestic appliance, furniture and etc.
For hotels
Example: - fridge, washing machine and guest chair and etc.
For university
Example: - bongard, boiling pan, mixer and etc.
But what makes omedad different from another company is the only sell distributor for
Riso and Ricoh machine in Ethiopia. Riso is duplicator machine and Ricoh is photo copy
machine.

Page 10
2.1.1 Activities of the system

There are a number of forms and documents which are used by the existing system. The
forms are used during the period of selling process such as receipt forms and also for the
employee to control input output items. They use these forms to assure the correctness of their
activity and to generate reports.
In addition to this, these forms are used to increase the
relationship with customers in such a way that customers can believe the cost of each materials
of the organization if they can get receipt form for each material to which they have purchased
from omedad plc.
The existing system performs different activities manually such as:
The new items will be registered on the manual file of the company.
Displaying information about the products.
Generate a report manually
2.1.2 Problem with the existing system

The main problem of existing system in Omedad plc is mentioned as follow:
Communication limitation between the warehouse manager, seller and customer.

There is no chance for customer to give their comment to the corporation.
Credit selling system i.e. late payment
The corporation uses manual system. Even though manual system by itself is not
a problem but it affects users time, cost, and energy compared to on line system.
There is lack of advertising the electronic equipment to their customer.
2.1.3 Business rule

When the user are going to manipulate this equipment selling system there are rule and
regulation. First the sellers go and see the equipment that are in omedad and ask the price of the
selected equipment then:
The payment system can be in cash or in credit as the users interest mean that as their
capacity so there is receipt so the company fulfills all the necessary information and the user sign
on the receipt.
Omedad plc gives transportation service and technical back up service this is also the
companys rule. Even though it has some problem they check and take it back to full fill the
customers comfort. And send the money to bank then write report and at last announce for the
Page 11
head manager office of Aksum omedad plc. Generally using those rules they sell equipment to
their customer.
2.2 Over view of the proposed system

In our proposed system importing and selling the equipment Management System the
admin and password is created by the developer to the general manager. Then the company
administrator can manage his default account which is given by the developer. And can set
setting, manage employees attribute, create omedad plc, manage omedad plc attribute, view all
activities in all omedad plc branches and view and print necessary files and recording the
equipment which are sold. Omedad plc selling system is a system which its analysis document is
developed by using an object oriented Software development system and its implementation part
using web pages as front end user interface and DBMS as back end for data storage strategy
which provide a set of tools for the construction of fault tolerant distributed application.
The proposed application should update record, registering customer, search equipment
easily and conveniently, delete unwanted data, add new equipment, check the availabilities of
equipment, and generate report for ware house manager. There for it has been believed that this
project benefits the Omedad in many aspects.
Update data: - The warehouse manager at the corporation updates data about selling equipment,
seller information.
Registration customer: - buyers register in the system for buying .the customer fill all necessary
information to order equipment.
Search equipment: - user wants to search equipment to see the availability and the price of it.
Add equipment: - The ware house manager adds equipment to the existing data base. The ware
house manager add equipment when the new equipment are purchased warehouse manager do
from the home page click the add button then fill the add equipment.
Delete unwanted data:- the ware house manager deletes the unwanted data.
2.2.1 Functional requirement

It is a system that the system must do. It refers to the entire business requirement that the
customer expects to be met in the finished online system.
The system provides the ability to record customers
The system provides the ability to record equipment type.
Page 12
The system provides the ability to search the equipment by number of search
methods, including search by equipment name, equipment type.
The system provides updating files.
The system provides virtual payment system.
The system provides process order.
The system provides a user authenticate.
The system should view the report.
The system provides deleting of unwanted files.
2.2.2 Non-Functional Requirement

Non-functional requirement is additional quality of the system which make our system
better than other system, including, performance, documentation. The system should be attractive
and easy to work with. The user interface online electronic equipment selling system shall be
designed for ease of use and shall be appropriate for computer literate user community without
additional training on the system.
The user interface should be user friendly.
The system developed should give a big emphasis to the issue of security. To
ensure this, user cryptography mechanisms are implemented in areas that are sensitive to
security,
The system should maintain a list of account for sellers, main warehouse
manager.
The system provides a secure means of allowing customers to paid purchase
order.
The system should browse the wanted window fastly.
The system will provide for many users at a time in distant place.
The system has full fill the quality requirement of the equipments for quality
Check.
The system must ensure allocation and use of services being requested for the
users by using minimum memory storage, cost, time and human power.
The proposed system can be avoided reputation of data anywhere in the database
All data in the system will be available all the time.
The new Omedad plc management system is error tolerant, when there is
incorrect data entry, the system identifies the error and displays appropriate error message
to correct that error.
The new system allows administrator to take regular backups based number of
transactions like it can be daily, weekly or monthly.
Page 13
The new system provides required full documentation, help contents and tips to
allow further maintainability, to support and guide users how to use the new system.
The system contains required full documentation which is useful in maintenance
after the product is released. It is developed in conformance to coding standards.
2.2.3 System requirement (hardware and software

requirement)
System requirement is the general expression of the system performance properly. It is a
term used to describe all the tasks go in to investigation scoping and definition of a new or
altered system.
To make our system functional the following software and hardware requirements are desired:
Window 2000/NT/me/XP and underling data base.

Personal computer with Pentium processor, high processor speed desired.
A minimum of 256 MB RAM for faster data processing.
A network card for connecting up to internet is desired.
A minimum of 80 GB hard derives is needed to hold data base.
2.2.4 Constraint
While we doing this project there was shortage of time mean that we were so busy and
also we had lack of resources such as money for transportation mean that while we go to ask
for interview and also sometimes they may not available in their office and sometimes lack of
network connection.
After we finished this project the system may have some problems because the proposed
Aksum omedad plc system is fully dependent on electricity so that cant perform any task
(preparing bill to customer, generating report, registering and searching for new products) in the
company. Because our system is computerized system, our system cannot perform online
transaction, it needs internet connection in order to perform the activity in the system.
2.2.5 Assumptions
Assume that each branch under Aksum omedad plc are connected to the central
mean that Aksum omedad plc using high bandwidth and reliable networks.
Assume that all employees that have a direct relationship with the system have
basic computer skills.

Page 14
Assume that there is at least one IT professionals in each branches of omedad plc.
There must be at least one system administrator who has a privilege for the central server.
Assume that there is a high performance central server which has large storage
capacity.
Assume that there is a good habit of taking back up.
CHAPTER THREE
3. System Modeling
System models are helps to discover and clarify the functionality of business system. This
model is used to recognize the system functionality using use case diagram, sequence diagrams,
class diagram.
3.1
Use case model
The Use Case Model describes the proposed functionality of the new system. A Use Case
represents a discrete unit of interaction between a user and the system. A Use Case is a single
unit of meaningful work; for example login to system, register with system. Each Use Case has a
Description which describes the functionality that will be built in the proposed system. A Use
Case may 'include' Another Use Case's functionality or 'extend' another Use Case with its own
behavior.
3.1.1
Actor Specification
Use Cases are typically related to 'actors', which are human or machine entities that use or
interact with the system to perform a meaningful work that helps them to achieve a goal.
Actor name
Customer
Use case
Order equipment, virtual payment system,
Seller
search equipment, create account

Virtual payment, create account, process order,
Warehouse manager
view report
Search equipment, create account, generate
report, view report, update equipment, add new
equipment, delete unwanted data

Page 15
3.1.2 Use case diagram

Page 16
3.1.3 Use case Description

Page 17
Table1: use case description for login

Use Case ID:
Use case name:
Actors:
Description:
Preconditions:
Post conditions:
Basic course of action:
UC1
Login
Customer, seller, ware house manager
Allows user to login to the system.
user has password and username
The user enters to the system.
Actor action
System response
1. The user fills and
2. The system checks
submits the username
the login information.
and password.
3. The system
displays their main
Alternate course of action
page.
If the entered user name and password is
incorrect the system displays error message.
Table2: use case description for order equipment

Use Case ID:
Use case name:
Actors:
Description:
Preconditions:
Post conditions:
UC2
Order equipment
Customer
Allows the customer to order the equipment.
The system has order forms
Order equipment
Actor action
System response
1.Customer fills order 2.The system submit
detail information
the ordered equipment

3.
The
system
displays the ordered

equipment.
Table3: use case description for search equipment

Use Case ID:
Use case name:
Actors:
Description:
Preconditions:
Post conditions:
UC3
Search equipment
Customer and ware house manager
Allows user to search the equipment
The system has equipment detail form
Search equipment
Actor action
System response
1.The user fills
2.The system displays

Page 18
equipment detail
the
information
equipment
searched
Table4: use case description for create account

Use Case ID:
Use case name:
Actors:
Description:
Preconditions:
Post conditions:
UC4
Create account
Ware house manager, customer, seller
Allows user to enter to their own page
The system has account form
Create account
Actor action
1. The user click
System response
2. The system
on the create
checks the
account form and
account.
fill the account
3. The system
details.
creates the
account.
Table5: use case description for update equipment

Use Case ID:
Use case name:
Actors:
Description:
Uc5
Update equipment
Warehouse manager
The warehouse manager allows to modify the
Preconditions:
equipment
The ware house manager enters to the update
Post conditions:
equipment page.
Update equipment
Actor action
System response
1. Enter to the update 3.The
system
equipment page
displays the updated
2.Click update page
equipment
Table6: use case description for add new equipment

Page 19
Use Case ID:

Use case name:
Actors:
Description:
Uc6
Add new equipment
Warehouse manager
Allow main warehouse manager to add new
Preconditions:
equipment
Warehouse manager entered to the add new
Post conditions:
Use Case ID:
equipment page
Add new equipment
Actor action
System response
1.enter to the add new 3. The system save the
equipment page
added equipment and
2.click add button
display
new
equipment.
Table7: use case description for delete unwanted data

Use Case ID:
Use case name:
Actors:
Description:
Uc7
Delete unwanted data
Ware house manager
Allow main warehouse to remove data that are
Preconditions:
Post conditions:
not necessary
Ware house manager click link on delete page
the unwanted data deleted
Actor action
System response
1.Ware
house 3.
The
system
manager entered on displays the deleted
the delete page
equipment.
2.Click delete button
Table8: use case description for view report

Use Case ID:
Use case name:
Actors:
Description:
Us8
View report
Seller and warehouse manager
Allow to view report in order to know
everything in the company

Page 20
Preconditions:
Post conditions:
:
The user has user name and password

View the report
Actor action
System response
1.The user login to 3.The system display
the report page
the viewed report
2.Stored the report
Table9: use case description for process order

Use Case ID:
Use case name:
Actors:
Description:
Preconditions:
Post conditions:
Us9
Process order
seller
the seller process the customer order
The user has user name and password
The seller process order
Actor action
System response
1.The seller enter
3.The system display
password and user
process order
name
2.Login to customer
order page
Table10: use case description for payment process

Use case name:
Actors:
Description:
Preconditions:
Post conditions:
Use Case ID:
Us10
Payment process
Customer and seller
Customer pay money to seller
Seller and customer must have a user account
Paying virtually
Actor action
System response
1. Customer enters to 3.
The
system
the payment page.
displays success full
2. Customer pays the message on customer

money
before
virtually page.
addressing

Page 21
equipment.
3. The seller receives
the money on line.
Table11: use case description for generate report

Use Case ID:
Use case name:
Actors:
Description:
Us11
Generate report
Warehouse manager
Warehouse manager generate report for the
Preconditions:
Post conditions:
company.
The user must have user name and password.
Generating report
Actor action
System response
1. The ware house 3.
The
system
Use Case ID:
manager enters to his displays the generated

page.
report on the ware
2. Select the report house manager page.

type and click on the
generate repot button.
3. Verify on the report
database.

Page 22
3.2
Sequence diagram

Page 23

Page 24

Page 25

Page 26

Page 27

Page 28

Page 29

Page 30
3.3
Class diagram

Page 31
CHAPTER FOUR
4. System Design
In this chapter we will deal with Design Goal, System Decomposition, System Architecture,
Deployment Diagram, Persistence Data Management, Access Control and Security and User
Interface Design depend on the merchants tax management system.
4.1
Design goal
So as to address the user requirement it is necessary to list out some of design the system
The function that has to been addressed is:
Access to equipment: - it helps the user to access the data or information from
the central shared database.
Viewing service from the home page to interact.
Check the availability transaction of equipment.
Based on the above used requirement we are going to set the design goal of the system. The
information used above is from the functional requirement and from the view of nonfunctional
requirement we will list the following.
Design Goals:1. Performance: determine how a system performs in terms of responsiveness and stability
under a particular workload.
2. Response time: taking less time for system to respond to the request.
3. Throughput or concurrency: impact true concurrency and maximum throughput or
transaction rate.
4. Memory utilization: take less memory space. Memory utilization also determines throughput
and or response times.
5. Simplicity: the new system will be simple to use and configure than the existing system.
Page 32
6. Reliability: the system will perform its intended functions and operations in a system's
environment, without experiencing failure or system crash.
7. Availability: the system will be available at any time if there is network connection.
8. Security: the system will be protected using cryptography security system.
9. Fault tolerance: the system will have the ability to satisfy requirements despite failures such
as hardware, software or network failures.
10. Modifiability: the system under construction will consider the new software user
requirements.
11. The system has graphic user interface.
4.2 System decomposition

A decomposition diagram shows a top-down system decomposition of a system and exposes
the systems structure. The objective of the system decomposition is to break down a system step
by step, beginning with the main function of a system and continuing with interim levels down to
the level of elementary functions. The diagram is the starting point for more detailed process
diagrams, such as data flow diagram (DFD).
Add new equipment sub system: - this deal with adding new equipment in the
data base.
Search equipment sub system:-this deals with searching equipment.
Update equipment sub system: - this deal with updating equipment in the data
base.
Create account sub system: - this deal with creating an account for the users.
Delete unwanted data sub system: - this deal with deleting unwanted data from
the database.
Process order sub system:-this deals with process ordering for every activity.
Order equipment sub system: - this deals with ordering equipment.
View report sub system:-this deals with viewing report on the user interface.
Generate report sub system: - this deal with generating report on the database.
Payment process sub system: - this deals with payment system virtually.

Page 33
Diagram below shows the system decomposition diagram for this project

Page 34
4.3 System architecture

Software architecture intuitively denotes the high level structures of a software system.
Software architecture also denotes the set of practices used to select, define or design software
architecture.
The architecture used in this project is the clientserver. The server type/role for the project
is a web server. A web server serves web pages and waits for incoming requests. Clients
therefore initiate communication sessions with server and request a server's content or service
function.
Diagram below shows the system architecture diagramfor this project

Page 35
4.4 Deployment Diagram

Deployment diagram is used to depict the relationship among the hardware and run time
nodes web server, for example, is a component that provides services to Web browsers. A
component is a physical unit of implementation with well-defined interfaces that is intended to
be used as a replaceable part of a system. Deployment diagrams are used to visualize the
topology of the physical components of a system where the software components are deployed.
The following deployment diagram three components like client browser, database server,
application server.
Diagram below shows the system deployment diagram for this project

Page 36
4.5 Persistent diagrams

Persistent data management is basically used to represent the design of the database,
usually a Relational Database. Database design is the process of producing a detailed data model
of a database. This logical data model contains all the needed logical and physical design choices
and physical storage parameters needed to generate a design in a Data Definition Language,
which can then be used to create a database.

Page 37
4.6 Access Control and Security

In many forms, but credentials that can't be transferred provide the most security. Access control
provide security by giving flexible control over who is allowed to enter or leave our system and when.
Access control is way of limiting access to a system or to physical or virtual resources. In computing,
access control is a process by which users are granted access and certain privileges to systems, resources
or information. In access control systems, users must present credentials before they can be granted
access. In physical systems, these credentials may come.
Table below shows the system Access control and security for this project
function
Actor
custome
r
seller
Main ware house

manager
Add new equipment
Update new equipment
Order equipment
Delete unwanted data
Process order
Create account
Payment process
Search equipment
Generate report
View report

Page 38

Chapter One o Me Dad PLC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter One o Me Dad PLC

Uploaded by

Copyright:

Available Formats

AKSUM UNIVERSITY

COLLEGE OF ENGINEERING AND TECHNOLOGY

Submitted Date: Nov 3, 2014

Background of the organization

Statement of the problem

1.3 Objective of the Project

Requirement Analysis Description

2.1 Overview of existing system

Use case model

ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.

3.1.2 Use case diagram

4.2 System decomposition

ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.

Background of the organization

Omedad plc is one of the services Provider Corporation in Ethiopia it was

Spare parts and consumable

Cutlery and kitchen utensils

House hold and office Furniture

Sports and camping goods

Reliable and prompt Technical service

Statement of the problem

Difficult to know daily and weekly selling equipment and the

Delay of daily total selling data.

There is no way of providing any service without extensive paper

work and time.

Customer devotes much time to be served or to buy equipment.

There is less security because of manually operation.

They delay in payment handling because it is paid by physically

going to the organization.

There is data redundancy in the existing Omedad plc.

Difficult in summarizing the transaction performed in the existing

1.3 Objective of the Project

1.3.2 Specific objectives

Allowing customers to search the equipment efficiently.

1.4 Scope and limitation of the project

customer who is currently need the equipment.

The system record goods or materials with

The system displays the price of good which

The system shall be checking the availability

their fixed cost.

The system shall be adding new equipment

The system shall be deleted unwanted

to the data base.

The system should have an administrative

Payment handling using virtual bank.

1.4.2 Limitation of the project

1.5 Purpose of the project

1.6.2 Design Methodology

1.6.3 Implementation methodology

Processor: x86 compatible processor

Software tools of the project

WAMP server:-used to write PHP code

1.6.4 Testing Methodology

1.6.4.1 Unit Testing

1.6.4.2 Integrity Testing

1.6.4.3 System Testing:

ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.

ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.

2.1.1 Activities of the system

In addition to this, these forms are used to increase the

Displaying information about the products.

Generate a report manually

2.1.2 Problem with the existing system