NOVEMBER 23, 2020

WORKORDER MANAGEMENT SYSTEM

FOR DHIRAAGU KOC
M322 SOFTWARE ENGINEERING PRINCIPLES ASSIGNMENT

MOHAMED FALAH DAWOOD

MIC06S37-5034
TABLE OF CONTENTS

M322 SOFTWARE ENGINEERING PRINCIPLES ASSIGNMENT......................................................0

Abstract..................................................................................................................................................3
INTRODUCTION....................................................................................................................................4
ORGANIZATION PROFILE.................................................................................................................4
objectives...........................................................................................................................................4
system analysis.......................................................................................................................................5
existing system...................................................................................................................................5
drawbacks......................................................................................................................................6
proposed system................................................................................................................................6
feasibility study...................................................................................................................................7
economical feasibility......................................................................................................................7
technical feasibility.........................................................................................................................7
operational feasibility.....................................................................................................................8
system specification...............................................................................................................................8
hardware requirements......................................................................................................................8
software requirements.......................................................................................................................9
Software Requirement for Normal User..........................................................................................9
Software Requirement for Computer Technician............................................................................9
software description.............................................................................................................................10
front end...........................................................................................................................................10
asp.net4.6.....................................................................................................................................10
C#.NET.........................................................................................................................................11
backend............................................................................................................................................11
features............................................................................................................................................12
Project description................................................................................................................................13
problem definition............................................................................................................................13
overview of the project......................................................................................................................13
module description...........................................................................................................................14
data flow diagram.............................................................................................................................15
Level0...........................................................................................................................................16

1
 level 1 administrator......................................................................................................................17
Level 1 Technical staff...................................................................................................................17
Level 1 Admin staff........................................................................................................................18
level 1 contractor...........................................................................................................................18
level 2 administrator.....................................................................................................................19
level 2 Technical staff....................................................................................................................20
Level 2 Admin Staff.......................................................................................................................21
Level 2 Contractors.......................................................................................................................22
ER Diagram.......................................................................................................................................23
database design................................................................................................................................24
SQL SERVER 2017.........................................................................................................................24
Table scheme................................................................................................................................25
input design......................................................................................................................................29
output design...................................................................................................................................29
system testing......................................................................................................................................30
unit testing.......................................................................................................................................30
acceptance testing............................................................................................................................30
test cases..........................................................................................................................................30
system implementation........................................................................................................................31
data preparation...............................................................................................................................31
user training......................................................................................................................................31
conclusion & future enhancements.......................................................................................................32
conclusion.........................................................................................................................................32
future enhancements........................................................................................................................32
appendix...............................................................................................................................................33
references.............................................................................................................................................36

2
WORKORDER MANAGEMENT SYSTEM
FOR DHIRAAGU KOC

ABSTRACT

Work order management system is software developed to manage the work orders awarded to the
contractors in Dhiraagu KOC department. Works like trenching and internal wirings for their
customers, are awarded to external contractors on respected islands. They use semi-manual
method for entering their records and manage them. Hence, they face problems while handling
their records, doing the payment processes for the contractors and reports. After the system is
completed they will be able to manage the work orders much more accurate and expedite.

In current system they use most of the processes manually. They face problems in searching for
previous records and duplicated work orders. This requires lot of time in using manually. When
maintaining the work orders, there are many manual processes in order to complete a single work
order. There are Forty-two islands under Dhiraagu KOC. On each island whenever they get a work
of trenching and internal wirings like works are managed via creating a work order for respected
work. The staff who manage these work orders struggle to check the status of a particular work
order. Currently all the work orders are saved on a share point created by them. Other details like
customer and contractors are being saved on a Google sheet and respected reports are being
created by the help of pivot charts on the google sheet. Because of these reasons with the old
system, we get motivated to create this system.

At the end of the project the problems mentioned above will be solved by fully computerizing the
system. When the system gets completed, the staffs of the organization will get easy and secure
access to the application, so that they can manage the work orders easily and accurately.

3
INTRODUCTION

ORGANIZATION PROFILE

Our company specializes in developing state of the art digital solutions with flexible customizability. We
are based in the small country Maldives where delivery of information has been very limited by the
nation's trivial and old practices throughout the years. We aim to change the way information is
distributed to the people and establish a base standard for information to be delivered. Our aim is to
carry our partners and our clients through this digital era with confidence and reassurance.

Services provided by our company include:

1. Software development.
● Mobile applications.
● Websites.
● Application integrations.
2. Network & Software consultancy.
● Feasibility study.
● System proposals.
● Network surveys & proposals

OBJECTIVES

Our objectives are to satisfy our customers’ needs copiously. We do give suggestions to our clients
incase customer is not sure about their needs, so that customer is completely satisfied with our final
product.

