000845202 kyar nyo thinn project

Myanma Computer Co. Ltd.,
Yangon Campus
B.Sc Top Up Programme
Date: 23 April 2015
A dissertation submitted in partial fulfillment of the requirements for the University of Greenwich’s
Bachelor of Science Degree in Business Information Technology
Word Count: 17,347 words
Supervisor: U SannLwin
PREPARED BY: KYAR NYO THINN
STUDENT ID: 000845202
PROJECT
CONCRETE BLOCK MACHINE WITH
CUSTOMIZED MOLD ONLINE ORDERING AND
DELIVERY SYSTEM

THE UNIVERSITY OF GREENWICH
DEPARTMENT OF
COMPUTING, INFORMATION AND MATHEMATICS
PROJECT REPORT HEADER SHEET
Student NCC Education Registration :
Family Name and Initials :
Project Title : Concrete Block Machine with Customized Mold Online
Ordering and Delivery System
Signed: Date :
Name : KYAR NYO THINN Project First Supervisor : U Sann Lwin
Second Supervisor : U AnungSoe Linn
For Centre of complete :
Date received :
Marker : U Sann Lwin
Total% :
Grade Point :

Abstract
This project will be done under the title "Concrete Block Machine with Customized Mould
Online Ordering and Delivery System" by final year student Kyar Nyo Thinn. This project is a
dissertation of University of Greenwich which must be submitted before 23rd
April, 2015. Main
topic area of this dissertation will focus on computerized project development and management
related theories and practical work. This will be done with the purpose of getting the successful
working system from step by step processes of project life cycle. Therefore, some main research
methods such as analyzing current trend, investigation methods, literature review, comparison
and evaluation on various elements will be done. As the result, various theories concerned with
SDLC, Methodology, Programming and Different Approaches which can get the accurate
business requirements can be applied in this project. Moreover, detailed stages from feasibility to
project roll out can be well understood from this project. To conclude, this project is very useful
to continue my further studies and career. Consequently, I also want to recommend other
students to reference good points and weakness (credit card payment system) from this project.

Acknowledgements
First of all, I would like to thank to my mother, who supports and helps to join with her
business friend’s company.
Secondly, I would like to thank to Sayar U Sann Lwin, my project supervisor who gives
ideas, suggestion and guide lines for my project. And also, he helps the functional scope of the
project.
Moreover, I would like to thank to “YELLOW HANDS Co.,Ltd” Owner, “U Kyaw
Myo” for giving time to answer my interview questions during the busy working hour and staffs
from “YELLOW HANDS Co.,Ltd” for explaining patiently about the company and helping to
get the system requirements.
Finally, Thanks to my friends who support, help and give to me good advices doing
during my project.

Introduction
I am Kyar Nyo Thinn. I am studying B.Sc (Hons) Business IT in Myanma Computer
Company (MCC) Ltd., MCC Training Institute, Yangon Campus. In this semester of BIT course,
I have to take six subjects and a practical computing project.
I have to study four subjects in this second-semester. They are Information Requirements
Analysis (IRA), Information Systems Management (ISM), Database Management and
Administration (DBMA) and Computing Project.
I have to do project in this second-semester course. So I choose to do the project for
“YELLOW HANDS Co.,Ltd” that is Concrete Block Machine with Customized Mould Online
Ordering and Delivery System. Web-based system is used for doing this project. I do my best
this project.

Table of Contents
Abstract....................................................................................................................................................... 3
Acknowledgements..................................................................................................................................... 4
Introduction ................................................................................................................................................ 5
Table of Contents........................................................................................................................................ 6
Section 1 – Background of organization ................................................................................................... 10
1.1 Introduction..................................................................................................................................... 10
1.2 Organization Background ............................................................................................................... 11
1.3 Functions of Existing System.......................................................................................................... 12
Section 2- Feasibility Study Report .......................................................................................................... 13
2.1 Feasibility Study Report.................................................................................................................. 13
2.1.1Technical Feasibility Study....................................................................................................... 13
2.1.2Operational Feasibility Study.................................................................................................... 13
2.1.3 Economic Feasibility Study ..................................................................................................... 14
Section 3 – System Development Life Cycle Model................................................................................. 15
3.1 Waterfall Life Cycle Model ............................................................................................................ 15
3.2 V-Model.......................................................................................................................................... 16
3.3 Spiral Model ................................................................................................................................... 17
3.4 Dynamic System Development Methodology (DSDM) and reason for choosing to use DSDM..... 18
Section 4 - System Development Methodology........................................................................................ 20
4.1 Structure System Analysis and Design Methodology (SSADM) .................................................... 20
4.2 Object Oriented Analysis and Design Methodology (OOADM)..................................................... 21
Section 5 - System Development Approach.............................................................................................. 22
5.1 Prototyping ..................................................................................................................................... 22
5.2 Iterative Development Approach .................................................................................................... 22
5.3 Incremental Development Approach............................................................................................... 23
5.4 Hybrid Approach ............................................................................................................................ 23
Section 6 – Choosing Developing Language ............................................................................................ 24
6.1 ASP.NET ........................................................................................................................................ 24
6.2 PHP................................................................................................................................................. 24
Section 7 - Literature Study and Review................................................................................................... 26
7.1 Literature Search............................................................................................................................. 26

7.1.1 Topics for Investigation ........................................................................................................... 26
7.1.2 Resources and Information Search Details............................................................................... 26
7.1.3 Information Searching.............................................................................................................. 27
7.1.4 Summary and Analysis ............................................................................................................ 27
7.2 Literature Study .............................................................................................................................. 28
7.2.1 Similar Concrete Block Machinery Manufacturing Factories Website Research ..................... 28
7.2.2 Related Website Research for my system ................................................................................ 34
Section 8 – System Investigation .............................................................................................................. 40
Section 9 – Proposed System.................................................................................................................... 43
9.1 WHAT THE PROPOSED SYSTEM WILL DO............................................................................. 43
9.2 Advantages of New System ............................................................................................................ 44
9.3 Functional Scope for User Level of New System............................................................................ 45
Section 10 - Requirement Definition ........................................................................................................ 47
10.1 Functions out of the scope of this system...................................................................................... 47
10.2 Legal, Technical and Social issues................................................................................................ 47
10.3 Functional Requirements .............................................................................................................. 47
10.4 Non-functional Requirements ....................................................................................................... 48
10.5 MoSCoW Prioritized Requirement List ........................................................................................ 48
10.6 Joint Application Design (JAD) Workshop................................................................................... 50
Section 11 – Database Design and Development...................................................................................... 51
11.1 Selection of Database.................................................................................................................... 51
11.1.1 Oracle..................................................................................................................................... 51
11.1.2 Microsoft SQL ....................................................................................................................... 51
11.1.3 MySQL .................................................................................................................................. 52
11.1.4 Oracle Vs MSSQL Vs MySQL .............................................................................................. 53
11.1.5 Why MySQL?........................................................................................................................ 53
11.2 Implementing Database................................................................................................................. 54
11.2.1 Normalization ........................................................................................................................ 55
11.2.2 ERD ....................................................................................................................................... 56
11.2.3 Class Diagram........................................................................................................................ 57
11.2.4 Object Diagram...................................................................................................................... 58
11.2.5 Constructing Database ........................................................................................................... 59
11.2.6 Saving and Displaying Test Data ........................................................................................... 66

11.2.7 Query on enquiry and reporting ............................................................................................. 67
Section 12 – System Design of Logical Design ........................................................................................ 69
12.1 Use Case Diagram......................................................................................................................... 69
12.1.1 Overall Use Case Diagram (High Level)................................................................................ 69
12.1.2 Secondary Use Case of Order Customized Mold ................................................................... 70
12.2 Activity Diagram .......................................................................................................................... 70
12.3 Robustness Diagram ..................................................................................................................... 71
12.4 Sequence Diagram ........................................................................................................................ 71
12.5 State Diagram ............................................................................................................................... 72
12.6 Deployment Diagram.................................................................................................................... 73
12.7 Packaging Diagram....................................................................................................................... 74
Section 13 – System Design of Physical Design....................................................................................... 75
13.1 Website Design............................................................................................................................. 75
Section 14 – Human Computer Interaction............................................................................................... 76
14.1 Human Computer Interaction (HCI) ............................................................................................. 76
14.2 Web page navigation Map ............................................................................................................ 77
Section 15 – Testing ................................................................................................................................. 78
15.1 Test Design ................................................................................................................................... 78
15.1.1 Black Box Testing.................................................................................................................. 79
15.1.2 White Box Testing ................................................................................................................. 79
15.1.3 Grey Box Testing ................................................................................................................... 79
15.1.4 Unit Testing ........................................................................................................................... 80
15.1.5 Integration Testing ................................................................................................................. 80
15.1.6 System Testing....................................................................................................................... 80
15.2 Test Plan for the Yellow Hands System........................................................................................ 81
15.3 Test Cases ..................................................................................................................................... 82
15.4 Test Log........................................................................................................................................ 86
Section 16 – Implementation Process ....................................................................................................... 87
Section 17 – Security Issues...................................................................................................................... 90
17.1 Potential Treats ............................................................................................................................. 90
17.2 Contingency Plan.......................................................................................................................... 91
Section 18 – Critical Appraisal and Conclusion........................................................................................ 93
18.1 Critical Appraisal.......................................................................................................................... 93

