Chapter One o Me Dad PLC
Chapter One o Me Dad PLC
GROUP MEMBERS
ID NO
1) DANAIT MESSELE
AKUR/2620/04
2) FREWEINI TESFAY
AKUR/2639 /04
3) ZEMBABA H/SELASSIE
AKUR/2751
Contents
CHAPTER ONE
1.
Introduction
1.1
1.2
System Modeling
3.1
3.1.1
Actor Specification
Sequence diagram
3.3
Class diagram
CHAPTER FOUR
4.
System Design
4.1
Design goal
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
1.2
Office Equipment
General stationary
Domestic Appliances
Consumer Electronics
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:
amount of money.
system.
Above all the current system of Aksum branch cannot attract the customer and better services to
the customer need.
ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.
Page 5
perfectly.
Making to decrease the number of employees in the company.
To browse the wanted information easily.
Allowing customer to use their time effectively.
The
system
register
the
new
account.
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.
Hardware tools
software.
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.
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.
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.
head manager office of Aksum omedad plc. Generally using those rules they sell equipment to
their customer.
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.
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.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.
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
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
Warehouse manager
view report
Search equipment, create account, generate
report, view report, update equipment, add new
equipment, delete unwanted data
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
and password.
3. The system
displays their main
page.
If the entered user name and password is
incorrect the system displays error message.
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
system
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
equipment detail
the
information
equipment
searched
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.
3. The system
details.
creates the
account.
Uc5
Update equipment
Warehouse manager
The warehouse manager allows to modify the
Preconditions:
equipment
The ware house manager enters to the update
Post conditions:
Basic course of action:
equipment page.
Update equipment
Actor action
System response
1. Enter to the update 3.The
system
equipment page
equipment
Uc6
Add new equipment
Warehouse manager
Allow main warehouse manager to add new
Preconditions:
equipment
Warehouse manager entered to the add new
Post conditions:
Basic course of action:
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
display
new
equipment.
Uc7
Delete unwanted data
Ware house manager
Allow main warehouse to remove data that are
Preconditions:
Post conditions:
Basic course of action:
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.
Us8
View report
Seller and warehouse manager
Allow to view report in order to know
everything in the company
Preconditions:
Post conditions:
Basic course of action:
:
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
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.
virtually page.
addressing
equipment.
3. The seller receives
the money on line.
Us11
Generate report
Warehouse manager
Warehouse manager generate report for the
Preconditions:
Post conditions:
Basic course of action:
company.
The user must have user name and password.
Generating report
Actor action
System response
1. The ware house 3.
The
system
3.2
Sequence diagram
3.3
Class diagram
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.
ONLINE SELLING AND BUYING EQUIPMENT FOR AKSUM OMEDAD PLC.
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.
Diagram below shows the system decomposition diagram for this project
Actor
custome
r
seller
Order equipment
Process order
Create account
Payment process
Search equipment
Generate report
View report