● Get rid of the extra files like google sheets and other data files
● Secured customer data
● Customized reports.
● Information can be pushed to the users in real time.
● Real-time requests.
● Payment process computerized

4
SYSTEM ANALYSIS

Systems development is a systematic process which includes phases such as planning, analysis, design,
deployment, and maintenance.

Systems Analysis

On this phase we will be collecting and interpreting facts, identifying the problems, and decomposition
of the system into its components.

System analysis is conducted for the purpose of studying a system or its parts in order to identify its
objectives. It is a problem-solving technique that improves the system and ensures that all the
components of the system work efficiently to accomplish the customer’s needs.

Systems Design

It is a process of planning a new system or replacing an existing system by defining its components or
modules to satisfy the specific requirements. Before planning, you need to understand the old system
thoroughly and determine how to over come the existing issues on current system.

System Design focuses on how to accomplish the objective of the system.

EXISTING SYSTEM

Work order management system supports the efforts to mitigate the process of labor works like
trenching the roads or customer premises, internal wirings of Dhiraagu customers.

When a customer requests for a Dhiraagu service like telephone, fiber broadband services, a survey is
carried out by the technicians, whether customer has an existing cable, do customer needs an internal
wiring…etc. If there is any cabling work to be carried out, technicians raise a work order saying the work
details to be done, whether trenching is required or internal wiring is required. This work order process
is carried on an online form which saved on a share point allocated for Dhiraagu KOC. Work order
access is given to all technicians. Customer details and contractor details has to be selected on this form
and the details need to be entered on a particular Google Sheet for the record purpose, manually. There
is no particular database for the inputs taken from the online forms.

Once the work order is been raised, there is an admin officer who handles all the work orders and
payment processes. 1st approval is done by the admin officer. Once 1 st approval is approved, work is
handed over to contractor by the technician who has raised the particular work order. This technician is
responsible for the particular work. Once the work is completed, measurements are taken by the
technician and entered on the previously raised work order form and sent for the 2 nd approval. Actual
measurements are also being entered to the google sheet by the technician. 2 nd approval is done by the
regional manager.

Once 2nd approval is approved by the manager, admin officer responsible for the work orders handling,
mails the particular work orders for the contractor for the invoice purpose. And once contractor sends
the invoices along with work order as a supporting document.

5
When the invoice is received by the contractors, admin officer checks the invoice and work order for any
quarries, and creates a payment request for the particular invoice on a program called “Shirt Front”
which is on a share point of Finance department Head office. Finance Department then do the process
of the payment for the contractors.

DRAWBACKS
On the study of the current system we have found several issues. Time is a very important thing on
today’s life. Number of jobs are increasing day by day though headcounts are not increasing for the
jobs.

There is no database for the records of the work orders.

Manual entry is required for each work order created for any of the jobs.
Duplicate records are found for the same works, since it using manual data entry for the
records.
Work order request forms include manual data entry of the customers and contractors’ details.
Work orders are sent via email for the invoices to the contractors manually.
Payment request is created for the contractors by admin officers for payment process
manually.

PROPOSED SYSTEM

Newly developed program will be replacing all of the manual data entry process with more reliable and
secured modern technologies. It is designed with the aim of providing most intuitive user experience as
possible.

 Fully automated database will be compiled with Dhiraagu customer records, and will be
integrated with their billing system for new customers.
 Automated work orders will be created when technicians fill the forms while doing the surveys
for the particular customer.
 Contractors shall be notified once the work order has been raised and completed the work.
 Automated payment requests shall be created once admin officers receive the invoices.
 Once the payment is done from finance, admin officers and contractors will be notified.

6
FEASIBILITY STUDY

A systems request must pass several tests, called a feasibility study, to see whether it is worthwhile to
proceed further! A feasibility study is a study conducted to assist decision-makers in determining
whether a particular project or program shall be implemented or not.

A feasibility study uses three main indexes to measure a proposal: operational feasibility, technical
feasibility, and economic feasibility.

ECONOMICAL FEASIBILITY
Economic feasibility means that the projected benefits of the proposed system outweigh the estimated
costs usually considered the total cost of ownership (TCO), which includes ongoing support and
maintenance costs, as well as acquisition costs.

It includes, People, including IT staff and users, hardware, software, trainings, licenses and fees and
facility costs.

Economic feasibility is about resources and amount of money spent on the projects. In order to do this
project, it requires maintaining the low and balanced money spent

 Existing server on Dhiraagu KOC can be used for database process which will not cost for any
hardware.
 Existing Laptops and pcs hardware specs are more than enough to run the new system to run.
 Extra application shall be used by the technician’s mobile phones while doing the surveys,
which does not require much mobile Data.
 And finally, for the Administrators for the new system will require a simple computer system to
manage or maintain the application. For all these reasons we can say, the developed program is
feasible economically.

