Fincha Sugar Factory Management System

UNIVERSITY OF GONDAR
FACULITY OF INFORMATICS
DEPARTEMENT OF COMPUTER SCIENCE
FINCHA SUGAR FACTORY MANAGEMENT SYSTEM
By Group members:-
Name ID
1. Habtamu Asayto GUR/01604/09
2. Taye Bitew GUR/01830/09
3. Wudie Alemneh GUR/01881/09
4. Getnete Alemnewu GUR/01586/09
5. Tirusew Giza GUR/01862/09
A group Project
Submitted to the department of Computer Science, Faculty of Informatics, and
University of Gondar in meeting the preliminary project requirement for partial
fulfillment of award of Bachelor of Science Degree in Computer science.
Gondar, Ethiopia
Date/Year: 02/06/2012
APPROVAL SHEET
This Group Project entitled Fincha sugar factory management system has been read and
approved as meeting the preliminary project requirements of the Department of Computer
science in partial fulfillment for the award of Bachelor of Science degree in Computer
science, University of Gondar, Gondar, Ethiopia.
Approved by:
1. Name of Advisor:
___________________________Signature:___________Date:________
2. Name of Project Coordinator:

___________________________Signature:___________Date:________
COMPUTER SCIENCE i
ACKNOWLEDGEMENTS
First and foremost, and above all our biggest thanks would be to Almighty God because
nothing could be possible without his help.
Secondly, we would like to express our deepest thank to our Adviser Instructor Fedlu
Nurhusien for his restless edition of our documentation, heart full guidance, valuable advice,
and providing to execute this project and also being a source of inspiration and for his
constant support in all phases of the project without boredom. He has been a constant
source of inspiration and motivation for hard work and very co-operative throughout this
project work.
Thirdly we would like the heart full thanks to Tsehay union employees and Mr Bekele
Tesema for giving the required information, answering our numerous questions and giving
reading materials that helps to us expected from them to precede our project.
Finally, we would like to thank to everyone who involved in our project.
COMPUTER SCIENCE ii
Table of Contents
APPROVAL SHEET ............................................................................................................................... i
ACKNOWLEDGEMENTS .................................................................................................................... ii
LIST OF FIGURES ............................................................................................................................... vi
LIST OF TABLES ................................................................................................................................ vii
ACRONYMS ....................................................................................................................................... viii
EXECUTIVE PROJECT SUMMARY .................................................................................................. ix
CHAPTER ONE ..................................................................................................................................... 1
1. INTRODUCTION .......................................................................................................................... 1
1.1. Introduction ............................................................................................................................. 1
1.2. Background of the project ....................................................................................................... 2
1.3. Statement of the problem and justification ............................................................................. 3
1.4. Objective of the project ........................................................................................................... 4
1.4.1. General Objective ........................................................................................................... 4
1.4.2. Specific objective ............................................................................................................ 4
1.5. Scope of the project ................................................................................................................ 4
1.6. Limitation of the project ......................................................................................................... 5
1.7. System Development Methodology ........................................................................................ 5
1.7.1. System development Approach ...................................................................................... 5
1.7.2. System Development Tools ............................................................................................ 6
1.8. Significance of the Project ...................................................................................................... 7
1.9. Beneficiaries of the project ..................................................................................................... 7
1.10. Feasibility Analysis ............................................................................................................... 10
1.10.1. Operational feasibility ................................................................................................... 10
1.10.2. Technical feasibility ...................................................................................................... 11
1.10.3. Economic feasibility ..................................................................................................... 11
1.10.4. Behavioral/Political feasibility ...................................................................................... 12
1.11. Project Schedule.................................................................................................................... 12
1.12. Project Budget ....................................................................................................................... 13
CHAPTER TWO .................................................................................................................................. 14
COMPUTER SCIENCE iii

2. REQUIREMENT ANALYSIS ..................................................................................................... 14
2.1. Introduction ................................................................................................................................ 14
2.2. Current system Description ................................................................................................... 14
2.2.1. Major function of current system .................................................................................. 15
2.2.2. Problem of Existing System .......................................................................................... 17
2.3. Requirement Gathering ......................................................................................................... 17
2.3.1. Requirement Gathering Methods .................................................................................. 18
2.3.2. Business rules................................................................................................................ 19
2.4. Proposed System Description ............................................................................................... 19
2.4.1. Overview ....................................................................................................................... 20
2.4.2. Functional Requirement ................................................................................................ 21
2.4.3. Nonfunctional requirements .......................................................................................... 23
CHAPTER THREE .............................................................................................................................. 27
3. SYSTEM MODEL........................................................................................................................ 27
3.1. Introduction ................................................................................................................................ 27
3.2. Scenario................................................................................................................................. 27
3.2.1. Use Case Model ............................................................................................................ 32
3.2.2. Use Case Diagram ......................................................................................................... 33
3.2.3. Description of Use Case Model .................................................................................... 34
3.2.4. Activity Diagram........................................................................................................... 41
3.2.5. Object Model ................................................................................................................ 46
3.2.6. Data dictionary .............................................................................................................. 47
3.2.7. Class Model .................................................................................................................. 53
3.2.8. Dynamic Modeling ....................................................................................................... 54
3.2.9. User Interface ................................................................................................................ 59
CHAPTER FOUR ................................................................................................................................. 62
4. SYSTEM DESIGN ....................................................................................................................... 62
4.1. Introduction ........................................................................................................................... 62
4.2. Current software architecture ................................................................................................ 62
4.3. Proposed software architecture ............................................................................................. 62
COMPUTER SCIENCE iv
4.3.1. System Decomposition ................................................................................................. 63
4.3.2. Hardware/ software mapping ........................................................................................ 65
4.3.3. Persistent data modeling ............................................................................................... 66
4.3.4. Access control and security........................................................................................... 67
4.3.5. Detailed class diagram .................................................................................................. 68
4.3.6. Package Diagram .......................................................................................................... 70
4.3.7. Deployment ................................................................................................................... 71
REFERENCES ..................................................................................................................................... 72
APPENDIX ........................................................................................................................................... 73
COMPUTER SCIENCE v
LIST OF FIGURES
Figure 1 - 1: Time schedule .................................................................................................................. 12
Figure 3 - 1: Use case Diagram............................................................................................................. 33
Figure 3 - 2: Activity diagram for login use case.................................................................................. 42
Figure 3 - 3: Activity diagram for Create account use case .................................................................. 43
Figure 3 - 4: Activity diagram for Order product use case ................................................................... 43
Figure 3 - 5: Activity diagram for marking attendance use case .......................................................... 44
Figure 3 - 6: Activity diagram for Manage finance use case ................................................................ 44
Figure 3 - 7: Activity diagram for view and send message use case .................................................... 45
Figure 3 - 8: Activity diagram for order transport use case .................................................................. 45
Figure 3 - 9: Object Model Diagram .................................................................................................... 46
Figure 3 - 10: Class Diagram ................................................................................................................ 53
Figure 3 - 11: Sequence diagram for login use case ............................................................................. 54
Figure 3 - 12: Sequence diagram for create own account use case ....................................................... 55
Figure 3 - 13: Sequence diagram for order product use case ................................................................ 55
Figure 3 - 14: Sequence diagram for approve order use case ............................................................... 56
Figure 3 - 15: Sequence diagram for manage finance use case ............................................................ 57
Figure 3 - 16: Sequence diagram for view and send message use case ................................................ 57
Figure 3 - 17: State chart diagram for Login use case .......................................................................... 58
Figure 3 - 18: State chart diagram for add attendance use case ............................................................ 58
Figure 3 - 19: Home page user Interface............................................................................................... 59
Figure 3 - 20: Login page user Interface ............................................................................................... 60
Figure 3 - 21: Administer dashboard page user Interface ..................................................................... 61
Figure 3 - 22: Create account page user Interface................................................................................. 61
Figure 4 - 1: System Architecture Model for Proposed System ........................................................... 63
Figure 4 - 2: Component diagram ......................................................................................................... 64
Figure 4 - 3: Deployment diagram ........................................................................................................ 65
Figure 4 - 4: Persistent data management ............................................................................................. 66
Figure 4 - 5: Detailed class diagram ..................................................................................................... 69
Figure 4 - 6: Package diagram .............................................................................................................. 70
Figure 4 - 7: Deployment diagram ........................................................................................................ 71
COMPUTER SCIENCE vi
LIST OF TABLES
Table 1 - 1: Software Development tools ............................................................................................... 6
Table 1 - 2: Hardware Requirements budget plan ................................................................................ 13
Table 3 - 1: Login use case description................................................................................................. 34
Table 3 - 2: Create own Account use case description ......................................................................... 34
Table 3 - 3: Order Product use case description ................................................................................... 35
Table 3 - 4: Manage Finance use case description................................................................................ 36
Table 3 - 5: Manage Schedule use case description .............................................................................. 37
Table 3 - 6: View and send message use case description .................................................................... 37
Table 3 - 7: Manage transaction use case description ........................................................................... 38
Table 3 - 8: Manage News use case description ................................................................................... 39
Table 3 - 9: Order transport use case description.................................................................................. 39
Table 3 - 10: Post job vacancy use case description ............................................................................. 40
Table 3 - 11: Apply to job vacancy use case description ...................................................................... 41
Table 3 - 12: Data dictionary ................................................................................................................ 47
Table 4 - 1: Access control and security ............................................................................................... 67
COMPUTER SCIENCE vii

ACRONYMS
API…………………………………………Application Program Interface
CSS…………………………………………Cascading Style Sheet
DB………………………………………….Database
DBMS………………………………………Database Management System
EC…………………………………………..Ethiopian Calendar
ESC…………………………………………Ethiopia Sugar Corporation
FSF…………………………………………Fincha sugar Factory
FSFMS……………………………………...Fincha Sugar Factory Management System
GB…………………………………………..Giga Byte
GTP………………………………………….Growth and Transformation Plan
HBA………………………………………..Holland association
HTML………………………………………Hyper Text Markup Language
HTTP……………………………………….. Hypertext Transfer Protocol
ID……………………………………………Identification
JS……………………………………………Java Script
LAN…………………………………………Local area network
MD5………………………………………… Message Digest 5
MYSQL……………………………………..Microsoft structural query language.
PHP…………………………………………Hypertext preprocessor
SQL…………………………………………Structural Query Language
UML………………………………………..Unified Modeling Language
WAMP……………………………………...Windows, Apache, MySQL, PHP
WPS…………………………………………Wi-Fi Protected Setup
XAMP………………………………………Cross-Platform, Apache, MariaDB, PHP
COMPUTER SCIENCE viii

