Project Proposal - ict.siit.tu.ac.thict.siit.tu.ac.th/senior-itcs/proposal/proposal-su1.pdf · Project Proposal Developing ... Zachman Framework ... layer is the perspective from

Project Proposal

Developing Enterprise Architecture Framework

Group Members

Ms. Jutiporn On-nkam (5422770610)

Ms. Supanij Leelataweewud (5422780940)

Advisor: Dr. Sasiporn Usanavasin

School of Information, Computer and Communication Technology,

Sirindhorn International Institute of Technology,

Thammasat University

Semester 1, Academic Year 2014

Date 23 September 2014

Table of Contents

1 Introduction ....................................................................................................................... 1

2 Background ....................................................................................................................... 2

3 Objectives ......................................................................................................................... 5

4 Outputs and Expected Benefits ......................................................................................... 6

4.1 Outputs ......................................................................................................................... 6

4.2 Benefits ........................................................................................................................ 9

5 Literature Review ............................................................................................................. 9

6 Methodology ................................................................................................................... 12

6.1 Approach .................................................................................................................... 12

6.2 Tools and Techniques ................................................................................................ 14

7 Project Schedule ............................................................................................................. 14

8 Project Progress (optional) .............................................................................................. 19

9 References ....................................................................................................................... 20

10 Appendix..........................................................................................................................21

Table of Figures

Figure1: Enterprise Architecture: Zachman Framework............................................................2

Figure2: Simplification Zachman Enterprise Framework..........................................................3

Figure3: TOGAF Document Structure.......................................................................................4

Figure4: Home page - Mock up version of the web application.................................................7

Figure5: Login page - Mock up version of the web application.................................................7

Figure6: Design page - Mock up version of the web application...............................................8

Figure7: Enterprise Architecture View page - Mock up version of the web application...........8

Figure8: Version Log Feature page - Mock up version of the web application........................ 8

Figure9: Interface of TOGAF MDG Technology.....................................................................10

Figure10: TOGAF Model Structure..........................................................................................11

Figure11: Zachman Framework interface diagram...................................................................11

Figure12: The Flow of Process.................................................................................................12

Figure13: Gantt chart during planning and analysing phase starting from 25 Aug 2014 to 24

Sep 2014....................................................................................................................................16

Figure14: Gantt chart during designing phase starting from 10 Sep 2014 to 21 Dec 2014..... 17

Figure15: Gantt chart during preparing practice presentation starting from 9 Sep 2014 to 15

Sep 2014....................................................................................................................................17

Figure16: Gantt chart during preparing proposal presentation and proposal report starting

from 30 Nov 2014 to 13 Dec 2014...........................................................................................17

Figure17: Gantt chart during developing phase starting from 22 Dec 2014 to 14 Mar 2015...18

Figure18: Gantt chart during testing phase, preparing final report and final presentation

starting from 15 Mar 2015 to 9 May 2015................................................................................18

Figure19: Business Model Canvas............................................................................................21

Figure20: User Story.................................................................................................................22

Table of Figures

Table1: Project Schedule..........................................................................................................14

Statement of Contribution

By submitting this document, all students in the group agree that their contribution in the

project so far, including the preparation of this document, is as follows:

Ms. Jutiporn On-nkam (5422770610) 50%

Ms. Supanij Leelataweewud (5422780940) 50%

Senior Project 2014 Developing Enterprise Architecture Framework

School of ICT, SIIT 1

1 Introduction

Information Technology systems are complex and unmanageable [1]

. Without well in

managing the process of developing the system, it would cost a lot of money for the enterprise

to maintain the system. The larger scale of the enterprise is, the more complexity of the

organization is. A large company would face with the problem of handling the management.

Inside the enterprise, each department might have to work on the similar projects. Each

department has to spend time and waste of the budget for working on the overlapping task

while they do not know that another department also has done with that task and the

information has already existed [2]

. By these reasons, it causes the enterprise in lowering the

business value. A well defined practice would help the enterprise in handling the problems.

Enterprise Architecture is a well-designed architecture for the enterprise to plan,

analyse, design, and implement the system to achieve the highest business value [3]

. Enterprise

Architecture would be the guideline for the company. Like constructing a house, the

engineers need to have a blueprint to illustrate the figure of the house. Blueprint would be the

communication tool between the house owner, the engineer, and the contractors. So, they