TECHNICAL FEASIBILITY
Technical feasibility assesses whether the current technical resources are sufficient for the new system.
If they are not available, can they be upgraded to provide the level of technology necessary for the new
system.

We have gathered information from Dhiraagu KOC and noticed that the hardware is okay to run the
system, since they have a configured server and worthy computer systems.

7
OPERATIONAL FEASIBILITY
Operational Feasibility defines the urgency of the problem and acceptability of any solution – will it be
used if a system is developed? It also includes people-oriented and social issues: internal issues, such as
work force problems, labor objections, organizational conflicts and policies. Also, external issues,
including governmental regulations and legal aspects, social acceptability of the new system.

Operational feasibility evaluates whether a system can work, and whether a system will work.
Minimizing the failure of the proposed system by evaluating the end-user or management resistance.

As we approached with new system to accommodate the current system’s issues and we got feedback
for the solution from the management. They are willingly supporting the project and are ready to
provide necessary resources for conducting trainings. Since there is no major concern from the
management and staff, the system is operationally feasible to build.

SYSTEM SPECIFICATION

HARDWARE REQUIREMENTS

Computer hardware is the physical the mechanical, magnetic, electronic, and electrical components
making up a computer system. Here are the recommended hardware requirements to run this system
in the organization.

 Intel Core i3 3.06 GHz: This should be the recommended processor speed of the system. Fast
processor will be required, since the system involves calculations and report generations.
 4GB DDR3 1333MHz RAM: The RAM capacity of the system should be high, hence the system
designed to do several different tasks at the time. The larger the RAM the processing will run
smoothly without a system halt.
 320 GB SATA Hard Disk: Though the system database is stored in the server, other processes
like emails may need to store in local systems. It is not recommended to have larger storage in
client PC’s since the documents are also stored in the server.
 17” LCD display: With 17” LCD the quality of the output will be increase hence it can support
over 1280 x 768 pixel, this will give a better user interface.
 Keyboard: The system requires lot of data entry. A good keyboard will be required to enter the
data.
 Laser Mouse: The system involves pointing and selecting. Hence a good quality mouse is
required.

8
SOFTWARE REQUIREMENTS

When developing software, defining requirements before starting development can save time and
money. A software requirement document clearly defines everything that the software must
accomplish and is a starting base for defining other elements of a product, such as costs and timetables.
There is no replacement for good requirements, but each development organization will take a unique
approach to the process based on their needs.

The software that need to have to run the system are as follows.

SOFTWARE REQUIREMENT FOR NORMAL USER

 Microsoft Windows 10
 Microsoft DotNetFramwork 4.5 or late version
 Microsoft Database Engine

SOFTWARE REQUIREMENT FOR COMPUTER TECHNICIAN

 Microsoft Visual Basic 2017 Professional Edition
 Microsoft Office Access 2016 or late version
 Microsoft Office Visio 2016: for Data Flow Diagram (DFD) and Entity Relationship Diagram
(ERD)

9
SOFTWARE DESCRIPTION

For developing this project “Work order management system” we will be using below tools,

1. Microsoft Visual Studio 2019

2. Microsoft SQL Server 2017

FRONT END

ASP.NET4.6
ASP.NET is more than the next version of Active Server Pages (ASP); it is a unified Web development
platform that provides the services necessary for developers to build enterprise-class Web applications.
While ASP.NET is largely syntax compatible with ASP, it also provides a new programming model and
infrastructure for more secure, scalable, and stable applications. On this project we use ASP.Net since it
is very user friendly and easy programming.

 ASP.NET is a new ASP generation. It is not compatible with Classic ASP, but ASP.NET may
include Classic ASP.
 ASP.NET pages are compiled, which makes them faster than Classic ASP.
 ASP.NET has better language support, a large set of user controls, XML-based components,
and integrated user authentication.
 ASP.NET pages have the extension .aspx, and are normally written in VB (Visual Basic) or C# (C
sharp).
 User controls in ASP.NET can be written in different languages, including C++ and Java.

When a browser requests an ASP.NET file, the ASP.NET engine reads the file, compiles and executes
the scripts in the file, and returns the result to the browser as plain HTML.

ASP.NET is a compiled, .NET-based environment; you can author applications in any .NET compatible
language, including VisualBasic.NET, BASIC, and JScript.NET. Additionally, the entire .NET Framework
is available to any ASP.NET application. Developers can easily access the benefits of these
technologies, which include the managed common language runtime environment, type safety,
inheritance, and so on.

Microsoft released ASP.NET 3.5 on November 19, 2007. Along with it, was released Visual Studio 2008.
This evolution from ASP.NET 2.0 to ASP.NET 3.5 is quiet gradual. ASP.NET 3.5 uses the same engine as
that of ASP.NET 2.0, with some extra features.