18.2 Conclusion .................................................................................................................................... 97
References ................................................................................................................................................ 98
Bibliography ........................................................................................................................................... 100
Appendices ............................................................................................................................................. 103
Appendix (A) – Proposal .................................................................................................................... 103
A - 1 Introduction ........................................................................................................................... 104
A - 2 Key Phrases ........................................................................................................................... 105
A - 3 Aim and Objectives of the Proposed System ......................................................................... 106
A - 4 Requirements of client computers for running the system ..................................................... 108
Appendix (B) - Project Development Plan and Schedule.................................................................... 109
B - 1 Project Development Plan...................................................................................................... 109
B –2 Project Development Schedule............................................................................................... 112
Appendix (C) – System Investigation Methods .................................................................................. 113
C – 1 Interview and Systems Study................................................................................................. 113
C - 2 Study and analysis of existing system .................................................................................... 119
Appendix (D) – System Design of Logical Design............................................................................. 120
D – 1 Use Cases and Use Case Descriptions................................................................................... 120
D – 2 Activity Diagram................................................................................................................... 133
D – 3 Robustness Diagram.............................................................................................................. 136
D – 4 Sequence Diagram ................................................................................................................ 138
D – 5 State Diagram........................................................................................................................ 139
D – 6 Packaging Diagram ............................................................................................................... 140
Appendix (E) – System Design of Physical Design ............................................................................ 141
E – 1 Website Design.......................................................................................................................... 141

Section 1 – Background of organization
1.1 Introduction
Nowadays, communication becomes very important for all people in the world. The Internet
offers many advantages to the business organizations and its customers. Likewise, business
organizations are also competing with each other so much in the market share. Therefore, they
want to understand the customer's demand and want long term relationship. At present, many
organizations work over the internet by using computers, tablets and mobile phones.
Increasing internet usage makes some organizations to change manual system to computerized
system. By using online system, everything will be streamline with 24 hour online storefront.
With less human resource and more service time, order can be increased and customers can make
enquiry at any time.
Moreover, advertising can be made with online system and this can reach worldwide. Operation
within Yellow Hands and outside the company can be better. Therefore, “YELLOW HANDS
Co., Ltd” strongly agreed to change some manual processes as online ordering website.
Therefore, current Yellow Hands system will be analyzed and its functions will be pointed out so
that they can be upgrade in the new system.

1.2 Organization Background
Yellow Hands Company Limited is a big size organization which is producing and selling
various concrete block machines and its related things. Currently, “YELLOW HANDS Co.,Ltd”
runs by using a manual system for ordering. “Concrete Block Machines” are mainly produced by
company and it also produces other products such as “Mixers” and “Molds”.
This company was started well since 1995 and it produced firstly “Concrete Block Machine
Korean Hydraulic System” by guidance of engineers. Mainly, there are three types of “Concrete
Block Machines” such as “Manual”, “Pneumatic” and “Hydraulic”. According to these guidance,
ideas and good production methods of the engineers, the company can produce the machines
such as greatest quality machine, updated models machines and fair cost machine for customers,
others construction companies and others.
Secondly, company produced “Mixers” (small and big sizes) and many types of “Molds Design”.
There are two main types of molds such as “Mold for Building” and “Mold for Pavements”.
Company has two showrooms in Mandalay and Yangon which are opened weekdays from 9 am
to 5 pm. The company is comprised with two main stakeholders and operating as the best
company in selling concrete block machines. Therefore, it is well known among the construction
companies.
Yellow Hands Company is intended to improve the construction field of Myanmar in the future.
Therefore, they are selling their products with high quality and reasonable prices so that
modernized and high standard buildings can be built throughout the countries. Moreover, Yellow
Hands also partner with KBZ bank for allowing the customers to pay money with installment.
Therefore, every people can start their business with a little money.

1.3 Functions of Existing System
Functions of Yellow Hands are similar with other retail shops. Therefore, existing system of
Yellow Hands has the following main functions:
 Recording raw materials and things which are included in each machine
 Registering the new machines and mould
 Selling product information
 Saving customer contact information
 Adding new staff biography
 Adding stock
 Invoicing
 Monthly order reports
 Designing customized mould
 Make payment with KBZ bank transfer
Since this system is manual one, all information is recorded by staffs of Yellow Hands.
Therefore, there is only one end-user type in this manual Yellow Hands System. Apart from this,
there are many problems with this manual system. They will be listed down as follow:
 Waste of time to visit the show room for customers (especially for customers from other
cities)
 Customers cannot choose and compare machinery easily
 Cannot reply 24 hours customer's enquiry service
 Gap with Yellow Hands' latest machinery information
 Staffs cannot check daily order list and stock quantity
 Information mismatched or wrongly recorded
 Inconsistent use of data recording system
 Requiring more human resources in handling order and replying customer's enquiries.
 Order cannot be performed with high speed

Section 2- Feasibility Study Report
2.1 Feasibility Study Report
Feasibility stage is the very initial stage of a project life cycle. Every project must go under this
feasibility stage before moving to any further stages. If this stage has not been done properly and
project is carried out, there can be a lot risks and waste in money and time can happen. Therefore
this feasibility checking will be done for Yellow Hands Project to access whether this is a worthy
project in terms of tangible and intangible benefits. There are three different feasibilities
checking in terms of technical, operational and economic behavior.
2.1.1Technical Feasibility Study
Technical feasibility must be checked before starting the software project so that stakeholders
can weigh whether the proposed project can be actually built and whether there are enough
technicians who can create this. For this Yellow Hands project, some technical skills such as
PHP, MySQL, DSDM, OOADM and UML are very essential to be proficient. This project is
going to be developed by myself and I am good at these technologies. Therefore, this project is
technically feasible to develop.
2.1.2Operational Feasibility Study
Operational feasibility must be checked to decide whether the stakeholders can get the
operational benefits in their working environment or not. This will be measured by analyzing
how well Yellow Hands can well operate with this new online system and how much this system
can assist both staffs and customers in making their daily operational activities.
As the result of analyzing Yellow Hands system, it is obvious that 24-hours every day working is
ability found to be the best thing which can help the operation of Yellow Hands without having
staffs in charge. Apart from this, repetitive tasks of staffs can be less than before because they
can order system just by one click. Thus, this feasibility testing has no problem with new Yellow
Hands System.

2.1.3 Economic Feasibility Study
Economic Feasibility must be checked to compare the costs and benefits which can be resulted
from the proposed online system. If proposed system has more benefits than costs, this system
should be chosen to develop. In calculating the costs for Yellow Hands system, some
development costs must be spent. To develop this online project and host it on the internet,
website development fees, hosting and domain fees are required. This will be about $1500 and
maintenance fees are also required to annually host the website and maintain the contents.
Since website must be used online, Yellow Hands must also buy Internet plan for their staff. In
Myanmar, fiber internet line is the best. For Yellow Hands, 2MB internet plan must be purchased
and it will be about $120 dollars per month. However, many benefits can also be found with this
system. With online system, customer's orders can be increased and customers can get more
satisfaction. Therefore, regular customers can be kept. After calculating NPV value, breakeven
point is forecasted to be reached within four years. Therefore, Yellow Hands Project is
economically feasible.

Section 3 – System Development Life Cycle Model
The success of a software project can be decided by tracing back its SDLC. Likewise, SDLC
provides the developers a quick way to access each activity. This is because SDLC can clearly
show work phases for system developers so that they can plan for designing, building, testing
and delivering the software projects. According to (GeekInterviews, 2008), SDLC can give the
clear ideas to the developers concerned with dos and don'ts while building the system. Since it
already has the clear ideas which can solve the problem domains, detailed plan with less error
can be created by following a SDLC. Since every process can be predefined before writing a
single code, the project's goals can be achieved on time.
SDLC is used to get the high quality systems which meet the customer requirements by
managing all processes clearly within the schedule timeframes and estimated costs. Therefore,
most software projects are developed by using it because the nature of these kinds of projects is
complex and difficult to predict. Therefore, I chose a SDLC to use with Yellow Hands so that the
best results can be got while developing this system. Some common SDLC used by software
industry are as following: Waterfall, V-model, Spiral and DSDM. After comparing these four
SDLC, I decided to use DSDM for this Yellow Hands project development.
3.1 Waterfall Life Cycle Model
Referenced from (Point, 2014), Waterfall Model was the firstly developed SDLC model for
ensuring the success of projects in the software engineering industry. This model is sometimes
defined as the linear-sequential SDLC. This is because it can illustrate all software development
processes in the linear sequential style. In other word, any phases in this development cycle only
starts if the previous one is complete. Therefore, phases in this waterfall model do not overlap
with each other. Since this is the most first developed SDLC, everything is designed for ease of
use and simplicity. Therefore, some advantages can be got from this model. For example, it is
easy to implement and too much resources are not required. However, it defines that one stage
cannot move after beginning the next one. This means that it does not have backward processes
for a finished phase in this SDLC. In the real world, there is always a need to go back to finished
phase. This can create the weakness of projects as well as this SDLC.

