Arba Minch Institute of Technology (Arba Minch University) : Import Management System For Agmas Medical Private Company

ARBA MINCH INSTITUTE OF TECHNOLOGY
(ARBA MINCH UNIVERSITY)
“Import Management System for Agmas Medical Private Company”
Group Members Name ID

1. Simon Birhanu RAMIT/1843/06
2. Aschalew Desta RAMIT/1590/06
3. Nebiyu Yihonas RAMIT/1507/05
4. Mihiretu Alemayehu RAMIT/1769/06
5. Eshetu Yibeltal RAMIT/1665/06
Advisor: Mr. .Amare Kebede(MSc.)
A senior project report

Submitted to Department of Computer Science and IT, Faculty of Engineering, AMIT, Arba
Minch University, in Partial fulfillment for the requirement of the Degree of Bachelor Science in
(Computer Science)
Arab Minch, Ethiopia
May27 ,2017
Arba Minch University
Page 1
Arba Minch Institute of Technology (AMIT)
Department of Computer Science and IT
Project Approval Sheet
---------------------------------------------------------------------------------------------------
-
This is to certify that the senior project titled “Import management system for Agmas
Medical” is
Submitted by
1. Simon Birhanu RAMIT/1843/06

2. Aschalew Desta RAMIT/1590/06
3. Nebiyu Yihonas RAMIT/1507/05
4. Mihiretu Alemayehu RAMIT/1769/06
5. Eshetu Yibeltal RAMIT/1665/06
To the department of Computer Science and Information Technology, Arba Minch University
for the partial fulfillment of the requirement of the Degree of Bachelor Science in Computer
Science, is a bona fide record of the project done by them under my supervision. The contents of
this document in full, or in parts, have not been submitted to any other institute or university for
the award of any degree or diploma.
Advisor by Mr.Amare Kebede Examiner by 1.Mr.Prince .T …………………
Signature………………. 2. Mr.Abey Bruck…..……………
3. Mr.Induraje…………………
Arab Minch, Ethiopia
May27, 2017
Page 2
Acknowledgment
First of all we would like to thank GOD keeping us healthy, second and foremost, we would
like to thank our advisor Mr. Amare Kebede for the valuable guidance and advice he gave us.
He inspired us greatly to work in this project. His willingness to motivate us contributed
tremendously to our project. We would like to express our gratitude towards our parents and
friends for their kind co-operation and encouragement which help us in completion of this
project.
Lastly, our thanks and appreciation also goes to AMIT, Department of Computer Science and
Information Technology in developing the project and people who have willingly helped us out
with their abilities.
Page 3
Table of Contents
Chapter One Introduction.............................................................................................................1
1. Introduction..............................................................................................................................1
1.1 Background of Institute Agmas Medical...................................................................................1

1.2 purpose of the Project............................................................................................................2
1.3 Team composition..................................................................................................................3
1.4 Problem statement..................................................................................................................3
1.5 Objective of the Project.............................................................................................................4

1.5.1 General Objective............................................................................................................4
1.5.2 Specific Objectives..........................................................................................................4
1.6 Feasibility Analysis...........................................................................................................4
1.6.1 Operational feasibility.....................................................................................................4

1.6.2 Technical feasibility........................................................................................................4
1.6.3 Economic Feasibility.......................................................................................................5
1.6.4 Behavioral/Political feasibility........................................................................................5
1.6.5 Schedule feasibility.........................................................................................................5
1.7 Scope and limitation..................................................................................................................6
1.8 Significance of the project.........................................................................................................7
1.9 Methodology..........................................................................................................................8
1.9.1 Data Source.....................................................................................................................8

1.9.2Fact Finding Techniques..................................................................................................8
1.9.3 Systems Analysis and Design..........................................................................................8
1.9.4Development Tools...........................................................................................................9
1.9.5 Testing procedure............................................................................................................9
1.9.6 Implementation (Parallel/Partial/Direct).......................................................................10
1.9.7 Limitation of the project................................................................................................10
Chapter Two: Description of the Existing System.......................................................................11
2.1 Introduction of Existing System..........................................................................................11
2.2 Players in the existing system..............................................................................................12
2.3 Major functions in the existing system like inputs, processes & outputs............................12
Page 4
2.4 Business rule of the current system......................................................................................13
2.5 Report generated in the existing system..............................................................................14
2.6 Forms and other documents of the existing systems............................................................14
2.7 Bottlenecks of the existing system.......................................................................................14
2.7.1 Performance (Response time).......................................................................................14

2.7.2 Input (Inaccurate/redundant/flexible) and Output (Inaccurate)...................................14
2.7.3 Security and Access permissions...................................................................................14
2.7.4 Efficiency.......................................................................................................................15
2.8 Practices to be preserved......................................................................................................15
2.9 Proposed solution new system that address problems of the existing system.....................15
2.10 Requirements of the Proposed System...............................................................................15
2.10.1 Functional requirements..............................................................................................15

2.10.2 Nonfunctional requirements........................................................................................17
Chapter Three: System Analysis...................................................................................................19
3.1 Introduction..........................................................................................................................19
3.2 System Requirement Specifications (SRS)..........................................................................19
3.2.1 Use Case Model.............................................................................................................19

3.2.2 Description of Use Case models...................................................................................21
3.2.3 Sequence diagram..........................................................................................................32
3.2.4 Activity Diagram...........................................................................................................40
3.2.5Analysis level class diagram (conceptual modeling).....................................................46
3.2.6 User interface................................................................................................................47
3.2.7 Supplementary specifications........................................................................................47
CHAPTER FOUR: System Design...............................................................................................48
4.1 Overview..............................................................................................................................48
4.2 Class type architecture.........................................................................................................49
4.3 Class modeling.....................................................................................................................51
4.4 State chart modeling.............................................................................................................52
4.5 Collaboration Modeling.......................................................................................................58
Page 5
4.6 Component Modeling..........................................................................................................62
4.7 Deployment mode................................................................................................................63
4.8 Persistence modeling............................................................................................................64
4.8.1 Database design.............................................................................................................65

4.9 User Interface design...........................................................................................................66
Chapter Five: Implementation and Testing.................................................................................69

5.1 Introduction..........................................................................................................................69
5.2 Final Testing of the system..................................................................................................69
5.3 Hardware software acquisitions...........................................................................................80
5.4 User manual preparation......................................................................................................80
5.5 Training................................................................................................................................80
5.6 Installation Process..............................................................................................................81
5.7 Start-up strategy...................................................................................................................81
Chapter Six: Conclusions and Recommandation..........................................................................82

6.1 Conclusions..........................................................................................................................82
6.2 Recommendations................................................................................................................82
APPENDIXS..........................................................................................................................83
Reference...................................................................................................................................84
Page 6
List of Figure
Figure1 Schedule feasibility............................................................................................................5

Figure 2 Use case model...............................................................................................................20
Figure 3 Sequence diagram for send message...............................................................................32
Figure 4 Sequence diagram for place order...................................................................................33
Figure 5 Sequence diagram for view order....................................................................................34
Figure 6 Sequence diagram for find supplier................................................................................35
Figure 7 Sequence diagram for find distributor.............................................................................36
Figure 8 Sequence diagram for add distributor.............................................................................37
Figure 9 Sequence diagram for add supplier.................................................................................38
Figure 10 Sequence diagram for payment.....................................................................................39
Figure 11 Activity diagram for login.............................................................................................40
Figure12 Activity diagram for create account:..............................................................................41
Figure13 Activity diagram for update account..............................................................................42
Figure14 Activity diagram for place order....................................................................................43
Figure15 Activity diagram for view order.....................................................................................44
Figure16 Activity diagram for payment........................................................................................45
Figure17 Class diagram.................................................................................................................46
Figure18 User interface.................................................................................................................47
Figure19 Class type architecture...................................................................................................49
Figure20 class model.....................................................................................................................51
Figure21 State chart diagram for login page.................................................................................52
Figure22 State chart diagram for Create account..........................................................................52
Figure23 State chart diagrams for Add product............................................................................53
Figure24State chart diagrams for Place order...............................................................................53
Figure25 State chart diagrams for order........................................................................................54
Figure26 State chart diagrams for Find supplier...........................................................................54
Figure27 State chart diagrams for Add supplier............................................................................55
Figure28 State chart diagrams for Find distributor........................................................................55
Figure29 State chart diagrams for Add distributor........................................................................56
Figure30 State chart modeling for Message..................................................................................56
Figure31 State chart modeling for view report..............................................................................57
Figure32 Collaboration model for login........................................................................................58
Figure33 Collaboration model for Add product............................................................................59
Figure34 Collaboration model for Order product..........................................................................59
Figure35 Collaboration model for Distribute product...................................................................60
Figure36 Collaboration model for Manage account......................................................................60
Figure37 Collaboration model for Supply product........................................................................61
Figure38 Collaboration model for Payment..................................................................................61
Figure39 Component model for Import management system.......................................................62
Figure40 Deployments model for Import management system....................................................63
Figure41 Persistence modeling......................................................................................................64
Page 7
Figure42 Database schema............................................................................................................65
Figure43 Home page......................................................................................................................66
Figure44 Admin page....................................................................................................................66
Figure45 User form page...............................................................................................................67
Figure46 Manager Page.................................................................................................................67
Figure47 Supplier home page........................................................................................................68
Figure48 Distributor page..............................................................................................................68
Figure49 Product list page.............................................................................................................68
Page 8
List of Table
Table 1.1 Team Compositions.........................................................................................................3