would understand in the same direction. The engineer and contractors would know the

requirement of the customer. The house owner would have the house as he or she wants.

Same as Enterprise Architecture, it likes a blueprint that is used inside the enterprise. So, the

company can focus on organization’s vision and Enterprise Architecture can help in

improving the efficiency of the system and increasing the business value. Moreover, the

Ministry of Information and Communication Technology of Thailand has announced for

Enterprise Architecture as a national policy. In government sector, they have to develop the

architecture before develop the system for reducing the cost of maintaining and to achieve the

vision of the government.

Nowadays, there are many theories and methodologies for developing enterprise

architecture, for example, Zachman Framework, The Open Group Architectural Framework

(TOGAF), the Federal Enterprise Architecture, and the Gartner Methodology. However, those

theories may not be suitable for every field in business world. Adaptation and combination of

the theories would lead to the most flexible architecture and the highest benefit for the

enterprise. In this senior project, we develop the web application which provides the tools for

developing the Enterprise Architecture for the company. The users for this web application

could be the people in the organization from the top level manager like an executive of the

enterprise until the based level staff like the developer teams. By developing the architecture,

the users just simply fill in the information into the framework in each layer of the

architecture. In the application, it also provides some of the information of Enterprise

Architecture. So, the users can understand and realize how Enterprise Architecture is

important for their companies.



2 Background

Enterprise Architecture is not that popular in Thailand’s enterprise even it is very

essential for the enterprise. Nevertheless, Enterprise Architecture has become a new trend for

the technology criteria in Thailand. Since Enterprise Architecture has a lot of deep and

complex details, so it would be difficult for the whole organization of the enterprise to study

all of the details. The main problem for this web application is that we have to develop the

tools that can be used by both IT and non-IT users. We also have to make it as easy as

possible with the most effective way for using the information given by the users via the web

application. So, the users who do not have any knowledge about this can be able to use it and

get the most efficient architecture.

Since Enterprise Architecture has studied and come out as many methodologies for

practicing, each of them has specific characteristics and leads to different criteria of benefit.

For this project, we are going to focus on these two popular methodologies which are

Zachman Framework and The Open Group Architectural Framework (TOGAF). As a

definition of Zachman Framework, it is an Enterprise Architecture framework which provides

a definition of the artefacts that are significant to the management of the enterprise [4]

. It

classifies as a matrix framework with six-by-six. It is the intersection of two dimensional

classifications. The first dimension is the common question words: what, how, where, who,

when, why. Another dimension is type of the stakeholders in the organization which will

provide the perspective of each artefact. This dimension is including the planner, owner,

designer, builder, subcontractor, and enterprise. The figure of Zachman Framework is shown

below in Figure1.

Figure1: Enterprise Architecture: Zachman Framework

Source: msdn.microsoft.com



At the top level of the horizontal row on the framework is called scope layer. This

layer is the perspective from the business owner to providing the organization’s vision and

goals. The second row is business layer which is given by the project manager for defining

the business process information of each project. In the next row, this is system layer for

providing the description of the logical models from the requirement as the perspective from

the system analyst. The forth layer is technology layer which expresses the physical models

and specific format of the technology from developers’ view. Next layer is detailed layer

which contains the detailed information as built from subcontractor. The last row is

functioning enterprise layer. This layer is for evaluation from the enterprise. These thirty-six

intersection cells would define all of artefacts that describe the system from every perspective

of the stakeholder.

Figure2: Simplification Zachman Enterprise Framework

Source: commons.wikimedia.org

The Open Group Architecture Framework or TOGAF was created by The Open

Group, it will provide the method and tools to construct and maintain the architecture of

enterprise for the production to be accepted [5]

.

TOGAF divide enterprise architecture into 4 categories [6]

:

1. Business Architecture was explained about framework of policy, benefit, and

vision of the project, it have to analysis and present about intended transaction that

always analysis an action both of by personality and the system.

2. Data Architecture was explained about group of data, data architecture, and data

characteristic that helps the organization to use the data together, and can bring the

different data to develop the system.

3. Application Architecture was explained about the element of the system that

service and connection between each working system that make it into the biggest

organization, and have a faster reaction for the big customer.

4. Technology Architecture was explained about the basic structure for example,

the specific technique about computer networking, the host computer system, the

other device including the basic software and relationship of each element that will

support the organization to construct the working system.



The structure of the TOGAF documentation reflects the structure and content of an