Because of this weakness, I cannot use this model for Yellow Hands project. Since I need to
trace back to finished phases and change the requirements to get the requirements correct, this
model has limitation for requirements of Yellow Hands.
3.2 V-Model
This V model SDLC is the extension of the waterfall model. However, it deviates from the
waterfall a little. The typical waterfall linearly goes downwards while phases in V model are
moving upwards after completing coding stage forming V shape. Another thing V-shape is
different from waterfall is including early test planning.
Since the purpose of V model is to do verification and validation, product testing is designed to
carry out in parallel with the development. This kind of model can be used for every kind of
project requirement. Moreover, going back to anywhere can be done during project development.
Although it is better than waterfall model, it still has some disadvantages and limitations. It
should only be applied only for small and medium projects and their requirements must be fixed
and defined first. However, this model would not be flexible to use for Yellow Hands Project
because this will not allow for making adjustments and for fixing wrong requirements during
development. Moreover, it needs resources a lot to use and my project has limitation for
resources.

3.3 Spiral Model
Spiral model uses the ideas of iterative development with systematic and well controlled some
aspects of waterfall model. It also combines two models such as waterfall and prototyping. In
other words, it is formed by combing sequential linear development model and the iterative
development model. Therefore, this can also be stated that upgraded waterfall model version of
high emphasis for risk. A good point of this model is allowing for incremental releases.
Refinements can be made by iterations around the spiral. Therefore, this model is suitable for
high-risk, large and complex projects. However, (TutorialPoints, 2014) stated that this model is
only good for long-term project because requirements can change with time and must develop all
these requirements. If changes are not well controlled, projects can be under high risks because
costs can be higher and requiring more time. Therefore, there are two main components such as
risk analysis and evolutionary processes which must be checked for the developers.

3.4 Dynamic System Development Methodology (DSDM) and reason for
choosing to use DSDM
DSDM is designed to fix the problems of RAD by adding some new disciplines to the existing
RAD. But, it is not a methodology and it is only a control framework. Their main difference is
that reducing development time by DSDM framework because DSDM's main goal is to
delivering high flexibility project with shorten development period.
Moreover, DSDM emphasize on active participation of users. Its iterative software production
nature and active participation help in identifying the requirements with minimal risks and less
time. Apart from this, necessary documents can be easily produced for facilitating the current
development and also for the future maintenance.
Therefore, (DSDM, 2014) described that this is a robust Agile project development monitoring
framework which can deliver the right solutions at the exact time when solutions are needed.
Since it has lots of advantages, it has been the leading Agile approach framework for decades
because it can provide a good project governance with added flexibility and agility. Therefore, a
lot of different organizations from both private and public sector are applying DSDM over two
decades.
This framework is designed to be vendor-independent and it includes the whole lifecycle of
project. With these best practice guidance, project can be completed on time, in the efficient and
effective budget manner. Now, this is the proven scalability framework which can be used for
addressing all project sizes in all business sectors.
DSDM mainly includes five phases: Feasibility Study, Business Study, Functional Model
Iteration, Design and Build Iteration and, finally Implementation. To assist these five phases,
DSDM Consortium describes nine principles to apply for DSDM projects. This can be checked
in the following DSDM figure. Moreover, there are four additional techniques (MoSCoW, JAD,
Prototype and Timeboxing) available for projects.

Reason for choosing DSDM
When deciding to choose the methodology, we must first understand the nature of our Project:
Yellow Hands. It is medium sized project with not complex calculation functions and requires
short time project development time. Six months time is very short for the real world project to
complete on time.
Moreover, Yellow Hands Company has interactive stakeholders who are very interested in
developing this project. Apart from this, functions and end-user types for this Yellow Hands
Project can be easily defined. These functions can be divided into some smaller ones for separate
development.
Since I am not too much familiar with such kind of ecommerce website, requirements must be
refined again and again during development. Therefore, only methodology which allows
iteration can be used. Moreover, business requirements must be incrementally shown to the
supervisors. Therefore, only DSDM is suitable with the nature of Yellow Hands.
To use this DSDM, required technical components are analyzed and I can conclude that all of
them are feasible and possible to use. I am also familiar with DSDM for developing this project.
Moreover, development team which will hand over this project after being finalized by me is
also proficient in using DSDM. For all these reasons, I chose DSDM as the one for Yellow
Hands Project.

Section 4 - System Development Methodology
4.1 Structure System Analysis and Design Methodology (SSADM)
SSADM is a special methodology designed for analyzing and designing IS Systems. Nowadays,
a lot of business organizations and consultants are using it. It was created in UK in 1980 to be
used as the standard for database projects. According to (Janssen, 2012), it is open standard
which is created based on Waterfall model. It takes nature of Waterfall from feasibility stage to
physical design stage. The most obvious feature is encouraging intensive user involvement at the
stage of requirements analysis. Users must agree the requirements after finishing this stage. They
must provide clear data about their system. After that, they do not need to involve with system
development. SSADM makes project as various stages and modules. Three famous modelling
techniques of SSADM are logical data, data flow and entity behavior.
Advantages of SSADM
 Can get quality information systems
 Enhance the methods of controlling and managing projects
 Better documentation standards and can use computer-aided software engineering tools
Disadvantages of SSADM
 SSADM makes it special emphasis on creating heavy documentation and analysis stage.
Sometimes, this can cause over-analysing and waste resources.
 Only good with large sized systems.
 Can take long duration and need high resources

4.2 Object Oriented Analysis and Design Methodology (OOADM)
OOADM appeared in order to solve the weakness in development of complicated projects, which
cannot be satisfied only with programming languages. Its focus is largely on object-oriented
analysis and design methodologies, procedures and functions. However, it can be said that
behavior of the system is more emphasized in this methodology.
Object includes data and operations which are united into the single unit. And, this includes real-
world elements which interact with information system. Each object may include different
attributes and similar object categories.
This methodology has two main sections. As its name stated, two parts: analysis and design in
object-oriented manner are included. This methodology models system functional requirements.
Unlike other methodology, OOAD mainly guide the developer with the guidance of what to
carry out to get the functional results of system. Moreover, it is used to identify the needs of
people who will use the system and the essential objects.
By using OOAD, conceptual models like various diagrams which can depict the whole system
with simple diagrams can be resulted. This can assist the developers to identify all problem areas
and also can be used to check system requirements.
Although OOAD has various techniques, Unified Modeling Language (UML) is the most useful
and effective ones. This let developers easily visualize about the system and then construct all
the necessary business models, functions and software systems. The followings diagrams are
involved in UML: they are Use Case Diagram, Class Diagram, Sequence Diagram, Activity
Diagram, State Diagram, Robustness Diagram, Deployment Diagram, Package Diagram and they
are used to understand the requirement of the system parts of analysis phase and design phase.
Advantages of OOADM
 To solve problems of complex applications development
 To help understanding more about problem domains
 To show the problem areas in more abstract detailed level
 To ensure system requirements are correct before moving to coding

Reason for choosing Object Oriented Analysis and Design Methodology with UML
After analyzing SSADM and OOADM, I think OOADM is a lot more suitable than SSADM.
SSADM costs a lot because of its heavy documentation and very detailed steps. Moreover, time
will take a lot in developing Yellow Hands Project. Apart from this, it can show only three views
of the system.
In contrast, OOADM does not require very much detail processes and high costs. Its famous
UML modelling can give the best demonstration of Yellow Hands System with nine diagrams
which show hardware, software, network, users and functional requirements. Moreover,
stakeholders can easily understand all these diagrams. Since it is also easy to draw even with pen
and on paper, I chose it for its ease of use and descriptive nature.
Section 5 - System Development Approach
5.1 Prototyping
In this prototyping model, four main stages exist to help the developers. These stages are:
identifying, developing, reviewing and revising. Processes of prototyping include all activities of
designing and implementing sample prototypes concerned with software projects. These
prototypes include all functional requirements of proposed system. However, this is not the
complete product for final result of a project. Two kinds of prototypes: evolutionary (built into
final product) and throwaway (not use in final product) can be found.
5.2 Iterative Development Approach
This iterative development approach does not try starting with the complete specification of
system requirements. Development stage begins by gathering requirements and then delivering
part of software in the working release. These parts can later be reviewed so that further
requirements can be identified. Throughout project life cycle, these processes are repeated so that
a new software version can be produced. Time-boxing is the best technique to control the
iterative development. The nature and duration iterative development approach changes in
accordance with project nature. This approach should be chosen when project is big and can split
into smaller parts.

5.3 Incremental Development Approach
This kind of development approach namely incremental model can be said as a type of
evolutionary model. This is because it breaks down and develops the functions in the multiple
linear sequences manner. For example, big functions are divided into modules. Each of them
passes all stages of product life cycle started from requirements finding to testing. Each
subsequent module must integrate with the previous one and this development process must
continue until final system is delivered. This approach can deliver project quickly and testing can
be done easier to the smaller module.
5.4 Hybrid Approach
This is the combination of iterative and incremental approach. Therefore, it possesses the nature
of both approaches. By using this approach, products can be delivered incrementally just like in
incremental approach. Moreover, if there are any changes to the existing defined requirements,
iteration can be used to go back to previous stages to change the requirements.
Reason for choosing to use Hybrid Approach
Hybrid approach must be used for Yellow Hands project because of these strong facts. Firstly, I
have to meet with supervisors frequently. Therefore, I will have to show him some progress to
check whether the work done by me is on the right track or not. Therefore, incremental approach
should be used to achieve this goal. Moreover, if there are changes made by supervisor, I will
have to update the finished work. Therefore, I will need iterative approach to do this. These are
the reasons why I chose hybrid approach.