EXECUTIVE PROJECT SUMMARY
Sugar industry is one of the largest agro-based industry in the world. In our country
perspective sugar industry projects are including under the biggest projects that takes more
than four million dollars to start production and it contains largest number of employees [1].
Fincha sugar factory management system is a system that minimize problems that are caused
by manual system that the factory is using at this time. Int this project we intended to change
current manual system into web based system with clear and simple interface to manage
activities of the factory. This project is very useful for customers to get important
information’s about the products at any time and to purchase products easily. It also
minimizing the work load of employees. Generally it provides fast, efficient, flexible, reliable
and secure services for customers and employees by automating and reducing unwanted
harassed and fatigue of them.
In order to achieve this goal we have proposed through this stage of life cycles: requirement
gathering, requirement analyzing, system designing, implementing, testing and maintaining.
For requirement gathering we use interview, observation and written documentation about the
Factories. For requirement analyzing and design we use Unified modeling language using
Software EdrawMax. For implementation phase we will use object oriented system analysis
and design development methodology by using programming language like MYSQL, HTML,
CSS, JS and PHP.
COMPUTER SCIENCE ix
CHAPTER ONE
1. INTRODUCTION
1.1. Introduction
Sugar Management System is an automated system aimed to manage all employee, customer
and other operation of the industries detaily with convenient way of accessing, retrieving and
storing of the factory information. This will help to improve ways in which services are
rendered to all customers and employee by increasing efficiency and reducing time taken to
deliver services. This sugar management system is designed and developed for Sugar
Corporation, customers, employee and other member of the industry to organize information
for creating convenient and quick way of interaction between customers through web. This
system intends to facilitate several steps in the process from visiting some important
information of the industry to the customer and employee registration and to more detail
employee and customer evaluation including transaction. During this process, there will be
many tasks that should be handled by this system including maintaining complete
information. Using this system administers of sugar corporation and employee of the factory
can provide maintainable information to the customer, administers can send schedule of
meeting to employee, can control inventories, manage purchase orders and other complex
tasks.
Currently in our world different factories and other business centers are performing their
operation based on computerized system. But in our country manual system is still executed
in many different organizations and business centers. Now a day’s ESC has a website to
publicize and to share some information’s about each sugar factories which is found in
Ethiopia because all sugar factories are controlled under ESC. But their system not including
detail management of each sugar factory including the distribution and purchasing of the
products. Wonji shoa, Fincha, Metehara, and Tendaho sugar factories are among the biggest
sugar factories in Ethiopia. Currently these factories performs most of their task manually.
Therefore, Employee of the factories waste most of their time to accomplish small task, the
services provided to the customer is not fast and fair. So, we propose this computerized
system to solve these problems.
1
INTRODUCTION
1.2. Background of the project
In Ethiopia modern sugar industry firstly started in 1946 EC at Wonji city. Initially it produce
around 1400 kuintal sugar in a day and 750,000 kuintal sugar in the year at Oromia region,
east arsi, Dodota zone, bishola woreda kebele gebere mahber. Notwithstanding it expand
again wongi sugar factory was closed after some years in 2004 and in 2005 because of
obsolete [2] [3].
After Wonji metehara sugar factory started the production of sugar in 1962 June 26 by
consortium of Ethiopian government and Holland foundation HBA. After expansion
currently metehara sugar factory can produce above 1.3 million kuintal sugar and 12.5
million liter ethanol.
Fincha sugar factory is the third sugar factory in Ethiopia which is started in 1967 EC at the
valley of Fincha. These factory is found around huro hudru wolega zone, in abay chomen
woreda, oromia region which is 350 km far from Addis Ababa. This sugar factory started by
the foundation of bukers agricultural international limited and the barrage of this factory
finished in 1991 by producing around 110,000 ton sugar and 8 million liter ethanol in the
year. Fincha sugar factory use Fincha River for planting sugar cane and other plants which
used as raw material for sugar production and this river is found at the west of the factory by
covering around 20,000 hectar. Fincha sugar factory totally covers (command area) 67,098
hectar [2] [3].
Wongi Shoa and Fincha sugar factories have successfully started their regular work with high
production capacity as of October, 2006 EC after completing their expansion project. The
expansion work has significantly upgraded the production capacity of the factories while it at
the same time has expanded their cane cultivation land. Accordingly, Fincha Sugar Factory is
expected to produce 2 million quintals of sugar in 2006 EC in Ethiopian budget year. The
amount has additional 900 thousand quintals when compared to the factory’s previous best
production record. When it reaches its full production capacity, Fincha Sugar Factory is
expected to produce 2.7 million quintals of sugar annually. Current production design
capacity of Fincha Sugar Factory is 270,000 tons of sugar and 20,000m3 of ethanol per
annum [3].
Fincha, metehara, Tendaho, Wonji shoa and other Sugar Factories organization is broadly
categorized as agricultural operations, factory operations and services. Agricultural
COMPUTER SCIENCE 2
FINCHA SUGAR FACTORY MANAGEMENT SYSTEM 2012E.C
operations encompasses the activities of growing cane, harvesting and transporting to factory
whereas factory operations looks after receiving the sugar cane as raw material, and
processing it to the final product, white sugar, ethanol and other by products like molasses for
comestible of animals. Service is responsible for administration, finance, inventory, and
budgeting, purchasing and other activities.
Generally, at the current situation Fincha sugar factory reserved around 3260 permanent
employee, 208 contrat employee and 9496 seasonal employees. Averagely based on the
above data each sugar factories have more than 10,000 number of employees. The seasonal
employees are mainly for cane cutting which are organized under agricultural operations.
Their duty is seasonal in nature i.e. for 7 to 8 months per year, and will be layoff for the
remaining months [4].
1.3. Statement of the problem and justification

Sugar manufacturing is one of the major focus areas in Ethiopians growth and transformation
plan as an important component of industrial development for economic transformation.
Fincha Sugar Factory is hence one of the factories where expansion project had been carried
out to increase its production capacity from 110,000 ton to 270,000 ton of sugar per annum
during the GTP period [5].
Currently there is a system that cooperate and share statistical information’s of all sugar
factory which is found in Ethiopia, but this system does not manage and contain detail
activities of each sugar industries; therefore most of sugar factories use manual system to
perform their action. Without well-structured system this type of largest industries are very
difficult to accomplish and manage tasks (activities) easily, efficiently and effectively. This
working system cannot allow to control many operations of the factory through production
process and does not create fair distribution of product to customer.
This sugar factory performs difficult activities though production and after production for
purchasing, distribution and exchanging purpose. Performing this type of activities using
manual system is very difficult.
Generally the current existing system is difficult to control/calculate the whole activity and
the whole assets of the factory, information’s are stored on a paper, it is difficult to update
and modify the data, High work burden for the employee and consuming much time and
COMPUTER SCIENCE 3
INTRODUCTION
money, there is no guarantee and security regard to stored information because; if storage
paper is damaged due to any case there is no way to backup information, difficult to share
information between customers and employee, employee and employee. Through the current
system data handling is very tedious because it is stored manually on a paper.
1.4. Objective of the project

In this section we explain general and specific objective of the project.
1.4.1. General Objective
The general objective of the project is to design and develop web based Fincha sugar factory
management system.
1.4.2. Specific objective
Specific objectives are objectives that help to achieve the general objective of the system.
Here are some specific objectives that would together help us to achieve the overall goal:
✓ Understand the current existing system of the factories

✓ Identify and know major problems
✓ Identify functional and non-functional requirements
✓ Design attractive user interface.
✓ Design database based up on analyzed data
✓ To test our system by using different testing methodology.
✓ To implement the system based on software specification to solve the problem on
existing system.
✓ To create clear and attractive system of financial information’s of the factories to
control the product and finance/budget of the factories that protect unnecessary
wastage of money from corruption.
1.5. Scope of the project
Scope is the coverage area or the boundary that the project covers and the activities or
operations that is performed by the system.
The scope of our system is to manage and control Ethiopian sugar factories especially we
design this system for Fincha sugar factory. Any sugar factory can use this system by adding
COMPUTER SCIENCE 4
necessary platform, because in Ethiopia sugar factories have similar activities and tasks. This
system keep track of purchasing system activities such as request, process, purchase, report,
payment, address final result of the factory. It can manage and control products and materials,
inventory accounts, sales and buy accounts, calculate and control whole asset of the factory
easily, budgeting and forecasting the capital of the factory, payroll systems, personnel
systems and other essential activities of the factories. Blind users can not able to use this
system.
1.6. Limitation of the project
This proposed system does not cover some activities due to the shortage of time, information,
resource, capability and other external factors. These are:-
✓ The proposed system cannot accessed using local language.

✓ Only literate persons can use this system.
1.7. System Development Methodology
System development methodology is used to structure plan and control the process of
developing an information system. In our project, we used object oriented system analysis
and design (OOSAD) because OO focuses on data rather than the procedures and it support
reusability of code. Therefore, the time and cost of development is inherently less. It includes
essential class diagram, system use case diagram, use case descriptions (scenarios), sequence
diagrams, activity diagrams and state chart diagrams.
1.7.1. System development Approach
There is several software approaches used to develop software. From that approach we
choose object oriented development approach because the Object oriented system
development approach gives easier way to break down problems into simple and small
components so that it reduces the vague appearance of the big problem..
Generally we select this type approach due to the following reason:
✓ It is a way to develop software by building self-contained modules or objects that can

be easily replaced, modified, and reused.
COMPUTER SCIENCE 5
INTRODUCTION
✓ The team can manage the complexity of software systems easily through this
approach.
✓ Identifying the source of errors becomes easier because objects are self-contained
(encapsulation).
1.7.2. System Development Tools
To develop the proposed system, we use different hardware and software tools for different
purpose.
Software Tools: - This project uses the following system development tools for different
activities.
Table 1 - 1: Software Development tools

Tools Activities
Notepad++, Notepad, Sublime, Atom, Visual For coding PHP web language
Studio.
CSS For making attractive layout
PHP Back end (Server side coding)
HTML Client side coding
MYSQL Back end(data base)
WAMP,XAMP Server For storing user information
Mozilla Firefox, IE, Google Chrome, Opera, Browsers

Baidu browser, Microsoft edge
Ms office word 2007, WPS 2019 For Documentation
Ms office PowerPoint 2007, WPS 2019 For Presentation
Edraw Max7.0.0.0 To draw UML Diagram and for designs
Adobe Photo Shop CS6 To design back ground images
Hardware:
✓ Laptop computer: used to deploy and implement the system.
✓ External Hard Disk
✓ Flash Disk 16GB: used for backup.
COMPUTER SCIENCE 6
✓ Printer: used to print files.
1.8. Significance of the Project
The new sugar factory management system is reliable, easy, fast and consistent system. It
will play a crucial role for the factory, factory employees, branch employees, and for
customers. The significance of the system includes:
✓ User friend ness is provided in the application with various controls by creating
attractive interface.
✓ To minimize time and efforts needed to perform complex tasks.
✓ To manage the employees, customers, transaction information and other important
operations of the factory easily.
✓ To create favorable condition for purchasing products online.
✓ Providing a well-organized and guaranteed record keeping system with minimum
space and effort need.
✓ Readily upload the latest updates by a legitimate user.
✓ To enable employee and customers sharing information using attractive discussion
page.
✓ To provides high level of security with different level of authentication.
✓ To avoids data redundancy.
✓ To increases the security and efficiency.
✓ To Representing important information using different formats like chart and graphs.
✓ To Create easiest way of sharing information between employee and customers.
✓ Job seekers can easily apply for the job in the factory and employer easily select the
job seekers based on criteria and educational documents.
1.9. Beneficiaries of the project