10
C#.NET
C#.NET allows you to build powerful, reliable, and scalable distributed applications. C#.NET is based on
the Microsoft .NET framework and uses the .NET features and tools to develop Web applications and
Web services.

 C# language is intended to be a simple, modern, general-purpose, object-oriented

programming language.
 The language, and implementations thereof, should provide support for software engineering
principles such as strong type checking, array bounds checking, detection of attempts to use
uninitialized variables, and automatic garbage collection. Software robustness, durability, and
programmer productivity are important.
 The language is intended for use in developing software components suitable for deployment
in distributed environments.

ADVANTAGES OF C#.NET
 .NET Compatible: - .NET compatibility feature of C#.NET provides applications to use the
features provides by .NET. Some of these features are multi-language support, compiled code,
automatic memory management, and .NET base class library. All C#.NET code is compiled,
rather than interpreted, which allows early binding, strong typing, and just-in-time (JIT)
compilation to native code, automatic memory management, and caching. The .NET base class
library (BCL) provides hundreds of useful classes. This library can be accessed from any. NET
supported language.
 Caching and State Management: - C#.NET provides two types of caching – page caching and
request caching. You use request caching to improve code efficiency and to share common data
across the pages and you use page caching to provide fast access to the Web applications from
clients.C#.NET provides easy-to-use application-state and session-state management, which
allows managing states of Web applications.
 Enhanced Security: C #.NET provides you to authenticate and authorize users for your
applications. You can easily remove, add to, or replace these schemes, depending upon the
needs of your application.
 Inline XML documentation comments.
 Language-Integrated Query (LINQ) which provides built-in query capabilities across a variety of
data sources.

BACKEND

11
FEATURES

Intuitive C++ based Language

Use a language modeled on C++ syntax, immediately familiar to C++ and Java developers, as
well as intuitive new language constructs that greatly simplify
Modern, Component-Oriented Language
Take advantage of inherent support for properties, indexers, delegates, single and
multidimensional arrays, advanced inheritance, attributes, versioning, and XML comments.
Powerful Debugging and Testing Tools
ASP .NET includes a powerful remote and multi-language debugger, enabling developers to
test applications and build reliable multi-tier solutions that span process boundaries and are
written in multiple programming languages.
NET Framework Class Library
Gain mature and powerful, built-in functionality, including a rich set of collection classes,
networking support, multithreading support, string and regular expression classes, and broad
support for XML, XML schemas, XML namespaces, XSLT, XPath, and SOAP.
Robust Web Development Environment
Create Web-based solutions in C# using the shared Web Forms Designer and XML Designer.
Developers can also use IntelliSense features and tag completion or choose the WYSIWYG
editor for drag-and-drop authoring to build interactive Web applications.

LINQ Support LINQ essentially is the composition of many standard query operators that allow you to
work with data in a more intuitive way regardless. The benefits of using LINQ are significant – Compile
time checking C# language queries, and the ability to debug step by step through queries.

Expression Blend Support: Expression blend is XAML generator tool for Silverlight applications. You
can install Expression blend as an embedded plug-in to Visual Studio 2008. By this you can get
extensive web designer and JavaScript tool.

Windows Presentation Foundation: WPF provides you an extensive graphic functionality you never
seen these before. Visual Studio 2008 contains plenty of WPF Windows Presentation Foundation
Library templates. By this a visual developer who is new to .NET, C# and VB.NET can easily develop the
2D and 3D graphic applications. Visual Studio 2008 provides free game development library kits for
games developers. Currently this game development kits are available for C++ and also 2D/3D Dark
Matter one image and sounds sets.

VS 2008 Multi-Targeting Support: Earlier you were not able to working with .NET 1.1 applications
directly in visual studio 2005. Now in Visual studio 2008 you are able to create, run, debug the .NET
2.0, .NET 3.0 and .NET 3.5 applications. You can also deploy .NET 2.0 applications in the machines
which contains only .NET 2.0 not .NET 3.x.

AJAX support for ASP.NET: Previously developer has to install AJAX control library separately that
does not come from VS, but now if you install Visual Studio 2008, you can built-in AJAX control library.
This Ajax Library contains plenty of rich AJAX controls like Menu, TreeView, webparts and also these
components support JSON and VS 2008 contains in built ASP.NET AJAX Control Extenders.

12
Nested Master Page Support: Already Visual Studio 2005 supports nested master pages concept
with .NET 2.0, but the problem with this Visual Studio 2005 that pages based on nested masters can't
be edited using web designer. But now in VS 2008 you can even edit the nested master pages.

PROJECT DESCRIPTION

This project is a new one. This is helpful to staffs who works on Dhiraagu KOC multi tasks. This program
will save a lot of time of the staffs, and minimize the human errors. The Statistical Report can be
prepared by getting the online from the newly compiled database. It provides a platform for the
management to know about the report details. It will also help the contractors to get their work load to
manage and the payment process shall be accelerated.