Section 6 – Choosing Developing Language
6.1 ASP.NET
ASP.Net is a complied language which is also based on object oriented programming language.
The strong point of it is having the libraries which have been designed to provide the reusable
classes. This technology is the member of .NET Framework because it is Microsoft product.
Therefore, any classes in .NET framework which can be used by ASP.NET applications can be
accessible. Therefore, this makes developer less effort in writing code.
Additionally, Visual Studio IDE is a powerful one for the designers and developers because of its
drag and drop and other debugging features, etc. Therefore, time can be saved and design can be
done in the effective manner. Debugging and tracing tool can also increase the efficiency of the
developer and errors can be detected within few minutes.
6.2 PHP
When PHP is firstly evolved, it was named as "Personal Home Page". However, demand of
using PHP is high and it was now using worldwide. Therefore, its name becomes unmatched
with its demand. And then, it changed its name into "Hypertext Pre Processor".
At present, this server side language is the most widely utilized scripting language found in may
websites. PHP is very suitable with website or web application development because it is
specially developed for web platforms. Although desktop application can also be written by
PHP, it is not the main choice for the programmer.
The main point which makes PHP famous is being open source software. Everyone can use it
free and do not need to worry vendor attached problems. Apart from this, it has high
compatibility because it proves to be compatible with different DBMSs. Moreover, its cross
platform ability seems to be famous too.

Reason for choosing PHP
The best reason for choosing PHP over ASP.NET is being open source rather than proprietary
software. This Yellow Hands Project is intended for my third year final project and I do not
know whether this will continue using by the stakeholders. Therefore, I chose to be low cost with
good built-in functions.
In this century, developers love open source technology over proprietary. Therefore, there is a
large community formed by the result of this. Developers from this community also share their
knowledge and try to improve PHP better than before. Therefore, bug free and low cost project
can be got with the help from this big community.
Moreover, scripting language like PHP has more productivity than compile language like
ASP.NET according to the research. The last reason is that PHP can run with different platforms
like OSX, Windows, Linux, etc. Thus, this will be useful while developing the project.

Section 7 - Literature Study and Review
7.1 Literature Search
7.1.1 Topics for Investigation
According to my project system, I will search the similar and related systems to use in my
project. We must study the literatures that are suitable with our project system. In my project, it
is concerning with ordering with customized system, delivering and payment system. So, I made
researching the literatures suitable for my project of topics for investigation such as:
 Online Concrete Block Machines and Moulds Sales Company
 Concrete Block Machines with customized moulds online ordering and delivery company
 Nature of E-commerce for online sales
 Online E-Commerce Market
 Online Customized Pre-ordered system
 Online E- Commerce payment system in Myanmar
 Online E-Commerce Services Free delivery system
7.1.2 Resources and Information Search Details
By studying Literatures, we can get different types of resource by searching from journals,
magazines, newspapers, business and IT e-books, the internet and others knowledge books and I
will be reused good resources in my project.
The information of similar websites and related websites for project gets from business and IT e-
books, journals, newspaper, study about the banks and e-commerce payment system in Myanmar
will be searched at library of my university and others library.
And also, the online customized ordering and delivery system and online e-commerce payment
system in Myanmar by surfing internet.

7.1.3 Information Searching
Now, I want to show the lists of journals, newspaper and websites links from Myanmar
languages internet search. And, I will use the information of searching in the literature review.
The information searching is as following:
Journals
 Planet Journal
 INTERNET Journal
 Net Guide Journal
Newspaper
 Myanmar Times
Internet Search
 www.planet.com.mm
 www.internetjournal.com.mm
 www.myanmar-business.org/
 www.elevenmyanmar.com/
 www.mmtimes.com/
 http://myanmar.mmtimes.com/
 http://www.cbbankmm.com/
 http://www.kbzbank.com/
7.1.4 Summary and Analysis
I have made analysis about other website similar to be with my application. And also I
discovered other related websites that has some features are the same in my application. By
means of studying this website I got some valuable experience about the function to include in
my application and get requirements to apply in my application.

7.2 Literature Study
7.2.1 Similar Concrete Block Machinery Manufacturing Factories Website Research
Firstly, I want to say about the similar literatures websites and there is no concrete block
machinery manufacturing factory website in Myanmar after studying and researching from all
countries of similar websites. So, I will explain two similar websites in other countries by
researching literatures from online internet.
7.2.1.1 About First Similar Website
Overview- Referenced from (Columbia Complete Concrete Product Solutions & Support ,
2015), this “Columbia Complete Concrete Product Solutions & Support” company website is
products advertising and ordering website from online internet. This company manufactures
many machines related with concrete blocks and other accessories products. In this website,
customer can view the products and others detail information as the customer wants. By online
internet register information with e-mail, customers can order products as they want. In this
system, customers can ask questions with e-mail such as about products and others which they
want to know.
Site map of Columbia company website
This site explains about products, molds, applications, customer care, about us, tradeshows and
blog.

Explaining in these functions of site map, products site will display three types of Concrete
Products Machines that the company can design. And also there are other types of products such
as Batching and Mixing, Product Handling, Accessories, Specialty Products and Plant Designs.
The main part of this site is molds. In this part there will be shown in details of mold that will
provide. In concrete products, they will display the types of molds that they can produce. The
customer can get the best design and beautifully products can be used for different purposes.
Design2Production, Mold Services, Mold Technical Support, Non-Columbia Molds, Large Pallet
Molds, Textures are including in about molds of this company. The customer can create all types
of design as they shown in website.
This company divides their applications site that they can create in three kinds of concrete
blocks. As they have been shown in website, the three types of concrete block are pavers,
concrete blocks, and retaining walls. In this applications site, this company clarifies about to
increase profits for customers by using their simple and fast mold change machines.
In customer care menu, they will provide their support contact information. They will display
about the service that can support for customer.
About us will explain their company information such as corporate divisions, partnership &
ventures, employment, history, locations, contact us information.

Functions of this company website
This website is developed to sell the concrete block machines around the world wide range. The
customer can buy the concrete block machine depends on their desires. This website divides five
functions to use. The customer can select their required machines in products function menu.
When they click on products, all types of machines will display on the left side of the site. The
customer can choose one as they want to see in details. This function is very useful for any type
of customers. The customer can decide easily what they want and what they need. The product
display function will show all available types.
Moreover, search box is also given at the top and this makes customers easy to search with
product name. In addition to this, there is a breadcrumb which lets users know on which page
they are and they can easily go back to the previous pages.
Advantages of this company website
Localization of language is also available. Therefore, this increases the efficiency of the
website. Using social icons can also make the company's brand more reachable to the
audience. This is the best choice for word of mouth marketing. Products categories can be
seen on left side of every page. Therefore, this is good for navigation. Apart from this, this
website is intended to help the customers too because contact us link and company's phone
no are put on top. Therefore, customers can easily contact company if they want to know
more detailed information or if they need help with company's service.
Disadvantages of this company website
There is no clear description for online payment system. Therefore, customers can get confused
when making payment. Moreover, there is no security assurance shown on the website and this
can decrease the potential order made by new customers. Another weak point is that website
cannot give the advanced searching to the customers. Another thing what we can conclude is that
it has lots of pages which are described as submenus under specific main menu. Although they
are described with well-arranged submenus, navigation system seems a bit complex.

Review on website design
Website design is the simplest design I have ever seen. As this is business website, the use
of colour is blue and white which represents business. Since black background is used, this
makes white website body more visible to the users. No advanced web technologies are seen
to be used. Therefore, website looks less attractive than other modernized one. However, a
good arrangement of website layout is found on this Columbia website.
7.2.1.2 About Second Similar Website
Overview
Referenced from (OLX, 2015), OLX is the international trading companies and has branches in
Philippines, Thailand and Indonesia. It is selling various machinery such as tools, generates,
concrete block machine and other accessories. It is a website which connects supplier and buyer
to make selling and buying the machinery online. Since there are different people from three
different countries, it can be assumed that this website has a strong customer base.

Site map of Company Website
It does not have too much pages and only following pages are included. Therefore, sitemap
structure is very simple unlike other ecommerce website. However, it still has the essential
informational pages which can let customers understand about company its services and policies.
They are as follow:
 About OLX
 Careers
 Disclaimer
 Privacy Policy
 Help Center
 Forum
 Register
 Login > Product Detail
 Help
Functions of this company website
It has the efficient product display page with sorting options and paging system. For example,
customers can arrange the products with posted date, price and updated date. Moreover,
customers can choose total items which can be displayed per page (20, 50, 100, 200) with paging.
A good searching system which allows searching with price, category, location, warranty and
posted date is also found on this website. Moreover, product can be searched with their name too.
Therefore, this website is perfect with customized search functions.
This website advertises their brand with social media. Lots of social media such as facebook,
google +, twitter, youtube, instagram and pinterest can draw the attention of the customers more
by keeping the customers in touch with OLX information on any social media. Moreover, total
members of OLX and currently using guests are mentioned on footer and this can let the
customers realize that OLX has lots of customers who believe in doing business with them.
Other help features such as back to top feature and help features can be found. Therefore, this
can give better usability to the customers.