Architecture Capability within an enterprise, as shown in Figure

Figure3: Structure of the TOGAF document

Source: http://pubs.opengroup.org/architecture/togaf9-doc/arch/

From the figure, TOGAF document is divided into seven parts. Part 1 is the

introduction, provides a high-level introduction to the key concepts of enterprise architecture

and in particular the TOGAF approach. It contains the definitions of terms used throughout

TOGAF and release notes detailing the changes between this version and the previous version

of TOGAF. Part 2 Architecture development methods, is the core of TOGAF. It describes the

TOGAF Architecture Development Method (ADM) - a step-by-step approach to developing

enterprise architecture. Part 3 ADM Guidelines and Techniques, contains a collection of

guidelines and techniques available for use in applying TOGAF and the TOGAF ADM. Part

4 Architecture content framework, describes the TOGAF content framework, including a

structured meta-model for architectural artefacts, the use of re-usable architecture building

blocks, and an overview of typical architecture deliverables. Part 5 Enterprise continuum &

tools, discusses appropriate taxonomies and tools to categorize and store the outputs of

architecture activity within an enterprise. Part 6 TOGAF reference models, provides a

selection of architectural reference models, which includes the TOGAF Foundation

Architecture, and the Integrated Information Infrastructure Reference Model. For the last part,

part 7 Architecture capability framework, this part discusses the organization, processes,

skills, roles, and responsibilities required to establish and operate an architecture function

within an enterprise.

In this project, we derive the methodology from two theories which are Zachman

framework and The Open Group Architectural Framework (TOGAF). Zachman framework is

the framework that tells what you have to do whereas TOGAF tells how you are going to do

for your enterprise to develop the system. With the combination of these two theories, it would provide the enterprise for both method and process for developing the system. So, the



enterprise would be able to develop the system with well defined architecture. It will help the

organization in managing the complexity of the system which will increase the efficiency of

the system and also the business value. Enterprise Architecture would satisfy the

organization’s vision.

3 Objectives

In this project, we will achieve the following goals:

- Understand about Enterprise Architecture methodologies which include Zachman

Framework, The Open Group Architectural Framework (TOGAF), the Federal Enterprise

Architecture, and the Gartner Methodology

- Develop Enterprise Architecture web Application Tools which would be easy to use

for both IT and non-IT users.

- Develop database of EA web application for the good performance

- Save money and time spend in the project which maybe occur from working on the

overlapping task

- Increase the highest business value by use Enterprise Architecture web applications

tools make the architecture that is consistent with the organization’s vision and goals.

- Make the same understanding within the organization

- To response the National Policy announced by The Ministry of Information and

Technology of Thailand.



4 Outputs and Expected Benefits

This project will produce an output as a web based application that can be used as a

tool for designing an Enterprise Architecture for an organization.

4.1 Outputs

Web application providing Enterprise Architecture developing tools

We are going to develop web application as a channel for the users to develop

Enterprise Architecture framework. The system will show the updated architecture.

Main functionalities of the application are shown as follows:

Input Vision of the organization

Each enterprise has to input the organization’s vision by the business

owner. So the employee in the organization would understand the vision clearly.

Develop the Enterprise Architecture Framework

The users would be asked to fill in the information or draw the diagram

to fulfil the framework in each layer for constructing the framework.

Update the Enterprise Architecture Framework

The system would show out the Enterprise Architecture. The users in

all level will be able to see all the layers in the architecture. So, it will make sure

that the employee can follow the architecture in the same direction.

Create new framework for a new project

The project manager can create new framework for a different project.

So, each project could have its specific description of work.

Version log from the system to trace back the previous version

In this application, it also provides version log in the system for

recording the version of architecture would help the organization to trace back

the information of the architecture. It will record for any modification of the

architecture. The name of the users, the details, and also the date of

modification would be kept in the track of version log.

Message notification for unworkable architecture

The system will be able to check whether the information in each cell

of the framework is corresponding with each other. With the system that is

able to notify for the unworkable architecture, the organization can improve

the architecture later on.



Login System of each enterprise

The users have to login into the system before working on their

projects. So the user can separately work on their specific layer.

Register System

The users have to create a new account before using the system. So the

user could login into the system.

Figures show our mock-up version of the proposed application.

Figure4: Home page - Mock up version of the web application

Figure5: Login page - Mock up version of the web application