The newly proposed system is benefited for employee, customers, Developers and any other
users of the factory. The factory can change most of operation into computerized
environment, which improves the quality of internal operations like accuracy, timeliness,
reliable, secured, relevant and valuable data usage for the financial departments. The quality
and performance of working system improved by reducing manual activities. Employees can
improve management and control system of their job.
Employee:
COMPUTER SCIENCE 7
INTRODUCTION
✓ Employee can help customers without time consumption and without boredom.
✓ They can search and retrieve indispensable information’s easily based on their
authority.
✓ Can see schedule and appointments.
✓ Can send and retrieve information to any member of the factory using private
messaging system.
✓ Reduce unnecessary workloads and wastage of time.
✓ Can view and share information with other employees and customers easily and
quickly.
✓ Reduce incorrectly fill in financial operations by using easy way of calculation.
✓ Can record and view products of the factory.
✓ Can record attendance easily.
✓ Can retrieve latest news about the factory from news portal of the factory.
✓ Effectively manage data statistically.
Developers:
✓ Obtain knowledge and experience from it.
✓ Use it for partial fulfilment of degree program.
✓ Gain income if it is complete.
✓ Can get mental satisfaction.
Customers:
✓ Can get indispensable information about the factory and the products.
✓ Can get equal access about information of the factory and distribution of products.
✓ The system manage and store their information securely.
✓ Reduce time, energy and money that they waste to go to the factory to get service, to
send request and to get permission for transaction.
✓ Authorize user easily change data, register and view.
✓ Can easily order products of the factory online (purchase) with transport system.
✓ Can get detail information about the branch of the factory.
✓ Customers can send and submit their complain and feedbacks to the manager of the
factory.
✓ Can easily register and get information’s from free discussion by asking and
answering with other customers and employee.
✓ Can get enhanced accuracy, speed, and security of services.
COMPUTER SCIENCE 8
✓ It enables to interact with the system easily because the system is user friendly.
Organizations (Sugar factory)

✓ Economically get benefit because man power will decrease and the money which is
paid for workers will be saved.
✓ Can decrease unwanted wastage of money for report.
✓ Automated data inserting, updating, retrieving on the database more organized,
secured and faster way.
✓ Can manage, handle and control the community of the factory including customer,
employee.
✓ Can control the distribution of the product and other byproducts carefully without
partiality.
✓ Can increase the number of customers by creating favorable conditions.
✓ Manage profit and loose in each day, week, month and year.
✓ Manage branches of the organization.
✓ Easily post and change schedule any appointments (meeting) for employee and
customer of the factory.
✓ Can create favorable condition for exporting and importing easily.
✓ Presenting important information’s using News portal.
✓ Can employ new workers without additional wastage.
✓ Can get customer’s and employee’s feedback easily.
✓ Can manage job vacancy portal for employing new job seekers.
Administrators(Factory Administrator)
✓ To manage the data easily.
✓ To update the information easily.
✓ To control and manage the whole activity of the factory.
Job applicants
✓ Online registration and reservation of vacancy for the person who want jobs.
✓ The job applicants can easily find jobs and applying to the job that they want online
using the website.
✓ It reduces transport cost and time for applying to the job.
Ethiopian Sugar Corporation (ESC)
COMPUTER SCIENCE 9
INTRODUCTION
✓ Can manage and control Production and Transaction processes of each Factory. This
helps to protect unfair distribution of the product and reduce Corruption.
1.10. Feasibility Analysis
Assessing feasibility means answering questions relating to the utility and capability of the
system that is going to be developed. This means answering the question is it cost-beneficial
to develop the proposed system? Is it possible to develop the proposed system? To answer
these questions, we conduct various kinds of feasibility analyses listed below.
1.10.1. Operational feasibility
The Proposed systems are beneficial only if they can be turned out into information system
and user friendly that meets the organization’s operating requirements. Operational feasibility
aspects of the project are to be taken as an important part of the project implementation.
Some of the important issues raised in Fincha sugar factory management system are to test
the operational feasibility of a project includes the following:
✓ Is the new system being easy for access and acceptable by the users?
✓ Will the system be used and work properly without failure if it is being developed and
implemented?
✓ When some serious problems were occurred, is the system will be easily maintained
by the team?
This system is targeted to be in accordance with the above-mentioned issues. In advance the
management issues and user requirements have been taken into consideration. So, there is no
question of resistance from the users that can undermine the possible application benefits.
We will propose the system which are operationally feasible and the project will be:
✓ User friendly and easily understandable to users.

✓ Reduce information redundancy which is a major problem in existed system.
✓ The system can be implemented easily.
COMPUTER SCIENCE 10
1.10.2. Technical feasibility
It is about how the organization (Fincha sugar factory) accesses the developed system. It is
also the measure of practicality of the specific technical solution and the availability of
technical resources (like hardware and software) and know-how the proposed system is also
simple to manage and maintain. Therefore, the new system is technically feasible.
The technical issue usually raised during the feasibility stage of the investigation includes the
following:
✓ Does the necessary technology exist to do what is suggested?
The system is going to be developed by technological development technique such as PHP

language with the XAMP Server and notepad++, Sublime, Atom and Visual studio editors,
MYSQL database to store files, Microsoft word and WPS for writing document, HTML,
JavaScript and CSS. The system that we going to develop is familiar with new technologies
and easy to understand by the system users. The technical feasibility issues usually raised
during the stage of fact finding includes the following:-
✓ This software is running in windows and Linux operating system.

✓ The system can be expanded in any system platforms.
1.10.3. Economic feasibility
Economic feasibility attempts to weight the costs of developing and implementing a new
system, the cost of developing and implementing a new system is less than the cost that
finding benefit from the developed system. This feasibility study gives the top management
and the economic justification for the new system. There for the system is economically
feasible. In our system, we will consider the following benefits.
Tangible Benefits: These benefits can be estimated in terms of money which means the
benefit is real or actual rather than imaginary or visionary. Since this project is going to be
online or LAN system, there is reduction of cost for material that used for manual operation,
save time and make comfortable working environment for the users.
Intangible Benefits: These are benefits to the organization but which cannot easily be
measured in monetary terms.
COMPUTER SCIENCE 11
INTRODUCTION
✓ Increasing the moral satisfaction of the organization’s employees.
✓ Increase accuracy.
✓ Gaining knowledge.
✓ Increasing the competitiveness of the individual.
✓ Faster decision making in organization.
✓ Facilitating information processing of organization system.
1.10.4. Behavioral/Political feasibility
The system to be developed is not conflict with any government directive. It also stated that
the developed system is must be meet to the rule and regulations of the organization and it
never contradicts with legal and criminal laws of the country. Because it gives services for
the people effectively and efficiently. So, the system will be politically feasible.
1.11. Project Schedule
Time schedule is a process of assigning the degree to which the initial time and completion
date for all major activity which in a project meet organizational deadlines. So, our project
will be accomplishing within months.
The figure below shows the time schedule of our project:
2019 2020
ID Task Name
Nov Dec Jan Feb Mar Apr May Jun
1 Project proposal
2 Requirement analysis
3 System design
4 Implementation
5 Testing
Figure 1 - 1: Time schedule
COMPUTER SCIENCE 12
1.12. Project Budget

Table 1 - 2: Hardware Requirements budget plan
No Materials Required Amount Unit Price (birr) Total Cost
1 Laptop 1 13500 13500
2 Print 400 1 400
3 Flash Disk 1(8G), 1(16G) 120,220 340
Total 14,040
COMPUTER SCIENCE 13
CHAPTER TWO
2. REQUIREMENT ANALYSIS
2.1. Introduction
Detailing System Requirements is the initial step of constructing the whole system. It is a
description of the project requirements that we have been gather and analyze. Without
requirements, the goal is unclear and the construction may be off track [6]. The document is
provided in order to ensure that the systems we produce will be consistent with the need of
the system’s user. Stating these requirements explicitly helps insure that any potential
miscommunications are corrected at early stage. The Factory gives different services in
addition to regular services without any additional payment such as importing and buying
necessary machineries and raw materials, planting raw materials like sugarcane, producing
sugar product and other by products like ethanol, feed of animals, distributing of the product
to the customers in different ways. When we see the distribution of the product to the
customer the current system does not provide effective information for users.
2.2. Current system Description

Most of the existing system is manual systems that put pressure on workers to be correct in
all details of their work at all times. This system is complex and prone to error. Before
moving into the major system design building blocks of this new system we need to analyze
the existing system and identify their weaknesses. System is dependent on good individuals,
reduction in sharing information and customer services, time consuming and costly to
produce reports, lack of security, and duplication of data entry. This leads to unsatisfactory
and very difficult to work.
Generally existing system has the following characteristics:-
✓ Reporting and checking the data is robust can be timely and expensive.
✓ Latest news and information’s are not shared to employees and customers of the
factory quickly.
✓ The distribution (transaction) of the products and byproducts is complex to control
efficiently.
✓ There is no a modern system that searches file of the employee and customer. This
manual system is difficult to update otherwise it wastes a lot of time and money.
✓ Loss of personal information.
✓ Salary payment is still manual.
14
✓ It is difficult to view someone’s profile.

✓ Low speed and efficiency.
2.2.1. Major function of current system
1. Administer / main director
✓ Pursue and manage whole operations.