PROBLEM DEFINITION

Dhiraagu KOC work order management involves a lot of manual data entries and other various time-
consuming process.

 Data stores on shared Google sheets

 Leads to human errors, time consuming and the process slows down
 Duplicated records and work orders for the same work
 Multiple records sheets for almost same work
 Chance of modify/delete data by any of the shared staffs

OVERVIEW OF THE PROJECT

Administrator is the person who deals with the login sections. This person has to enter the details of the
contractors and the pricings of the works to be carried out. And if it changes, make the amendments
accordingly.

Technical staffs deal with the survey and raising the particular work order with accordance to the
survey.

Admin officer can login to the system and proceed with the approval of the work orders

Manager shall login to the system and do the final approval of the work orders.

Customer details are integrated with the billing system, Administrator can override if there are any
changes to the customer details. Admins or technical staff can generate the asset detailed reports from
the database. The reports will be available in a statistical form. For a better understanding we use a
graphical chart including, pie-charts, line charts, bar charts & column charts up to the user to decide on
which their needs.

Contractors also can login to the system, can view the pending work orders, and payments to be
received…etc.

13
MODULE DESCRIPTION

The system design is the architecture of the entire software system. The overall system contains mainly
four modules.

1. Administrator: - The administrator enters the details of the contractors, users, work details,
and the pricing for the particular works. The main purpose of this module is for acts as an
interface between technical staffs, admin staffs and the contractors. They are having the
functionalities of adding the work orders, Updating the work details and the pricings, and also
provision for the Change of password and their own profile.

I. Inbox: which contains the messages send by Contractors.

II. Suggestion Box: suggestions sent by the contractors or staffs.
III. Add User: Adding the users.
IV. Add Contractor: additions of the new contractors.
V. Add works: Adding of works to be done by the contractors.
VI. User Account Details: Can create the user account details.

2. Technical Staff: - The staff login to the system and requests for the new work orders. That are
the main functions of a staff who is doing the survey for the particular customer. Apart from
this function staff’s module add the following:

I. Message: Option for send/view messages to contractors and administrator.

II. Approval: Option to the levels of approval before sending the particular workorder to
contractor.
III. Work order details: option to change the automated work details taken from the
survey.
IV. Profile update: Updating the user profile
V. Change password: User credentials change
VI. Work order amend: Option for the changes, before the final approval of the particular
workorder, which may arise during the work

3. Admin Staff: - Authority of the work order. Has the authority to cancel a particular workorder.
Or decline the process of proceeding to the contractor. Makes the final reports of the
workorders. Also raise the payment process to financial department.

I. Message: Option for send/view messages to contractors and administrator.

II. Approval: Option to the levels of approval before sending the particular workorder to
contractor.
III. Work order details: option to change the automated work details taken from the
survey.
IV. Profile update: Updating the user profile.

14
 V. Change password: User credentials change.
VI. Work order amend: Option for the changes, before the final approval of the particular
workorder, which may arise during the work.
VII. Add Contractor: additions of the new contractors.
VIII. Add works: Adding of works to be done by the contractors.
IX. Amend works: Amend of works to be done by the contractors.
X. Amend price: amend price of works to be done by the contractors.

4. Contractor: - Has no much privileges on the system.

I. Message: Option for send/view messages to Technical & admin staff.

II. Approval: Option to accept the workorder and upon completion of work, submit the
completed detail of the workorder
III. Work order details: View work details taken from the survey.
IV. Profile update: Updating the user profile
V. Change password: User credentials change

DATA FLOW DIAGRAM

Data Flow Diagram represents one of the most ingenious tools used for structured analysis. A data flow
diagram or DFD as it shortly called is known as bubble chart. It has the purpose of clarifying system
requirements and an identifying major transformation that will become programs in System design. It
is the major starting point in the design phase that functionally decompose the requirements
specifications down to lowest level of detail. A DFD consist of serious bubble joined by lines. The bubble
represents data transformation and lines represent data flow in the system.

15
LEVEL0

Accoun
Workor t details
der det
Admin ails

Workorder request
Technical Staff Workorder
Management
rovals System
Report request/app

Admin Staff
ils
o rde r deta
Wor k
Reports/
Contractor Workorder details/
User details

DataBase

16
LEVEL 1 ADMINISTRATOR

Login Error
Login Tab
Login
Page tials
log in creden
ge Ch ec k
Pa
in
Log
To

Home Page
Administrator Home
Page
W
o
Pa rko
g e rd
er
re
po
rt
View report
Reports
Workorder Requirement

LEVEL 1 TECHNICAL STAFF

Login Error
Login Tab
Login
ls
Page
gin credentia
Pa
ge Check lo
in
Log
To

Home Page
Tech Staff Home
Page
W
o
Pa rko
ge rd
er
re
po
rt
View report
Reports
Workorder Requirement