Table 2 Budgets...............................................................................................................................6
Table 3 Development tools..............................................................................................................9
Table 4 Functional Requirement Syste..........................................................................................16
Table 5 Find Supplier Use case Description..................................................................................21
Table 6 Import Process Use case Description...............................................................................21
Table 7 Place Order Use case Description....................................................................................22
Table 9 View Order Use case Description....................................................................................23
Table 10 View Message Use case Description..............................................................................23
Table 11 Create Account Use case Description............................................................................24
Table 12 Update Account Use case Description...........................................................................24
Table 13 Manage Supplier Use case Description..........................................................................25
Table 14 Manage Distributor Use case Description......................................................................25
Table 15 Manage Profile Use case Description.............................................................................26
Table 16 Manage Product Use case Description...........................................................................26
Table 17 View Product Use case Description...............................................................................26
Table 18Generate Report Use case Description............................................................................27
Table 19 Send Message Use case Description..............................................................................27
Table 20 Login Use case Description............................................................................................28
Table 21 Logout Use case Description..........................................................................................28
Table 22 Add supplier use case description..................................................................................29
Table 23 Add distributor use case description...............................................................................29
Table 24 Find distributor use case description..............................................................................30
Table 25 Payment Table................................................................................................................30
Table 26 Manage Supplier Use case Description..........................................................................31
Table 27 Test case to Login...........................................................................................................70
Page 9
ABSTRACT
Import Management System is the system that allows the very soft relation between the
suppliers, Agmas Medical Import Company& distributors. Those are easily interacted by system
Import Management System. Import management activities are performed manually; it takes a
lot of time to finish all the activities. There is no searching and data retrieving mechanism. The
new system is developed using the HTML, CSS, JavaScript, PHP and MySQL Programming
language. The module includes operation like online payment, searching mechanism, adding
suppliers and distributors and ordering products.
Page 10
Abbreviation
Abbreviations Description
Admin ……………..………………………Administrator
BR ………………………………………….Business rule
CSS ………………………………...........Cascading Style Sheet
HTML ….………………………………….Hypertext Markup Language
MRI….........................................................Magnetic Resonance Imaging
MS …………………………......................Microsoft
MS …………………………......................Microsoft
PHP........ …………………………………..Hypertext Preprocessor
OS ………………………………. ……....Operating system
SQL…………………………………….…Standard Query Language
WWW………………………….............World Wide Website
Page 11
Chapter One Introduction
1. Introduction
Import management system is a system that is used to manage import process of raw
materials and products from foreign countries. Import companies are the basic institutions in
Ethiopia which directly or indirectly facilitate its general economy. They also manage demand
and supply of all institutions of the Agmas Medical.
Ethiopia is one of the developing countries. When Ethiopia is compared with developed
countries, the import process is not suitable and interactive for the concerned bodies in the
process. So we are interested to develop this system to replace the current manual system. We
are highly motivated to change this manual system in to computerized web based system to
increase the quality of the service, decrease workload, man power, and cost and store the data in
the database to change the current paper based data record process.
1.1 Background of Institute Agmas Medical

Agmas Medical, the leading Medical Equipment and Supplies Importer and Distributor in
Ethiopia. Agmas Medical was established in June 1995 as a private company.
It is the Leading private company engaged in Importing and Distributing Medical Equipment,
Medical Supplies and giving before & after sale service that has proved to make significant
contribution to the development of the country's economy. Agmas Medical is the largest store for
medical equipment materials in Ethiopia. It is a one-stop-shop for all medical equipment and
supplies making it the first of its kind in the country. Currently, Agmas Medical have more than
20 Exclusive Suppliers that supply Digital radiography machines; High frequency remote control
radiography machines, CT Scanners, MRI, Doppler Ultrasounds, Hospital Furniture, Stainless
Steel Products, Surgical Instruments, Dentals, Emergency Room Equipment, Biochemistry
Analyzers, Diagnostic Reagents .
Vision:
The vision of Agmas Medical is to become a leader in supplying the most advanced, up to date,
highest quality medical equipment in East Africa and see healthy and productive community...
Page 1
Mission:
Agmas Medical operates with a mission by focusing on satisfying its customers. Agmas believes
those customers are our assets where those professional staff strives to realize this mission.
Hence, in particular Agmas aspires:
 To meet customers' demand swiftly and ethically

 To provide medical equipment and after sale services timely and without any delay
 To coordinate with customer in the health and pharmaceutical industry to supply
equipment with latest technology,
 To fill the gap of supply and demand
 To work closely with stakeholders in the industry and find ways and play a role
in improving the overall efficiency of the health system
 To satisfy our customers with the delivery of our up-to date products and
introduce modern technology and know-how.
1.2 purpose of the Project

The purpose of this Project is to present a detailed description of the Import management
System. It will explain the purpose and features of the system, the interfaces of the system, what
the system will do, the constraints under which it must operate and how the system will react to
external stimuli. This project is intended for both the administrator and the customer of import
management system. The following are the main outlined purpose of the project:
 To present a detailed description of the Import management System.
 Clarify the tasks and detail description of the system.
 To develop software development knowledge and skills.
1.3 Team composition

Import Management System (IMS)
Page 2
Prepare No. Name ID. No. Email/Mobile Responsibility
d By 1 Simon RAMIT/1843/06 Simonbirhanu71@y Coding
Birhanu ahoo.com Team leader
2 Eshetu Yibeltal RAMIT/1665/06 eshetuyibeltal@gmail Requirement elicitation
.com Design
3 Mihiretu RAMIT/1769/06 mihiretuab@gmail. Design
Alemayehu com Testing
4 Aschalew RAMIT/1590/06 Aschalewdesta1000 Requirement elicitation
Desta @gmail.com Installation
5 Nebiyu Yihons RAMIT/1507/05 NEBIYU23@yaho Testing
o.com Requirement analysis
Date December19/2016
Advisor Mr.Amare Kebede(MSc) kbde.amex@gmail.com
Table 1 Team Compositions
1.4 Problem statement

Even though Agmas Medical has its own website, it does not have functionality other than
advertisement, so the current system is manual systems which have many problems in relation to
import process and database management.
 Lack of Online payment.
 The current system makes the performance of the company slower.
 Since more import management activities are performed manually.
 It takes a lot of time to finish all the activities.
 Since the system they currently use is semi manual system; it is not economically.
 There is redundancy of activities.
 Unnecessary materials are using such as stationary materials to office and main