✓ Scheduling meeting.
✓ Create cooperation between employees.
✓ Prepare report.
2. irrigation and building Fringe
✓ Building new irrigation and building for the factory and community of the factory.
✓ Renewing old irrigations and building.
✓ Conservation of the factory environment.
3. Operations Fringe
✓ pursuit the machineries and sugar cane farming
4. factory community Accumulator Fringe
✓ Arrangement and build up, cooperation, pursue sugar cane production in small
institutions.
✓ People correlation around the factory and planting areas include satisfy the claim and
complains of the people.
✓ Create favorable condition for the family of employee in factory.
5. Commercialization Fringe
✓ Sugar, ethanol and other byproducts mart (market) research and promos ion.
✓ Navigate the distribution of product (sugar, ethanol and molasses) in side of the
country.
✓ Managing exporting of product and logistics management.
6. training and checkup
✓ Training for how produce sugar cane for new seasonal employees.
✓ Sugar cane and other raw materials breeding development to increase production of
raw material.
COMPUTER SCIENCE 15
REQUIREMENT ANALYSIS
✓ Create favorable condition to give training for employee of the factory by experts
about sugar machinery technologies which is invented from our country and invention
of other developed country on important machineries.
7. planning project
✓ Planning corporate policies.
✓ Operation planning.
✓ Pursue, control planning.
✓ Planning training on projects.
8. human resource Management Fringe
✓ Navigate and control human resource of the factory properly.
✓ Facilitate employee and employee, employee and customers, customers and
customers with industry correlation.
✓ Expand and enlarge human resource system of the factory furtherance.
9. Finance
✓ Financial and other ramify operations of the factory.
✓ Pursue, manage and control finance and administer funds of the factory.
10. Sugar cane production and Industry Building fringe
✓ Furtherance sugar cane plants and other raw materials supplied and production.
✓ Building important infrastructures for improves the production of sugar.
11. Corporate caizen design
✓ Design and spread variety transformations systems in the factory
✓ Manage and Pursue caizen.
✓ Design new working principle programs.
12. Buy and sell / export and import
✓ Buy materials (machineries, raw materials and etc…).
✓ Capital and faculty management.
13. Byproduct and other agro-proceedings of the factory
✓ Prepare food of animal from sugar byproducts by combining other by products.
✓ Prepare natural fertilizer from sugar and ethanol byproducts.
✓ Planting other crops beside of the sugar cane such as sugar potato, vegetables and
other supportive plants.
✓ Dry lot finishing cattle’s.
COMPUTER SCIENCE 16
✓ Breeding cows and producing milk and dairy products beside of the main sugar
production.
✓ Planting fruits.
14. Machinery spare apart and repair machineries
✓ Machinery, farm machineries, transport cars, motor bicycle, irrigation pumps,
generator and other spare apart fulfilment.
✓ Repairing important machineries such as construction, barnyard, small and heavy
machineries, irrigation design pumps, epiphytes apparatus and motor bicycles, fixing
service concentric.
2.2.2. Problem of Existing System
Since it is manual based the existing system and customers have faced many problems.
Among those problems the problem of data management is the core one because data is not
easily accessible, not well organized, not secured from damage and it is stored redundantly in
the form of multiple copies of files. Since it is manual based the system is not efficient, do
not give better quality service to the customers so the customer is not satisfied with the
service. Employee cannot efficiently manage and control activities in the factory.
Generally the existing system has the following problems:-
✓ Requires more time and effort to perform tasks.

✓ Difficult to search, update, modify and access particular employee and customer
information when the numbers of employees become large.
✓ Managing is difficult when the number of employee increase etc.
✓ Inconsistence of data: there will be unavailable for feature use, because notice might
get misplaced during manual notice management.
✓ It is difficult to control and secure these manual records, since it does not have any
authentication and authorization system.
✓ It consumes resources like papers, man power, time, pen etc. Therefore the existing
system cost is in terms of the above factors very high.
2.3. Requirement Gathering

The method to be used for achieving the development of this project is based on need of
getting appropriate information related to the factory and sugar transaction and distribution
COMPUTER SCIENCE 17
for the customers. For the purpose of getting appropriate information we used the following
types of data gathering methodologies including Interview, direct observation, and document
analysis.
2.3.1. Requirement Gathering Methods

This section describes the methods that we used to gather data and what data we gather by
using the methodologies. These includes: -
Observation
We observed how the factory distribute and purchase sugar product to the people and
customers. This customers are either unions/associations in each regions or candy industries.
We also observe real forms that the current system is using to register customers to purchase
sugar products from sugar factories.
Interview
To get important information about the factories and distribution system of sugar product we
are interviewing some customers (unions/association) of the factory and Ethiopian sugar
corporation employees through head-on, phone and email. We prepare some questionnaires
for that (look appendix).
Finally we can get important information about the factory that includes work division of
employees, the process of white sugar production, living conditions of the community of the
factory, rule and regulation of the factory, the process of product distribution and others.
Generally we gather information about problem and barrier of the existing system.
Document Analysis
To get more information about the project we used earlier documents that help us to develop
this project. During the analysis of documents, we considered those documents which can
bring more features to the project relevant to develop the proposed system. Sugar factories
are far from our city to observe and interview the employees face to face, we cannot going to
there because of lack of money to transport, there for we select documents as major data
collection methods from the internet about the factory.
COMPUTER SCIENCE 18
2.3.2. Business rules
Business rules are rules that are used as guide to perform all tasks according to the rules and
regulation. The following are some of the business rules of Fincha sugar factory in the current
time.
Rule 1: Each employee has a unique employee ID and a profile. The profile includes First
name, Last name, sex, Age, salary, and also other necessary information in general it
contains detail personal information.
Rule 2: Each employee and customers must have legal account to login with their own
user name and login password to the System to do over all activities.
Rule 3: All information of customers and employee should be kept in one record office.
Rule 4: Employer should have to check if the Applicants document fulfills the minimum
requirements of the posted job, then approve applicants and reject if not.
Rule 5: users can access their own History.
Rule 6: The factory should have to secure the customers personal file.
Rule 7: All employee should respect the right of others.
Rule 8: Each employee should come at the work place on the time, otherwise wage of late
employee is discounted.
Rule 9: Employee should use materials and machineries carefully.
Rule 10: Employee should work 48 hour in the week, if employee need he/she can works
overtime to get additional payment.
Rule 11: employees are not allowed to come in work place after drinking alcohol.
2.4. Proposed System Description
The new system deals with automating the system that Fincha sugar factory is using. It is
efficient in facilitating different tasks in the factory, like online customers or employee’s
registration by giving unique username and giving them authority as they deserve, easily
retrieve/ handling information’s, to delete and update customer and employees account,
easily sharing of information between employees and customers.
This new proposed system can increasing accuracy, reducing the rate of increase in costs in
labor-intensive activities, increased effectiveness, and permits decentralized access to
records. In addition to this, Offices and suppliers can see the status of an order without
changing files and without travelling to the order department to interrupt their work in order
COMPUTER SCIENCE 19
to find out and check to see whether a request/material is ready, departments and branches
can request their purchasing needs online without travelling to the order department offices.
2.4.1. Overview
Based on the problem of existing / current manual system understanding all the problems
occurred during every activity on, we desired to design a system that solve the problems of
the current system. The new system designed will help the management to use computer
system to find customer, employee and product information with regards to view customers,
employee and products detail, purchasing, easily allow to information sharing and etc. Every
data regarding every information about the factory and the customer is stored at the central
database in high capacity server. Accuracy is maintained, as the computer information will
yield an accurate result. The speed of operation of the factory system in production process
and purchasing products become very high when compared to manual method. The software
performs every mathematical computation like calculate number of employee (number of
contrat employees, number of seasonal employees, and number of permanent employees) in
each month, half year and year, and count number of relationships with other organizations.
The system show profit/Income, loose/Expense, forecasting and previous capital of the
factory in each day, week, month and year.
This new system can reduce unnecessary stress of employee of the factory by creating
favorable and attractive system. This system will do the analyzing and storing of information
either automatically or interactively. It will make use of online access to Internet.
The proposed system will also have some other features like: -
✓ Gives accelerated service for all users and this users can register in to the system
securely.
✓ Users can login to the system using their own account based on their authority and
position (Administer, Employee, Customer...). Any unauthorized person can't
enter in to the system.
✓ Can search required information.
✓ Admin system can manage all data base of the Factory. System identifies registered
person and unregistered person.
✓ Users can handle accurate data about their profile and information of the factory.
COMPUTER SCIENCE 20
✓ Fast rate of operation and excellent response time.

✓ The system is flexible i.e. it can be accessed at any time.
✓ Easy way of back up or duplicating data in diskettes in case of data loss.
✓ Better storage and faster retrieval system.
✓ There is private messaging and group messaging system for sharing information
between employee and customers.
✓ There is also news portal system for posting latest news about the factory and
commercialization systems. Therefore necessary information’s are accessed by user of
the system on time.
✓ Factories can easily manage inventory system.
2.4.2. Functional Requirement

The functional requirement is fundamental building block requirements that directly related
to the function of the system. It is a statement of exactly what the system must do and It can
also be defined as a description or statement of function, feature or condition that a user seeks
to have implemented in a system or it is a function or feature that must be include in an
information system to satisfy the business needs and be acceptable to the users and solve the
problem in the current system. Generally Functional requirement is describing the interaction
between a system and its environment [5].
The following are the functional requirements of the system.
For sugar factories
A. Administer
✓ Manage Accounts: The system allows the administrator to manage employees and
customers account of the factory in case of updating, deleting, and creating new
account.
✓ Activate and deactivate the users: based on credential administer can activate and
deactivate employees and customers account.
✓ Retrieve All information: administer can manage and view any information in the
system.
✓ Generate Report: the system allow administer to view customers and employees
history, transaction/purchase history, financial information and generate report for it.
COMPUTER SCIENCE 21
✓ View feedbacks and orders: Administer can view the feedbacks of customers and
employees about the service that factory is giving.
✓ Manage Budgets: administer manage budgets and planning maintenances for
facilitating the production process.
✓ Manage branches/sections: Metehara, Wonji, Tendaho, Fincha sugar Factories are
largest sugar Factories in Ethiopia, therefore it should have to manage through
dividing by departments in different section based on their task to simplify operations.
✓ Scheduling meeting and appointments: announces meeting/appointment date.
✓ Manage Transaction/distribution: record, store and calculate purchase information
quickly with simple calculation method.
✓ Control Import and exports: manage/control the export to other organizations which is
from other countries such as sugar product, ethanol and other important byproducts
and the import of important new technologies, raw materials and machineries for
facilitating the production.
✓ Hold backups of the record: there may be depredation of the record by unexpected
accidents, therefore administer can back up the records.
✓ Manage own account: administer can view, update and increase security for their own
account.
✓ Manage product: Fincha sugar factory produce around 750 ton sugar product 60m3
ethanol in a day and 270,000 to sugar and 20,000 m3 ethanol in a year, therefore this
huge number of product should be managed and distribute to the customers carefully
by the administer.
✓ Manage payroll: based on the budget of the employee administer can manage and
Calculate the wage of each employee.
✓ Manage Billing and financial information’s: Record and Calculate for the expenses
and income of the factory.
✓ Post latest news and job announcement: administer post and announce latest
important information and jobs.
✓ Calculate interest rate for loan and deposit money.
✓ Register daily income: the user easily announce the day to day works in order to know
the tax amount.
B. Employee
✓ Employee can create their account with login username and password.
COMPUTER SCIENCE 22
✓ Can view and update their own account/profile.

✓ View schedules and notifications from administer and employee of the factory.
✓ The system allows new job applicants to see the posted job and login to the system
using their user name and password.
✓ Can share information with other employees through notification system.
✓ System allows to all employee to show the recorded product, customer and other
important activities.
✓ Can send their displeasure to administer of the factory.
✓ Generate report about the done task. Report may be daily, weekly, monthly or
annually work.
✓ Can count and record outgoing products from the factory into the database.
C. Customer (Capital cities, Regions, Zones, Woreda, Kifle Ketema corporations)