Poor in navigation structure because users cannot see the navigation menu at the top of the page.
Navigation links are only included on the footer. Therefore, it is not easy to see and needs effort
to go to the footer every time users want to go to another page. No advanced security is shown
on this OLX web page although company's policies and disclaimers are well mentioned on OLX
website.
Review on Website Design
Simple and clear website design and layout are created for this OLX website. Therefore, this
website can be said as a good business website with the good choice of match colors such as
white, black, blue and gray. For the price, red color in bold font style is used, and therefore, users
can easily identify the price because red is the bright color. Topics are used with different colors
and large font sizes to let the visitors see the main points on the website. Therefore, website
design is perfect with simple use of design elements by blending with correct use of color.
7.2.1.3 Functions from above similar websites to use in my system
According to the study of above similar websites, I will know the requirements and good plans to
become a perfect system. After analyzing and studying these two websites, I like to use and add
some ideas of functions and advantages of them into my system. Moreover, I will also add some
essential functions and things after fixing the disadvantages as well as bugs from these websites.
For website design, simple and neat layout design style will be considered for Yellow Hands
website. Moreover, attractive product images will be needed to make website fabulous.
Advanced search and paging for products must be included. Moreover, advertising with social
media is the most efficient during these days. Thus, the most popular facebook and twitter will
be used for advertising products of Yellow Hands.
Navigational links will be shown with top menu navigation bar, left category bar and footer page
links. With these three main navigation systems, customers can get the easy navigation system.
When choosing the main theme color, yellow is decided to use because company name is Yellow
Hands. Therefore, its symbolic color Yellow must be used. Other colors which will match with
yellow will be used to create a beautiful website.

Help functions such as FAQs, contact page, policy pages and breadcrumb will be created for
better efficiency and better help for visitors. Apart from this, security issues must be considered
and concerns of customers will be reduced by showing SSL security logo on Yellow Hands
website.
7.2.2 Related Website Research for my system
In this online era, e-commerce trend becomes the most used word and almost all business
companies apply this e-commerce system together with online payment. E-commerce sometimes
called as e-business can be defined as the interactive processes such as buying, selling, sharing
and exchanging products or information with the help of online network.
In my country, online shopping becomes trendy. Therefore, I would like to make some research
for related website search for payment system used in here.
In Myanmar, there are populated banks: KBZ, CB, AGD, etc,..Almost banks use now online
payment system in Myanmar. They are “MyanPay”, “Paypal”, “ATM” by linking with “MPU”,
“Visa” and “Master” card. But, “MyanPay Online Payment System” is most famous using
among people in Myanmar.
We can make payment by using with these online payment systems among the e-commerce. By
using online payment system, we can get many advantages and we can save time and money.
I want to explain about studying online payment system because I founded the weakness of
online payment system in Myanmar and it is associated with my project web research that is no
e-commerce of concrete block machines with customized molds online ordering and delivery
system sales website in Myanmar.
But, I will show the related e-commerce websites of their functions to use in my system by
studying their online payment system in Myanmar.

7.2.2.1 About Related E-commerce Online Payment Website in Myanmar
After studying the literatures, I founded one related e-commerce with online payment website in
Myanmar that is “ZawGyi Mart Online Store”, referenced from (ZawGyiMart , 2015).
Overview– “ZawGyi Mart E-Commerce Web Site”uses with e-commerce online payment
system. In this “ZawGyi Mart Online Store” website, customers can order different kinds of
different brands from online internet. This website can make two types of payments that is
Myanmar Kyats (MMK) or USD by using online MyanPay Payment Gateway, PayPal, Cash on
Delivery and Bank Transfer.
Functions for customer in this site
In this online store website, we can see the functions of in this system are as follows:
 Can know about the functions of this site
 Can see many categories
 Can search and view the products to order as we want
 Can create new account to login and order
 Must make registration by user
 Can make ordering and choosing the products by price range with quantity number
 Can review each own shopping cart how much products of quantity we buy
 After review, customer can order and check out with online payments by looking the total
payments
 Therefore, customers can also make pre-order of other products as they need with
customized system.

 Can logout from own account
 Can look from facebook connect with this website
Advantages of this online website
 Prices can be viewed in Kyats and Dollars
 Free delivery service is provided
 Payment options are described on footer
 Integration with social networks
 Many help features and good policy
Disadvantages of this online website
 Left side bar only appears on mouse over.
 Therefore, customers cannot easily see all product categories at once.
 Lot of advertisements on website.
 Clear white background and black text (not attractive but simple)
 Dull colour grey is also used
 Good looking icons are used for better usability
 Bold and big font for important data such as topic and important button (buy now)
 Simple navigation website
 No animation effect make less attention on website

7.2.2.2 About Related Machines Company website not in Myanmar
Overview– Referenced from (TONGLI MACHINERY, 2015), “Henan Tong Li Machinery
Manufacturing Co., Ltd” manufactures many machines products. This website is an online
ordering and delivery website of many different machines and different categories. If the user
ordering, user firstly makes the information register. Payments will made online payment or e-
credit with USD. And then, it will make delivery to user who is ordering the product.
Functions of the site
In this company websites, we can see the functions of in this system are:
 Can view and search the products
 Can choose the products by model number with price range
 Can make ordering the products
 To join the supplier with e-mail
 Can create new account to order
 Sign-in or join-in free
 To make the user information register
 Can make order registration the product by product description, quantity, unit, price
(USD) and amount (USD).
 To make the information of the delivery type with shipping method such as “Sea
Freight”, “Air Cargo”, “Express”
 Can choose payment method: ESCROW, e-Credit Line and others
 To make “New Shipping Address” and submit

 To review the “Order Preview” completely
 Can calculate and view the total amount of order
Firstly, I think that there are a lot of benefits in this system such as:
 If user want to know about company, they can see at “Company Profile” page
 They show the list of many product categories and their details at the “Product
Categories” page.
 User or customer can easily search and select from the products
 They show their products by model number with price range
 User can order the products with price range from online direct
 After ordering and registration, it can show the summary costs with overview of order
form after the user ordering as they want quantity
 Can make online payment with bank transfer or with credit card
 And then, they will reply the confirm with e-mail
The disadvantages of this system are-
 It cannot show the services such as discount promotions, delivery charges discount
 I think that it should show the discount promotions because every user want to know the
services or promotions discount
 Website design, especially, header and navigation bar design can reflect this is
construction related product selling website
 Body text is too small to read
 Product name is described in bold font but not with different colour (not good for
differentiation)
 Light background with simple design, i.e, no special effect is included

7.2.2.3 Functions from above related websites to use in my system
According to compare above related websites, I realized some requirements and good plans to
become a perfect system. So, I like to use the ideas that the functions and advantages from these
company sites.
From Zawgyi mart, two facts will be taken.
 Customer can make “Customized Moulds Design” in my system as like as this website of
Customized Ordering for pre-order: “You can order items from other online store, Just
fill up the form.”
 And, my company has “free delivery charges”, so I want to describe this with obvious
designs and colours so that customers can get this message immediately at first glance.
From both websites, common type of payment will be chosen.
Both of them accept bank transfer and credit card payment. Since this system must be completely
online, credit card payment will be used. However, credit card payment has some limitation for
coding. Thus, I will show it as a demonstration and complete procedure of credit card payment
will not be included.

Section 8 – System Investigation
System Investigation Methods
Referenced from (Wells, 2015), system investigation methods are used to support and analyze
the processes which are currently carried out by an organization if an upgraded or new system is
going to be brought into this organization. Although the way proposed system may function will
be quite different from the current system, the data which is being managed and the major
functionalities will remain unchanged sometimes.
Thus, system investigation methods can be used to provide the basis for proposed system's
designs. To understand the project scope, operations, data, existing problems and system
boundaries, some system investigation methods can be used. They are:
 Observation
 Questionnaires
 Record searching
 Interviewing, and
 Workshops
Observation
This method let the analyst observes how users are actually using the present system. With this
method, analyst can see the complete flow of processes from start to end and then record every
single detailed interaction which happens in the system. Therefore, this is very useful to be
familiar with the end-users using the system. Moreover, it can also give the short list of
information which can be used to gather information while interviewing the clients. However,
this method is a very time consuming one and analyst may need pre training of the current
system by the end-user if system is a very complex one.
Questionnaires
Questionnaire method can be done by preparing a single document which can gather information
from the participants without needing interviewer to be present. This method enables the analysts
to abstract the opinions of the large amount of end-users and general answers can be got.
Therefore, this method can be used for statistical purposes. Moreover, it is easier to be used than

face-to-face interviewing method. However, detailed data cannot be got with this method and
sometimes participants do not give the correct answer.
Record searching
Record searching includes examining the existing documentation concerned with how system is
carried out in the past time, its policies and procedures. Existing documents can show these
information such as input, output, file structure, system specification, form interfaces, etc.
Therefore, this method has many advantages in finding the historical data of the system. With the
well-arranged documentation, more accurate data can be got. However, since data are only on
paper, some information may be missing and sometimes it can result incomplete or out of date
data.
Interviewing
This method is the best way to communicate with the clients for abstracting data. Face to face
communication can make clear the problems and confused thoughts of both parties. Complicated
functions can be understood in depth by asking the end-users. This method can also increase the
mutual understanding and familiarities between analyst and end-users. As the result, both soft
and hard factors can be easily found out. Consequently, this can assist in the further system
development and operations.
Workshops
Workshop can also be held to gather the user requirements. To make this successful, a large
resource is required. Firstly, there must be at least eight persons to attend the workshops at the
same time. To handle the workshop and to deliver the expected results, analyst must be working
as the workshop facilitator. Therefore, if analyst is lack of good communication skills,
everything will not be completed as planned. However, workshop can be very effective in
gaining the best result in the hand of a good facilitator and plan.
Reasons for choosing Interviewing Fact Finding Technique
This is a good method to get the detailed idea and function of the proposed system from the end-
users because of its face-to-face communication method unlike one way communication
methods. Since interviewing can be taken place one by one person, all staffs no need to be free at
the same time. Therefore, this can save the end-user's time. So, interview method will be used for
Yellow Hands System.