administrator.
 Most of the company`s information was collected by inaccurate manner.
 Customers do not get the required information and report on time, so this makes the
current system non interactive to work with.
Page 3
1.5 Objective of the Project
1.5.1 General Objective
 To develop web based import Information management system.
1.5.2 Specific Objectives
 Use system initiation and planning phase for starting and setting outline of schedule
and budget for developing the proposed system.
 Requirement gathering and elicitation.
 Use design and analysis step to identify the suitable models and designs for the
system.
 Implement the system according to the requirement business processes.
 To develop centralize database
 Provide easy searching mechanism.
 Provide a user friendly user interface.
 Provide authentication mechanism for administrator
1.6Feasibility Analysis
A feasibility study is a preliminary study undertaken to determine and document a project
practicality. We can say the project which is web based application development for Agmas
Medical import management system is feasible because it can full fill all the requirement of good
software which are economical, technical, and operational feasible.
1.6.1 Operational feasibility
Operational feasibility is the process of examining the possibility of the project will achieve its
desired objective. So the project we are developing is operationally feasible and the project will
be:
 Easy for users to operate the system.
 User friendly.
 Easy to navigate the pages.
1.6.2 Technical feasibility
The programming languages and technologies to be used for developing the system are HTML,
CSS, JavaScript, PHP and MySQL and we can find this technology in open source and our team
members have sufficient knowledge of the listed programming language to develop and
Page 4
implement the system. Therefore we can say the project is technically feasible. Because the
customer has access privilege also compatible with modern technology. This system will be
implemented based on computerized web based system.
1.6.3 Economic Feasibility
Economic feasibility evaluates the cost of the system development against the ultimate income or
benefits gets from the developed system. So the system is economical feasible because the
proposed system can uses software and hardware tools that are accessible by low cost with a
limited time. Therefore the advantage of the system is it makes the registration process easier and
time saving with the elimination of redundancy data.
1.6.4 Behavioral/Political feasibility
This project will be behaviorally feasible, because different company was open minded to wards
the acceptance of new system and there is no specialized training needed for the users. The
proposed system is a significant contribution to the development of Agmas medical Importer and
hence politically feasible since it does not oppose the FDRE constitution of Ethiopia.
1.6.5 Schedule feasibility
 Time visibility of the project
Figure1 Schedule feasibility
Page 5
Costs of the project during development time are summarized in the following table:
NO Reason of cost Type Quantity Unit Price in Total Price in

ETB ETB
1 Flash disk 8GB Sony 1 150.00 150.00
2 Stationary
Paper A4 1 packet 150.00 150
Pen BIC Rotring 10 3.00 .0
Pencil (fixer) - 3 20.00 30.00
3 Personal cost
Transportation - - 1500.00 1500.00
Telephone - - 300.00 300.00
4 Printing Expenses - - 300.00 300.00
5 Indirect cost - - 2000.00 2000.00
6 TOTAL PRICE in ETB 4,000.00
Table 2 Budgets
1.7 Scope and limitation

Import management system has boundary or scope that determines its business objective. It is
limited within the stakeholders.
 Scope
This web based system will be Import Management System for Agmas Medical Private
Company. This system will be designed to maximize the imported product by providing online
information transferring and the order transferring between the stalk holders.
 Registration for suppliers and distributors.
 View product price.
 E-mail communication.
 Online payment system.
 Searching mechanism.
 Advertisement.
Page 6
1.8 Significance of the project
Import management system will facilitate the overall process of importing products and it will
provide a positive effect in the country’s economy in additional to the participating companies.
Upon the completion of the project, it will provide different significance.
For Agmas Medical Private Company
 It reduces the work load of the importing company because the company can perform its
using the system functionalities.
 It reduces the cost that is needed to complete the import process because there is no need
to spend extra cost for searching suppliers and distributors.
 The company will be able to communicate with both distributors and supplier at any time
needed.
 It facilitates the working process and reduce the time needed to complete the task.
For the Supplier
 The supplier can easily see the ordered products and this will facilitate its working
process.
 The supplier will be able to view its products to importing company using the system.
For the Developers
 It helps us to improve our project management knowledge and skills.
 It gives us more knowledge on how to work such kinds of projects and manage the
problems that we faced during the project development time.
 It improves our interpersonal skills with our team members and by creating a team spirit
for the better accomplishment of the project.
 It improves our communicational skill throughout the requirement gathering phase.
Page 7
1.9 Methodology
For the project we use object oriented analysis and design method for reusability of the
system with agile model.
Agile Methods break the product into small incremental builds. These builds are provided in
iterations. Every iteration involves cross functional teams working simultaneously on various
areas like planning, requirements analysis, design, coding, unit testing, and acceptance testing.
1.9.1 Data Source

The primary source of data such as different forms, reports business rules and regulations are
obtained from Agmas Medical Private Company. The other data sources are the respective
official websites of Agmas Medical Private Company.
1.9.2Fact Finding Techniques

From the various facts finding methods the following methods will be used:
 Interview
Getting some sort of information about the current administration system from the import
management system’s employee that helps to analyze the system. They also give us some import
management system forms of suppliers and distributes.
 Personal Observation
Assessing and analyzing the overall administration system has been carried out by personally
observing the current working system.
 Document analysis
By reading and analyzing the current system documents, we can use it to understand the current
system and make improvement in the proposed system.
1.9.3 Systems Analysis and Design

We have used Object Oriented System Analysis and Design (OOSAD) using Unified
Modeling Language (UML).Because of the following reasons:
 These techniques enable to reduce the communication gap between user and
designers.
 These techniques enable designers to model the real world accurately.
 These techniques have usability features (it allows to use codes repeatedly on
other system).
Page 8
 Allows full exploitation of the power of object-based and object-oriented
programming languages
1.9.4Development Tools
The programming tools that the project concentrates are the following software requirements
and its environment.
Activities Tools/ Programs

Client side coding HTML/Java script
Client side scripting JavaScript
Platform MS Windows
Database server Mysql
Web server Apache
Server-side scripting Php
Browsers Mozilla Firefox, Internet Explorer
Editors EdrawMax , Notepad++, Php designer
Documentation MS Word 2007
User Training MS PowerPoint
User interface design HTML
Varied technologies As per the technical requirement in future
Table 3 Development tools

1.9.5 Testing procedure
Developing software is a complex process. No matter how hard is it, we try to eliminate all faults
simply by going through the phases of requirements, analysis, design, specification, and
implementation. Therefore, through good practice we can make sure that the most series fault
does not occur in the first place. In addition we need a separate testing phase, with the goal of
elimination all remaining faults before release. To simplify the testing process the project team
followed the different types of tests that break the testing process up into the distinct levels.
These types testing are unit testing, integration testing and system testing.
 Unit testing
In this level of testing process, the import management system developers test the different sub
procedures, functions and tested by applying the black box and white box testing.
Page 9
Sample Tests
 Check whether the return type of the functions is correct.
 Check how the sub procedures or functions are called correctly.
 Check if the correct output is produced for different inputs.
 Check the efficiency of the code with respect to the memory and CPU processing
time.
 Integration testing
In this level of testing we have examined how the different procedures work together to achieve
the goal of the sub system.
Sample Tests
 Get Add supplier (supplier ID) function is called after the set Add supplier
(supplier ID) is invoked for the particular supplier ID otherwise it calls the error
function.
 User acceptance testing
To verify if specific requirements are working for the user we use feedback from users as a
testing method. If the feedback is positive and there is no identified problem the system will
continue operating as it is, otherwise the identified problem will be solved.
1.9.6 Implementation (Parallel/Partial/Direct)
The system is implemented by using the development tools expressed under the above
development tools table and besides using the expressed hardware and software under the
chapter five (implementation part) of this project as well as the internet connection.
1.9.7 Limitation of the project

 Governmental Offices:-We could not consider the licenses & related issues which can
connect with governmental offices.
Chapter Two: Description of the Existing System
Page 10
2.1 Introduction of Existing System
The existing system of the Agmas Medical Private Company is working manually. This
manual can be used as a template for any company wishing to implement their own
unique import compliance program. Identifying potential supplier involves different
study about the items, supplier’s background and these tasks are done by the company’s
business group and individuals who have a better knowledge about the item to be
imported.
 Importer (Agmas Medical Company) – it is the main and central player of the whole
process. It is responsible to manage the company, identify items to import, pay the
suppliers and take legal possession of the imported goods, choose supplier and
distributor to work with, cover all the financial expenses to import items, study the
business, provide necessary document for the process and other main activities within
the company.
 Supplier – the supplier is the one who supplies the goods for the importer. Suppliers and
importers should communicate frequently to reach on mutually beneficial business
agreement and know the work progress.
 Distributor – it is responsible to facilitate movement of goods between importer and
recipient i.e. by distributing the imported goods in different regions, buyers can purchase
the goods at any amount as they want.
 Banks – after a contract is deal between importer and supplier. Importer’s bank supplies a
letter of credit to supplier. Supplier provides bill of lading to bank in exchange for
payment. Supplier's bank exchanges bill of lading for payment from importer's bank.
Importer’s bank exchanges bill of lading for payment from the importer. The other roles
of banks in addition to payment services are providing foreign exchange for the importer.
 Government offices: – different governmental offices work with importers such as
Ministry of Trade, Ministry of Finance and Economic Development and Ethiopian
Investment Agency to control the overall and detailed import process.
 Ethiopian shipping and logistic services enterprise: -The main focus of the Shipping
Sector of ESL is to provide Coastal and International Marine Transport services for the
goods to be imported and safe storage of discharged cargoes from vessels in Djibouti Port
until they have been transported to their destination in the country.
Page 11
 Dry ports – Major services delivered in Port and Terminal Sector include:
 Receiving and delivering cargoes
 Cargo loading and unloading
 Stuffing and un-stuffing of container goods
 Temporary storage for import and export cargoes
 Banking and Insurance
2.2 Players in the existing system

 Importer (Agmas Medical Private Company) – it is the main and central player of the
whole process. It is responsible to manage the company.
 Supplier – the supplier is the one who supplies the goods for the importer.
2.3 Major functions in the existing system like inputs, processes & outputs
The following section will summarize the function of existing system with their input, process
and output.
 Input
 Identifying potential supplier involves different study about the items, supplier’s background and
these tasks are done by the company’s business group and individuals who have a better
knowledge about the item to be imported.
 This groups will check the company’s former supplier (if any) according to the item to be
imported; different documents about different suppliers; business rules of the supplier
and other important information about the supplier.
 Chambers of commerce, industry associations, foreign embassies and consuls and
government departments of trade can help in the process of supplier identification.
 Process
Page 12
 To obtain a catalogue, sample, prices and payment terms; the importer will communicate
with the supplier using phone calls, emails or on person to obtain information catalogue
about the items, payment terms and get a few samples of the item.
 Select customs broker to facilitate the importation process and understand the local
custom rules. The importer needs to find individual who has the knowledge of the
working process rule and laws of the local area. Custom broker works for quick trouble
free clearance of goods.
 The importer will communicate with banks to get the needed foreign exchange to import
the goods.
 Output
 Place an order with the supplier request a written confirmation of receipt and acceptance
of order. Ensure the terms and conditions of the contract of sale are clear to both parties
e.g. product quality, specifications, quantity, price, price basis, payment terms, date
required, freight arrangements and documentation.
 Identify suppliers after the goods have reached their destination. The company will post
bid notice on newspapers and other Medias then interested bidders will register.
 The winning bidders will take the task of distributing the goods to different regions of the
country according to the business plan.
 Distribute the goods:-it is the responsibility of distributors
2.4 Business rule of the current system

A business rule is effectively an operating principle or policy in which the import system
must satisfy.
BR1: Authorize to the import system. Every supplier distributor must have bank account and the
importing license
BR2: The importer administrator should administer the import and give accesses (Views) to
those supplier and distributor as per their priority manual documentation style.
BR3: The suppliers distributor fill the correct information’s to the format.
2.5 Report generated in the existing system
Page 13
Reports are important in order to check up the business rules. It plays a vital role to
achieve the importer company goal. The company generates a report for the existing system in
the form of files and forms per month. In an existing system the reports are prepared manually.
2.6 Forms and other documents of the existing systems

As mentioned before, forms are used for different purposes. Also they are the backbone of the
system.
2.7 Bottlenecks of the existing system
There are a lot of problems in the existing system as compared to the proposed system.
These problems can be seen from the following perspectives like performance, information,
control, efficiency and services given by the existing system to the users. The current systems of
Agmas Medical Import management System performs different functionality with their system to
generate report about what type of items are found, how much items are found in the company
and finding and retrieving of items by using shelf items control.
2.7.1 Performance (Response time)

The administrations have so many duties such as; supplier information, guideline
distribution for suppliers and distributors, since all these activities are performed manually; it
takes a lot of time to finish all the activities. In the current system is no searching and data
retrieving mechanism.
2.7.2 Input (Inaccurate/redundant/flexible) and Output (Inaccurate)

During filling the form user make error at that time erase and change another form this
one of redundant file that means the existing system is inflexible to change because the system is
manual due to this reason the output of the system also inaccurate.
2.7.3 Security and Access permissions

The application will only allow valid users and customers to access the system. The main
users of the system are Administrator, supplier and distributor. Access to data must be controlled
because of sensitivity property of tablets no one can log into the system without a registered user
name and password.
Page 14
2.7.4 Efficiency
Agmas Medical import management system experiences many problems such as,
unnecessary data redundancy, consumption of cost and time. Hence, the existing manual system
is not as efficient as enough.
2.8 Practices to be preserved

This project will come up with a solution that can minimize the above listed problems of
the system in the and enable the medicine to be effective and efficient by considering the limited
resources they have by considering those strengths of the existing system.
2.9 Proposed solution new system that address problems of the existing system
The new proposed system tries to address the problems existing system. Some components of the new
system that solves the existing system are:-
 There is no need of extra man power to register the supplier and the distributor on the
paper document.
 It reduces the time taken in the manual system.
 This system depend on web based computerized system so that it will minimize the
workload of the organization and the humans power.
 User login is secured by the user authentication.
 The working process will be fast, attractive and accurate.
 Give data availability, confidentiality and integrity.
 Retrieve data from the database.
 It has online ordering and payments.
2.10 Requirements of the Proposed System

The proposed system has Functional requirements and Non-functional requirements.
2.10.1 Functional requirements

A functional requirement specifies what the proposed system should do?
A requirement specifies a function that a system or component must be able to perform.
Functional requirements specify specific behavior or functions.
The functional requirements of the proposed system are listed as follows:
Page 15
Sub System Functionality Description
Add supplier and The administer find supplier
Agmas Medical distributers and distributers and add to the
Private Company system.
Administrator Order item The impotor see the product of
the supplier and order the
product they want.
Supplier Supply product The suppliers fill their product
to the website.
Distributers Distributed product The distributer order the
administer and then distributes
the product to the user
Order Order the product they want to
the admin
Table 4 Functional Requirement Syste
 Agmas Medical Private Company Administrator

 Create account
 Update account
 Control Manager
 Agmas Medical Private Company Manager
 Add supplier and distributers
 Order item
 Send e-mail
 Online payment
 Manage supplier
 Generate report
 View order
 Supplier
Page 16
 View profile
 View order
 Add product
 Login
 Send e-mail
 View message
 Distributers
 Order item
 View product
 Login
 Online payment
 Send e-mail
 View massage
2.10.2 Nonfunctional requirements

The non-functional requirements focus on the quality of the application systems needed to be
developed from different evaluations point of view. The non-functional requirements proposed
system include:-
Security:
 The interface of this system consists of Login form for the registered users.
 Users must be registered in order to enter into the page.
 The system should be secure and must use encryption to protect the databases.
Performance:
 The performance of the system will depend on availability in which the site will
be available all the time.
Page 17
 Avoiding redundancy of codes increase the time of operation and memory space
of the system.
Accuracy: proposed system will be better due to reduction of error. All operation can be
done correctly and it ensures that whatever information is coming from the data base is
accurate.
Reliability: The reliability of the proposed system will be better due to proper storage of
information when users access the application.
Efficiency: The system must ensure allocation and use of services being requested for
the users by using minimum memory storage, cost, time and human power.
User friendly Interface:
 The interface of this system consists of Login form for the registered users –
users must be registered in order to enter into the page.
 Registered user has the interface which he/she can access the order and
product information.
 Administrator has also its own interface for registering users, viewing
products, validate different customers and update users’ information.
 The system has report form which generates the important process reports.
Backup and Recovery

● If the connection between the supplier, distributor and the system is break down the
system will automatically save the filled information and the remaining can enable by
the administrator by contacting the costumer using phone or email.
● To recover a data we will have a copy of the original data in another place.
Chapter Three: System Analysis
3.1 Introduction
The proposed system is a web based application that makes all the registration changes
from the manual paper based into computerized system. The system will perform tasks quickly
Page 18
and accurately. This proposed system solves the problems faced in the current system and the
data will be stored in database.
3.2 System Requirement Specifications (SRS)

Actor Identification
 Importer (Agmas Medical Private Company) – it is the main and central player of the
whole process. It is responsible to manage the company and identify items to import.
 Supplier – the supplier is the one who supplies the goods for the Agmas Medical Private
Company.
3.2.1 Use Case Model

A use case diagram at its simplest is a representation of a user's interaction with the system
that shows the relationship between the user and the different use cases in which the user is
involved.
Page 19
Figure 2 Use case model
Page 20
3.2.2 Description of Use Case models
Description 1
Use case name Find_ supplier

Use case number 1
Use case description Finds the supplier from the other countries
Uses -----
Participating Actor Agmas Medical Private Company Manager
Pre-condition Manager login to the system by using her/his account.
Flow of events 1. Manager clicks on the Supplier link from the IMS home
page.
2. The system displays find Supplier link.
3. Manager, search supplier from the page and send request
with their email.
Post condition The system connects with in the www.alibaba.com web page.
Alternative flow of When user performs this task connection should not be down.
Events
Table 5 Find Supplier Use case Description
Description 2
Use case name Maintain_ process _order

Use case number 2
Use case description Maintain importing process from supplier to Manager e.g.
from china to Ethiopia
Uses -----
Participating Actor Agmas Medical Private Company, suppliers
Pre-condition Agmas Medical Private Company Manager login to the system
by using her/his account.
Flow of events 1. Agmas Medical Private Company Manager place order.
The supplier view order products and send it using DHL.
2. The system display delivered or pending select box
Post condition The system saves all product information in the database
Alternative flow of If user made error when filling the form and click the order
product button with error, the system displays an error message
Events
and it allows her/him to try again.
Table 6 Import Process Use case Description
Page 21
Description 3
Use case name Order_item

Use case number 3
Use case description Distributor Place order to the Agmas Medical Private
Company and Agmas Medical Private Company place order to
the supplier
Uses -----
Participating Actor Agmas Medical Private Company Manager, Distributor
Pre-condition Agmas Medical Private Company Manager login to the system
by using her/his account.
Flow of events 1. Agmas Medical Private Company Manager and
Distributor clicks on the order link from the IMS home
page.
2. The system displays the products list.
3. Agmas Medical Private Company Manager and
Distributor select the product to order.
4. The system displays the orders list.
Distributor select from Delivery Method and Payment
Method and click checkout.
6. The system displays personal information form of the
order owner.
Distributor fill all the information that given in the form
and click confirm.
8. The system displays the reporting document.
Post condition The system saves all product information in IMS database
Alternative flow of If user made error when he fill the form and click the order
product button with error, the system displays an error message
Events
and it allows to fills all field.
Table 7 Place Order Use case Description
Page 22
Description 4
Use case name View_ order

Use case number 4
Use case description Agmas Medical Private CompanyManager view order placed
by distributor and supplier view order placed by Agmas
Medical Private CompanyManager
Uses -----
Participating Actor Agmas Medical Private CompanyManager, Supplier
Flow of events 1. Manager/Supplier clicks on the order link in IMS home
page.
2. The system displays order information.
3. Manager/Supplier views all the product information that
place order by distributor.
Table 8 View Order Use case Description
Description 5
Use case name View _message

Use case number 5
Use case description Agmas Medical Private CompanyManager view The message
that send from supplier and distributor
Uses -----
Participating Actor Agmas Medical Private CompanyManager, supplier,
distributor
Pre-condition Manager/supplier/distributor login to the system by using
her/his account.
Flow of events 1. Manager/supplier/distributor clicks on the message link
from the IMS home page.
2. The system displays the users that communicate with
him/her.
3. He/she clicks the user from the list and views the message
list.
Table 9 View Message Use case Description
Page 23
Description 6
Use case name Create_ account

Use case number 6
Use case description Create User Account
Uses -----
Participating Actor Agmas Medical Private Company Administrator
Pre-condition Administrator login to the system by using her/his account.
Flow of events 1. Administrator clicks on the user link from the IMS home
page.
2. The system displays the user information page and add
user link.
3. Administrator clicks add user menu.
Alternate Case If user made error when filling the user form and click the add
user button with error, the system displays an error message
and it allows to her/him to try again.
Table 10 Create Account Use case Description

Description 7
Use case name Update_ account

Use case number 7
Use case description That edit the user account
Uses -----
Participating Actor Agmas Medical Private Company Administrator
Flow of events 1. Administrator clicks on the user link from the IMS home
page.
2. The system displays the user information page
3. Administrator clicks the edit menu.
4. The system displays the user form.
5. Administrator edits all information in the user form and
click edit user.
Alternate condition If user made error when editing the user information and click
the edit user button with error, the system displays an error
message and it allows to her/him to try again.
Page 24
Table 11 Update Account Use case Description
Description 8
Use case name Manage _supplier

Use case number 8
Use case description Manage suppliers information like search , edit , view and add
suppliers
Uses -----
Participating Actor Agmas Medical Private CompanyManager
Flow of events 1. Manager clicks on the supplier link from the IMS home
page.
2. The system displays the all the suppliers information page.
3. Manager Views, Edits and Searches the suppliers
information.
Table 12 Manage Supplier Use case Description
Description 9
Use case name Manage _distributor

Use case number 9
Use case description Manage distributor information like search , edit , view and
add distributor
Uses -----
Flow of events 1. Manager clicks on the distributor link from the IMS home
page.
2. The system displays the all the distributors information
page.
3. Manager Views, Edits and Searches the distributors
information.
Table 13 Manage Distributor Use case Description
Page 25
Description 10
Use case name View _all _profile

Use case number 10
Use case description To send message from supplier and distributor
Uses -----
Participating Actor Distributor, Supplier
Pre-condition Distributor/supplier login to the system by using her/his
account.
Flow of events 1. Distributor and supplier cannot contact each other
Post condition -----------------------------
Table 14 Manage Profile Use case Description
Description 11
Use case name Manage_ product

Use case number 11
Use case description Manage all the products
Uses -----
Flow of events 1. Manager clicks on the product link from home page.
2. The system displays all the product information.
3. Manager manages the products information.
Table 15 Manage Product Use case Description
Description 12
Use case name View_ products.

Use case number 12
Use case description View the Manager imported products
Uses -----
Participating Actor Distributor
Pre-condition Distributor login to the system by using her/his account.
Flow of events 1. Distributor clicks on the product link from home page.
2. The system displays the all the products information page.
3. Distributor Views and the products that store on the
Manager.
Table 16 View Product Use case Description
Page 26
Description 13
Use case name Generate_ report

Use case number 13
Use case description Prepare report for the Manager
Uses -----
Participating Actor Manager, suppliers
Flow of events 1. Manager clicks the generate link from IMS Homepage
2. The system displays the report information.
3. Manager/suppliers view report information, so print button.
4. The system prints the report information.
Table 17Generate Report Use case Description
Description 14 send message
Use case name Send _message

Use case number 14
Uses -----
Participating Actor Supplier, Distributor, Manager,Adminstrator
Pre-condition Distributor/Supplier login to the system by using her/his
account.
Flow of events 1. Supplier/Distributor/Manager/Administrator clicks the
message link in the IMS Home page
2. The system displays the user list from the conversation.
3. Supplier/Distributor/Manager/Administrator select the user
from the list and click to send messages
4. The system display text area for texting.
5. Supplier/Distributor/Manager/Administrator typing and
click send buttons.
6. System displaying the conversation message from other
users.
Alternate Case If user made error when writing message and click send button
with error, the system displays an error message and it allows
user to fills all necessary fields.
Table 18 Send Message Use case Description
Page 27
Description 15
Use case name Login

Use case number 15
Use case description The entering authentication
Uses -----
Participating Actor Supplier, Distributor, Administrator, Manager
Pre-condition 1. Supplier/Distributor/Manager/Administrator have valid
username and password.
2. Supplier/Distributor/Manager/Administrator also have the
URL (web site) of IMS.
Flow of events 1. Supplier/Distributor/Manager/Administrator writes the
URL of IMS in address bar of web browser and press
enter key
2. The system allows the user to enter their username and
password.
Alternate Case: If the username and password are invalid, the system displays
an error message and allows the user to try again.
Post condition The system saves the authentication information in IMS
database
Table 19 Login Use case Description
Description 16
Use case name Logout

Use case number 16
Uses -----
Participating Actor Supplier, Distributor, Administrator,Manager
Pre-condition User login to the system by using her/his account.
Flow of events 1. Supplier/Distributor/Administrator/Manager have their
own homepage and click the logout menu
2. The system or exit from the home page
Table 20 Logout Use case Description
Page 28
Description 17
Use case name Add_ supplier

Use case number 17
Use case description Suppliers registration
Uses -----
Participating Actor Manager
Flow of events 1. Manager clicks the supplier link in the IMS Home page
2. The system displays add supplier link.
3. Manager clicks on the add supplier link.
4. The system displays the supplier form.
5. Manager fills all the supplier information.
Alternate Case: If the username and password are invalid, the system displays
an error message and allows the user to try again.
Table 21 Add supplier use case description
Description 18
Use case name Add_ distributor

Use case number 18
Use case description Distributor registration
Uses -----
Flow of events 1. Manager clicks the distributor link in the IMS Home page
2. The system displays add distributor link.
3. Manager clicks on the add distributor link.
4. The system displays the distributor form.
5. Manager fills all the distributor information.
Alternate Case: If the username and password are invalid, the system displays an
error message and allows the user to fills all fields.
Table 22 Add distributor use case description
Description 19
Page 29
Use case name Find distributor
Use case number 19
Use case description Find search distributor
Uses -----
Flow of events 1. Manager clicks on the distributor link from the IMS home page.
2. The system displays find distributor link.
3. Manager clicks www.sheger.net/www.dellala.com link, search
distributor from the page and send request with their email.
Post condition The system connects with in the www.alibaba.com web page.
Alternative flow of When user performs this task connection should not be down.
Events
Table 23 Find distributor use case description
Description 20
Use case name Payment

Use case number 20
Use case description Payment method
Uses
Participating Actor Manager/supplier/distributer
Pre-condition Manager/supplier/distributer login to the system by using
her/his account
Flow of events 1. Manager/supplier/distributer has bank account.
2. Manager buys from supplier. balances will be withdraw
and deposit to supplier account
Alternate Case: If the account is invalid the system displays an error message
and allows the user to add again
Table 24 Payment Table
Description 21
Page 30
Use case name Control Manager
Use case number 21
Use case description Manage Manager information like search , edit , view ,and add
suppliers
Uses -----
Participating Actor Agmas Medical Private CompanyAdministrator
Flow of events 4. Administrator clicks on the manager link from the IMS
home page.
5. The system displays the all the manager information page.
6. Manager Views, Edits and Searches the s manager
information.
Table 25 Manage Supplier Use case Description
3.2.3 Sequence diagram

A Sequence diagram is an interaction diagram that shows how objects operate with one another
and in what order. It is a construct of a message sequence chart.
Page 31
sd Send Message
Manager
IMS Index IMS Data Base message Send Message send
log in()
chek whether the data found or not()
Incorrect account ()
Display Message Menu()
click()
Write the Message()
if not found()
some tng error is happend()
Sent()
Figure 3 Sequence diagram for send message
Page 32
sd Place Order
Manager
IMS Index IMS Data Base Order Add Order Place Order
log in()
Display Order menu()
Click()
Fill neccessary order info()
Fiilcorrectly()
click()
Figure 4 Sequence diagram for place order
Page 33
sd View Order
Manager
IMS Index IMS Data Base Order Order List
log in()
Display Order menu()
Click()
View Order()
Figure 5 Sequence diagram for view order
Page 34
sd Find Supplier
Manager
IMS Home Page IMS Data Base Supplier Find Supplier Alibaba
log in()
Check whether the data found or not ()
DisplaySupp
Menu ()
Click ()
Return to home page no supp ()
click()
View Supplier Information ()

Get Supplier ()
Send Email Request ()
Figure 6 Sequence diagram for find supplier
Page 35
sd Find distributer
Manager
IMS Home Page IMS Data Base Distributer Add Distributer sheger or
Delala.com
log in()
Display
distributer
menu()
click ()
Return to home page no

distributer()
Send Email Requst()
View Distributer Information

()
Get Distributer
()
click()
Figure 7 Sequence diagram for find distributor
Page 36
sd Add distributer
Manager
IMS Home Page IMS Data Base Distributer Add Distributer
log in()
Display
distributer
menu()
click ()
Display distributer Form()

Fill Distributer Info()
Click Add Distributer()
Figure 8 Sequence diagram for add distributor
Page 37
sd Add Supplier
Manager
IMS Home Page IMS Data Base Supplier Add Supplier
log in()
Display
Supplier
menu()
click ()
Display supplier Form()

Fill Supplier Info()
Click Add Supplier()
Figure 9 Sequence diagram for add supplier
Page 38
Figure 10 Sequence diagram for payment
Page 39
3.2.4 Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic aspects of the
system. Activity diagram is basically a flow chart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system.
act Requirements
Ini ti al
login
fi ll account
no is username and password correct?
yes
HomePage
end
Figure 11 Activity diagram for login
Page 40
act Requirements
Ini ti al
login
fi l l account
no i s username and password correct?
yes
HomePage
cl i ck
User
cl i ck
add user
fi l l user i nfor
no i s the correct fi l d
yes
account
created
end
Figure12 Activity diagram for create account:
Page 41
act Requirements
Ini ti al
login
fi l l account
yes
HomePage
cl i ck
User
cl i ck
update user
edi t user
i nfor
no i s edi ted the

correct fi l d?
yes
account
updated
end
Figure13 Activity diagram for update account
Page 42
act Requirements
Ini ti al
login
fi l l account
yes
HomePage
cl i ck
Order
cl i ck
order product
fi l l order products
no
i s the fi l d
correct?
yes
place order
end
Figure14 Activity diagram for place order
Page 43
act Requirements
Ini ti al
login
fi l l account
yes
HomePage
cl i ck
Order
vi ew the order l i st i n rows
end
Figure15 Activity diagram for view order
Page 44
Figure16 Activity diagram for payment
Page 45
3.2.5Analysis level class diagram (conceptual modeling)
Class diagram describes the relationship between objects and class. It shows the attributes and
operations of each class.
Figure17 Class diagram
Page 46
3.2.6 User interface
Figure18 User interface
3.2.7 Supplementary specifications

The Supplementary Specifications capture the system requirements that are not readily captured in the use
cases of the use-case model. Such requirements include:-
 Legal and regulatory requirements and application standards.

 Quality attributes of the system to be built, including usability, reliability,
performance, and supportability requirements.
 Other requirements such as operating systems and environments, compatibility
requirements, and design constraints.
The other Supplementary specifications are the business rules .The business rules is a principle or a policy
in which the proposed system operates accordingly.
Page 47
CHAPTER FOUR: System Design
4.1 Overview
Design is the first step into the development phase for any engineered product or system. Design
is a creative process. A good design is the key to effective system. It may be defined as a process
of applying various techniques and principles for the purpose of defining a device, a process or a
system in sufficient detail to permit its physical realization. The system design develops the
architectural detail required to build a system or product. The design phase is a transition from a
user oriented document to the programmers or database personnel. The project is designed in a
manner that solves the problems of the organization by minimizing the work load of the existing
system and employee. It provides more efficient, reliable and time saving system. Generally this
project design describes how the project is designed, what tasks done under this project and
different modules and their way of functioning. System design is the transformation of the
analysis model into a system design model. System design is the first part to get into the Solution
domain in a software development. This document describes the design issues of the overall
system. It provides the complete architectural overview of the proposed system. It is intended to
capture and express the significant architectural decisions which have been made on the system.
The following points describe the general functionality of the system:-
 Efficiency: the system doing something well and thoroughly without waste of money and
time.
 Flexibility : the system able to change to suite new condition or situation
 Reliability: the system is reliable.
Page 48
4.2 Class type architecture
User Interface Layer
Process Layer
System layer
Domain Layer
Persistence layer
Database
Figure19 Class type architecture
 User interface layer

This Layer is the form which provides the application to either programmer or end user.
 Controller/process layer
The process layer implements business logic that involves collaborating with several domain
classes or even other process classes.
 Business/Domain layer
This layer is used to transfer data from application layer or presentation layer to data layer. This
layer is also used when a class variables are declared corresponding to the fields of the database
Page 49
which can be required for the application and make the properties. So that, the team can gets or
sets the data using these properties into the variables.
 Persistence layer
Persistence layers encapsulate the capability to store, retrieve, and delete objects/data
permanently without revealing details of the underlying storage technology in the system. Often
implement between object schema and database schema and there are various available to us. For
instance, our system uses MySQL database.
 System layer
This Layer provides operating-system-specific functionality for our applications, isolating our
software from the operating system (OS) by wrapping OS-specific features, increasing the
portability of our system.
Page 50
4.3 Class modeling
Page 51
Figure20 class model
Page 52
4.4 State chart modeling
In this part the team used to model the behaviors of the objects by drawing the state diagram.
That shows the sequence of states that an object goes through, the events that cause the transition
from one state to the other and the actions that result from a state change.
Figure21 State chart diagram for login page
Figure22 State chart diagram for Create account
Page 53
Figure23 State chart diagrams for Add product
Figure24State chart diagrams for Place order
Page 54
Figure25 State chart diagrams for order
Figure26 State chart diagrams for Find supplier
Page 55
Figure27 State chart diagrams for Add supplier
Figure28 State chart diagrams for Find distributor
Page 56
Figure29 State chart diagrams for Add distributor
Figure30 State chart modeling for Message
Page 57
Figure31 State chart modeling for view report
Page 58
4.5 Collaboration Modeling
A collaboration diagram shows an interaction organized around the objects in the interaction and
their links to each other. Unlike a sequence diagram, a collaboration diagram shows the
relationships among the objects. On the other hand, a collaboration diagram does not show time
as a separate dimension, so sequence numbers determine the sequence of messages and the
concurrent threads.
Figure32 Collaboration model for login
Page 59
Figure33 Collaboration model for Add product
Figure34 Collaboration model for Order product
Page 60
Figure35 Collaboration model for Distribute product
Figure36 Collaboration model for Manage account
Page 61
Figure37 Collaboration model for Supply product
Figure38 Collaboration model for Payment
Page 62
4.6 Component Modeling
Component diagrams allow modelers to provide a simplified high-order view of a large system.
Classifying groups of classes into components supports the interchangeability and reuse of code.
This diagram shows us how these components are composed and how they interact in a system.
Figure39 Component model for Import management system
Page 63
4.7 Deployment mode
A deployment diagram shows how artifacts are deployed on system hardware, and how the
pieces of hardware connect to one another. The main hardware item is a node, a generic name for
a computing resource.
Figure40 Deployments model for Import management system
Page 64
4.8 Persistence modeling
Persistence models in our system are used to communicate the design of database. This is
basically the entity relation in database application. The system that we design overall persistent
modeling is described at class modeling part.
Figure41 Persistence modeling
Page 65
4.8.1 Database design
Entity relationship diagram
Figure42 Database schema
Page 66
4.9 User Interface design
Figure43 Home page
Figure44 Admin page
Page 67
Figure45 User form page
Figure46 Manager Page
Page 68
Figure47 Supplier home page
Figure48 Distributor page
Figure49 Product list page
Page 69
Chapter Five: Implementation and Testing
5.1 Introduction
This chapter illustrates the system testing and implementation phases. The testing phase involves
some modification to the pervious design phase and system testing has been done to minimize
the programming and system error. During implementation and operation, physical design
specification must be turned into working computer code, and then the code is tested until most
of the errors have been detected and corrected. The user sites are prepared for new system and
user must come totally on the new system rather than the existing.
5.2 Final Testing of the system
Once code has begin, the testing process can begin and proceed in parallel as each program
module is produced, it can be tested individually. The following are different testing strategies.
Black box testing: -
To test our system, the tester may use black box testing, if he/she has not enough time to check
internal modules or codes. By looking only input /output or user interface, the tester can test our
systems functionalities without looking the internal code. We used this testing technique for the
following reasons:-
 This testing type is more effective on larger units of code.

 Tester needs no knowledge of implementation, including specific programming
languages.
 Tester and programmer are independent of each other.
 Tests are done from a user's point of view.
White box testing: -
In this type of testing, skilled man in different programming languages tries to test the logic of
our system. If the person who tests the system is not skilled, it is difficult to understand our
systems functionality. If any failures occur while testing the system in all of the above testing
methods, the team will take immediate correction where this fault occurred before jumping to
next work. So, that it will meet the goal.
Page 70
Test Case 1: Login
Test case objective : To login to the system
Test case description: Admin enters Username and Password, then presses login button.
Client program contacts with server, server contacts with the database, and database checks for
authentication and displays administrator page.
Requirements Verified: Yes
Test Environment: Apache mysql server must be in running state, Database Should contain
appropriate table and link must be established between server and client program.
Test Setup/Pre-Conditions: Apache server should be in running state and Username and
Password fields should be filled correctly.
Actions Expected Results
The administrator should enter the correct user name and Displays administrator page.
password to login.
If user name and password are not filled correctly the system display to fill the user name and
password again.
Table26 Test case to Login

Sample home web page source code
<html>
<head>
<title>Wellcome to AMIMS</title>
<meta charset="UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="shortcut icon" href="img/season-change.jpg" type="image/x-icon">
<title>HealthCare</title>
<link href='http://fonts.googleapis.com/css?family=Abel' rel='stylesheet' type='text/css'>

<link href='http://fonts.googleapis.com/css?family=Roboto:400,300,500' rel='stylesheet' type='text/css'>
<link href='http://fonts.googleapis.com/css?family=Dosis:300,400,500,600' rel='stylesheet' type='text/css'>
<link rel="stylesheet" type="text/css" href="assets/css/animate.css">
<link rel="stylesheet" type="text/css" href="assets/css/bootstrap.min.css">
Page 71
<link rel="stylesheet" type="text/css" href="assets/css/owl.carousel.css">
<link rel="stylesheet" type="text/css" href="assets/css/owl.theme.css">
<link rel="stylesheet" type="text/css" href="assets/css/owl.transitions.css">
<link rel="stylesheet" type="text/css" href="assets/css/font-awesome.min.css">
<link rel="stylesheet" type="text/css" href="assets/css/main.css">
<link href='http://fonts.googleapis.com/css?family=Roboto+Condensed:400,300' rel='stylesheet' type='text/css'>
</head>
<body>
<section class= "navs">
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container-fluid">

<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-
navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand logo" href="#">
<span><i class="fa fa-stethoscope"></i></span>
Agmas medical
</a>
</div>
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<li class="active"><a href="#">Home</a></li>
<li><a href="gallery.html">Products</a></li>
<li><a href="doctors.html">About Us</a></li>
<li><a href="contact.html">Contact Us</a></li>
<li><a href="lo.php">login</a></li>
</ul>
Page 72
</div>
</div>
</nav>
</section>
<section class= "starting-text">
<div class="container">
<div class="row">
<div class="welcome">
<h2 class="welcome-title">Welcome to Agmas Medical </h2>
<p class="welcome-txt"> Welcome to Agmas Medical, the leading Medical Equipment and Supplies
Importer and Distributor in Ethiopia. Agmas Medical was established in June 1995 as a private company. It is the
Leading private company engaged in Importing and Distributing Medical
Equipment, Medical Supplies and giving before & after sale service that has proved to make significant contribution
to the development of the country's economy. Agmas Medical is the largest store for medical equipment materials in
Ethiopia. It is a one-stop-shop for all medical equipment and supplies making it the first of its kind in the country.
</p>
</div>
</div>
</div>
</section>
<section id= "testimonial" class="text-center">
<div class="testimonial-wrapper">
<div class="row client-content text-center">
<div class="col-md-8">
<div class="row">
<h1>What We Offer</h1>
</div>
<div class="row">
<div class="sub-headline">
</div>
</div>
<div id="carousel-example-generic" class="carousel slide" data-ride="carousel">

<div class="carousel-inner" role="listbox">
Page 73
<div class="item active">
<div id="client-speech">
<div class="item">
<div class="row">
<i class="fa fa-quote-left"></i>
</div>
<div class="col-md-8 col-md-offset-2">
<p class="client-comment text-center">
</p>
</div>
<i class="fa fa-quote-right"></i>
</div>
<div class="col-md-4 col-md-offset-4 col-sm-6 col-sm-offset-3 col-xs-6 col-xs-offset-3">
<img class="img-circle img-responsive center-block" src="assets/img/client3.jpg" alt="Image">
</div>
</div>
<div class= "row text-center">
<p class="client-name text-center">Julia Doe</p>
</div>
</div>
</div>
</div>
<div class="item">
<div class="item">
<div class="row">
</div>
Page 74
</p>
</div>
<i class="fa fa-quote-right"></i>
</div>
<div class="col-md-4 col-md-offset-4 col-sm-6 col-sm-offset-3 col-xs-6 col-xs-offset-3">
<img class="img-circle img-responsive center-block" src="assets/img/client1.jpg" alt="Image">
</div>
</div>
<div class= "row text-center">
<p class="client-name text-center">John Doe</p>
</div>
</div>
</div>
</div>
<div class="item">
<div class="item">
<div class="row">
</div>
</p>
</div>
<a class="left carousel-control" href="#carousel-example-generic" role="button" data-slide="prev">
<i class="fa fa-angle-left fa-3x"></i>
<span class="sr-only">Previous</span>
</a>
<a class="right carousel-control" href="#carousel-example-generic" role="button" data-slide="next">
Page 75
<i class="fa fa-angle-right fa-3x"></i>
<span class="sr-only">Next</span>
</a>
</div>
</div>
<div class= "appointment">

</div>
</div>
</div> 
</div>
</div>
</section> 
<section id="footer">
<div class="row">
<ul class="text-center contact">
<li class= "socials-icons">
<a href="#" data-toggle="tooltip" title="Share in Facebook" class="facebook"><i class="fa fa-
facebook"></i></a>
</li>
<a href="#" data-toggle="tooltip" title="Share in Twitter" class="twitter"><i class="fa fa-
twitter"></i></a>
</li>
<a href="#" data-toggle="tooltip" title="Share in Google +" class="google-plus"><i class="fa fa-google-
plus"></i></a>
</li>
<a href="#" data-toggle="tooltip" title="Share in Instagram" class="instagram"><i class="fa fa-
instagram"></i></a>
</li>
Page 76
<a href="#" data-toggle="tooltip" title="Share in Pinterest" class="pinterest"><i class="fa fa-
pinterest"></i></a>
</li>
<a href="#" data-toggle="tooltip" title="Connect with Skype" class="skype"><i class="fa fa-
skype"></i></a>
</li>
</ul>
</div>
</div>
<div class="row">
<div class="copy-right-text text-center">
© Copyright 2017, www.agmas.com. Theme by <a href="https://www.agmass.com/">agmas</a>
</div>
</div>
</div>
</div>
</section>
<script type="text/javascript" src="assets/js/jquery.min.js"></script>
<script type="text/javascript" src="assets/js/owl.carousel.min.js"></script>
<script type="text/javascript" src="assets/js/isotope.pkgd.min.js"></script>
<script type="text/javascript" src="assets/js/wow.min.js"></script>
<script type="text/javascript" src="assets/js/bootstrap.min.js"></script>
<script>
new WOW().init();
</script>
<script>
$(document).ready(function() {
$("#starting-slider").owlCarousel({
autoPlay: 3000,
navigation : false, // Show next and prev buttons
slideSpeed : 700,
Page 77
paginationSpeed : 1000,
singleItem:true
});
});
</script>
<script>
$( function() {
// init Isotope
var $container = $('.isotope').isotope
({
itemSelector: '.element-item',
layoutMode: 'fitRows'
});
// bind filter button click
$('#filters').on( 'click', 'button', function()
{
var filterValue = $( this ).attr('data-filter');
// use filterFn if matches value
$container.isotope({ filter: filterValue });
});
// change is-checked class on buttons
$('.button-group').each( function( i, buttonGroup )
{
var $buttonGroup = $( buttonGroup );
$buttonGroup.on( 'click', 'button', function()
{
$buttonGroup.find('.is-checked').removeClass('is-checked');
$( this ).addClass('is-checked');
});
});
});
</script>
Page 78
<left>
</left>
</body>
</html>
Sample login web page source code
<html>
<head>
<title>Login to ims</title>
<link rel="stylesheet" href="css/style.css" type="text/css" />
</head>
<body>
<div id="header">
<div align="center">
<label>
<h1><a href="home.php"><img src="images/bg/lo.JPG" class="logo_banner"></a></h1>
</label>
</div>
</div>
</div>
<center>
<form method="post" action="#">
<div class= "form">
<table bgcolor="#A9A9A9" align="center" style="border:1px margin-top:15px;10px 20px 10px black;"

width="200" height="300px >
<tr><td colspan=3 align=right ><p style="margin-right:3%;"><font color=green></td></tr>
<tr colspan="3"><td colspan="3"><img width="500"height="180"src="images/bg/log.jpg"/></td></tr>
<tr>
<td ><input type="text" name="username" placeholder="Username" required /></td>
</tr>
<tr>
<td><input type="password" name="password" placeholder="Password" required /></td>
</tr>
Page 79
<tr>
<td>
User Type: <select name="user" class="form-control">
<option value="1 " selected>Manager </option>
<option value="2">Supplier </option>
<option value="3">Distributor </option>
<option value="4">Administrator </option>
</select>
</td>
</tr>
<tr>
<td align="center"><button name="enter" type="submit" name="">LogIn</button></td>
</tr>
</table>
</form>
</div>
</center>
</body>
</html>
5.3 Hardware software acquisitions

For this system implementation, the following Hardware and Software are used.
Hardware acquisitions
Page 80
Computers: for client side and server side TOSHIBA with Hard Disk: 699GB RAM: 4GB
Processor: Intel Core 5 DUO CPU (TM) i5-3210m @ 2.5GHZ (4cpus), ~2.5GHz
Printer: To printing the documents.
Server: To create connection to the client computer (to host the system)
Software acquisitions
 PHP designer
 Xammp server
 MySQL database
 Notepad ++
 Microsoft Windows 8 and Windows 7 Ultimate SP1
5.4 User manual preparation.
Since the system is web based and easily user friend, everything important for the users will be
explained and implemented while giving short training when the system is deployed. There is no
need of preparing full user manual because it is only deployed (hosted) on a single machine that
is server. So anyone who can access the internet can also access the system easily within the
given permission by the system administrator.
5.5 Training
During the deployment of this system, the project group members will give short time training
for the system administrator and importer how the system works and in what way they can
manage their system.
5.6 Installation Process
Our system is a web based System, there is no need to install it on particular machine ones it is
deployed on a server by developer, the user of the system can use it at any time and any place.
Page 81
5.7 Start-up strategy
Once the system is hosted, it has two start-up strategies: the first start-up strategy is for the
administrator, manager, supplier and distributor which require the username and password to
access the system. The user’s accessibility part is restricted for the users and the other one is for
system administrator. The second start-up strategy part is the system home page which does not
require the username and password and it can be viewed by anybody.
Chapter Six: Conclusions and Recommandation
6.1 Conclusions
So far we were intended in analyzing the existing system of the Agmas Medical Import
management system up to proposing our new system that solves the difficulties related to the
existing system. To say something on the existing system: it is running almost manually, hence it
is highly exposed to the manual related problems, like the productivity of the organization is not
effective, the work procedure is susceptible to error, Data is not flexible, Data is not secure as
Page 82
well as it is not well organized. By having this over the existing system our aim was to build a
new system that have greater functionality that enhance effectiveness and efficiency related
parameters on the system. By keeping in mind that the new system will [have greater usage
on]/bring the existing system fully functional.
It is known that developing a web based system for Agmas Medical Importer company how is
importing manage by the system is not easy and system will facilitate the overall process of
importing products. But the team has developed interesting web based Import management
system for Agmas Medical Private Company. This system that allows the very soft relation
between the suppliers, Import Company & distributors.
It is flexible, accurate and attractive with easy GUI approach. Generally, the team confidently
can ensure that the software is completed successfully with negligible errors. makes it more
reliable and efficient than the previous manual system.
6.2 Recommendations
We would like to recommend that the system is open for interested groups or individuals who
wish to add new functionalities especially stock management. Next, the team would recommend
that further work should be done on the system in order to make the system fully functional like
official website.
Finally we would like to recommend to the Agmas Medical to use this system to enhance the
import management process by using our system.
APPENDIXS
Symbol Description
Actor
Use Case, Attribute
Message line extend from the lifeline, Entity

Attribute relationship
Starting point of activity/state diagram
Page 83
Entity
Ending point of activity/state diagram
Dependency line
Return message extend from the lifeline of one
object
Decision
Note
Activity
Boundary Object
Control Object
Entity Object
DB Database
SD Sequence Diagram
UC Use Case
UI User Interface
UML Unified Modeling Language
Reference
[1] Project Management Institute. 2012. PMI Lexicon of Project Management Terms. Available
fromhttp://www.pmi.org/lexiconterms
[2] Prentice object oriented software engineering using UML patterns and java 2010.third
edition. Munich Germany.
[3] Project Management Institute. 2013. The Standard for Program Management – Third
Edition. Newtown Square, PA: PMI.
[4] Project Management Institute.2013. Guide to project management body of knowledge-

PMBOK guide fifth edition Newtown Square, Pennsylvania
Page 84
[5] School of information management. Software project management- Second Edition
University of Brighton London.
[6] http://www.Alibaba.com.
[7] http://en.wikipedia.org/wiki/Web+application+security
[8] Ethiopian Ministry of Trade and industry
[9] http://www.agmas medical.com
Page 85

Arba Minch Institute of Technology (Arba Minch University) : Import Management System For Agmas Medical Private Company

Uploaded by

Copyright:

Available Formats

You might also like

Arba Minch Institute of Technology (Arba Minch University) : Import Management System For Agmas Medical Private Company

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

Arba Minch Institute of Technology (Arba Minch University) : Import Management System For Agmas Medical Private Company

Uploaded by

Copyright:

Available Formats

ARBA MINCH INSTITUTE OF TECHNOLOGY

(ARBA MINCH UNIVERSITY)

“Import Management System for Agmas Medical Private Company”

Group Members Name ID

Advisor: Mr. .Amare Kebede(MSc.)

A senior project report

Arba Minch University

Department of Computer Science and IT

Project Approval Sheet

1. Simon Birhanu RAMIT/1843/06

Advisor by Mr.Amare Kebede Examiner by 1.Mr.Prince .T …………………

Signature………………. 2. Mr.Abey Bruck…..……………

Arab Minch, Ethiopia

Arba Minch University

1.1 Background of Institute Agmas Medical...................................................................................1

1.3 Team composition..................................................................................................................3

1.4 Problem statement..................................................................................................................3

1.5 Objective of the Project.............................................................................................................4

1.6.1 Operational feasibility.....................................................................................................4

1.9.1 Data Source.....................................................................................................................8

2.2 Players in the existing system..............................................................................................12

2.5 Report generated in the existing system..............................................................................14

2.6 Forms and other documents of the existing systems............................................................14

2.7 Bottlenecks of the existing system.......................................................................................14

2.7.1 Performance (Response time).......................................................................................14

2.10 Requirements of the Proposed System...............................................................................15

2.10.1 Functional requirements..............................................................................................15

3.2 System Requirement Specifications (SRS)..........................................................................19

3.2.1 Use Case Model.............................................................................................................19

4.2 Class type architecture.........................................................................................................49

4.3 Class modeling.....................................................................................................................51

4.4 State chart modeling.............................................................................................................52

4.5 Collaboration Modeling.......................................................................................................58

4.7 Deployment mode................................................................................................................63

4.8 Persistence modeling............................................................................................................64

4.8.1 Database design.............................................................................................................65

Chapter Five: Implementation and Testing.................................................................................69

5.2 Final Testing of the system..................................................................................................69

5.3 Hardware software acquisitions...........................................................................................80

5.4 User manual preparation......................................................................................................80

5.6 Installation Process..............................................................................................................81

5.7 Start-up strategy...................................................................................................................81

Chapter Six: Conclusions and Recommandation..........................................................................82

Figure1 Schedule feasibility............................................................................................................5

Table 1.1 Team Compositions.........................................................................................................3

1.1 Background of Institute Agmas Medical

 To meet customers' demand swiftly and ethically

1.2 purpose of the Project

1.3 Team composition

1.4 Problem statement

1.6.4 Behavioral/Political feasibility

1.6.5 Schedule feasibility

 Time visibility of the project

Figure1 Schedule feasibility

NO Reason of cost Type Quantity Unit Price in Total Price in

1.7 Scope and limitation

1.9.1 Data Source

1.9.2Fact Finding Techniques