✓ Create, update their own account.
✓ View posted latest news.
✓ Search and view products.
✓ Send Comment / feed backs: - The system shall allow users to send feedback to the
employee and administer of the factory.
✓ Customer send order request by filling product detail based on their need.
✓ Zone commerce director Moderate, adjudge and order the amount of sugar which is
needed by Tsehay union (association) or other known associations based on their
order and send letter to the union/ association easily. After receiving the letter from
zone commerce the union/association can easily send/order the product to the factory.
D. Transport associations
✓ They can easily participate to the tender to transport sugar into the customer store
from factory stores using the system.
✓ Winner of tender can easily transport the product using map / direction, distance
indicator.
2.4.3. Nonfunctional requirements

Non-functional requirement is a requirement that specifies criteria that can be used to judge
the operation of our system, rather than specific behaviors. This should be contrasted with
functional requirements that define specific behavior or functions. Non-functional
COMPUTER SCIENCE 23
requirements are often called qualities of a system. Other terms for non-functional
requirements are constraints, quality attributes, quality goals and quality of service
requirements. Non-functional requirements are often more critical than individual functional
requirements [5].
Generally, the system has the following non-functional requirements to achieve its
functionality are Performance, Scalability, Availability, Reliability, Maintainability, Security,
Environmental, Usability and Interoperability.
2.4.3.1. Performance
Performance is characterized by the amount of task that are accomplished by a system within
given time and resources used.
The performance of our system improve through the following characteristics:
✓ Use short response time for performing tasks using proposed project.
✓ High efficiency.
✓ The system shall support use of multiple users at a time.
✓ It works very well with short response time, high availability. System must stay up 24
hours a day within 7 days in a week.
✓ Reduce costs and time waste by providing access to system in available place and
time where Internet connection is available.
2.4.3.2. Scalability
Fincha sugar factory is the largest sugar industry in Ethiopia, but still now Ethiopia Sugar
Corporation can not satisfy the need of the customers. Therefore this factory will be
expanded in the future to satisfy the need of the customer. The number of employee, amount
of production and budget will expand in the future. To overcome this problem proposed
system is easy to modify (scalable) by the users.
✓ Can add new feature and functionality.
2.4.3.3. Availability
Availability The probability that a system, at a point in time, will be operational and able to
deliver the requested services. The availability of a system is the probability that it will be up
and running and able to deliver useful services to users at any given time [5].
COMPUTER SCIENCE 24
✓ The system is available at anytime from anywhere where there is an internet

connection or if there is LAN.
✓ The users of system can access the system successfully.
2.4.3.4. Reliability
Mean time to failure Probability of unavailability Rate of failure occurrence Availability. The
system is expected to perform perfectly/smoothly without major errors and failure. The
system should satisfy the user and should be fault tolerant. Reliability is one feature of the
system significantly validates user inputs
To achieve this:-
✓ We will install our system on high quality hard wares.

✓ Back up regularly.
✓ Control external factors like power loss as much as possible.
2.4.3.5. Maintainability
Maintainable software is software that can be adapted economically to cope with new
requirements, and where there is a low probability that making changes will introduce new
errors into our system.
To achieve the maintainability of our system:-
✓ The user interface of this system is user friendly and interactive so it is easy to fix
while errors occur. The failure of the system causes many problems repairing the
system must not be difficult since users to easily fix the problem.
✓ The system will be modifiable at any time to enhance features based on the need of
our country.
2.4.3.6. Security
Security is a system attribute that reflects the ability of the system to protect itself from
external attacks, which may be accidental or deliberate. The security service provided by the
system maintain the security, confidentiality and integrity of the system [5].
To overcome this security problem of our system should be:-
✓ Only accessed by authorized persons and on their privileges. This all activities are
managed by administer. Unauthorized customers cannot allow to login in to the
employee page. Employees also cannot visit administer page.
COMPUTER SCIENCE 25
✓ Login with two layer authentication (user name, password) based on the position of
the user. Without login by using (copying, pasting and searching) URL cannot access
any data and cannot be backtracking to the system after logout.
✓ Use session to restrict users from accessing page without their privilege so we will
give session time that it will expire after the time passes.
✓ Protected the system from access of external intruders by using password encryption
methods like SHAL, MD5 and etc.
2.4.3.7. Environmental
The environmental conditions in which the system functions are part of the requirements.
This environmental requirement such as hardware, platform operating system, and other
software changes. The proposed system is environmental to change hardware and software
requirements.
2.4.3.8. Usability
This property reflects how it is easy to use our system. It depends on the technical system
components, its operators, and its operating environment [5].
It also includes the following points:-
✓ Every one authorized to use the system can use it without any difficult.
✓ The system is easy and understandable to use since it does not require much more
expert or skill.
✓ More efficient to use-it takes less time to accomplish a particular task by designing
attractive and interactive user interface.
✓ More satisfying to use.
2.4.3.9. Interoperability
Interoperability is the ability to share information and services. Defining the degree to which
the information and service are to be shared is a very use full architectural requirement,
especially in a complex organization and extended enterprise.
It includes the following points:-
✓ The proposed system will be use API system to allow other organizations and any
other users to share specific information of the system.
COMPUTER SCIENCE 26
CHAPTER THREE
3. SYSTEM MODEL
3.1. Introduction
In this chapter we discusses use case diagrams, use case documentation, class diagram,
activity diagram, sequence diagram of the new system.
3.2. Scenario
Scenario Name: login
Participating actor: System administer, Customer, employee, Transport association’s
director.
a. Ethiopian sugar Corporation Actors: - corporation Manager.
b. Sugar factory actors: - Factory manager, Finance and Human Resource Manager,
wholesaler.
Event
User browses the system and systems display home page that contain login link. User click
login link, system display login form. Then user enters username and password the system
checks weather the username and Password is valid. If it’s valid user login to the system and
the system displays available user page based on their authority. If the entered values are
incorrect error message is displayed and systems promote the user place enter user name and
password.
Scenario Name: Manage own Account

Participating actor: System administer, Customer, employee, Transport association’s
director.
purchasing (buy/sell) manager.
Event
The user log in to the system with user name and password. System displays manage own
account menu, then user can select manage own account menu. System display enter personal
detail of the user with old password, new and confirm password. User fills the form and
submits. System validates the entered password and displays a message Password changed
27
SYSTEM MODEL
successfully. If not valid password the system promote the user enter the valid password.
Beside the user can change the profile by filling required inputs.
Senior name: Manage user
Participating actor: System administer.

Event
Admin login to the system and the system displays all available operation done by admin.
System administer select manage users menu, the system display user management form.
Admin fill the form by active or in active the status of member and press submit menu. The
administer can also register new users. If valid Information is entered, system display a
message managed successfully. If the entered values are incorrect error message is displayed
and systems promote the user place enter correct information.
Scenario Name: Manage Finance.

Participating actor
a. Ethiopian sugar Corporation Actors: - Corporation manager.
b. Sugar factory actors: - Finance and Human Resource Manager.
Event
After login to the system the user press finance menu, then it display available information’s
about finance of the factories with menus like payroll, profit and loose, income/expense,
forecast and previous capital, budgets of factory. By selecting each menu the user can
manage each operations.
If the user select/press payroll menu system displays employee information including the
number of employees in the factory with the amount of capital which is budgeted for
employees, list of employee with pay button for each employee, then the user can press pay
menu and by filling required inputs such as allowances , deductions with employee personal
information. Finally by calculating total salary of employee user can press pay button. If valid
Information is entered, system display a submitted successfully. If the entered values are
incorrect error message is displayed and systems promote the user place enter correct
information.
If the user select profit/loose menu the system display previous daily, weekly, monthly or
annually profit and loose of the factory using different format example graph or pie chart.
COMPUTER SCIENCE 28
The user can add new profit/loose by pressing add profit or add loose. After then entering
required inputs and finally press add button.
Follow similar process for income/expense and forecasting capital menus.
Scenario Name: Manage Notification / Private Message.

Participating actor: System administer
Wholesaler.
Event
After users login there is notification menu with number of notification which is sent by any
user. The user can press that notification menu, then the user can view, delete and reply that
received message. There is also private chat menu to send new messages for any user. If the
user select private chat menu the system displays online users and all users of the system
respectively on the interface with previous written messages. After then the user should enter
required inputs and press send button. If valid Information is entered, system display a
message sent successfully. If the entered values are incorrect error message is displayed and
systems promote the user place enter correct information.
Scenario Name: Manage Transaction / Purchase.

Participating actor: customers
a. Ethiopian sugar Corporation Actors: - strategy support/ Corporation manager.
b. Sugar factory actors: - Wholesaler.
Event
After login to the system purchasing manager can view purchasing page of the system with
posted sale products and the price of the product, relationships between other organizations.
Purchasing manager can press recording/adding menu. After that he/she can enter detail of
the products with price of it and press add button into the purchasing page finally view result
message either success or not success. In similar way the manager can add new relationships
with other organizations.
System displays sales products (sugar products) with quantity and location of the factory
(Fincha, metehara, Tendaho …) and order menu to customer. Customer press order menu and
the system display purchasing form. Then the customer fill required information’s and
COMPUTER SCIENCE 29
SYSTEM MODEL
payment accounts. Finally press finish button and view result message either success or not
success.
Scenario Name: Manage Transport.

Participating actor: Wholesaler, transporter.
Event
After transaction committed wholesaler click order transport link. Then the system displays
list of transporters that transport the product from the factory into any regions, zone or capital
cities (customers). The wholesaler view current status of each transporter and click one of
active transporter from the list. Then the system displays transport order form, based on the
form the wholesaler fills each required fields and press order button. Finally view result
message either success or not success.
If the transport is ordered successfully the notification is sent to the transporter with essential
information.
Scenario Name: Manage News portal.

Participating actor: System Administer.
Event
After system administer logging into the system it display previous posted news by category
and add news menu. If system administer press add news menu the system displays news
portal form with required inputs (title, sub title, detail about news and Image…). Finally press
add button then view result message if the message is either success or not.
Any user can view posted news and advertisements without restriction/login at index page.
They can select and search news, view comments, send comment in each category.
Scenario Name: Manage online discussion.

Participating actor: System Administer, customers, employees.
Event
After login user can select discussion menu. After that the system display discussion page
which allows to any logged user to view/read and send message. Employee and employee,
Customers and employees or any user can share information’s with each other, but if there is
inconsistent message system administer is responsible to delete that message, other user are
allowed only to send and read message.
Scenario Name: Manage attendance.
COMPUTER SCIENCE 30
Participating actor: System Administer, Human resource manager, employees.

Event
After login users can see number of late comer, absent and on time comer employees in
percentage. Employees search their personal information by using their id number and they
can view their attendance.
After looking list of employees based on employee’s status Logistic manager select the date
and press (present, absent or late) button.
Scenario Name: Manage/view schedule.