17
LEVEL 1 ADMIN STAFF

Login Error
Login Tab
Login
Page tials
g in creden
Pag
e Check lo
i n
Log
To

Home Page
Admin Staff Home
Page
W
o
Pa rko
g e rd
er
re
po
rt
View report
Reports
Workorder Requirement

LEVEL 1 CONTRACTOR

Login Error
Login Tab
Login
ls
Page
gin credentia
ag
e Check lo
gi nP
o Lo
T

Home Page
Contractor Home
Page
W
o
Pa rko
g e rd
er
re
po
rt
View Pending
Details
Workorder Requirement

18
LEVEL 2 ADMINISTRATOR

Work Details tab

Login Tab Users
Suggestions tab

Update
Update
User
work
Details
Details

Change Update
password Add/Update Update work
Password profiles contractors Details
Change works and price

Suggestions by
users
ADMIN
HOME
To Administrator
Home
Suggestions by
users Add
contracto
Messages by the rs
Contractors

Send/
receive
Contractors tab
Messages

Messages tab

19
 LEVEL 2 TECHNICAL STAFF

Final Changes
Login Tab Users
WO Change

Update
Update
User
work
Details
Details

Change Update
password Add/Update workorde
Password profiles Final Assessment r
Change

Amendment of
workorder
Technical staff
HOME
To Technical Staff
Home
Workorder
Messages of the Approval req
Approvals
Contractors/Admin
Staff/Administrator

Send/
receive
Messages WO Stats

Messages tab

20
 LEVEL 2 ADMIN STAFF

Work Details tab

Login Tab User
s Price tab

Update
Update
User
work
Details
Details

Change
password Add/Update Update Update work
profiles contractors price Details
Password
Change works and price

Price update of
the contractors
ADMIN Staff
HOME
To Admin Staff
Home
Add New
contractors Add
Payment req to Messages by the contracto
rs
Finance Contractors/Techs

Send/
receive
Messages Contractors tab
Payment
process

Messages tab

Payment Req

21
 LEVEL 2 CONTRACTORS

Login Tab Users

WO Change

Update
User
Details
Update
workorde
Change r
password Add/Update
Password profiles
Change
Submission of WO
After work is
completed
Contractors
HOME
To Contractors
Home
Pending works
Messages of the Pending
WO
Contractors/Admin
Staff/Administrator

Send/
receive
Messages WO Stats

Messages tab

22
ER DIAGRAM

The entity relationship (ER) data model has existed for over 35 years. It is well suited to data modelling
for use with databases because it is fairly abstract and is easy to discuss and explain. ER models are
readily translated to relations. ER models, also called an ER schema, are represented by ER diagrams.

user_register
admin_add rule
uname varchar(50) liscen_no varchar(50)
selid varchar(50) name varchar(50)
no varchar(50)
name varchar(50)
gender varchar(20)

Technical_Staff login
pc_id varchar(50) uid varchar(50)
pc_name varchar(50) uname varchar(50)
Staff_name varchar(50) password varchar(50)
uname varchar(50)

User_complaints
Admin_Staff
Msg_id varchar(50)
Staff_id varchar(50)
Uname varchar(50)
staff_name varchar(50)
name varchar(50)
uname varchar(50)
subject varchar(50)

Contractor_info
Case_no varchar(50) Price_info
Contract_id varchar(50) Case_no varchar(50)
Driver_id varchar(50) Day varchar(50)
Desc varchar(50)

Work order_report
WO_rpt_id varchar (50) Works_modi
WO_no varchar (50) Tr_id varchar(50)
cause_accident varchar(50) title varchar(50)
Desc varchar(50)
Pc_name varchar(50)
prepare_report
rpt_id varchar(50)
mnth varchar(50) Contractor_blacklist
year varchar(50) Contr_no varchar(50)
no_injured varchar(50) name varchar(50)

23
DATABASE DESIGN

Database design is the process of producing a detailed data model of a database. This logical data
model contains all the needed logical and physical design choices and physical storage parameters
needed to generate a design in a Data Definition Language, which can then be used to create a
database. A fully attributed data model contains detailed attributes for each entity.

SQL SERVER 2017

SQL Server 2017 was released in October 2nd 2017. It included native support for managing XML data, in
addition correlational data. For this purpose, it defined an xml data type that could be used either as a
data type in database columns or as literals in queries. XML columns can be associated with XSD
schemas; XML data being stored is verified against the schema. XML is converted to an internal binary
data type before being stored in the database. Specialized indexing methods were made available for
XML data. XML data is queried using XQuery; SQL Server 2017 added some extensions to the T-SQL
language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to
XQuery, called XML DML, that allows query-based modifications to XML data. SQL Server 2017 also
allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets
encapsulated with in SOAP (protocol) requests. When the data is accessed over web services, results
are returned as XML.