Reasons for choosing Questionnaires Fact Finding Technique
This is the best way to understand some general functions or problems in the effective estimated
statistical number. A large number of staffs can be reached and the most possible solutions can
be got easily without having a large cost. Since this is cost effective method and users can give
their answers to questions when they are free and later, submit to the analyst, time can be saved
for both analysts and end-users. Thus, this should also be used for Yellow Hands Project too.
On 19 Jan 2015, I visited Yellow Hands company and met with Company Owner, U Kyaw Myo
and General Manager, U Kyaw Lwin for permission and introduction for the following
interviews and questionnaires filling up. U Kyaw Lwin nominated some of his staff and in the
following week I did investigation. A series of the interview were made with his staff. Also by
questionnaires I study their willingness about new system.
***We can be seen in Appendix (C) ***
The facts I got through investigation are described in System Investigation chapter.

Section 9 – Proposed System
9.1 WHAT THE PROPOSED SYSTEM WILL DO
This proposed system will focus on ordering of concrete block machine, mixer and mold and not
on the manufacture processes. Therefore, recording raw materials and things which are included
in each machine will be left out here because they are only needed for factory and not for the
customer and order accepting department.
In this proposed yellow hands system, customer will be able to register to be online customer
because only registered users will make ordering of products. After registering, customers also
have right to update their personal information and change password for better security. There
will be three types of products: mixer, mould and block machine. They will be able to search
with model no, description and category type.
Moreover, customized ordering system will be available for mould product. This will be the
special function of proposed system. Customized order can be canceling or changed by customer
before Yellow Hands confirms it. To help the customers, they will also submit enquiry form via
Yellow Hands website.
For payment, online system will not use KBZ installment method. But, customers do not have to
make full payment for their ordered machines and molds. They can pay half first and then, give
the remaining when machines are delivered to their place. Or, they can make full payment as
soon as order has been made. After submitting order, customers can print out their invoice form.
To manage Yellow Hands system, staffs will be able to use admin panel which can let them add,
update, delete and generate reports for better operational performance.

9.2 Advantages of New System
If we will make the new system of online customized ordering and delivery system, we will get
many advantages such as:
 Customers can give their information and contact address via online registration from
everywhere any time
 Get the advanced search for different types of machines and moulds and their detailed
and up-to-date information
 To help Yellow Hands achieve its potential growth in the market by expanding into
online market
 To expand the market through social media correctly
 To reduce the effort, time and money
 To provide rapid response for customer's enquiry and feedbacks
 If customers want to confirm or cancel the customized products, cancellation is only one
click process.

9.3 Functional Scope for User Level of New System
And I will define the functional scope for user level of new system. They are:
Managers
Managers can have access to generate all types of report for presenting to general manager and
MD. Only managers have right to create reports.
Admin Staffs
Admin staffs will make all the entry and updating processes. They can also view any data except
reports.
Customers
Customers can register their information by themselves and make online shopping. Moreover,
they can enquiry the information that they want to know. They can also edit their customized
order.
Functions of proposed Yellow Hand will be described according to the view from specific users:
customers, admin staffs and managers.
From Customer View
Data Entry Functions
 Make New Customer Registration
 Purchase Products (including delivery and payment)
 Order Customized Mould
Enquiry/Response Functions
 Enquiry Required Info
 Searching concrete block machine, mixer and mould by name
 Searching concrete block machine, mixer and mould by their subcategory types
 Searching concrete block machine, mixer and mould by price
 Searching bought products
Update Functions
 Update Customer Info

 Update Customized Mould Info
From Admin Staff View
 Register New Admin Staff
 Save Products
 Manage Stock
 Save Subcategories
Update Functions
 Update Admin Staff Info
 Update Customer Info
 Update Product Info
 Update Customized Mould Info
 Update Subcategories
 Update delivery information
From Manager View
Reporting Functions
 Report Stock Quantity
 Report Order
 Report Customized Mould Order
 Report Outstanding Payment
 Report Invoice
 Report Undelivered Order

Section 10 - Requirement Definition
10.1 Functions out of the scope of this system
In this Yellow Hands project, all required functions which make up the complete ecommerce
ordering system website are included. However, some functions have to be ignored and they are
regarded as the out of scope functions because of only six months development time and weak in
the technical skills.
This function is credit card payment system. This is very difficult function for me to implement
as the complete function. In real world, if credit card system is used, we have to request API
from the respective payment gateway. However, this is very difficult to handle for me because I
do not have knowledge about it.
10.2 Legal, Technical and Social issues
Some vital issues must be considered for Yellow Hands. Since this is online system, information
on the website will be accessible by all users. Therefore, all data must be made correct and
should not be copied from other sources. If used, credits must be given to the sources from which
information is taken. If this has not done properly, legal issues concerned with digital rights can
be happened.
There are no much technical issues just like stated in feasibility stage. However, website must be
kept to be live and must guarantee for over 95% availability. Apart from this, social issues such
as protecting user's information must be done. Yellow Hands must take care not to sell
customer's information to other third parties. If customer's information is leak, there are some
risks in their social lives.
10.3 Functional Requirements
Functional requirements can be said the most essential things in a system. They are usually the
business requirements of a project. Without having the right functional requirements, a system
cannot be successful and customer's requirements cannot be met. There are low level and high
level functional requirements.

Low level requirements are detailed requirements of the system while high level requirements
are main functions of the system. For example, there will be purchase product which is high level
requirement of Yellow Hands system. This high level can be divided into low level functions
such as saving supplier, selecting supplier and saving purchase detail. They can be checked in
the use case diagrams include in this report.
10.4 Non-functional Requirements
Non-functional requirements are the additional requirements of a system. A system can be built
without considering these requirements if time and money is limited. However, a system without
having these requirements can give problems or difficulties at some point. Therefore, if it is
possible, these non-functional requirements should be included for Yellow Hands Project.
Although there are many non-functional requirements, I will choose usability, accessibility,
security, availability, robustness and high performance non-functional requirements for Yellow
Hands Project.
10.5 MoSCoW Prioritized Requirement List
This DSDM technique is very effective in managing time and required functions. While deciding
the functions, it is required to know their priority so that decisions can be made in case of run out
of time. MoSCoW is acronym for functional requirement prioritization.
 Must (for essential functional requirements)
 Should (for nearly mandatory ones)
 Could (for being able to leave out ones)
 Want (for optional ones)
Therefore, functional requirements of Yellow Hands will be measured in accordance with these
four criteria. And then, they must be listed under each category. Prioritizing like this can be very
useful when there is any change in time and budget and then negotiation with Yellow Hands
Company is required. Functional requirements resulted from use case diagram will be prioritized
with MoSCoW as shown below.

From Customer View
 Make New Customer Registration (Must)
 Purchase Products (including delivery and payment) (Must)
 Order Customized Mould (Must)
Enquiry/Response Functions
 Enquiry Required Info (Would)
 Searching concrete block machine, mixer and mould by name (Could)
 Searching concrete block machine, mixer and mould by their subcategory types (Could)
 Searching concrete block machine, mixer and mould by price (Could)
 Searching bought products (Could)
Update Functions
 Update Customer Info (Should)
 Update Customized Mould Info (Should)
From Admin Staff View
 Register New Admin Staff (Must)
 Save Products (Must)
 Manage Stock (Should)
 Save Subcategories (Must)
Update Functions
 Update Admin Staff Info (Should)
 Update Customer Info (Should)
 Update Product Info (Should)
 Update Customized Mould Info (Should)
 Update Subcategories (Should)
 Update delivery information (Should)
From Manager View
Reporting Functions
 Report Stock Quantity (Would)
 Report Order (Could)

 Report Customized Mould Order (Could)
 Report Outstanding Payment (Could)
 Report Invoice (Could)
 Report Undelivered Order (Would)
10.6 Joint Application Design (JAD) Workshop
Referenced from, (Joint Application Design, 2015), JAD is a technique applied in project life
cycle of DSDM for collecting functionalities of a system. This technique enhances user
participation and improves the accuracy of specifications. Moreover, a workshop which let
knowledge users and IT experts discuss to define and refine the functional requirements of
proposed system.
The participants include authorities from end-users who can give the accurate project
information and decide on requirements. Therefore, these workshops can work more actively
with stakeholders in the shorter timeframe. JAD is the most efficient technique for small and
clearly focused systems. However, it is not too good for large complex projects.
Since Yellow Hands Project is not large complex project, JAD is suitable for finding
requirements. Most JAD workshop has the good agenda which guide the participants to get the
desired goals. Therefore, agenda will be planned well for this Yellow Hands project.
Moreover, a team of not more than nine people is required to hold the workshop. I will act as
facilitator to get the required information from stakeholders. This role is the most important in
JAD because problems have to dissolve and negotiation must be made during workshop.
Therefore, I must do with great care not to miss the list included in agenda.