Participating actor: System Administer, Factory and Logistic Manager.
Event
After login to the system users select/press schedule menu then the system displays time
schedule. User can select date, month and year then press add Event button. The system
display schedule form that includes event title, event purpose, detail and others. User fill that
required inputs and finally press add button.
Scenario Name: Manage/view Product and materials.

Participating actor: Factory and Logistic Manager, Farm Manager.
Event
After users login to system, the system displays recorded information’s product, raw material
and machineries of the factory. There is also add product, add raw material and add
machinery buttons to record other new materials. The user can select each buttons, fill
required inputs and add to the database.
Scenario Name: Manage the marketing of the corporation.

Participating actor: corporation manager/ strategy support.
Event
First login to the system then the system displays information’s about finance and
income/loose of each factories with some menus that includes international markets and
national market. Reports are also displayed on the system which is sent by purchase
managers. Then the manager can view each listed reports and give comment for that.
Scenario Name: Manage finance of corporation.

Participating actor: corporation manager/ strategy support.
Event
COMPUTER SCIENCE 31
SYSTEM MODEL
After login the system displays total financial information of factories that includes total
profit/loose, total distribution of product and others by comparing the amount of products
with their price. The system displays transaction reports which is sent by distributer
(Customers), producer (Factory and Logistic Manager, Finance and Human Resource
Manager) in a category.
Then the system can automatically calculate, balance and display the result after calculating
the total product and total purchased product with price based on producer report a and
distributer report. After viewing the result strategy support can give feedbacks to the
distributer and producer by pressing give feedback button.
Strategy supporter can plan, arrange and lead works based on strategic plans by pressing new
plan button. After filling required information about the strategy/plan press send button.
By this way this manager can calculate, balance and record each income and outcome of each
factories; therefore it is easy to control/protect the flow of budget from corruptions.
3.2.1. Use Case Model

The project development team used an object oriented system development methodology.
Because the Object oriented system development approach gives easier way to break down
problems into simple and small components so that it reduces the vague appearance of the big
problem. The major activities covered in this chapter are constructing a use case model,
documenting the use case course of events, constructing sequence and activity diagrams and
class diagram about the proposed system. The new system changes the existing working
system into new system and provide suitable graphical user interface.
COMPUTER SCIENCE 32
3.2.2. Use Case Diagram
Manage own View recent

Account order
View
notification View Purchased
Employee Products Transporter
<<include>> <<include>>
Visit News
Portal <<include>>
<<include>> View product
<<include>>
<<extend>> <<include>>
Record own
Attendance
<<include>>
View Schedule <<include>> Login <<include>>

View transaction
Post Job
vacancies <<include>>
Receive comment Corporation manager
<<extend>>
<<include>>
Manage Sales&
Finance <<include>>
<<include>>
Finance Manager
<<extend>> <<include>>
Manage <<include>> View Posted Jobs
Logistic Manager Attendance
Apply to job
Manage <<include>>
<<include>> vacancy
Schedule Job Seeker
<<include>>
Wholeseler
Manage Product View Reply
<<include>> Logout
& Material
Order transport Manage News

Portal
Manage
Transaction Manage
Notification
Check
availability
Customer Manage User

Order Item
Administer
Send Feedback
Figure 3 - 1: Use case Diagram
COMPUTER SCIENCE 33
SYSTEM MODEL
3.2.3. Description of Use Case Model

Use case description contains brief information about use cases by including the components
like use case name, use case ID, participate actor, description, basic course of action,
alternative course of action, pre-condition and post-condition of one use case to identify how
to perform activities by the actors.
Table 3 - 1: Login use case description
Use case id UC-1

Use case Name Login
Actor Users
Description Allows the users login into the system based on their privilege
Precondition The user must have user name, password and status
Post condition User get access to the system according to their predefined
system privilege and finally he/she logout or turn off the page
Basic course of action User action System response
Step 1. User activates the Step 2. The system response by
system. displaying the login interfaces
Step 3. User fills his or her and prompts the user for the
user name and password user name and password.
and click login button.
Step 4. System verifies user
Step 5. User authenticated
name and Password and display
and gets access to the
own page based on his/her
system.
privilege.
Step 6. Use case end.
Alternative course of action The system displays error message when the user enters
incorrect password and user name and the system returns to
step 3.
Table 3 - 2: Create own Account use case description
Use case id UC-2

Use case Name Create own Account
Actor Administer, employee, corporation manager, transporter
COMPUTER SCIENCE 34
Description System allows users to create own account for them.

Precondition User browse into the system.
Post condition The user will have own account.

Step 1. User click create Step 2. The system displays
own account link. registration form.
Step 3. The user fills
Step 5. The system checks the
required inputs.
validity of the input..
Step 4. The user Click
Step 6. The system records the
register button.
account.
Step 7. The system display
successful message.
Step 7. Use case end.
Alternative course of action Step 5.1 If the required input is invalid and fields are missed
the system display error message and the system return back
to step 3.
Table 3 - 3: Order Product use case description
Use case id UC-3

Use case Name Order product
Actor Customer
Description Allows customer to order products
Precondition Customer must login into the system
Post condition The system will order product/s according to they want
Step 1. The customer view Step 2. The system display
recorded Product with product order form.
current price and click Step 4. The system display
purchase button. successful message and send
Step 3. The customers fill order request to the wholesaler
the required information and automatically.
COMPUTER SCIENCE 35
SYSTEM MODEL
press submit button. Step 5. The use case end.

Alternative course of action If the customer inserts invalid data and missing the field the
system displays an error message and the system returns back
to step 3.
Table 3 - 4: Manage Finance use case description
Use case id UC-4

Use case Name Manage Finance
Actor Finance Manager
Description Allows Finance Manager to add and manage financial information
of factory.
Precondition Finance Manager must login into the system
Post condition The system will send report about financial information of the
factory to the corporation.
Step 1. The Finance manager Step 2. The system display
click finance link. statistically described financial
Step 3. The Finance manager information of the factory that
click add link. includes income/expense,
Step 5. The Finance manager profit/loose and capital
fills each inputs and press add forecasting information of the
button.
factory with add link.
finance register form with
required inputs that includes
income/expense, profit/loose
and capital forecasting in a tab.
Step 6. If inputs are valid the
system display successful
message.
Step 5. The use case end.
Alternative course of 6.1 If the customer inserts invalid data and missing the field the
action system displays an error message and the system returns back to
COMPUTER SCIENCE 36
step 5.
Table 3 - 5: Manage Schedule use case description
Use case id UC-5

Use case Name Manage Schedule
Actor Logistic Manager
Description Allows Logistic Manager to record and send notice for other
employees.
Precondition Logistic Manager must login into the system
Post condition The system will send schedules and notice to employee.
Step 1. Logistic Manager click Step 2. The system display
the link called add schedule. schedule table.
Step 3. The customers select Step 4. The system display
date, month and year then schedule form that includes
press add Event button. event title, event purpose, detail
Step 5. The customer fills each and others.
inputs and press add button. Step 6. The system display
successful message.
Alternative course of action If the customer inserts invalid data and missing the field the
system displays an error message and the system returns back to
step 2.
Table 3 - 6: View and send message use case description
Use case id UC-6

Use case Name View and send message
Actor Employee, Corporation manager, Transporter. customer
Description Allows users to share information between them.
Precondition users must login into the system
Post condition Users can send and receive information easily.
COMPUTER SCIENCE 37
SYSTEM MODEL

Step 1. User login to the Step 2. The system display some
system. links that includes Chat link.
Step 3. The user click chat Step 4. The system display total
menu. number of online users and list
Step 5. The user click any user of users with their status either
that he/she want to send/view a online or not.
message.
Step 7. The user insert a Step 6. The system display chat
message and click send button. form.
message sent successfully.
Alternative course of action If the user inserts invalid data and missing the field the system
displays an error message and the system returns back to step 7.
Table 3 - 7: Manage transaction use case description
Use case id UC-7

Use case Name Manage transaction
Actor Wholesaler
Description According to the order request wholesaler record and approve or
reject the transaction.
Precondition Wholesaler must login into the system
Post condition The system allows wholesaler to manage the whole transaction.
Step 1. Wholesaler view and Step 2. The system display all
click the link called order. orders which is the order request
Step 3. The user click commit of the customer.
button to sell ordered items. Step 4. The system record the
transaction and send the report to
the corporation manager
automatically.
COMPUTER SCIENCE 38
success message.
Alternative course of action If the store is empty system displays store empty message and the
system returns home page.
Table 3 - 8: Manage News use case description
Use case id UC-8

Use case Name Manage News
Actor Administer
Description Create a news portal page that exhibit news.
Precondition Administer must login into the system
Post condition The system allows to distribute information about the factory
through news portal.
Step 1. Administer view recent Step 2. The system display
posted news and click add popup news portal form.
news menu. Step 4. The system display
Step 3. The Administer insert success message.
required inputs and press add Step 5. The use case end.
button.
Alternative course of action If the Administer inserts invalid data and missing the field the
step 3.
Table 3 - 9: Order transport use case description
Use case id UC-9

Use case Name Order transport
Actor Wholesaler
Description The system announce transporter to transport purchased products
for customers.
Precondition Wholesaler must login into the system
COMPUTER SCIENCE 39
SYSTEM MODEL
Post condition The system displays purchased products to transporter.

Step 1. After committing the Step 2. The system display
transaction, wholesaler should transport deployment form with
press deploy transport link. required inputs.
Step 3. The wholesaler inserts Step 4. The system display
required inputs and press success message.
deploy button. Step 5. The use case end.
Alternative course of action If the wholesaler inserts invalid data and missing the field the
step 3.
Table 3 - 10: Post job vacancy use case description
Use case id UC-10

Use case Name Post job vacancies
Actor Finance and Human Resource manager
Description The system allow to post new job vacancies for Finance & HR
manager.
Precondition Finance & HR manager must login into the system
Post condition New job vacancy is posted to job tracking site.
Step 1. Finance & HR manager Step 2. The system displays job
view previous recorded job vacancy registration form.
vacancies. Then click add Step 4.The system post job
vacancy link. vacancy to job seeker and
Step 3. Finance & HR manager display success message.
insert required inputs and click Step 5. The use case end.
add job button.
Alternative course of action If the Finance & HR manager inserts invalid data and missing the
field the system displays an error message and the system returns
back to step 3.
COMPUTER SCIENCE 40
Table 3 - 11: Apply to job vacancy use case description
Use case id UC-11

Use case Name Apply to job vacancy
Actor Job seeker
Description The system allow to job seekers to apply for job vacancy.
Precondition Job seeker must have CV and prepare it into appropriate
format(.pdf)
Post condition Job seeker can successfully apply to the job without consuming
extra time and money.
Step 1. Job seeker browse the Step 2. The system displays new
page/system. job vacancy lists.
Step 3. Job seeker select the Step 4. The system display job
job and press apply to the job application form with required
button. inputs.
Step 5. Job seeker fill inputs Step 7. The system displays
and upload cv. success message.
Step 6. Click apply button. Step 8. The use case end.
Alternative course of action If the Job seeker inserts invalid data , missing the field the system
and upload un supported cv the system displays an error message
and the system returns back to step 5.
3.2.4. Activity Diagram