Common Language Runtime (CLR) integration was introduced with this version, enabling one to
write SQL code as Managed Code by the CLR. For relational data, T-SQL has been augmented with
error handling features (try/catch) and support for recursive queries with CTEs (Common Table
Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and
better error recovery systems. Data pages are check summed for better error resiliency, and optimistic
concurrency support has been added for better performance. Permissions and access control have been
made more granular and the query processor handles concurrent execution of queries in a more
efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a
cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET
Framework

SQL Server 2017 supports previous features like "MARS" (Multiple Active Results Sets), a method of
allowing usage of database connections for multiple purposes.

24
SQL Server 2017 allows DMVs (Dynamic Management Views), which are specialized views and
functions that return server state information that can be used to monitor the health of a server
instance, diagnose problems, and tune performance as on SQL Server 2005.

SQL Server 2017 additional new features

 is now on the platform of or choice; SQL Server 2017 on several Linux distros, that can
run on Docker containers, and SQL VM in Azure, along with the good ol’ SQL Server on
Windows.
 expands its reach to support Graph database technology
 includes automatic database tuning
 supports Machine Learning by adopting Python
 contains new dynamic management views and functions
 has new string functions

TABLE SCHEME

Login

This table describes the login details

Description

Attribute Description Type Examples of values

id Type of user varchar(20) 0

uname username varchar(30) rajukv

password password Varchar(30) !@#WELCOME123

Primary Key uname

Foreign Keys uname

SQL Code Insert,update,select

25
 Work details

This table describes work details for the contractor

Description

Attribute Description Type Examples of values

wname Work Detail varchar(20) Fiber Internal Wiring

c_name Contractor varchar(50) AJ Enterprise

c_number Contractor ID Varchar(100) 190-230-120

w_number Work order ID varchar(20) WO-KOC-2020-0321

cst_name Customer name Varchar(50) Ahmed Ali

cst_contact Contact number Varchar(10) 7985263

cst_Add Customer Address Varchar(50) Viludholhi

Primary Key c_number

Foreign Keys c_number

SQL Code Insert,update,select

26
 contractor_register

This table describes the contractor register details

Description

Attribute Description Type Examples of values

Name of the
name varchar(50) AJ Enterprise
Contractor

c_number Contractor ID Varchar(100) 190-230-120

Maalihaa dhirun
addr address Varchar(50)
1st floor

contact Contact number Varchar(20) 9846100100

email Email id varchar(20) info@ajent.com.mv

uname username Varchar(20) cnt_ajent

Primary Key uname

Foreign Keys uname

SQL Code Insert,update,select

27
 customer_info

This table describes the customer information

Description

Attribute Description Type Examples of values

order_no Order number varchar(20) 01435847539

Order identity
order_id varchar(50) TV128374392
details

cst_name Customer name Varchar(50) Anil Ahmed

service-no Service Number Varchar(50) TV128374392

serv_type Type of service Varchar(30) TV

cst_no Customer contact Varchar(50) 7638492

cst_id Customer ID Varchar(30) A231339

cst_add Customer address varchar(20) Rahmedhuge

Primary Key cst_id

Foreign Keys Service-no

SQL Code Insert,update,select

28
INPUT DESIGN

Input design describes how we designated the input forms. Inaccurate data is most common source of
errors in data processing. Input design is the process of converting user-oriented description of the
inputs to a computer-based business system by programmer-oriented specification. The objective of
input design is to create an input that is to follow and does not include operator errors.

 Login Form: - There are separate login for Staffs and contractors. By entering the correct
username and password the user can enter into their corresponding home page.
 Registration Form: - If the user is new to the system, he can do the registration and can attain a
username and password.
 Technical staff Home: - The staff enter into this section after successful login. Here he can view
the final reports included. From here, he enters the data of the particular work order.
 Contractor Home: - The contractor enters the details of works carried out and submits.
 Admin staff Home: - From where admin staff can view the details of the work orders and
payment process of the particular work order
 Payment request form: - All the payments requests are entered by admin.
 Work details: - The work details are entered with the customer details and the works to be done
by the technical staff
 Contractor: - All the contractor details are entered by admin staff or system administrator.

OUTPUT DESIGN

Computer output is the most important and direct source of information to the user. Efficient and
intelligent output design will improve system relationship with the user. Designing output require
understanding users output requirement, the output format and output devices. We have designed the
output with the objective of its meaningfulness to the potential users.

 Common Report: - To display the total workorders, total customers and total assets as a table
in terms of year.
 Month Report: - To display the workorder report of a particular month in a year as a pie chart.
 Yearly Report: To display the workorder report of particular year as regular report or charts
 View Suggestions: - To view the suggestions send by the users.
 Inbox (Tech Staff): - which contains the messages that are send by administrator, admin staff or
contractor.
 inbox (Admin Staff): -which contains the messages that are send by the contractor, tech staff &
administrator.
 Inbox (Contractor): - which contains the messages that are send by the admin staff, tech staff &
administrator.
 report: which contains the workorder reporting details by the database

29
SYSTEM TESTING

When developing a system, the system designer and the programmers must make sure that the system
is error free and all the processes are working properly. Any system will be developed to solve a
problem or problems. So, at the end of the development, the system should function properly, without
any difficulty. A system with errors and incomplete processes will lead the user to get frustrated, and it
will be a huge loss to the client. Therefore, the system needs to be fully tested.

There are two major type of testing done in system development. They are known as Unit testing and
acceptance testing.

UNIT TESTING

This test will be conducted in the programming level, by the programmers. In this testing the
programmers will fix the bugs which arise in the programming phase.

In the development of the system there were errors that was been found by testing. Almost all the
errors are fixed. But the system is still under development, so the future errors will also be fixed during
the development process.

ACCEPTANCE TESTING

This test will be conducted after the system development process is completed. This test will be done
by the end users. The system will be given to some user to test and to identify the things which need to
be corrected.

To test this system, we gave the system to some of the developers and staff from Dhiraagu KOC and
they found some problems in the system. But the problems they found were minor and it was very easy
to fix, and all the problems they found was now fixed. When the system development is fully
completed, it will be again tested in the both the ways.

TEST CASES

A CASE workbench consists of tools that cover and integrate the entire SDLC, not just a single phase
(that is how it is different from a toolkit). It also offers us with a choice of tools and techniques the DFD
symbols of one methodology and structure chart symbols of another methodology. A workbench
ensures that the output of one phase successfully becomes the input for another phase and that there is
no loss of data between two phases; this is done though the repository.

30
SYSTEM IMPLEMENTATION

Unlike the other phases, there are no standard methodologies for implementation. However,
Implementation Planning is an important activity of the Software Development Life Cycle (SDLC).

However, despite such individual variations there are some kinds of standard activities to be performed
during the implementation process:

 Creation of an Installation plan

 Implementation of physical procedures
 Data preparation and conversion
 Conducting user Training
 Running the system

DATA PREPARATION

Data Preparation is normally the most time consuming and tedious task in the implementation of most
systems.

During the implementation of a new system, all data backlog has to be transcribed to fit into the new
formats and coding schemes, and errors are rigorously checked to ensure no loss of information

Data conversion is the process of converting data from the old system into a format required by the
new, automated system.

USER TRAINING

The successful implementation of any software is dependent in good measure on the quality of training
imparted to the users of the system. Different user groups need to be identified.

A Training need Analysis has to be done for each of these groups to find the kind of training that is
required for each.

Usually two types of users can be identified for the system:

 Hands on users
 End users

31
CONCLUSION & FUTURE ENHANCEMENTS

CONCLUSION

Implementing a good workorder management solution will ensure technical and admin staff of
Dhiraagu KOC enable their work load enhancements. This helps significantly reduce work disruptions
and at the same time reduce the time and effort spent by technical and admin staffs on maintaining
accurate work order records.

We believe that by using of this system, Dhiraagu KOC will manage work order records more efficiently,
and reduce workload, paper work, and use time wisely.

We thank our lecturer Prasanth sir for his valuable time and effort to train us.

FUTURE ENHANCEMENTS

Software improvement is essential because it is the process of making meaningful changes and
enhancements that result in new users or increased benefits realized by existing users. The two most
popular ways to make product improvements are to add new product features or improve existing
ones.

New features expand the scope of the existing software, often making a big development, getting a
version bump, and resulting in some new benefits. Though, the new features are risky, it needs to be
confident that the users will be valued the new features.

Some of the new features of this software:

1. Status of the workorders requested will be viewed for the contractors.

2. Work orders will be mailed to the e-mail of the contractor automatically when it’s created.

3. Responsible person will be notified if the workorder has been completed.

4. Workorders will be printable if it’s required.

5. User will be notified by SMS when a workorder has been raised, completed.

32
APPENDIX

Sample of a work order

33
34
35
REFERENCES

Leave Management System for Hdh.Atoll Council project made for Information Technology Project
(CPT221) Bachelor of Information Technology by Ibrahim Zakariyya & Mohamed Ali from Maldives
National University, 2019.

“Public Transport Accident Monitoring System” sample given by Prasant sir.

Introduction to software engineering Unit 1 by MI College.

Software development process Unit 2 by MI College.

Software development life cycle Unit 3 by MI College.

Requirements Gathering and analysis Unit 4 by MI College.

Analyzing the system & Data modeling Unit 5 by MI College.

Software Design concepts Unit 6 by MI College.

Software maintenance Unit 7 by MI College.

Software Implementation & Case Unit 8 by MI College

36