Figure6: Design page - Mock up version of the web application

Figure7: Enterprise Architecture View page - Mock up version of the web application

Figure8: Version Log Feature page - Mock up version of the web application



4.2 Benefits

Develop the systems together with achieving organization’s vision

The enterprise would have the framework for developing the systems which are

suitable and meet with the organization’s vision.

Cover for almost every sectors of the organization

Enterprise Architecture is workable to both private and government sector. Since this

application is developed for the IT and non-IT people, so it would cover for all users. The

users of this application will be business owner, project manager, system analyst, developer,

sub-contractor, and enterprise architect.

Focus on enterprise’s goal

By developing Enterprise Architecture framework, the organization could focus on their

project and can go along together in the same direction from the vision’s of chief executive to

the products and services that are created by developer team. The customers of the enterprise

would obtain the products and services as the requirement has defined. The chief executive

would achieve the highest business value for the enterprise.

Manage the complexity of the system

As long term, the well defined architecture of the system would help in managing the

complexity of the system. This will save the cost of maintenance of the system and reduce the

budget of the enterprise.

5 Literature Review

Enterprise Architecture is become an important tools to construct a model of

enterprise within a structural approach as John A. Zachman (2014 JOHN A. ZACHMAN

Biographical Sketch, Zachman International, Inc.) who is the originator of Enterprise

Architecture Framework or well-known as Zachman framework, which has receive broad

acceptance around the world. Mr.Zachman tell that Zachman consist of the thirty-six frame

that occurred by the intersection of two horizontal classification (2008 John A.

Zachman, Zachman International, Inc.).

Not only Zachman that was accepted, they still have The Open Group Architecture

Framework or TOGAF which develop by The Open Group. It provides a comprehensive

approach to the design, planning, implementation and governance of enterprise architecture.

TOGAF is a high level and holistic approach to design, which is typically modeled at four

levels - Business, Application, Data, and Technology. As an open standard, TOGAF is widely