An activity diagram describes the flow of control in a system. So it consists of activities and
links. The flow can be sequential, concurrent or branched. Activity diagrams are used to
visualize the flow of controls in a system [6, 7].This is prepared to have an idea of how the
system will work when executed. Activity diagram is basically a flow chart to represent the
flow form one activity to another activity. The activity can be described as an operation of the
system. So the purposes can be described as:
COMPUTER SCIENCE 41
SYSTEM MODEL
✓ Draw the activity flow of a system.

✓ Describe the sequence from one activity to another.
✓ Describe the parallel, branched and concurrent flow of the system
Figure 3 - 2: Activity diagram for login use case
COMPUTER SCIENCE 42
Figure 3 - 3: Activity diagram for Create account use case
Figure 3 - 4: Activity diagram for Order product use case
COMPUTER SCIENCE 43
SYSTEM MODEL
Figure 3 - 5: Activity diagram for marking attendance use case
Figure 3 - 6: Activity diagram for Manage finance use case
COMPUTER SCIENCE 44
Figure 3 - 7: Activity diagram for view and send message use case
Figure 3 - 8: Activity diagram for order transport use case
COMPUTER SCIENCE 45
SYSTEM MODEL
3.2.5. Object Model

In this section we will describe the class diagram depicting the inheritance relationships and
associations that exist between the entities objects that are available on the system. The class
diagram focuses mainly on the relationship among application domain concepts. The object is
represented in the same way as the class. The only difference is the name which is
underlined. Object model of administer, employee, customer, wholesaler, logistic manager,
finance manager, corporation manager, transporter and job seeker in the following format.
Figure 3 - 9: Object Model Diagram
COMPUTER SCIENCE 46
3.2.6. Data dictionary
Table 3 - 12: Data dictionary
Class Attribute Data type Description

Customer First name String Customers are regular
Last name String purchaser of the product in
Email address Varchar each week and months.
Phone number Varchar They can easily order
Gender Char products at their
Organization name String home/organization without
City String consuming their time,
Region/zone String money and energy.
Nationality String
Address Varchar
Date date
User-id Varchar
Username Varchar
Password Varchar
Employee First name String Employees are the

Last name String producer of white sugar
Email address Varchar and ethanol in different
Phone number Varchar role’s starting from sugar
Gender Char cane production up to final
Age Int purchasing of the products.
Registration date Varchar

City String
Nationality String
Address Varchar
Employment type String
Classification role String
Payment type String
Working time Time
COMPUTER SCIENCE 47
SYSTEM MODEL
Salary Float
Username Varchar
Password Varchar
Administer First name String Admin is the person that

Middle name String manages the whole system.
Last name String
Email address Varchar
Phone number Varchar
Gender Char
Role String
Username Varchar
Password Varchar
Corporation First name String Corporation manager is the

manager
Middle name String manager of Ethiopian
Last name String sugar corporation who
Email address Varchar manage the whole sugar
Phone number Varchar factories in Ethiopia.
Gender Char He/she balance the whole
Age Int financial system and other
Address Varchar activities.
Role String
SSN Varchar
Username Varchar
password Varchar
Job seeker First name String Job seeker is any user who
want to apply for posted
Middle name String
jobs. He/she receive
Last name String notification if he/she is
Email address Varchar selected by the human
resource manager for the
Phone number Varchar job.
Gender Char
COMPUTER SCIENCE 48
Age Int
City String
Address String
Experience Varchar
Photo Blob
CV .pdf
nationality String
Transporter First name String Transporter is the manager

Middle name String of transport associations
Last name String who participated to the
Email address Varchar tender and make contract
Phone number Varchar with wholesaler of the
City String factory. If transporter win
Address Varchar the tender.
Date Date
Association name String
Username Varchar
Password Varchar
Product Product name Varchar Products are items which is

Category String produced by sugar
Production date Date factories such as white
Expiration date Date sugar, ethanol, fruits and
Store Varchar etc.
Availability String
Quantity Number
Base cost Float
description String
News portal News title String News portal is a portal

Sub title String used to post new
Posted date Date information of the factory
COMPUTER SCIENCE 49
SYSTEM MODEL
Description Varchar to the users.

Picture Blob
Job vacancy Job name String Job vacancy is favorable

Job category String way of finding a job for
Factory branch String job applicants.
Branch location Varchar

Applicant experience Number
salary Float
Application started Date time
Application dead line Date time
Job detail String
Order product Customer detail Order product is the

Product detail process of sending request
Quantity Number to wholesaler of the factory
Transaction date Date to purchase the product.
Price Float
Discount Float
Tax Float
Total price Float
Transport order Origin address Varchar This is dispatcher to the

Destination city String transporter.
Destination woreda String
Destination address Varchar
Driver license Varchar
Track plate number Varchar
Trailer Varchar
Side number Varchar
Track capacity Number
Shiper String
Consignee Varchar
COMPUTER SCIENCE 50
Operation number Number

Commodity String
Quantity Number
Distance Varchar
Arrival date Date time
Driver association Varchar
Driver name String
Operation number Number
Schedule Event title String Schedule is used to send

Sub title String notification to employees.
Purpose String
Type String
Detail String
Date Date
Attendance Employee id Varchar Attendance is used to

Name String record and manage
Status String employees working time.
Cause String
Time in Time
Time out Time
Payroll Employee detail Payroll is a way of paying

Allowance cause String salary to employees of the
Total allowance Float factory.
Deduction cause String
Total deduction Float
Allowance – Deduction Float
Allowance/deduce by String
Total salary Float
Category String
COMPUTER SCIENCE 51
SYSTEM MODEL
Budget Total budget Float Budget is used to add

Date Date money for factory
Detail String expansion, tax, salary and
other purposes.
Chat Sender name String This category is used to

Receiver name String send and receive
Date Date information’s to other
message String members of the factory.
Feedback Name String Feedback allows user to

Email Varchar Send and display the
feedback about working
system of the factory.
COMPUTER SCIENCE 52
3.2.7. Class Model
Figure 3 - 10: Class Diagram
COMPUTER SCIENCE 53
SYSTEM MODEL
3.2.8. Dynamic Modeling

Dynamic model represents the behaviour of an object over time. It is used where the object's
behaviour is best described as a set of states that occur in a defined sequence. The
components of the dynamic model are states, state transitions, events, actions and activities
[10]. We represent this objects using:
a. Sequence Diagram
Sequence diagrams are used to model the logic of usage scenarios. Usage scenario is exactly
which its name indicates-the description of a potential way of the system is used. The logic of
usage scenario developed here comprises the basic course of actions. The team use sequence
diagram in order to easily define sequence of tasks that accomplished by the actors of the
system.
Home Page Login Form Validator User Page

All users
Browse ()
Click login button()
Display login form ()
Enter un , Pwd and press login button

Check validation ()
Invalid
Display login fail message ()
Renter un , Pwd and Press login button () Valid
Display ()
Main page displayed ()
Figure 3 - 11: Sequence diagram for login use case
COMPUTER SCIENCE 54
Home Page Create account Form Validator Database

Users
Click Create account

link()
Display create account form ()
Fill required inputs & press create button ()
Check validation ()
Invalid
Unsuccessful register , try again
Valid
Fill the form again and press create button ()
Save to database ()
Account created successfully ()
Figure 3 - 12: Sequence diagram for create own account use case
Main Page Order product Form Validator Database

Customer
Login to main page ()

View posted product &
click order link ()
Display order form ()
Fill the form, add

payment receipt & press
button()
Check validation ()
Invalid
Re-fill the form and press order button ()
Valid
Save to database ()
Item ordered successfully ()
Figure 3 - 13: Sequence diagram for order product use case
COMPUTER SCIENCE 55
SYSTEM MODEL
Main Page Order approval page Order Validator Database

Wholesaler
click order list link ()
Click one of ordered list ()
Display list of orders ()

Display detail about
the order ()
Press approve button ()

Check validation ()
Invalid
Please approve again ()
Valid
Save to database ()
Item approved successfully & send receipt ()
Figure 3 - 14: Sequence diagram for approve order use case
COMPUTER SCIENCE 56
Main Page Finance Page Validator Database

Finance manager
Click add finance link ()
Display finance
management form ()
Fill the form & press

add button()
Check validation ()
Invalid
Please fill the correct data & try again ()
Re-fill the form & press add button()
Valid
Save to database ()
Finance Added successfully ()
Figure 3 - 15: Sequence diagram for manage finance use case
Main Page Message form Validator Database

Employee

Click private chat link ()
Display private
message form ()
Fill the form &

press send button()
Check validation ()
Invalid
Please fill the correct data & try again ()
Re-fill the form & press add button()
Valid
Save to database ()
Message send successfully ()
Figure 3 - 16: Sequence diagram for view and send message use case
COMPUTER SCIENCE 57
SYSTEM MODEL
b. State Chart Diagram

The state chart diagram shows the change of an object through time based upon events that
occur and it shows how the object changes from start to finish. We have many state chart
diagram but we elaborate some of them. It is shown as below:-
Figure 3 - 17: State chart diagram for Login use case
Figure 3 - 18: State chart diagram for add attendance use case
COMPUTER SCIENCE 58
3.2.9. User Interface

User interface design is the specification of the interaction between the system users and a
system. The process involves input mechanism design, output mechanism design, and
navigation mechanism.
✓ Navigation mechanism is part of user interface that takes the user form one part of
the system to the other user system. That includes menus or links, buttons, icons,
dialog boxes etc.
✓ Input design is about designing a form and its controls for GUI system.
✓ Output design is about designing reports like detailed, summarized, exceptional,
graph, chart, text document report and extra.
Home Page: This form contains some information about the website and linked menus which
appear to the user after he/she login to his/her own page.
Figure 3 - 19: Home page user Interface
COMPUTER SCIENCE 59
SYSTEM MODEL
Login Page: this is the login form for users to go to their page based on their username,
password and position.
Figure 3 - 20: Login page user Interface
Administer dashboard Page: this page contains important link menus which is available for
the user/administer.
COMPUTER SCIENCE 60
Figure 3 - 21: Administer dashboard page user Interface

Create Account Page:
Figure 3 - 22: Create account page user Interface
COMPUTER SCIENCE 61
CHAPTER FOUR
4. SYSTEM DESIGN
4.1. Introduction
In this chapter, we describe the overview of the current and the proposed system architecture
and specify design goals to improve the quality of the system by reducing response time and
operating cost, and increasing usability of the system. We also describe system
decomposition into subsystems with their respective services and also specify the
Hardware/software mapping by depicting deployment diagram, as well as the persistent data
management. In this project design the team will try to show:
✓ How the project is designed
✓ The different modules and their way of functioning are described here
✓ What are tasks done under the whole project
The goal of system design according to the proposed project is to manage complexity by
dividing the system into smaller, manageable pieces and to increase 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
Security: the system should be secured, i.e. not allow unauthorized users to access the
system.
Reliability: the system should be reliable.
4.2. Current software architecture