Section 11 – Database Design and Development
11.1 Selection of Database
Since Yellow Hands is going to be the database-driven ordering website, the best suitable
database must be utilized for better success. Hence, web developer has the main responsibility to
in-depth evaluate the best databases which can satisfy the business needs. Following three
RDBMS can be seen as follow:
11.1.1 Oracle
Oracle produced database server with its own name and now it gets the highest place in the data
handling server market. Gradually, it becomes the proven and secure RDBMS which is mostly
used all over the world. To be perfect with end-user's needs, three different editions can be
requested to make purchase. Oracle announced that it upgrade its functions started from version
12c by including a lot more enterprise functions and options. To fulfil some customers who
require high security, performance, availability, manageability and data analytical functions,
Oracle database is highly designed.
Therefore, this is the reason why large sized global enterprises are utilizing it in their operational
data environment to get the fully robust and scalable database server. Good point of Oracle is
possessing ability to run on multi platforms. However, what we have to notice is high costs due
to its high quality, functionality and security.
11.1.2 Microsoft SQL
This is RDBMS produced by Microsoft and it is currently the most commonly used type of
database server for Windows operating system. Its significant character is that it can operate only

on windows and it is not designed to compatible with other operating systems. When developers
use ASP.NET as the server side, they usually choose this MSSQL. This is because they two are
the same products by Microsoft and they are the perfect match.
This can manage thousands of concurrent transactions made by concurrent users. Therefore, this
can be said as the robust RDBMS ever. Several versions and editions are available in accordance
with the included features. Four paid editions can be purchased from Microsoft.
MSSQL is very secure one because it has functions for database clustering and mirroring.
Moreover, it can support for data partitioning needed for the distributed databases. Therefore,
data can be safe and sound.
11.1.3 MySQL
MySQL was firstly introduced by Sun and it is now continue distributing by Oracle Corporation.
A lot of survey mentioned about MySQL that it becomes the most widely applied RDBMS in
this age of web technology. This RDBMS is usually used together with a lot of web applications
based on open source technologies.
This survey also shows that a great number of most busiest and large traffic website such as
Google, Facebook and Adobe are also heavily relying on this technology for saving their time
and money. This RDBMS is very powerful that it can power such kind of high-volumes
websites.
In addition to this, MySQL supports developer for running on different platforms. These main
platforms include Solaris, Linux, OSX, IBM AIX & Windows. This is also a type of technology
which can be downloaded so easily and quick installation is also provided. In spite of its ease of
use and availability with FOC, it has best optimization system and security features.
Oracle is now managing MySQL and developers can still get it as free version because this
RDBMS was firstly distributed as open source. However, this "MySQL Community Edition" as
well as free version can even be used for big size project requiring high performance.

11.1.4 Oracle Vs MSSQL Vs MySQL
11.1.5 Why MySQL?
Security, Functionalities & Operational Capability
After evaluating these three database technologies, Oracle seems to be the most powerful ones
which can provide more advanced features in security and complex functionalities than MSSQL
and MySQL. But, there is some weakness in usability of Oracle database and it is not designed
for novice database administrator like me. Apart from this, I have experiences with MSSQL and
MySQL which are more easy to use than Oracle. Among MSSQL and MySQL, second one is
more useful in operational capability because of its multiple platforms support.
Compatibility
PHP is chosen for Yellow Hands and suitable database with PHP is researched. Finally, I found
that MySQL which is under same open source category is the most compatible with it.
Total Cost of Ownership
TCO of these three RDBMs are calculated in accordance with market standard. And, it seems
that Oracle is the highest in TCO. Moreover, MSSQL is a bit more costly than MySQL in terms
of TCO. Therefore, MySQL will be used to support Yellow Hands website.

11.2 Implementing Database
While implementing database for Yellow Hands, some steps must be followed so that a complete
and robust database can be produced systematically. These steps are as follow.
1. Analysing and finding data for Normalization
2. Drawing draft Entity Relationship Diagram (ERD)
3. Designing Class Diagram based on ERD
4. Drawing Object Diagram based on Class Diagram
5. Constructing database with selected MySQL RDBMS
6. Saving some data as the test data and then show the records result
7. Query on enquiry and reporting

11.2.1 Normalization
Third Normal Form (3NF)
Customer Staff Order Block Machine Category
CustomerID
RegistrationDate
Username
Password
FullName
ContactPhone
Email
Address
StaffID
RegistrationDate
StaffType
Username
Password
FullName
ContactPhone
Email
Address
OrderID
CustomerID*
OrderDate
OrderType
OrderStatus
OrderDescription
BlockMachineCategoryID
CategoryType
BrickQuantity
ProductBrickQuality
ProductionBrickRate
Invoice Enquiry OrderDetail MIXERCATEGORY
InvoiceID
OrderID*
InvoicingDate
InvoiceStatus
TotalAmount
EnquiryID
CustomerID*
EnquiryDate
EnquiryStatus
EnquirySubject
EnquiryDescription
OrderID*
ProductID*
OrderedQuantity
OrderedPrice
MixerCategoryID
CategoryType
MixerHoldingCapacity
MixerSize
Delivery Stock PRODUCT MOULDCATEGORY
DeliveryID
OrderID*
DeliveryStatus
DeliveryAcceptPerson
DeliveryAcceptPhone
DeliveryAddress
DeliveryRemark
StockID
ProductID*
EntryDate
AddStockQuantity
ProductID
BlockMachineCategoryID*
MixerCategoryID*
MouldCategoryID*
StaffID*
RegistrationDate
ProductModelNo
ProductName
ProductDescription
ProductPrice
MouldCategoryID
CategoryType
MouldOrderType
BrickQuantity
MouldSize

ProductImage
ProductQuantity
ProductRemark
PaymentAccount
AccountID
AccountNo
PINNo
AccountType
TotalBalance
11.2.2 ERD
ERD for Yellow Hands Concrete Block Machine with Customized Mould Online Ordering and Delivery System
Staff
ProductOrder DetailOrder
Invoice Stock
CustomerEnquiry Mixer MouldBlock Machine
Mixer Category Mould CategoryBlock Machine
Category
PaymentAccount
Delivery

11.2.3 Class Diagram
Referenced from (Class Diagram, 2015), Class diagram gives the structure of the system by
showing its classes. It represents the responsibilities of each class and the relationships between
them. It only displays what interacts but not what happens when they do interact.
Class Diagram for Yellow Hands Concrete Block Machine with Customized Mould Online Ordering and Delivery System
Staff
- StaffID: int
- RegistrationDate: Date
- StaffType: string
- Username: string
- Password: string
- FullName: string
- ContactPhone: string
- Email: string
- Address: string
+ Login(Username, Password)
+ RegisterNewAdmin()
+ SaveProduct()
+ ManageStock()
+ ReportStockQuantity()
+ ReportOrder()
+ ReportCustomizedMouldOrder()
+ ReportOutstandingPayment()
+ ReportInvoice()
Customer
- CustomerID: int
- Username: string
- Password: string
- FullName: string
- ContactPhone: string
- Email: string
- Address: string
+ MakeNewCustomer
Registration()
+ PurchaseProducts()
+ OrderCustomizedMould()
+ EnquiryRequiredInfo()
Product
- ProductID: int
- BlockMachineCategoryID: int
- MixerCategoryID: int
- MouldCategoryID: int
- StaffID: int
- ProductModelNo: string
- ProductName: string
- ProductDescription: string
- ProductPrice: int
- ProductImage: string
- ProductQuantity: int
- ProductRemark: string
+ SaveNewProduct()
+ UpdateProductInfo()
+ DeleteProduct()
Stock
- StockID: int
- ProductID: int
- EntryDate: Date
- AddStockQuantity: int
+ SaveNewStock()
+ UpdateStockInfo()
+ DeleteStock()
Order
- OrderID: int
- CustomerID: int
- OrderDate: Date
- OrderType: string
- OrderStatus: string
- OrderDescription: string
+ SaveNewOrder()
+ UpdateOrderInfo()
+ DeleteOrder()
+ CheckOrderStatus()
save
1
1*
Order Detail
- OrderID: int
- ProductID: int
- OrderedQuantity: int
- OrderedPrice: int
+ SaveNewOrderDetail()
+ DeleteOrderDetail()
Enquiry
- EnquiryID: int
- CustomerID: int
- EnquiryDate: Date
- EnquiryStatus: string
- EnquirySubject: string
- EnquiryDescription: string
+ SaveNewEnquiry()
+ UpdateEnquiryStatus()
+ DeleteEnquiry()
Invoice
- InvoiceID: int
- OrderID: int
- InvoicingDate: Date
- InvoiceStatus: string
- TotalAmount: int
+ SaveNewInvoice()
+ UpdateInvoiceInfo()
+ DeleteInvoice()
+ CheckInvoiceStatus()
1
*
entry
1 *
is on
1
*
include
*
make
request
1
*
1
1
produce
BlockMachine Mixer Mould
BlockMachineCategory
- BlockMachineCategoryID: int
- CategoryType: string
- BrickQuantity: int
- ProductBrickQuality: string
- ProductionBrickRate: int
+ SaveNewCategory()
+ UpdateCategoryInfo()
+ DeleteCategory()
MixerCategory
- MixerCategoryID: int
- MixerHoldingCapacity: string
- MixerSize: string
+ SaveNewCategory()
+ DeleteCategory()
MouldCategory
- MouldCategoryID: int
- MouldOrderType: string
- BrickQuantity: int
- MouldSize: string
+ SaveNewCategory()
+ DeleteCategory()
has
1
* has
1
*
has
1
*
Delivery
- DeliveryID: int
- OrderID: int
- DeliveryStatus: string
- DeliveryAcceptPerson: string
- DeliveryAcceptPhone: string
- DeliveryAddress: string
- DeliveryRemark: string
+ SaveNewDelivery()
+ UpdateDeliveryInfo()
+ DeleteDelivery()
+ CheckDeliveryStatus()
1
has
1
PaymentAccount
- AccountID: int
- AccountNo: string
- PINNo: int
- AccountType: string
- TotalBalance: int
+ SaveNewCreditCard()
+ UpdateCreditCardInfo()
+ DeleteCreditCard()
+ CheckTotalBalance()
*
Paid with
1