adopted to support EA (TOGAF 9.1 White Paper An Introduction to TOGAF Version 9.1

http://www.opengroup.org/togaf).

http://www.opengroup.org/togaf



TOGAF and Zachman will be developed as a program to use for design architecture of

enterprise. For example, Sparx System company which is a specialist in high performance and

scalable visual modeling tools for the planning, design and construction of software intensive

systems (2000 - 2014 About us, Sparx Systems Pty Ltd) [7]

. They are developed the

enterprise architecture tools that calls “TOGAF MDG Technology” (2000 - 2014 TOGAF,

MDG Technology, Sparx Systems Pty Ltd) which provides TOGAF 9 Architecture

Development Method.

Figure9: Interface of TOGAF MDG Technology

Source: http://www.sparxsystems.com.au/products/mdg/tech/togaf/

From the picture, interface is a TOGAF ADM that can double-clicking on a cell of the

interface diagram opens the model package and diagram corresponding to that particular

ADM phase and each ADM phase is modelled as the highest-level package inside the

Framework model [8]

, following the picture below:

http://www.sparxsystems.com.au/

http://www.sparxsystems.com.au/



Figure10: TOGAF Model Structure

Source: http://www.sparxsystems.com.au/products/mdg/tech/togaf/

Sparx System Company also developed enterprise architecture tools that based on

Zachman Framework which call “Zachman Framework MDG Technology” [9]

. The picture

below shown the Zachman Framework interface diagram, which serves as a template for the

development of Enterprise Architecture based on the Zachman classification framework.

Figure11: Zachman Framework interface diagram

Source: http://www.sparxsystems.com.au/…/mdg/tech/zachman/index.html



Although, TOGAF and Zachman will be developed to achieve maximum performance

to the user, but there is only a few user that can understand and use the program .This is

usually the people who have knowledge or experience with this before. With this reason, we

try to develop the enterprise architecture tools into web application which is easy to use for

everyone based on using TOGAF model and Zachman Framework.

6 Methodology

6.1 Approach

The steps of this project will follow the phases of System Development Life Cycle

which start from planning, analysing, designing, developing, and testing phase. So, we could

classify the type of work and can perform the process orderly. The schedule and deadline will

be shown in the Project Schedule part of this report. In this part, we are going to describe the

detail of each phase of the project.

Figure12: The Flow of Process



Planning Phase

This phase is the beginning of the process for meeting with the advisor and

discussing about the detail of the project. We also plan and set up a rough schedule for

a whole project and then, divide the task and responsible in the team.

Analysing Phase

After we have done with planning phase, we continue with analysis and research.

We gather and find out all the information to clarify with the definition of Enterprise

Architecture and summary for the scope of the project to predict the output of the

project that what should it be. In this phase, we also develop the Business Model

Canvas to illustrate the value of the project in the business. Business Model Canvas is

shown in Figure19 of Appendix part. Moreover, we develop User Story to specify the

requirements that will be needed for the user and prioritize for each requirement. User

Story is shown in Figure20 of Appendix part.

Designing Phase

For designing phase, we design the user interface of our web application since our

project would be developed as the web application. We start from designing the

logical process of our web application and then perform mock-up version of the

application. We also design the architecture based on the SIIT organization as an

example to see that what we understand and design can be used in reality.

Developing Phase

After we have done with designing phase, we are going to develop the web

application. This phase is classified into two main stages which is the application and

database part. The application will cover all the features that the users will interact

with, for example, main application interface, register and login system, designing and

developing the architecture part, version log feature, and mismatch message function.

For database part, it will be divided into database which are architecture and enterprise

database. Architecture database will keep the information of the architecture while

enterprise database will record the information of the users of each enterprise.

Testing Phase

Testing phase is the last phase of the project to test the system and fix all the

problems in the application and may also develop some of the documents that are

related to the project for any further development in the future.



6.2 Tools and Techniques

The technique or technology that we use to develop the tools for designing and

developing the enterprise architecture is web application since internet has played a key role

for human a lot in nowadays. So, we choose web application because it would be appropriate

for all kinds of users. We are using HTML5 language for developing the web application

because HTML5 is a basic language for coding the web application and it is very popular.

Moreover, HTML5 also provides many features that are able for us to develop the application

appropriately and easily for the users to use.

The tool that we are going to use is MySQL database which will collect all the data for

the system, for example, the enterprise architecture information and the user’s details. So, we

are going to use PHP language as well.

Another technique that will be used in this project is data mining or text mining to

analyse the information that the users have entered into the system. The system will do cross

check for checking the information in each cell of column is corresponding with each other or

not. If not, the system will notice the users with some message to improve the architecture.

7 Project Schedule

Task Description Person Duration Deadline Status

1 Planning Phase

- Meet with project advisor

- Plan and Set up Schedule

- Divide the task and responsible in

the team

JO, SL

2d 26 Aug 14 -

2 Analysing Phase

- Do the research

- Summary the scope of the project

- Develop the Business Model

Canvas

- Develop User Story

- Estimate the time and improve the

schedule

JO, SL

JO, SL

SL

SL

JO, SL

2w

2w

1w

1w

1w

10 Sep 14

10 Sep 14

2 Sep 14

16 Sep 14

24 Sep 14

-

3 Design Phase

- Design the user interface of the

web application

- Design the architecture for SIIT

Remark: Skip midterm examination

week for 2 weeks (29 Sep – 10 Oct)

JO

JO, SL

5w

13w

26 Oct 14

21 Dec 14

40%. Main user interface

has done except interface

for each feature

20%. First Layer of the

architecture has done

4 Prepare practice presentation JO, SL 1w 15 Sep 14 -



5 Prepare Proposal Presentation (final) JO, SL 2w 14 Dec 14 -

6 Prepare Proposal Report (final) JO, SL 2w 14 Dec 14

7 Develop Phase

Develop the web application

- Main application interface

- Framework of the architecture

- Tools for developing the

architecture

- Version log feature

- Mismatch message feature

- Login System

- Register System

- Contact and EA Information

Develop the database

- Architecture Database

- Enterprise Database

Develop documents (optional)

- Develop User Manual

JO

JO

JO

SL

SL

SL

SL

JO

SL

JO

JO, SL

10w

10w

1w

14 Mar 15

14 Mar 15

28 Feb 15

8 Testing Phase

- Test the application

- Fix bugs in the application

SL

JO

6w

6w

25 Apr 15

25 Apr 15

9 Prepare Final Report JO, SL 2w 9 May 15

10 Prepare Final Presentation JO, SL 2w 9 May 15

Table1: Project Schedule



These following figures are showing the project schedule as Gantt chart. Gantt chart is the bar chart showing the timeline of the project which

includes the start date, finish date, duration, and also the completeness of each task [10]

. Since this project takes a couple months, so we could capture

only the Gantt chart as a rough version shown in here.

Figure13: Gantt chart during planning and analysing phase starting from 25 Aug 2014 to 24 Sep 2014



Figure14: Gantt chart during designing phase starting from 10 Sep 2014 to 21 Dec 2014

Figure15: Gantt chart during preparing practice presentation starting from 9 Sep 2014 to 15 Sep 2014

Figure16: Gantt chart during preparing proposal presentation and proposal report starting from 30 Nov 2014 to 13 Dec 2014



Figure17: Gantt chart during developing phase starting from 22 Dec 2014 to 14 Mar 2015

Figure18: Gantt chart during testing phase, preparing final report and final presentation starting from 15 Mar 2015 to 9 May 2015



8 Project Progress (optional)

Since we have met with our project advisor, we have talked about the project and we

got an assignment for doing the research about the definition of the Enterprise Architecture.

Then, we have met with our project advisor again to conclude the scope of the project and the

characteristic of the system that we are going to develop in senior project and what we have to

do is to develop the system as a web application.

For analysis of the requirement, we have developed Business Model Canvas to gather

the information of the features that we need to deliver to our customer and combine with the

business which show what would be the cost we have to spend and the way how we can get

the revenue. The figure 19 below in the appendix part is showing the Business Model Canvas

diagram. We also develop user stories to sum up all the features and rank the priority of each

feature. We also did some part of design phase. We designed the user interface for our web

application via online mock-up website which will save our time and then we have designed

by coding with HTML5for the logic of each page to prepare for the coding time. The

designing phase will be finished by the end of November and will start developing phase in

the beginning of December.



9 References

[1] Sessions, R., "A Comparison of the Top Four Enterprise-Architecture Methodologies".

Retrieved August, 2014 Available: http://msdn.microsoft.com/en-us/library/bb466232.aspx

[2] Daniel, D., "The Rising Importance of the Enterprise Architect". Retrieved September,

2014 Available: http://www.cio.com/article/2439397/it-organization/the-rising-importance-

of-the-enterprise-architect.html

[3] "What is Enterprise Architecture? animated video definition". Retrieved December,

2014 Available: https://www.youtube.com/watch?v=d1MPEmMBqc0

[4] John A. Zachman, "About the Zachman Framework". Retrieved August, 2014

Available: https://www.zachman.com/about-the-zachman-framework

[5] “TOGAF 9.1”. Retrieved November, 2014 Available:

http://pubs.opengroup.org/architecture/togaf9-doc/arch/

[6] "Thailand e-Government Interoperability Framework". Retrieved November, 2014

Available: http://egif.mict.go.th/document/THeGIF2.pdf

[7] "Sparx Systems - About Us". Retrieved November, 2014 Available:

http://www.sparxsystems.com.au/about.html

[8] "MDG Technology for TOGAF User Guide". Retrieved November, 2014 Available:

http://www.sparxsystems.com.au/downloads/pdf/TOGAFHelp.pdf

[9] "MDG Technology For Zachman Framework User Guide". Retrieved November,

2014 Available: http://www.sparxsystems.com.au/downloads/pdf/ZFUserGuide.pdf

[10] "Gantt Chart". Retrieved September, 2014 Available: http://www.gantt.com/



10. Appendix

Figure19: Business Model Canvas



In Figure19, it is the figure of Business Model Canvas which showing the information

of the requirement in business field. It is divided into 9 boxes. First one is customer segment

which tells who is the user of the system. The second box is value proposition to show what

will the users or customers will get from our application. Customer relationship is how we

support our customers. Channel is the way how we provide our service to the customer. The

fifth box is key activity which showing what we are going to do for the project and key

resources are the resources that will be used for developing the project. Key partner is the

company or the enterprise that we are going to cooperate together but for our project we

didn’t involve with that. Cost structure is showing what would be the cost that we will spend

for the project and revenue stream is the way how we are going to earn the revenue.

Figure20: User Story



Figure20 is user story which is a diagram for describe how the users want for each

features and also prioritize for how much important of that feature. The higher number of

priority means the more important of the feature.

Documents

Project Proposal - ict.siit.tu.ac.thict.siit.tu.ac.th/senior-itcs/proposal/proposal-su1.pdf · Project Proposal Developing ... Zachman Framework ... layer is the perspective from