Fincha sugar factory perform tasks using manual based system so it is difficult to manage and
control the whole activity of the factory.
4.3. Proposed software architecture

As we have said the software architecture of the system is client/server architecture [11].
The purpose of designing proposed architecture is to show the direction as to how application
is developed and to obtain clear and enough information needed to derive the actual
implementation of the application. The work is based on the services provided in the internet
or LAN to customer and employee. The architecture used for the system is a 3 level
client/server architecture where a client can use internet browsers to access the Fincha sugar
62
factory management system within the local area network of the factory or anywhere using
the internet.
It stores these data in a relational database management system. The middle level
(web/application server) implements the business logic, controller logic and presentation
logic to control the interaction between the application’s clients and data. The controller logic
processes client requests such as requests reservation and show services provided the printing
enterprise s from the database. Business rules enforced by the business logic dictate how
clients can and cannot access application data and how applications process data.
Figure 4 - 1: System Architecture Model for Proposed System
When a request is made on a web page through the browser, PHP that is residing on the web
server processes the request. It connects to the database to retrieve the requested information
and sends its response back to the browser which displays the output on another web page.
The advantage of this architecture is that the database is more secured as it is only accessible
by the application logic that resides on the web server.
4.3.1. System Decomposition

To reduce the complexity of the solution domain, we decompose a system to simpler part
called subsystem, which are made of a number solution domain class. In the case of complex
subsystems, we recursively apply this principle and decompose a sub system into simpler
subsystems. Decomposition results large systems in to a set of loosely dependent parts which
make up the system. Sub-system decomposition is the way that helps us to distinguish the
part of the operations that takes place under the organization [6].
COMPUTER SCIENCE 63
SYSTEM DESIGN
The following are the sub system that are derived from the functionality of the system of
Fincha sugar factory management system:
Figure 4 - 2: Component diagram
COMPUTER SCIENCE 64
4.3.2. Hardware/ software mapping

When the project team say hardware/software mapping for the system, it describes how
subsystems are assigned to hardware and off-the-shelf components. It also lists the issues
introduced by multiple nodes and software reuse. In this system design mainly there are three
hardware components. The client side, server side and database when the team applies the
system, necessary software will be loaded to each side hardware components. Network
should be installed between each side. Then each subsystem software will be assigned and
configured to the mapped hardware. Then the local area network will be connected to the
internet and the system will be functional [12] [13].
Figure 4 - 3: Deployment diagram
COMPUTER SCIENCE 65
SYSTEM DESIGN
4.3.3. Persistent data modeling

Persistent data management describes the persistent data stored by the system and the data
management infrastructure required for it. This section typically includes the description of
data schemes, the selection of database, and the description of the encapsulation of the
database. Here As the system includes huge data received from users and implemented in
large organization such as universities, colleges, and nongovernmental organization, it needs
persistence data storage. So that our software system uses a database called SQL server to
manage and store data persistently. Keys index and integrity rules. A DB schema specifies
details based on the capabilities, terminologies, and constraints the chosen DBMS.
Figure 4 - 4: Persistent data management
COMPUTER SCIENCE 66
4.3.4. Access control and security

In the systems, different actors have access to different functionality and data. Therefore
these privileges prevent unauthorized users from accessing data’s which they don’t have
granted to access.
Authentication: This take place by letting users to insert their user name and password in the
displayed login form.
Authorization: This takes place by preventing users from participating in specific tasks on
which he/she doesn’t have grant to access.
Table 4 - 1: Access control and security
Actor Admin Employee Wholesaler Logistic Finance Customer Job ESC

Trans
manager manager seeker porter
manager
Abject
Create
own
account
View
report
View
notificatio
n
View
news
portal
Add
attendance
View
schedule
Post job
Manage
finance
Manage
attendance
Manage
schedule
Manage
product &
material
Order
transport
Manage
transactio
COMPUTER SCIENCE 67
SYSTEM DESIGN
n
Order
product
Send
feedback
View
report
Receive
comment
View &
apply to
posted job
Manage
news
portal
Manage
notificatio
n
Manage
user
4.3.5. Detailed class diagram

Class diagram with visibility and signature specified for each attributes and operations. In this
class diagram we define which attributes and operations are private to that class, which
attributes and operations can be accessed by the class decedents (protected), and which
attributes and operations are publicly accessible by the class user (public). We also define the
return type of each operations as well as the number and type of parameters of each
operations.
COMPUTER SCIENCE 68
Figure 4 - 5: Detailed class diagram
COMPUTER SCIENCE 69
SYSTEM DESIGN
4.3.6. Package Diagram

In this section we describe the decomposition of sub system in to packages. We first classify
the subsystems into three packages. The first group is interface package, this contains the FSF
Client. The second group is Application Logic package, this includes two sub packages
which are Server package and Data Management package. Server package holds FSFMS
Server subsystem.
Figure 4 - 6: Package diagram
COMPUTER SCIENCE 70
4.3.7. Deployment
The software going to be developed is allowed by UML model. UML deployment diagram
show physical view of system, taking software into real world by showing how software gets
assigned to hardware and how communicates.
Figure 4 - 7: Deployment diagram
COMPUTER SCIENCE 71
REFERENCES
[1] U. J. Yadav, "International Journal of Advanced Research in computer science and software
engineering," 8 August 2012. [Online]. Available: www.ijarcsse.com.
[2] "Ethiopian Sugar Corporation," [Online]. Available: www.etsugar.gov.et. [Accessed 5 1 2020].
[3] "www.etsugar.gov.et," Ethiopian Sugar Corporation, [Online]. Available: www.etsugar.gov.et.

[Accessed 1 1 2020].
[4] T. daba, "assessment of Reward Management Practice in fincha sugar factory," 2018.
[5] L. Somerville, Software engineering, 2006.
[6] S. W. Ambler, Agile development for use case diagram with UML, 2003.
[7] I.Booch, Object-Oriented Analysis and Design with Applications, Addition-Wesley, April 2007.
[8] [Online]. Available:

https://www.google.com/search?q=what%20is%20dynamic%20modeling&cad=h. [Accessed 14
January 2020].
[9] H. O. J. P. Kruchten, "The Past, Present and Future of Software Architecture," in IEEE Software,
22-30, November, 2006.
[10] B. A. H. Dutoit., "Object-Oriented Software Engineering," 3 ed., Prentice Hall, United States,
1985.
[11] "Deployment diagram," [Online]. Available: https://en.wikipedia.org/wiki/Deployment_diagram.

[Accessed 12 November 2018].
[12] "Component Diagram," [Online]. Available:

https://creately.com/diagram/example/gqz0nrua1/Component+Diagram. [Accessed 13 1 2020].
[13] U. J. Yadav, "International Journal of Advanced Research in," 8 August 2012. [Online].
Available: www.ijarcsse.com. [Accessed 4 1 2020].
72
APPENDIX
Interview questions that we asked during requirement gathering.
 What are rule and regulation of the factory?

 The input and output of the current system?
 What are major challenges of Fincha sugar factory?
 Actor of the current system and their role?
 How distribute and purchase the product to the customer?
a. Online?
b. Manual?
 Is there social services for employees and their families in the factory? (yes or no)
 How does this existing system performing the activities?
a. Is it manual?
b. Is it computerized?
73

Fincha Sugar Factory Management System

Uploaded by

Copyright:

Available Formats

You might also like

Fincha Sugar Factory Management System

Uploaded by

Document Information

Original Description:

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

Fincha Sugar Factory Management System

Uploaded by

Copyright:

Available Formats

UNIVERSITY OF GONDAR

DEPARTEMENT OF COMPUTER SCIENCE

FINCHA SUGAR FACTORY MANAGEMENT SYSTEM

2. Taye Bitew GUR/01830/09

3. Wudie Alemneh GUR/01881/09

4. Getnete Alemnewu GUR/01586/09

5. Tirusew Giza GUR/01862/09

2. Name of Project Coordinator:

Finally, we would like to thank to everyone who involved in our project.

LIST OF FIGURES ............................................................................................................................... vi

LIST OF TABLES ................................................................................................................................ vii

ACRONYMS ....................................................................................................................................... viii

EXECUTIVE PROJECT SUMMARY .................................................................................................. ix

CHAPTER ONE ..................................................................................................................................... 1

1.1. Introduction ............................................................................................................................. 1

1.2. Background of the project ....................................................................................................... 2

1.3. Statement of the problem and justification ............................................................................. 3

1.4. Objective of the project ........................................................................................................... 4

1.4.1. General Objective ........................................................................................................... 4

1.4.2. Specific objective ............................................................................................................ 4

1.5. Scope of the project ................................................................................................................ 4

1.6. Limitation of the project ......................................................................................................... 5

1.7. System Development Methodology ........................................................................................ 5

1.7.1. System development Approach ...................................................................................... 5

1.7.2. System Development Tools ............................................................................................ 6

1.8. Significance of the Project ...................................................................................................... 7

1.9. Beneficiaries of the project ..................................................................................................... 7

1.10. Feasibility Analysis ............................................................................................................... 10

1.10.1. Operational feasibility ................................................................................................... 10

1.10.2. Technical feasibility ...................................................................................................... 11

1.10.3. Economic feasibility ..................................................................................................... 11

1.10.4. Behavioral/Political feasibility ...................................................................................... 12

1.11. Project Schedule.................................................................................................................... 12

1.12. Project Budget ....................................................................................................................... 13

CHAPTER TWO .................................................................................................................................. 14

COMPUTER SCIENCE iii

2.1. Introduction ................................................................................................................................ 14

2.2. Current system Description ................................................................................................... 14

2.2.1. Major function of current system .................................................................................. 15

2.2.2. Problem of Existing System .......................................................................................... 17

2.3. Requirement Gathering ......................................................................................................... 17

2.3.1. Requirement Gathering Methods .................................................................................. 18

2.3.2. Business rules................................................................................................................ 19

2.4. Proposed System Description ............................................................................................... 19

2.4.1. Overview ....................................................................................................................... 20

2.4.2. Functional Requirement ................................................................................................ 21

2.4.3. Nonfunctional requirements .......................................................................................... 23

CHAPTER THREE .............................................................................................................................. 27

3.1. Introduction ................................................................................................................................ 27

3.2.1. Use Case Model ............................................................................................................ 32

3.2.2. Use Case Diagram ......................................................................................................... 33

3.2.3. Description of Use Case Model .................................................................................... 34

3.2.4. Activity Diagram........................................................................................................... 41

3.2.5. Object Model ................................................................................................................ 46

3.2.6. Data dictionary .............................................................................................................. 47

3.2.7. Class Model .................................................................................................................. 53

3.2.8. Dynamic Modeling ....................................................................................................... 54

3.2.9. User Interface ................................................................................................................ 59