11.2.4 Object Diagram
Object Diagram direct relationship to the database.
Object Diagram for Yellow Hands Concrete Block Machine with Customized Mould Online Ordering and Delivery System
Staff
- StaffID: 1
- RegistrationDate: 11-01-2015
- StaffType: Manager
- Username: kyarnyo
- Password: ******
- FullName: Kyar Nyo
- ContactPhone: 298765
- Email: kyarnyo@gmail.com
- Address: No. 12
+ RegisterNewAdmin()
+ SaveProduct()
+ ManageStock()
+ ReportStockQuantity()
+ ReportOrder()
+ ReportCustomizedMouldOrder()
+ ReportOutstandingPayment()
+ ReportInvoice()
Customer
- CustomerID: 1
- Username: thinthin
- Password: *******
- FullName: Thin Thin
- ContactPhone: 323829
- Email: thin@gmail.com
- Address: No. 34
+ MakeNewCustomer
Registration()
+ PurchaseProducts()
+ OrderCustomizedMould()
+ EnquiryRequiredInfo()
Product
- ProductID: 1
- BlockMachineCategoryID: 1
- MixerCategoryID: 1
- MouldCategoryID: 1
- StaffID: 1
- ProductModelNo: CB001
- ProductName: Big Machine
- ProductDescription: Very good
- ProductPrice: 1000000
- ProductImage: image.jpg
- ProductQuantity: 10
- ProductRemark: best product
+ SaveNewProduct()
+ UpdateProductInfo()
+ DeleteProduct()
Stock
- StockID: 1
- ProductID: 1
- EntryDate: 11-01-2015
- AddStockQuantity: 1
+ SaveNewStock()
+ UpdateStockInfo()
+ DeleteStock()
Order
- OrderID: 1
- CustomerID: 1
- OrderDate: 11-01-2015
- OrderType: Existing
- OrderStatus: Confirm
- OrderDescription: Want
Immediate
+ SaveNewOrder()
+ UpdateOrderInfo()
+ DeleteOrder()
+ CheckOrderStatus()
save
1
1*
Order Detail
- OrderID: 1
- ProductID: 1
- OrderedQuantity: 1
- OrderedPrice: 1000000
+ SaveNewOrderDetail()
+ DeleteOrderDetail()
Enquiry
- EnquiryID: 1
- CustomerID: 1
- EnquiryDate: 11-01-2015
- EnquiryStatus: Replied
- EnquirySubject: Delivery
- EnquiryDescription: Plz tell me
delivery duration
+ SaveNewEnquiry()
+ UpdateEnquiryStatus()
+ DeleteEnquiry()
Invoice
- InvoiceID: 1
- OrderID: 1
- InvoicingDate: 11-01-2015
- InvoiceStatus: Half
- TotalAmount: 1000000
+ SaveNewInvoice()
+ UpdateInvoiceInfo()
+ DeleteInvoice()
+ CheckInvoiceStatus()
1
*
entry
1
*
is on
1
*
include
*
make
request
1
*
1
1
produce
BlockMachine Mixer Mould
BlockMachineCategory
- BlockMachineCategoryID: 1
- CategoryType: Manual
- BrickQuantity: 1
- ProductBrickQuality: 600PSI
- ProductionBrickRate: 200
+ SaveNewCategory()
+ DeleteCategory()
MixerCategory
- MixerCategoryID: 1
- CategoryType: Big
- MixerHoldingCapacity: 5GL
- MixerSize: 3 ft x 18 ft
+ SaveNewCategory()
+ DeleteCategory()
MouldCategory
- MouldCategoryID: 1
- CategoryType: Pavement
- MouldOrderType: Customized
- BrickQuantity: 5
- MouldSize: 7" x 8" x 3"
+ SaveNewCategory()
+ DeleteCategory()
has
1
*
has
1
*
has
1
*
Delivery
- DeliveryID: 1
- OrderID: 1
- DeliveryStatus: Pending
- DeliveryAcceptPerson: Hla
- DeliveryAcceptPhone: 236789
- DeliveryAddress: No. 4
- DeliveryRemark: Nth
+ SaveNewDelivery()
+ UpdateDeliveryInfo()
+ DeleteDelivery()
+ CheckDeliveryStatus()
1
has
1
PaymentAccount
- AccountID: 1
- AccountNo: AC001
- PINNo: 123456
- AccountType: Visa
- TotalBalance: 10000000
+ SaveNewCreditCard()
+ UpdateCreditCardInfo()
+ DeleteCreditCard()
+ CheckTotalBalance()
*
Paid with
1

11.2.5 Constructing Database
Database for Yellow Hands will be constructed by using MySQL database. This must be done
based on the class diagram drawn above. Respective fields, data type and keys must be placed in
the database as shown in the class diagram. After transforming class diagram into database,
following database design is resulted. There will be thirteen database tables in total.
Figure (1) Structure of Block Machine Category Table

Figure (2) Structure of Customer Table
Figure (3) Structure of Delivery Table

Figure (4) Structure of Enquiry Table
Figure (5) Structure of Invoice Table

Figure (6) Structure of Mixer Category Table
Figure (7) Structure of Mould Category Table

Figure (8) Structure of Order Table
Figure (9) Structure of Order Detail Table

Figure (10) Structure of Payment Account Table
Figure (11) Structure of Product Table

Figure (12) Structure of Staff Table
Figure (13) Structure of Stock Table

11.2.6 Saving and Displaying Test Data
Some test data must be added to the tables in the database. Here, example of test data in the
customer table and product table are described. Test data is added by clicking on the insert
button at the menu and then entered some test data. Eg. For one table “Customer” table. You can
see others tables in database.

11.2.7 Query on enquiry and reporting
Query on enquiry for “Searching product with Mixer Category Type 'Small'
Query on reporting for “Stock Quantity Report for Specific Product”
Query on reporting for “Order Report (Search with specific customer name YeYintOo)”

Query on reporting for “Customized Mould Order Report”
Query on reporting for “Outstanding Payment”
Query on reporting for Invoice with Specific Customer and Order No

Section 12 – System Design of Logical Design
12.1 Use Case Diagram
Referenced from (Use Case Diagram , 2015), Use Case Diagram is one of the Unified Modeling
Language and it can emphasize the technical feature. It is one of the excellent techniques to
collect the user requirements. It can describe by the point of view. By drawing use case, we can
know actually the relation with the requirements and users. Every Use Case Diagram has use
case descriptions and my project has also use case descriptions. These use case descriptions for
each use case are built to help to develop the new system.
12.1.1 Overall Use Case Diagram (High Level)

12.1.2 Secondary Use Case of Order Customized Mold
Order Customized Mould Use Case
Customer
Login
Give Customized
Mould Detailed Data
Check
Username and
Password
<<include>>
Add Delivery
Information
Make Payment
***We can see others use cases and use cases descriptions at Appendix (D) – D - 1***
12.2 Activity Diagram
Referenced from (Activity Diagram, 2015), Activity diagram is the diagram to draw the business
procedure by the objects. According to structured analysis, the equivalent of data flow can be
happened.
Register New Admin Staff Activity Diagram
Login
Fill New Staff
Detailed Data
[Not Valid User]
[Valid User]
Admin Staff
Save New Admin
Staff
[Existing Username]
***We can see others activity diagrams at Appendix (D) – D - 2 ***

12.3 Robustness Diagram
Referenced from (Robustness Diagram-An Agile Introduction, 2015), Robustness Diagram can
be drawn through the use case diagram and sequence diagram. To create robust model, it will be
brought into the design model and construction process.
Robustness Diagram for Register New Customer and Login
Customer
Customer
Login
Page
Give Username
and Password
Login Page
Valid Account
Customer Home
Page
W
rong
Account
Registration
Page
Give username,
password
and detail info
***We can see others robustness diagrams at Appendix (D) – D - 3 ***
12.4 Sequence Diagram
Referenced from (Sequence Diagram, 2015), Sequence Diagram is excellent in real time process
and complex use case. Through the analysis and design of the development lifecycle, sequence
diagram are applied.
Admin Staff
Login(Username
and Password)
A Staff
Register New Admin Staff Sequence Diagram
Check(Username,
Password)
aStaff:
Staff
FillNewStaff
DetailedData()
aStaff:
Staff:Login Page
View()
CheckExistingUsername()
***We can see others sequence diagrams at Appendix (D) – D -4 ***

000845202 kyar nyo thinn project

000845202 kyar nyo thinn project

Recomendados

Recomendados

Más contenido relacionado

Destacado

Destacado (10)

Similar a 000845202 kyar nyo thinn project

Similar a 000845202 kyar nyo thinn project (20)

Último

Último (20)

000845202 kyar nyo thinn project