training management system (tms) for siam commercial bank

Training Management System (TMS) for Siam Commercial Bank

by Ms. Thatchar Trenatre

A Final Report the Three-Credit Course CS 6998 System Development Project

Submitted in Partial Fulfillment of the Requirements for the Degree of

Master of Science in Computer Information Systems

Assumption University

November 2006

Project Title

Name

Project Advisor

Academic Year

Training Management System (TMS) for Siam Commercial Bank

Ms. Thatchar Trenatre

Dr. Settaphong Malisuwan

November 2006

The Graduate School of Assumption University has approved this final report of the three-credit course, CS 6988 System Development Project, submitted in partial fulfillment of the requirements for the degree of Master of Science in Computer Information Systems.

Approval Committee:

(Dr. Settaphong Malisuwan) Advisor

(Prof.Dr. Srisakdi Charmonman) Chainnan

(Assoc.Prof. Somchai Thayamyong) CHE Representative

November 2006

ABSTRACT

Siam Commercial Bank is one of the country's financial institutions which has

many training programs each year. Since the company has been growing, the cmTent

training management cannot be managed efficiently and training expenses are high

costs so competitive advantages of training strategies are its weakness. The proposed

modified Training Management System reduces the operating time of course enrollment

and tracking enrollment information, training expenses, and increases the training hours

of employees. This project will suppo1i learning programs building which include both

classroom and e-leaming programs, and course enrollment management which includes

the approval process via the notification. The application is web-based application

which emphasizes self services workflow so Training Management System can link

organizational goals to employees, managers and training division, provide a catalogue

of available (and relevant) courses, self-enrollment, and notification events, and deliver

content in classroom-based ore-learning fonnats.

The SDLC methodology is applied to the proposed system which tracks a project

from an idea developed by the user, tlu·ough a feasibility study, systems analysis and

design, programming, pilot testing, implementation, and post-implementation analysis.

System request describes the business reasons for building a system and the value that

the system is expected to provide. The object-oriented design technique is applied to the

project. The functional modeling, structure modeling, behavioral modeling, database

design, interface design, output design and network design are applied to the system

analysis and design which depict the functional and technical specifications.

Finally, the training costs will decrease, and the proposed system can enhance the

achievement of the organizational goals. The future system expansion can integrate to

other business operations of the organization also.

ACKNO\VLEDGEMENTS

This project is accomplished as a result of reviews by several people who

generously gave their time and expertise. I would like to acknowledge their efforts and

thank them for their kind contributions.

I would like to thank LTC.Assoc.Prof. Settaphong Malisuwan, my project advisor,

for his valuable suggestions and advice given in the preparation of this project.

I would like to thank Dr. Quen Pin-Ngem for the instruction on the system

analysis and design technique, and all MS.CIS, MS.CEM instructors for their

instruction on technology and business principles programs.

I extend my sincere thanks to my family for educating me with aspects from both

arts and sciences, for their unconditional support and encouragement to pursue my

interest and for giving me life at all times.

Finally, I would like to thank HRMS staffs of Siam Commercial Bank for their

timely assistance and information provided while HRMS project is carried out, and all

help that was required for my project also.

11

TABLE OF CONTENTS

Chapter Page

ABSTRACT

ACKNOWLEDGEMENTS 11

LIST OF FIGURES v

LIST OF TABLES Vlll

I. INTRODUCTION 1

1.1 Background of the Project 1

1.2 Objectives of the Project 2

1.3 Scope of the Project 3

1.4 Deliverables 4

1.5 Project Plan 5

II. THE EXISTING SYSTEM 8

2.1 Background of the Organization 8

2.2 Business Functions and Operations 11

2.3 Current Problems and Areas for Improvement 12

III. THE PROPOSED SYSTEM 14

3.1 Requirement Analysis 14

3.2 System Design 17

3.3 Analysis of Candidate Solutions 36

3.4 Hardware and Software Requirement 43

3.5 Network Requirements 47

3.6 Security and Control 48

3.7 Cost and Benefit Analysis 50

IV. PROJECT IMPLEMENTATION 53

111

Chapter

4.1 Overview of Project Implementation 53

4.2 Coding 54

4.3 Testing 54

4.4 System Conversion 55

4.5 Documentation and Training 55

V. CONCLUSIONS AND RECOMMENDATIONS 57

5.1 Conclusions 57

5.2 Recommendations 58

APPENDIX A USE CASE DESCRIPTION 59

APPENDIX B DATA DICTIONARY 70

APPENDIX c CLASS-RESPONSIBILITY-COLLABORATION CARDS (CRC CARDS) 74

APPENDIX D SEQUENCE DIAGRAMS 88

APPENDIX E COMMUNICATION DIAGRAMS 100

APPENDIX F DATABASE TABLES 106

APPENDIX G USER INTERFACE DESIGN 117

APPENDIX H OUTPUT REPORTS 132

APPENDIX I COST ANALYSIS OF CANDIDATE SOLUTIONS 134

BIBLIOGRAPHY 140

IV

LIST OF FIGURES

Figure Page

1.1 Project Plan of Training Management System 7

2.1 The Organization Chart of Siam Commercial Bank 10

2.2 Context Data Flow of Existing Diagram 12

3.1 Element of Context Diagram (Use Gane and Sarson Symbol) 18

3.2 Context Diagram 19

3.3 Element of Activity Diagram 21

3.4 Activity Diagram 22

3.5 Element of Use Case Diagram 24

3.6 Use Case Diagram 25

3.7 Element of Class Diagram 29

3.8 Class Diagram 30

3.9 Mapping problem domain classes to RDBMS tables 34

3.10 Network Infrastructure 48

D.1 Element of Sequence Diagram 88

D.2 Sequence Diagram for Create Course Use Case 89

D.3 Sequence Diagram for Create Offering Use Case 90

D.4 Sequence Diagram for Create Class Use Case 91

D.5 Sequence Diagram for Create Leaming Object Use Case 92

D.6 Sequence Diagram for Add Enrollment Use Case 93

D.7 Sequence Diagram for Enroll Class Use Case 94

D.8 Sequence Diagram for Approve Course Use Case 95

D.9 Sequence Diagram for Attend Class Use Case 96

D.10 Sequence Diagram for Browse Class Use Case 97

v

Figure

D.11 Sequence Diagram for Track Enrollment Use Case

D.12 Sequence Diagram for Search Course Use Case

E.1 Element of Communication Diagram

E.2 Communication Diagram for Create Course Use Case

E.3 Communication Diagram for Create Offering Use Case

E.4 Communication Diagram for Create Class Use Case

E.5 Communication Diagram for Create Leaming Object Use Case

E.6 Communication Diagram for Add Enrollment Use Case

E.7 Communication Diagram for Enroll Class Use Case

E.8 Communication Diagram for Approve Course Use Case

E.9 Communication Diagram for Search Course Use Case

E.10 Communication Diagram for Attend Class Use Case

E.11 Communication Diagram for Browse Class Use Case

E.12 Communication Diagram for Track Enrollment Use Case

G.1 Login Form

G.2 Main Menu Form

G.3 Catalog Form

G.4 Create Course Form

G.5 Create Offering Form

G.6 Create Leaming Object Form

G.7 Create Class Form

G.8 Enrollments Form

G.9 Add Enrollments Form

G.10 Select Leamer Form

Vl

Page

98

99

100

101

101

102

102

103

103

104

104

105

105

105

117

118

119

120

121

122

123

124

125

126

Figure Page

G.11 Leamer Self-Service Form 127

G.12 Notification Form 128

G.13 Notification Message Form 129

G.14 Content Link Form 130

G.15 Content Details Page 131

H.1 Enrollments Tracking Report 132

H.2 Enrollments Summary by Class Report 133

I.1 Break-Even Point of Candidate 1 135



Vll

LIST OF TABLES

Table Page

3.1 System Request - Training Management System (TMS) 14

3.2 List of Actors, Use Case name, Use Case description 26

3.3 Multiplicity 28

3.4 Feasibility Analysis Matrix 40

3.5 The Hardware Specification for Application Server 43

3.6 The Hardware Specification for Content Server 44

3.7 The Hardware Specification for Database Server 44

3.8 The Hardware Specification for Each Client Machine 44

3.9 The Software Specification for Application Server 45

3.10 The Software Specification for Content Server 46

3.11 The Software Specification for Database Server 46

3.12 The Software Specification for Each Client Machine 47

5.1 Degree of achievement of proposed system 57

A.I Create Course Use Case Description 59

A.2 Create Offering Use Case Description 60

A.3 Create Class Use Case Description 61

A.4 Create Leaming Object Use Case Description 62

A.5 Add Enrollment Use Case Description 63

A.6 Enroll Class Use Case Description 64

A.7 Approve Course Use Case Description 65

A.8 Attend Class Use Case Description 66

A.9 Browse Class Use Case Description 67

A.IO Track Enrollment Use Case Description 68

Vlll

Table Page

A.11 Search Course Use Case Description 69

B.1 Data Dictionary of Proposed system 70

C.1 Course Class CRC Card 74

C.2 Offering Class CRC Card 75

C.3 Delivery Mode Class CRC Card 76

C.4 Leaming Object Class CRC Card 77

C.5 Class Class CRC Card 78

C.6 Enrollment Class CRC Card 79

C.7 Notification Class CRC Card 80

C.8 Employee Class CRC Card 81

C.9 Training Administrator Class CRC Card 82

C.10 Manager Class CRC Card 83

C.11 Organization Class CRC Card 84

C.12 Users Class CRC Card 85

C.13 Responsibility Class CRC Card 86

C.14 Menu Class CRC Card 87

F.1 Course Table 106

F.2 Delivery Mode Table 106

F.3 Leaming Object Table 107

F.4 Offering Table 108

F.5 Class Table 109

F.6 Notification Table 110

F.7 Enrollment Table 111

F.8 Employee Table 112

IX

Table Page

F.9 Organization Table 113

F.10 Users Table 114

F.11 Responsibility Table 115

F.12 Users_Resp Table 115

F.13 Menu Table 116

F.14 Resp_ Menu Table 116

I.1 Cost-Benefit Analysis of Candidate 1 134



x

I. INTRODUCTION

1.1 Background of the Project

No commercial organization today would be without its corporate strategy, its

business development plan and its marketing, personnel and financial strategies. In

recent years, the organization has come to realize the benefits of having quality and

information-technology strategies, but few have yet to develop comprehensive strategies

for training management system.

Siam Commercial Bank has many training programs each year because of the

company's growth, but the current training management cannot be managed efficiently;

takes a long time to process and its competitive advantage of training strategies are its

weakness. Moreover, training expenses have increased every year such as copy and

distribution costs for review of materials, production and printing costs for related print

materials, inventory costs for storing materials, costs of building and maintaining a

learning center, travel and accommodating costs.

So, Training Management System (TMS) will be developed to provide the

efficiency and effectiveness to enhance the organization's training strategies. As the

strategic planning and management system for training within a company, a TMS can

link organizational goals to employees, managers and training division, provide a

catalogue of available (and relevant) courses, self-enrollment, and notification of events,

and deliver content for e-learning formats. The system also has the ability to manage

enrollment, as well as course content, timing, and tracking via the web-based

application.

1.2 Objectives of the Project

This project is studied in order that the proposed modified Training Management

System would cover and reduce the operating time of course enrollment and tracking

1

enrollment information, training expenses, and increasing the training hours of

employees. Things needed to be accomplished in this project are:

1. To study and analyze the existing system of training management in training

division in terms of business process flow regarding the planning of new

additional tools I application system.

2. To identify the problems in the existing information system.

3. To analyze the problems and causes and to find out the solutions for those

problems.

4. To identify the information system requirements as the proposed additional

computerized system, considered in terms of cost effective solution and

estimated budget.

5. To identify the knowledge, skills and abilities required to meet the

organization's strategic plan.

6. To improve the efficiency and effectiveness of the company and reduce

costs regarding the elimination of the problems identified in existing system.

7. To develop the customized software which base on web-based application

using ASP.net to be the development tool

8. To design the computer-based Training Management System that is suitable

and effective to the work processes of the organization, based on all

requirements both functional and non-functional requirements specified by

users.

Training Management System for Siam Commercial Bank is designed for benefits

as follows:

1. Reduced Time, minimize the costs of training such as materials, instructor

or learner travel costs, accommodation costs and facility operating costs.

2

2. Be an effective and efficient system of free self-paced personal training,

available over the Internet.

3. Advantage in case of training operations when compare with other

competitors.

4. Increase employee training hours which will have more perfonnance

effectiveness.

5. Information control is centralized which is more reliable and accurate.

6. Leamer can access anywhere anytime that is convenient for branch network.

7. Capture enrollment details of employee for approval and reference purposes.

8. Determine course structure and categorize classes which depend on the

program delivering.

9. Can extend to other interface systems such as Content server, Finance

system, Core HR, Employee Self-Service.

1.3 Scope of the Project

Training Management System (TMS) is developed on Microsoft Visual Studio

.net using ASP.net which is a web-based application. This project will support the

following business processes.

First, organizational learning programs building are created as the catalog

hierarchies which include both classroom and e-leaming programs. Online classes will

link to content server which is used for e-content development.

Second, course enrollment management will receive the request from learners via

Employee Self-Service or training administrators will enroll courses to learners by

themselves. The approval process is required which allows only direct manager in

supervisor hierarchy to approve the requested course via Manager Self-Service

responsibility. Training administrators can track every enrollment stages, and submit the

3

enrollment summary report when enrollment process completed.

Moreover, usemame and password will be assigned before logging to the system

which is followed by security profiles using roles and responsibilities concepts.

Employees and managers will use Employee Self-Service and Manager Self-Service

responsibility to see theirs own home page which is used for receiving the notification

and launching the online class.

1.4 Deliverables

The deliverables of the projected Training Management System are as follows:

(1) Project Introduction

(a) Background of the project

(b) Objectives

(c) Scope

(d) Deliverables

(e) Project Plan

(2) The Existing System

(a) Background of the organization

(b) Current problems and areas for improvements

(3) The Proposed System

(a) Requirement Analysis

(1) System request

(b) System Design

(1) Context diagram

(2) Activity diagram

(3) Use case diagram

( 4) Class diagram

4

( 5) Sequence diagram

( 6) Communication diagram

( c) Hardware and software requirement

(d) Network requirement

(e) Security and controls

(f) Cost/benefit analysis

(4) Project Implementation

(5) Conclusions and Recommendations

• Appendix A Use Case Description

• Appendix B Data Dictionary

• Appendix C Class-Responsibility-Collaboration Cards (CRC Cards)

• Appendix D Sequence Diagram

• Appendix E Communication Diagram

• Appendix F Database Tables

• Appendix G User Interface Design

• Appendix H Output Reports

• Appendix I Cost Analysis of Candidate Solutions

• Bibliography

1.5 Project Plan

The project plan of the proposed system takes about 4 months. From the project

plan, it can be divided into:

1) Analysis of the existing system

At the beginning, we will define the objective and scope of the

training management system first. Next, we will study the existing system

by reviewing existing documents and staff interviewing. Then we will study

5

the business flow in order to analyze the gap between the proposed system

and the existing system. Then, we will create the functional modeling, and

study network architecture of the organization. Finally, we will do the cost

and benefit analysis.

2) Analysis and Design of the proposed system

In this process, we will use details from user requirements to analyze,

and design the new proposed system into the structure and behavioral

modeling. We will get the functional specifications, and then create

technical specifications including program, interface, network, database,

output design.

3) Implementation of the proposed system

After analyzing and designing the new proposed system, it is ready to

build the application. In this process, we will start to develop the application

with coding, and then test the proposed system before migration to

production environment. To implement the system, it includes hardware and

software installation, conversion, training and support after implementation

to ensure the application is satisfied.

This project plan of Siam Commercial Bank Public Company Limited: Training

Management System is given in Figure 1.1

6

No.

I

I.

1 I

2 3 4 5 6 7 IL

-...)

I

8 9 10

11

I

12

I II

I.

13

I

14

I

15

16

17

Tas

k N

ame

Ana

lysi

s o

f th

e E

xist

ing

Sy

stem

Def

ine

the

Obj

ecti

ve a

nd S

cope

Stu

dy th

e E

xist

ing

Sys

tem

Iden

tify

the

Exi

stin

g P

robl

ems

Stu

dy th

e E

xist

ing

Com

pute

r S

yste

m

Dev

elop

Act

ivit

y D

iagr

am

Dev

elop

Use

Cas

e D

iagr

am

Cos

t and

Ben

efit

Ana

lysi

s A

naly

sis

an

d D

esig

n o

f th

e P

ropo

sed

Syst

em

Web

Int

erfa

ce D

esig

n

Rep

ort D

esig

n

Dat

abas

e D

esig

n

Net

wor

k D

esig

n

Pro

gram

Des

ign

Imp

lem

enta

tio

n o

f th

e P

rop

ose

d S

yst

em

Cod

ing

Tes

ting

Har

dwar

e In

stal

lati

on

Sof

twar

e In

stal

lati

on

Con

vers

ion

May

20

06

1

I 2

I 3

I 4

~

June

200

6 1

I 2

I 3

I 4

.... ,....

... ...

~ ~

July

200

6 A

ugus

t 20

06

1 I

2 I

3 I 4

1

I 2 I

3 I

4

~

- ~

... ...

~,. ~~~

~

~ ~~~~

Fig

ure

1.1

Pro

ject

Pla

n o

f Tra

inin

g M

anag

emen

t S

yste

m

II. THE EXISTING SYSTEM

2.1 Background of the Organization

As the first and oldest Thai commercial bank, Siam Commercial Bank has a

history dating back as early as the reign of King Rama V, when the country's banking

system was served only by foreign banks. Realizing that a sound and independent

financial system was vital for Thailand's economic development, HRH Prince

Mahisararajaharuethai initiated the establishment of the Thai banking business under the

name of" The Book Club" in 1904. As its operations received wider recognition, His

Royal Highness sought Royal Assent and transformed it into the Siam Commercial

Bank Company Capital Limited, a full-fledged commercial bank, on January 30, 1906.

Because of his far-sighted undertaking, HRH Prince Mahisom is revered as " The

Father of Thai Banking," and the Siam Commercial Bank is regarded as a prototype of

Thai commercial banks.

For almost a century of business operations, the management of the Siam

Commercial Bank has consistently adhered to the philosophy set forth by its founder

which is to dedicate ourselves to the quality and righteousness of our work, to work as a

team so that we shall provide the best of services, to respect human values, and to

participate to the best of our ability in our society and nation.

Since the Siam Commercial Bank has been granted to establish in 30 January

1906(B.E. 2449), it plays important roles to serve Thai people and their society

indulgence and keeps its path simultaneously with the country economic growth. As a

professional and well-managed bank, it has demonstrated a leadership in utilizing

modem technologies to enhance and develop new services for customers.

Under the mission " to be the Bank of Choice for our customers, shareholders, and

employees", Siam Commercial Bank is committed to continuous development

8

according to the current environment. Recently, the Bank has initiated "Change

Program" to restructure its organization for a better efficiency and flexibility. SCB aims

to demonstrate its international performance through innovation, service enhancement

and operational efficiency to achieve the highest customer satisfaction from each

individual group of customers. With a strong financial foundation, over Baht 760,000

million assets, it conforms the Bank to be the country best financial institution and the

country best innovative service.

Siam Commercial Bank has divided many organization types which are president

and CEO, groups, divisions, units and teams. Finance Group takes proactively a leading

role in financial planning to enhance SCB's financial position, and be a dynamic

business partner through its quality and effectiveness of decision support within a strong

internal control framework. Operations Group is responsible for cooperation to business

staff in order to solve the problem of operation processes, and enhancement customer

satisfaction which analyze from the problem of work flows and the result of operations.

Retail Banking Group is responsible for financial transaction of individual customers

which are deposition, withdrawal, transferring and personal credit. Corporate Banking

Group take care large business credits such as government, telecommunication, a public

utility, and real estate. Human Resources Group is responsible for staffing and

development, training, compensation, human resource administration and human

resource client service division will take care separately for their customers. Information

Technology Group will support for information technology operation including data

management, security, IT resource management and solution development which IT

client services will get the requirement from user before forwarding to concerned

person. The organization chart is shown as Figure 2.1. Below:

9

........

0

RE

TA

IL B

AN

KIN

G G

RO

UP

PRO

DU

CT

S &

MA

RK

ET

ING

D

IVIS

ION

SA

LE

S&

SE

RV

ICE

D

IVIS

ION

RE

TA

IL C

RE

DIT

&

BU

SIN

ESS

SU

PPO

RT

D

IVIS

ION

INFO

RM

AT

ION

T

EC

HN

OL

OG

Y G

RO

UP

PR

ES

IDE

NT

AN

D C

HIE

F E

XE

CU

TIV

E O

FF

ICE

HU

MA

N R

ESO

UR

CE

S G

RO

UP

FIN

AN

CE

GR

OU

P

ITG

EX

EC

UT

IVE

SU

PPO

RT

IT C

LIE

NT

SE

RV

ICE

S D

IVIS

ION

IT S

OL

UT

ION

DE

LIV

ER

Y

DIV

ISIO

N

DE

VE

LO

PME

NT

! D

IVIS

ION

DE

VE

LO

PME

NT

2 D

IVIS

ION

ITD

AT

A M

AN

AG

EM

EN

T

DIV

ISIO

N

IT S

CE

UR

ITY

DIV

ISIO

N

IT R

ESO

UR

CE

S M

AN

AG

EM

EN

T D

IVIS

ION

HR

AD

MIN

!ST

RA

TIO

N

DIV

ISIO

N

TR

AIN

ING

DIV

ISIO

N

STA

FFIN

G&

D

EV

EL

OPM

EN

T D

IVIS

ION

HR

CL

IEN

T S

ER

VIC

ES

DIV

ISIO

N

FIN

AN

CIA

L R

EPO

RT

ING

&

CO

NT

RO

LS

DIV

ISIO

N

MIS

& F

INA

NC

IAL

PL

AN

NIN

G D

IVIS

ION

BA

LA

NC

E S

HE

ET

M

ON

ITO

RIN

G D

IVIS

ION

INV

EST

OR

RE

LA

TIO

NS

DIV

ISIO

N

FIN

AN

CIA

L

MA

NA

GE

ME

NT

SY

STE

MS

DIV

ISIO

N

OPE

RA

TIO

NS

GR

OU

P

PA

YM

EN

TS

&

SET

TL

EM

EN

TS

DIV

ISIO

N

CR

ED

IT O

PER

AT

ION

S D

IVIS

ION

CO

LL

EC

TIO

NS

DIV

ISIO

N

CA

RD

OPE

RA

TIO

NS

DIV

ISIO

N

TR

EA

SUR

Y &

FU

ND

S O

PER

AT

ION

S D

IVIS

ION

INT

ER

NA

TIO

NA

L T

RA

DE

O

PER

A T

IO N

S D

IVIS

ION

PLA

NN

ING

& C

ON

TR

OL

D

IVIS

ION

Fig

ure

2.1.

T

he O

rgan

izat

ion

Cha

rt o

f Sia

m C

omm

erci

al B

ank

CO

RPO

RA

TE

BA

NK

ING

G

RO

UP

CO

RPO

RA

TE

DIV

ISIO

N l

CO

RPO

RA

TE

DIV

ISIO

N 2

FIN

AN

CIA

L&

IN

STIT

UT

ION

AL

DIV

ISIO

N

BU

SIN

ESS

PR

OD

UC

TS

DIV

ISIO

N

JAPA

NE

SE D

IVIS

ION

BU

SIN

ESS

BA

NK

ING

D

IVIS

ION

CO

RPO

RA

TE

BA

NK

ST

RA

TE

GIC

PL

AN

NIN

G

2.2 Business Functions and Operations

The existing training business processes are manual which can be summarized as

follows:

Process 1: Build Individual/ Organizational Learning Program

The process of responding to the training needs assessment with planned

educational activities, including learning content design and structuring, sourcing

of supplies, project management. This also considers financial aspects of the

training courses. Program development unit receives the training requirements

from different units, and then drafts the training plan in order to send to the group

head for approval. After obtaining approval from the group head, program

development unit prepares training program details and budget. If the budget is

not planned, the request for the budget is required. Otherwise, program

development unit prepares the logistics of the course.

Process 2: Maintain Knowledge Management

This procedure covers the process of general internal training. The Program

Development, Training Administrator and Training Delivery units will prepare

training program proposal such as content, trainer and target audience. After

approved in principle by each program, they will set up the course, class and

learner as the planned, and then book resources to central administration division.

Training Administrator and Training Delivery units have to wait for the response

from client unit approval and employee reply in order to make class enrollments.

Also, they have to update class status to be confirmed and update employee

enrollment status to be enrolled before reporting the attendee lists. In the e

learning courses, employee can launch via the intranet of the bank in the training

homepage.

11

After completing the attendance, Training Delivery unit has to summarize

the training evaluation results and training expenses in order to send to financial

reporting and controls division.

The existing business functions and operations can be explained through a

context data flow diagram as Figure 2.2.

Central Training Requirements Administration

Approval Program Results Division

Client Units

I \

" 't w

Training Programs Resources Booking

Enrollment Results --Training Training Expenses

~ Financial Reporting

Division , And

Controls Division

' ,I

Figure 2.2. Context Data Flow of Existing Diagram

2.3 Current Problems and Areas for Improvement

According to the existing manual system, there are many problems which can be

represented as follows:

1) There are many units in training division which have to work together so the

manual system has duplicate and inconsistent data.

2) The enrollment processes take a long time for the operation such as approval

process.

12

3) Training administrators cannot track the enrollment status immediately since

to enrollment transaction information are offline which is inconvenient for

replying to their customers.

4) Course catalogs are not centrally defined.

5) The existing system is not secured in case of data security.

6) There are many training expenses such as paper, staff administration.

7) The manual system can not interface to e-leaming homepage and employee

directory system.

8) Employees have time limit for training hours because they have to train in

working hour, and use intranet at office only for self-training.

The proposed system is developed in order to solve those problems which areas

for improvement will be shown as follows:

1) Training expenses will decrease according to e-leaming delivery mode and

can save learner expenses and administrative expenses.

2) Employees can increase training hours because they can access from

anywhere and anytime so training performance of the organization is more

advantageous than other competitors.

3) Training administrators operate training tasks efficiently including course

centralized defines, real time enrollment tracking and accuracy information.

The proposed system also takes less enrollment time than the existing

system, and provides self-service to learner and manager conveniently.

4) Using role-based access control for training administrators and users which

will increase data security.

5) The proposed system supports future businesses which can extend and

integrate to external system easily.

13

III. THE PROPOSED SYSTEM

3.1 Requirements Analysis

According to the existing system, Training Division had only the manual

processes which each task is done for a long time because of the inconsistent

information and redundant data. Siam Commercial Bank Public Company Limited

needs to construct Training Management System (TMS) in order to facilitate the various

processes of functional training tasks and solve the problems occurring from the

existing manual system. Moreover, our organization would like to develop more e

Leaming class in order to reduce training costs.

A system request below describes the business reasons for building a system and

the value that the system is expected to provide.

Table 3.1. System Request - Training Management System (TMS)

Project Sponsor : Senior Executive Vice President of Human Resource Group

Business Need : This system has been initiated to increase the operational

efficiency and to decrease training costs using e-Leaming classes.

Business Requirements :

Using Web-based application, learners can logon to the system via the web

browser, search for the classes which are allowed for self-enrollment and enroll online.

Their supervisors will receive notification via Manager Self-Service and can approve

their training requests online. Training administrator can create the course catalog and

add enrollment for specific training courses which are required for employee

competency. The system must be accessed to content server in order to launch contents

or other learning objects fore-Leaming classes.

14

Table 3.1. System Request - Training Management System (TMS) (Continued)

The functionalities that the system should have are listed below:

• Categorize courses and schedule both for classroom and on-line training

• Access to classroom and launch e-Leaming classes

• Enroll courses and support self-enrollment

• Track enrollment details

• Approve the request courses from the direct manager

• Send the notification for enrollment processes

• Interface to content server

Business Value :

Banks expect that Training management System (TMS) will decrease the training

costs. Training costs are divided into course costs 70% including content copyright and

trainer costs, learner costs 20% including travel and accommodating costs, and

administrative costs 10%. On-line classes will save learner and administrative costs,

and also decrease some course costs because banks pay only content copyright not per

learner. Banks expect the operational process time and paper work will be decreased

because of the real time transactions and some document form is not essential. Also,

training hours for employee development will be increased because e-Leaming need

not to learn in working hours so learner can access anywhere, anytime and continue

from the latest access. Conservative estimates of tangible value to the bank include:

• 3,500,000 Baht training costs deduction

• 450,000 Baht paper work will be reduced

15

Table 3.1. System Request - Training Management System (TMS) (Continued)

Special Issues or Constraints :

• Learner behavior cannot be controlled to attend e-Learning classes in time.

• User friendly interface in e-Content design is difficult.

• PC at the branch may have not enough for employees to attend e-Learning

classes, and Head Office network connections are limited the bandwidth.

In order to achieve the target, the new proposed Training Management System

(TMS) must do the function requirements as follows

(1) Training administrator can categorize courses and schedule both classroom

training and on-line class.

(2) Employees or learners can access to the classroom and launch e-Learning

classes.

(3) Employees or learners can enroll for courses which are allowed for self

enrollment.

(4) Training administrator can add enrollment for required courses for learners

and track the enrollment.

(5) Enrollments require direct manager approval.

(6) Enrollment processes need to have notifications to learner and manager.

(7) The system can interface to content server which manages digital assets

used for developing learning objects. These tools usually include templates,

interactive quizzing features and test administrator, can incorporate files and

documents from various sources, including Microsoft Word, PowerPoint,

video, audio, and graphics.

16

Moreover, the new proposed Training Management System (TMS) must have the

non-function requirements as follows

(1) The system should be able to work on a Web browser.

(2) The system should allow access from anywhere outside the bank, and be

available for use 24 hours per day, 365 days per year.

(3) Log on user should have an employee number with at least 8 characters for

application of password, and outside the bank connection should require

authentication access.

3.2 System Design

3.2.1 Functional Modeling

Context Diagram shows data flow through the system. Context diagram

level 0 of Training Management System (TMS) is shown in the Figure 3.2 which

comprises of four external agents; Employees, Managers, Training Administrators

and Content Server. Training Administrators create course details as input

transactions through the system in order that the system will generate output

transaction such as course outlines to Employees. Also, e-Leaming classes need to

define learning objects; contents, tests, evaluations in order that Content Server

can interface with Training Management System (TMS). Both of Employees and

Training Administrators can make enrollments which depend on course

definitions. The enrollment transaction will send enrollment details to the system

after that the system will generate two notifications; enrolled course notification

and requested course notification to Employees and Managers in sequence.

Managers need to take approval actions as approval results via notifications then

the system will send the result to Employees as approval notification. After

manager approved courses, the system will show attendance lists to Employees in

17

order to be able to access the class both of e-Leaming and classroom classes.

Finally, the system will generate enrollment report to Training Administrators

which can track enrollment details at each enrollment states.

Process

External Entity

Data Flow

/

Name

Name

Data Name '-->

Round Rectangle

Square

Solid-line with arrow

Figure 3.1. Element of Context Diagram (Use Gane and Sarson Symbol)

18

Enrollment Details Approval Results

Employees Attendance Lists Managers ~ ....

j~ .t. •l •l

Course Requested Course Outlines ,, ,, Notification

r ' 0

Approval Training Course Details -

Notification -Enrolled Course

Management Enrollment Details -Notification System - I

'\.

·• Training Content - Administrators Server

. Leaming Objects Enrollment Report

Figure 3.2. Context Diagram

19

Activity Diagram is the object-oriented equivalent of flow charts and

data-flow diagrams (DFDs). Activity diagram of Training Management System

(TMS) is shown in the Figure 3.4 which initial activity state are about course

catalog that consists of create course, create offering, create learning object,

create class. Courses information hold generic information about a course of

learning, whereas offerings are specific instances of course that provide more

details about the delivery of the learning, as well as, in the case of online course,

linking to learning objects; actual contents, tests, evaluation and so on. Leaming

objects contain metadata that describe the physical content stored on content

server. A class is a specific occurrence of an offering which learner enroll in and

attend, or take online. Classes identify individual dates, time, and location of

scheduled courses. After training administrator categorized courses next activity

state are about enrollment processes which will be allowed to take enrollments or

not so check class status activity state will be checked. If class status is Planned it

is not allowed for enrollment, but if class status is Normal, check enrollment type

activity state will check the class conditions that is self-enrollment or not. The self

enrollment option enables the learner to enroll class from Learner Self-Service

while training administrator can add enrollment also if self enrollment option is

not provided. After enrollment, the system will create two notifications to the

learner about enrolled information and to manager about requested notification

then manager have to response this action from Manager Self-Service, enrollment

and notification data store will be updated status to be approved or rejected.

Learner can attend class if and only if manager approved the course which is the

final activity for Training Management System (TMS) processes.

20

An Initial Node: - Portrays the beginning of a set of actions or e

activities

A Final-Activity Node: -- Is used to stop all control flows and object flows in an activity

An Activity:

~ - Is used to represent a set of actions - Is labeled by its name

An Object Node:

I I - Is used to represent an object that is connected to

Class Name a set of Object Flows

- Is labeled by its class name

A Control Flow: ~

- Shows the sequence of execution ~

A Object Flow: - Shows the flow of an object from one activity to ------------------~

another activity

A Decision Node: - Is used to represent a test condition to ensure that the control flow or object flow only goes down one path +[Decision [Decision+

- Is labeled with the decision criteria to continue Criteria!] C1iterial]

down the specific path

A Merge Node: Lr__J - Is used to bring back together different decision paths the were created using a decision-node

A Join Node: \ I - Is used to bring back together a set of parallel or concurrent flows of activities ,,

Figure 3.3. Element of Activity Diagram

21

r----1 I

't

Leaming Object Info. ------~ Course Info. [

I I I I I I I I I

I..-----

[E-Learning Class] [Classroom]

Create Learning Object

Offering Info.

• I I I I I I I I I I

Create Offering _____ J

Class Info. ~------- Create Class

Check Class Status

[Self-Enrollment] [Not Self-Enrollment]

Enroll Class Add Enrollment --------- Enrollment Info.

Enrollment Info.

I I I I I I I I I I I I I I I I I I I I I I I I I I I

Notify Learner

NotifyManager ____________ .J :

I I I I I ________________ J

__________________________ J

Figure 3.4. Activity Diagram

22

Use Case Diagram is a functional diagram in that they po1iray the basic

functions of the system which is what the users can do and how the system should

respond to the user's actions. Figure 3.6 below shows use case diagram of

Training Management System (TMS) which are separated to 11 major use cases

that the system will perform the benefits following the requirements needed.

From the functional modeling of the proposed training management

system, there are 11 use case activities design; Browse Class, Enroll Class, Attend

Class, Create Course, Create Offering, Create Class, Create Learning Object, Add

Enrollment, Track Enrollment, Search Course, Approve Course. The total actors,

use case name, use case description are listed in the Table 3.2 List of Actors, Use

Case name, Use Case description. There are three basic parts to a use case

description; overview information, relationships, and the flow of events.

Overview information comprises the use case name, ID number, importance level,

primary actor, type, and a brief description. Detailed use cases extend the

overview with identification and description of the stakeholders and their interest,

the trigger and its type, the relationships in which the use case participates

(association, extend, generalization, and include), the normal flow of events, the

sub flows, and any alternate or exception flows to the normal flow of events. A use

case description contains all the information needed to build the diagram as

follows, but it expresses it in a less formal way that is usually simple for users to

understand. All of each use case description will be shown in APPENDIX A: USE

CASE DESCRIPTION.

23

An Actor: - is a person or system that derives benefit

from and is external to the subject - Are placed outside the system boundary - Is labeled with its role

A Use Case: - Represents a major piece of system functionality - Is placed inside the system boundary - Is labeled with descriptive verb-noun phrase

An Association Relationships: - Links an actor with the use case(s) with which it

interacts

Figure 3.5. Element of Use Case Diagram

24

Actor/Role

Use Case Name

* *

Training

Administrator

*

Training Management System

Browse Class

A * Enroll Class

* * Leamer

Attend Class * *

Create Leaming Object

*

Approve Course 1-------+---i-* *A Manager

Figure 3.6. Use Case Diagram

25

Table 3.2. List of Actors, Use Case name, Use Case description

Actor Use Case Name Use Case Description

Training Administrator Create Course This use case describes how to create

courses

Training Administrator Create Offering This use case describes how a course is

delivered; synchronous or

asynchronous, online or offline as well

as what are the learning objects for

online courses

Training Administrator Create Class This use case describes how to define

schedule dates, times, locations, and

enrollment designation. Also, classes

are further broken down to sessions to

specify different times and locations

Training Administrator Create Leaming This use case describes how to associate

Object the learning object with the physical

content files that are located on content

server

Training Administrator Add Enrollment This use case describes how to enroll

learners with single enrollment to

classes which are not allowed self

enrollment

Leamer Enroll Class This use case describes how to use self

enrollment option from Leamer Self-

Service in order to request the course

26

Table 3.2. List of Actors, Use Case name, Use Case description (Continued)

Manager Approve Course This use case describes how manager

take approval actions from Manager

Self-Service in order to response the

requested course

Learner Attend Class This use case describes how to launch

online offerings in the player, whereas

offline offerings are not launched within

the application

Learner Browse Class This use case describes how to find the

class that are self enrollment

Training Administrator Track Enrollment This use case describes how to track the

enrollment transaction

Training Administrator Search Course This use case describes how to see the

catalog hierarchy

3.2.2 Structure Modeling

Structure models. describe the underlying data structure of an object

oriented system. The models provide an internal static view of the evolving

system such as how the objects are organized in the system.

Class diagram is a graphical description of the information contained on

the CRC cards. It shows the classes and relationships between classes. The

visibility of the attributes and operations and the multiplicity of the relationships

are additional information that the class diagram portrays, which is not included

27

on the CRC cards. Class diagram of Training Management System (TMS) can be

classified to 14 classes which store and manage information in the system (See

Figure 3.8). The attributes of a class and their values define the state of each

object that is created from the class, and the behavior is represented by the

operations. There are 4 aggregation relationships such as Course and Offering

classes because offerings are part of the courses, and the generalization of

relationship; Training Administrators and Managers are kinds of employees.

Association relationships are shown by drawing lines between classes and a line

label represents exactly how the two classes are related to each other.

CRC cards model the classes, their responsibilities, and their

collaborations which are shown at the front of the card, and the back of the card

contains the attributes and relationships (See APPENDIX C: CLASS-

RESPONSIBILITY-COLLABORATION CARDS (CRC CARDS)).

Table 3.3. Multiplicity

Multiplicity Notation

Minimum Maximum Interpretation Instances Instances

Exactly one 1 1 1

Zero or more o .. * 0 Many (>1)

One or more l..* 1 Many (>1)

Zero or one 0 .. 1 0 1

Specified range 2 . .4 2 4

Multiple, disjoint ranges 1..3, 5 1, 5 3, 5

28

A Class: - Represents a kind of person, place, or thing

about which the system will need to capture and store infonnation

- Has a name typed in bold and centered in its on top compartment

- Has a list of attributes in its middle compartment - Has a list of operations in its bottom

compartment - Does not explicitly show operations that are

available to all classes

An Attribute: - Represents properties that describe the state of

an object - Can be derived from other attributes, shown by

placing a slash before the attribute's name

An Operation: - Represents the actions or functions that a class

can perform - Can be classified as a constructor, query, or update operation

- Includes parentheses that may contain parameters or information needed to perform the operation

An Association: - Represents a relationship between multiple

classes, or a class and itself - Is labeled using a verb phrase or a role name, whichever better represents the relationship

- Can exist between one or more classes - Contains multiplicity symbols, which represent

the minimum and maximum times a class instance can be associated with the related class instance

A Generalization Relationship: - A "solid line with a large hollow triangle" used

to connect lines between two classes denotes the generalization (or inheritance) relationship

An Aggregation Relationship: - A "diamond" used to connect lines between two

classes denotes the aggregation relationship

Classl -attribute 1

+operation!()

attribute name /derived attribute name

operation name ()

O .. * Verb phrase

I Class A J Li:-

I Class B I

I Class A

~ ~

I Class C I

j Class B j

Figure 3.7. Element of Class Diagram

29

w

0

Co

urs

e D

eliv

ery

Mod

e

-cou

rse

code

I

-dm

_id

--c

ours

e_ na

me

--d

m_n

ame

-des

crip

tion

-d

m_o

nlin

e -s

tart

_ dat

e -d

m_s

ynch

rono

us

-end

_dat

e

uses

0

1

has

o .. *

Off

erin

g ~ o

.. *

Lea

rnin

g O

bje

ct

-off

erin

g_ id

~

-obj

_id

-off

erin

g_ na

me

-obj

_ nam

e -s

tart

_ dat

e ,..

O .. *

con

tain

s l

-des

crip

tion

-e

nd_d

ate

-aut

hor

"""

-cat

alog

-c

atal

og_ n

umbe

r I

list

s -v

ersi

on

o .. *

-con

tent

_ typ

e

Cla

ss

-ser

ver_

nam

e -s

erve

r_ di

rect

ory

-cla

ss_i

d -i

niti

al_ f

ile

-tit

le

-sta

rtin

g_ ur

l -t

rain

ing_

cent

er

-loc

atio

n +

load

Con

tent

()

-sta

tus

-sta

rt_ d

ate

-end

_dat

e -s

tart

_tim

e -e

nd_t

ime

I re

cord

s o ..

* -d

urat

ion

-uni

t -e

nrol

lmen

t_st

art_

date

-e

nrol

lmen

t_ en

d_ da

te

-min

_ att

ende

es

-max

_att

ende

es

-sel

f_ en

roll

men

t

+up

date

Sta

tus(

)

Use

rs

Res

pons

ibil

ity

Men

u

-use

r_id

o ..

* ha

s o ..

* -r

esp_

id

cont

ains

-m

enu

id

o .. *

o .. *

--u

ser_

nam

e -r

esp_

nam

e -m

enu_

nam

e -u

ser _

pass

wor

d -c

reat

ion_

date

-p

age_

nam

e -c

reat

ion_

date

-l

ast_

upda

te_d

ate

-cre

atio

n_ da

te

-las

t_up

date

_dat

e -l

ast_

upda

te_ d

ate

-las

t_lo

gon_

date

I 0 ..

1 ho

lds

I 1 E

mpl

oyee

N

otif

icat

ion

-em

ploy

ee_i

d -n

otif

icat

ion_

id

-fir

stna

me

-em

ploy

ee_i

d -l

astn

ame

Org

aniz

atio

n

reco

rds

2 .. *

-m

essa

ge_ n

ame

-add

ress

-s

tatu

s -e

mai

l -o

rg_c

ode

-act

ion_

type

-p

hone

_num

ber

o .. *

belo

ngs

I -o

rg_n

ame

-fro

m_i

d -h

ire_

date

-o

rg_t

ype

-cre

atio

n da

te

--s

alar

y -d

ate_

from

-due

dat

e -j

ob

-dat

e_to

-

+up

date

Act

ionT

ype(

) -p

erso

n_ ty

pe

1 -m

anag

er_i

d +

upda

teS

tatu

s()

En

roll

men

t I

+en

roll

Cla

ss()

-enr

ollm

ent_

id

+re

ceiv

eNot

i fic

atio

n()

-enr

ollm

ent_

date

+

atte

ndC

lass

()

-sta

tus

is a

~

is a

-c

ompl

etio

n_ da

te

o .. *

regi

ster

s I

I

+up

date

Sta

tus(

) T

rain

ing

Ad

min

istr

ato

r M

anag

er

+se

ndN

oti f

icat

ion(

)

+ad

dEnr

ollm

ent(

) +

rece

i veN

otif

icat

ion(

) +

subm

itR

epor

t()

+ap

prov

eCou

rse(

)

Fig

ure

3.8.

C

lass

Dia

gram

3.2.3 Behavioral Modeling

This model represents the underlying of the business process portrayed by

interaction diagrams in UML which focuses on the object level. There are two

different diagrams (sequence and communication) that can be used to model the

interactions that take place between the objects in an information system.

Sequence diagrams· are shown in APPENDIX D: SEQUENCE

DIAGRAM which illustrate the objects that participate in a use case and the

messages that pass between them over time for one use case.

Communication diagrams are shown m APPENDIX E:

COMMUNICATION DIAGRAM which provide a view of the dynamic aspects

of an object-oriented system that emphasizes the flow of messages through a set

of objects so communication diagrams are very useful to show process patterns of

activity that occur over a set of collaborating classes.

The proposed system is divided into eleven major use cases which are:

Use Case 1: Create Course

Training Administrator creates courses which are the first level of catalog

hierarchy, the system will generate course information.

Use Case 2: Create Offering

Training Administrator looks up the course that would like to create an

offering then select the delivery mode. If the mode is online, training

administrator has to select the learning object before creating an offering.

Use Case 3: Create Class

Training Administrator looks up the offering that would like to create a

class then create class information.

31

Use Case 4: Create Learning Object

Training Administrator creates learning objects for online class which are

linked to content server.

Use Case 5: Add Enrollment

Training Administrator selects the class from class infonnation, then

selects learner from employee information to create an enrollment. After an

enrollment object is created, the system will generate notification information in

order to inform the learner and manager for approval enrollment.

Use Case 6: Enroll Class

Leamer selects classes from the class information via learner self-service

responsibility then enrolls the class. After an enrollment object is created, the

system will generate notification information in order to inform the learner and

manager for approval of enrollment.

Use Case 7: Approve Course

Manager will receive the notification via manager self-service then take

approval actions. After the result, the system will update status to notification and

enrollment information. Also, the result will be notified to learner.

Use Case 8: Attend Class

Leamer attend class via learner self-service which are shown as

attendance lists. Fore-learning class, learner can use online player.

Use Case 9: Browse Class

Leamer browses class from class information to make an enrollment.

Use Case 10: Track Enrollment

Training Administrator track enrollments from any criteria such as class

name, enrollment number, enrollment status, person type and organization.

32

Use Case 11: Search Course

Training Administrator look up course catalogs from the search criteria.

3.2.4 Database Design

Data management layer designs focuses on both data access and

manipulation logic along with the actual design of the storage. The data storage

component of the data management layer manages how data is stored and handled

by the programs that run the system. The proposed system selects relational

databases design as object-persistence formats of storage. The database design

technique to store objects, objects must be converted so that its can be stored in a

table. From a design perspective, this entails mapping the problem domain classes

in a UML class diagram to the RDBMS-based data management layer tables

which are shown in Figure 3.9. As the rules of mapping problem domain objects

to RDBMS, all the concrete problem domain classes are mapped to RDBMS

tables. Second, single-valued attributes are mapped to columns of the table. Third,

methods are mapped to stored procedures or to program modules. Aggregation

and association relationship are mapped by placing the primary key from one

table into the related table as a foreign key, but if there are multi-valued

aggregation and association relationship, a new associative table is created which

relates the two original tables together then copy the primary from its to the new

associative table. Generalization relationship is mapped by adding column to each

table that represents a subclass for each of the concrete superclasses of the

subclass, also the primary key of superclass and subclass have to be similar.

The database table will be shown in APPENDIX F: DATABASE

TABLES. It will include attribute name, data type, length, default value,

uniqueness and description.

33

w

.+;:..

RD

BM

S T

able

s

Fig

ure

3.9.

Pro

blem

Dom

ain

Cla

sses

Map

ping

pro

blem

dom

ain

clas

ses

to R

DB

MS

tab

les

Not

ific

atio

n

-not

ifica

tion _

id

-em

ploy

ee _i

d -m

essa

ge_ n

ame

-sta

tus

{.;..

)

Vl

RD

BM

S T

able

s

Fig

ure

3.9.

Prob

lem

Dom

ain

Cla

sses

Map

ping

pro

blem

dom

ain

clas

ses

to R

DB

MS

tab

les

(Con

tinu

ed)

3.2.5 User Interface Design

Based on the examination of use case, sequence diagrams and

requirements from users describe commonly employed patterns of actions that the

user will perform so the interface design specifications will be created.

The propose system is designed to be Web-based interfaces and Graphical

User Interface (GUI) which the input screen will be developed to be user friendly.

Input mechanism facilitates the entry of data into the computer system such as

course code, description, enrollment number, status and so on which is designed

to be simply and easily capture accurate information for the system. It will be

shown in the APPENDIX G: USER INTERFACE DESIGN.

3.2.6 Output Reports

Output mechanism presents information· to users so they can accurately

understand it with the least effort. Output specifications have been derived from

user requirements and existing reports.

Reports of the proposed system are designed in different types of reports,

such as detailed report and summary report. The report will respond to a query

with matching the criteria. The system produces outputs, whether on the screen

that is the web report for enrollment state, on paper. The user will see information

in tabular format in the application, and can export to excel file. It will be shown

in the APPENDIX H: OUTPUT REPORTS.

3.3 Analysis of Candidate Solutions

As the system request, Siam Commercial Bank Public Company Limited has own

process for the feasibility analysis including 4 techniques; operational feasibility,

technical feasibility, economic feasibility and schedule feasibility. The results of these

techniques are combined into a feasibility study deliverable that is given to the approval

36

committee. Cost-Benefit analysis identifies the financial risk associated with the project

which will be used for economic feasibility along with the Feasibility Analysis Matrix

in Table 3.4.

To do the feasibility analysis, Feasibility Analysis Matrix will use for identifying

candidate system solutions and analyzing the feasibility for those solutions. Each

candidate solution will be used for comparison in Feasibility Analysis Matrix.

• Candidate number one is an alternative of packaged software which IS

Oracle Leaming Management System (OLM).

• Candidate number two is an alternative of custom development which is

developed by SCB Information Technology Solution Division. The

application is developed by using Visual Basic .net with SQL server

database management system.

• Candidate number two is an alternative of outsourcing development which

is developed by PWS Consulting Company Limited. The application Is

developed by using Java with DB2 database management system.

To perform a cost-benefit analysis as shown in APPENDIX I: COST ANALYSIS

OF CANDIDATE SOLUTIONS, the analysis is determined by identifying costs and

benefits associated with the system, assigning values to them, and then calculating the

cash flow and return on investment for the project.

Cost-benefit analysis usually contains costs and benefits over five years to show

cash flow over time. For example, APPENDIX I lists amount for training costs and

material costs for all five years.

Net Present Value (NPV) is used to compare the present value of future cash

flows with the investment outlay required to implement the project. The present value

(PV) of the costs and benefits are calculated first. Then NPV is calculated, and it shows

37

the discounted rate of the combined costs and benefits. In this case, the rates of change

use interest rate at 6 percents to calculate PV and NPV which are shown as the formula

below;

PV = Arnount/(1 + interest rate t ; n = number of years in future

NPV = PV Benefits - PV Costs

The return on investment (ROI) is a calculation that measures the amount of

money an organization receives in future for the money it spends. Candidate two has

highest ROI which can be calculated as below;

ROI =((Total benefits -Total costs)/ Total costs) x 100

= ((20,092,342.55 - 7,987,340.50)/ 7,987,340.50) x 100

= 152 %

The break-even point is determined by looking at the cash flow over time and

identifying the year in which the benefits are larger than the costs. Candidate two can be

calculated as below;

Break-Even point= (Yearly NPV* - Cumulative NPV)/ Yearly NPV

= (3,222,054.11 - 1,587,431.47)/ 3,222,054.11

= 0.51 **

= 1.51 years (break-even occurs in year 2)

* Use the Yearly NPV amount from the first year in which the project has a

positive cash flow.

**Add the above amount to the year in which the project has a positive cash flow.

In conclusion, after analyzing and ranking in Feasibility Analysis Matrix, the

candidate three is selected as it provides the best advantages to the system and

organization with the details as follows:

38

Operational Feasibility

Even the candidate number one is more competitive than other candidates

because the package can support future business, but some current work

procedures must be changed to associate with standard functions of the package,

some functions will not be used according to the inconsistency of user

requirements, and user interface needs to be modified as personalization of

organization. The candidate number two and three are parallel alternatives, but

candidate number two is the most suitable for current business as custom

development is entirely dedicated to the company which means they are more

accessible than a firm might be, and the services they provide are flexible and may

be customized easily.

Technical Feasibility

As the bank's IT expertise increases, it will help for internal system

development. The candidate number two can develop and maintain the system

easily and conveniently using Visual Basic .net with SQL server.

Economic Feasibility

The candidate number two is the best worth in cost effectiveness because

the custom development is made by SCB Information Technology Solution

Division so the development cost will have less than other candidate solutions.

Also, there are the highest return on investment and fastest for break-even point.

Schedule Feasibility

The candidate number one is packaged software so the implementation time

will be less than the other candidates which are the custom development.

39

Table 3.4. Feasibility Analysis Matrix

Feasibility Wt Candidate 1 Candidate 2 Candidate 3

Criteria

Operational 30%

Feasibility

Functionality OLM software Fully supports user Same as

package supports requirements candidate 2

the basic functions because of the

and operations of system specification

Training is designed

Management specifically for

System including training business

some excessive processes of the

modules which are organization

not essential for

current business

processes. Also,

software package

need to be modified

the interface to

satisfy the user

requirements.

Political The application is The system will be Same as

standard function so accepted by all candidate 2

some work flow stakeholders easily

processes might be as it is designed to

changed. Functional support cover the

users and business needed.

stakeholders need

more consideration.

Score: 95 Score: 90 Score: 90

40

Table 3.4. Feasibility Analysis Matrix (Continued)


Criteria

Technical 30% OLM software SCB Technical PWS Consulting

Feasibility package has been Teams are familiar Company Limited

famous on the with Visual Studio is famous

market so there are .net developer tool software house

many site references because current which has

in Thailand. The applications at the certified by IBM,

application bank are almost Microsoft and so

development is base web-based on. According to

on Java technology application so limited resources,

and use oracle technical teams have SCB need to pay

developer tool many skills which for outsourcing

which SCB can develop and software

technical teams have maintain easily. development.

been less skills so in Training Training

the implementation Management Management

need skills transfer System (TMS) is System (TMS)

from oracle base on Visual will develop on

consultants and Basic .net with SQL Java language

some training server. withDB2.

courses. Oracle will

not support any

customizations that

are performed by

customers so the

extension need more

implementation

charge and its may

have the effect to

another modules.


41

Table 3.4. Feasibility Analysis Matrix (Continued)


Criteria

Economic 30%

Feasibility

Present Value Approximately Approximately Approximately

(PV) of Costs: 11,777,414.27 baht. 7 ,987 ,340.50 baht. 9,113,965.89 baht.

Net Present Approximately Approximately Approximately

Value (NPV): 8,314,928.28 baht. 12,105,002.05 baht. 10,978,376.66 baht

Return On Approximately Approximately Approximately

Investment 71% 152% 120%

(ROI):

Break-Even Approximately Approximately Approximately

Point: 2.64 years. 1.51 years. 1.83 years.

Detailed See APPENDIX I: See APPENDIX I: See APPENDIX I:

.· calculations: COST ANALYSIS COST ANALYSIS COST ANALYSIS

OF CANDIDATE OF CANDIDATE OF CANDIDATE

SOLUTIONS SOLUTIONS SOLUTIONS


Schedule 10% 1-2 months 1-4 months 1-2 months

Feasibility


Ranking 100% 81.5 92 87.5

42

3.4 Hardware and Software Requirements

According to the requirement, the system reqmres high capacity which can

support a maximum of 300 - 400 simultaneous users at peak use times. Also, the

response time must be less than 7 seconds for any transaction over networks, and the

notification must be transmitted immediately so the system needs to have high

processing time. The volume of data expected each year will store data in approximately

300 class enrollments both for classroom and E-learning classes for a total of about 100

meg of data, and there are many multimedia files for E-learning content which are

stored in content server. Training division have planned to develop Training

Management System more in the next phase which means the size of database need to

be supported for five years.

As has been shown, - the server hardware specification must have high

performance as shown in Table 3.5 - 3.8.

Table 3.5. The Hardware Specification for Application Server

Hardware Specification

CPU Intel 2x Xeon Processor 3.0 GHz, FSB 800 MHz ,L2 Cash 2MB

RAM 4GB

Hard Drive ULTRA SCSI 160GB 10,000 RPM

Display Card ATI Redeon with 16MB SDRAM

LAN Intel PR0/1000 MT single port Gigabit NIC

CD-ROM COMBO DVD 16X DVD ROM And 24X CD-RW/DVD

INPUT Device USB Keyboard , Dell PS/2-style mouse

43

Table 3.6. The Hardware Specification for Content Server



RAM 2GB






Table 3.7. The Hardware Specification for Database Server



RAM 4GB






Table 3.8. The Hardware Specification for Each Client Machine


CPU Intel Pentium Class

44

Table 3.8. The Hardware Specification for Each Client Machine (Continued)

Cache Memory 256 KB or higher

RAM 256 KB or higher

Hard Drive 80 GB or higher

Display Card VGA Standard

LAN Ethernet 10/100

CD-ROM 52X or higher

INPUT Device Standard Keyboard , PS/2-style mouse

Microsoft has provided a lot of software, which can communicate with a normal

Intel-based PC server, Content Server, Application Server and Database Server. The

software is designed to integrate with Microsoft Windows Server 2003, and is also

packed together with Microsoft Back Office suite as shown in Table 3 .9 - 3.10.

The proposed system, the client machines will have a high capacity to run the

program which is a web-based application. The output will show via web browser such

as Microsoft Internet Explorer, and more software required as Table 3.12.

Table 3.9. The Software Specification for Application Server

Software Specification

Operating System Microsoft® Windows® Server 2003, Enterprise Edition

Internet software Microsoft Internet Explorer 6.0 SP2

Internet Information IIS 6.0

Services (IIS)

Connection Tool Microsoft SQL Server Native Client

45

Table 3.9. The Software Specification for Application Server (Continued)

Framework Microsoft .NET Framework 2.0

Table 3.10. The Software Specification for Content Server


Operating System Microsoft® Windows® 2000 Professional with SP2



Services (IIS)

Content Builder Siebel SimBuilder Version 7.703

PowerPoint import Microsoft PowerPoint 2000, 2002

MS Word export Microsoft Word 2000, 2002

Audio Windows Media Player 9 or Higher

Flow Chart import Microsoft Visio 2003

Table 3.11. The Software Specification for Database Server


Operating System Microsoft® Windows® Server 2003, Enterprise Edition



Services (IIS)

Reporting Services ASP .NET2.0

DBMS Microsoft SQL Server 2005 Enterprise Edition

46

Table 3.12. The Software Specification for Each Client Machine


Operating System Microsoft® Windows® XP


Application Software Microsoft Office 2003 Professional Edition

3.5 Network Requirements

The proposed network requirement needs to connect to server from three

locations. First, Head office connects to server through intranet line (LAN). Second,

Branches connect to server through leased line of the company. Also, Siam Commercial

Bank allows only employees who have privileged access from external network

(Internet) through internet line. Any connection has to pass the firewall before the

switching hub will be forwarded to the proposed application server. Moreover, access

from internet must connect through the internet web server to authenticate to the system

before connecting to the application. The network diagram will be shown in Figure 3.10

below.

47

Server Fann

Application Server

Database Server Content Server

Intranet Line

Leased Line

Figure 3.10. Network Infrastructure

3.6 Security and Control

PC Client

BRANCH

PC Client

INTERNET

PC Client

The following minimum requirement of security standards must be applied to the

computerized system to prevent unauthorized access and data security. Security access

control is an important aspect of any system. Security access control is the act of

ensuring that an authenticated user accesses only what they are authorized to and no

more. Security and control for the proposed system can be listed as follows

3.6.1 Authentication and Authorization (System Security)

Authentication is the act of determining the identity of a user and of the host

that they are using. The goal of authentication is to first verify that the user, either

a person or system, which is attempting to interact with the system is allowed to

do so. The second goal of authentication is to gather information regarding the

48

way that the user is accessmg the system. Therefore gathering basic host

information, such as its location and security aspects of its connection which is it

encrypted, is it via a physical line and the private connection is critical so the

proposed system will get that information from the bank network detection

system. To protect against unauthorized access to the application and the database,

user id and password approach is the most common, and typically the simplest to

identify someone.

Authorization is the act of determining the level of access that an authorized

user has to behavior and data. For the application level access, we use the concept

of roles and responsibilities which role designs are considered to functions,

people, data and approvals hierarchy. Roles are the concept of responsibility

design which consider the segregation of duties in organization and the internal

controls that need to be enforce. We assign to the user one or more responsibilities

such as Manager Self-Service, Employee Self-Service and Training

Administrator. Responsibilities provide the link between the user and the menu

which the menu access will be defined to its. Authorization can be enforced in the

database tier so the permission techniques are set up. A permission defines the

type of access that is permitted, such as the ability to update a table or to run a

stored procedure. In SQL, permissions are given via the GRANT command and

removed via the REVOKE command. When a user attempts to interact with a

database his or her permissions are checked, and if the user is not authorized to

perform part of the interaction which could be a transaction, the interaction fails

and an error are returned as database log files.

3.6.2 Data Security

1) Control Configuration and Setting

49

Users and developers will not be authorized to change the

configuration and setting on the production environment. System will be

controlled with the change control processes. Any change requests will be

done only by the person who is the system administrator and database

administrator to prevent any loss or damage that might be caused by

changing the configuration of the system.

2) To protect against physical destruction

Physically, the computer system is vulnerable. The computer server

should be placed in a safe place that is allowed only authorized access. This

is to prevent the system from both physical destruction and unauthorized

access.

3) Virus Protection

Symantec security software is currently implemented in the

organization, each client will be installed and will be automatically updated

the latest virus protection from the server every day when clients log on to

the bank network.

4) Backup and Recovery

The system also has the back up and recovery function in order to

protect loss of data from any unexpected events such as forces of nature. All

training information will be backed up once a month which will be kept in

the tape library. Also, organization has implemented controls to limit

damage such as contingency plans for continued operations so the system

would be ready to use for system recovery anytime required.

3.7 Cost and Benefit Analysis

Cost and benefit analysis identifies the financial risk associated with the project

50

which is to perform an economic feasibility analysis in the selection of candidate

solutions. As in-house development has been selected, the costs and benefits can be

broken down into four categories;

1) Development costs

Development costs are the tangible expenses that are incurred during

the construction of the system, such as hardware and software expenses,

development team salaries. Development costs are usually thought of as

one-time costs.

2) Operational Costs

Operational costs are the tangible costs that are required to operate the

system, such the salaries for operations staff, software and software

upgrades, hardware repairs, software licensing fees. Operational costs are

usually thought of as ongoing costs which are expected to increase 10

percentages each year.

3) Tangible benefits

Tangible benefits are revenues and cost savings which the proposed

system enables the organization to collect. Siam Commercial Bank has

increased approximately 10 percentages of training costs each year because

of the organization growth which requires the new staff training. Training

Management System (TMS) can decrease the training cost by 30 percent

according to the e-leaming classes need not to pay for administrative costs,

and learner expenses such as travel costs, accommodation costs. Moreover,

the proposed system can decrease material costs, such paper work for

enrollment processes, training materials.

51

4) Intangible benefits

The proposed system also can affect the organization's bottom line by

reaping intangible benefits which are based on intuition and belief in order

to facilitate or satisfy the organization. Intangible benefits include decreased

processing times such as the course approval processes, enrollment

processes, and increased training hours due to the e-leaming classes can

attend anywhere and anytime. Employees need not to attend in working

hours, and can also continue the lessons from the previous one in the period

of class schedule so this intangible benefit is expected to increase by 50

percent the employee training hours.

Of course, the depreciation cost of hardware and software have to be analyzed to 5

percentages. The details of costs and benefits analysis will be shown in APPENDIX I:

COST ANALYSIS OF CANDIDATE SOLUTIONS.

52

IV. PROJECT Il\1PLEMENTATION

4.1 Overview of Project Implementation

Project implementation is the process of system construction and delivery of the

proposed system to the organization. The project implementation must follow the

project plan or timeline that has been specified in the earlier section. The process of

project implementation must include.

1) Hardware and software acquisition, development and installation

Either the software selection are software package, outsourcing software

development, or in-house software development, the hardware or software that

support the proposed system need to be acquired and installed in the organization.

In this project, the in-house software development is selected. The proposed

system will be acquired and installed the new hardware and software in the

organization, but some of existing environment hardware and software is used as

the shared instance in order to be centralization controls such as Internet Web

Server which is used entire the organization.

2) Coding

Coding is the process of developing the proposed system to the organization

according to functional specification designs. The final output is followed by the

technical specification design which must meet the users' requirements.

3) Testing

Testing IS conducted to ensure that the proposed system IS working

properly. Various steps are used for fulfilling this objective.

53

4) System Conversion

System conversion is the process of converting the existing data into the

proposed system. The conversion plan is set up step by step. The conversion

technique is applied according to their purposes.

5) Documentation and Training

Documentation and training is the process of creating the functional and

technical manual and aiming for training the proposed system to users who will

operate the business process of the proposed system. The objective of training is

to have more understanding and be familiar with the proposed system.

4.2 Coding

After the functional specification design, developers have to create the

instructions for the proposed system which are followed by technical design

specifications. The proposed program is developed by Visual Basic .NET development

tool, and then the technical document will be delivered when the developed program has

been coded.

4.3 Testing

There are three types for testing the proposed system in order to verify that it is

ready to be used in the production environment. The test script will be prepared

following the functional specification and the business process flows.

1) Unit Test

Development teams will perform the unit test in the development instance in

order to ensure that each module of the developed program works correctly.

Tester focuses on whether the class meets the requirements stated in the

specifications. The test plan sources are CRC Cards, Class diagrams, Contracts

and Method Specification.

54

2) Integration Test

This test includes the user interface function testing, use case testing,

interaction testing which is used when the system performs data processing, and

system interface testing which proves that other system interface can integrate

together such as the proposed system must play the content files which are stored

at the content server. The test plan sources are Class diagram, Sequence diagram,

Communication diagram and Use case diagram.

3) User Acceptance Test (UAT)

UAT is done primarily by the users with support from the project team. This

testing is to confirm that the system is complete, meets the business needs that

prompted the system to be developed, and is acceptable to the users.

4.4 System Conversion

This step is to convert the data from the existing system to the proposed system.

Data conversion is usually the most technically complicated step in the migration plan.

Often, separate programs must be written to convert the data from the existing system to

the new formats required in the proposed system and store it in the proposed system

files and databases. Direct conversion style is used in order to convert the existing data

into the proposed system immediately. Although, this style is high risks, but it is

suitable for the application because training data have been created periodically which

can cut over the data easily. Also, direct cutover cost is less than parallel conversion,

and the time is the fastest.

4.5 Documentation and Training

Documentation will be produced after the proposed system is fully tested and all

errors are fixed. This includes the technical and user manual of the proposed system.

The user manual will explain users how to use the application correctly while technical

55

manual will be used by developers or technical administrators to refer to the details of

the proposed system in technical terms.

Training will be provided to train the training administrators and employees who

are the first pilot group of the organization, and the remaining employee will be trained

when they request to the training division. Classroom training is the way to deliver

training in which many users are trained at the same time by the same instructor.

56

V. CONCLUSIONS AND RECOMMENDATIONS

5.1 Conclusions

This project studies the problems of the existing system. Problems occur because

of an inefficient manual system of training management which is not fully utilizing

business management to its best use. The proposed system will help in increasing of

competitive training management strategies, and reduce the operating time of course

enrollment and tracking emollment information, training expenses, and increases the

training hours of employees.

The proposed system has been developed to replace the existing one. The

proposed system development and operational costs is 7,987,340.50 baht for 5 years

while the proposed system can generate all benefits 20,092,342.55 baht for 5 years. The

return on investment that the organization will receive in future for the money it spends

is 152 percent with the net present value of 12,105,002.05 baht. The break-even point in

which the benefits are larger than the costs is approximately 1 year 5 months. All of

these indicators indicate that this project is worth the investment.

Table 5.1. Degree of achievement of proposed system

Process Existing System Proposed System

Create Course (per course) 1 hour 30 minutes 30 minutes

Emollment Course (per course) 24 hours 8 hours

Approve Course (per person) 30 minutes 5 minutes

Training Duration (per course) 60 hours 40 hours

Data Verification (per report) 45 minutes 15 minutes

Create Report (per report) 1 hours 10 minutes

57

Table 5.1. Degree of achievement of proposed system (Continued)

I Total I 87 hours 45 minutes I 49 hours

From the Table 5 .1 Degree of achievement of the proposed system, it is obvious

that the response time of the proposed system will be much faster than the existing

system.

5.2 Recommendations

Training Management System is a part of human resources management which

plays an important role in operating the core business. Most organizations may gain a

competitive advantage if they apply the information system to their organization

properly. Besides, implementation of the proposed system can help the organization to

improve the business processes and reduce the training operating costs in order to gain

the competitive advantage over other businesses. After implementation of the proposed

system, all information will be kept in the same place so the proposed system can

provide the valuable information to all levels of training staffs in the organization

according to several purposes.

In the future, this system should extend the scope to cover all training business

processes needed, and integrate to core human resources management system and other

systems. For example, the application should be modified to support creating and

managing finance headers and lines in order to integrate to financial system. Second,

resource booking for each class needs the booking form in the application in order to

request to central administration division. Moreover, the application should be modified

to integrate employee competency in core HR after employees complete the course. The

proposed future work can be done to improve the performance and efficiency of the

proposed system to cover the business operations of the company.

58

APPENDIX A

USE CASE DESCRIPTION

Table A.1. Create Course Use Case Description

Use Case Name: Create Course I ID: l I Importance Level: High

Primary Actor: Training Administrator Use Case Type: Detail, essential

Stakeholders and Interests:

Training Administrator - wants to create courses information

HR Client Service Division - get training course requirements

Client Units - request for training courses

Program Development- develop new program regarding the requirement

HR Group Head - wants to review about training program and budget

Brief Description: This use case describes how to create courses.

Trigger: Training Administrator have a new training course which is required.

Type: External

Relationships:

Association: Training Administrator

Include:

Extend:

Generalization:

Normal Flow of Events:

I. Client Units contact HR Client Service Division when they want to request

training course or Program Development develop new training program.

2. After group head approved, Program Development identify course outlines.

3. Training Administrator create course information to the system.

Subflows:

Alternate/Exceptional Flows:

59

Table A.2. Create Offering Use Case Description

Use Case Name: Create Offering I ID: 2 I Importance Level: High

Primary Actor: Training Administrator I Use Case Type: Detail, essential


Training Administrator - wants to define delivery mode and links to learning objects for online

courses

Brief Description: This use case describes how a course is delivered: synchronous or

asynchronous, online or offline as well as what are the learning objects for online courses.

Trigger: Training Administrator have already created courses and need to specify instances of

courses.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator selects courses that they want to create offerings. It should

be at the second level in the catalog hierarchy.

2. Training Administrator selects delivery modes.

If the delivery mode is e-Learning (online),

Training Administrator needs to execute the create learning object use case

before putting learning objects information, or else execute the create class

use case.

3. Training Administrator provides offering information to the system.

Subflows:


60

Table A.3. Create Class Use Case Description

Use Case Name: Create Class l ID: J. Importance Level: High

I Primary Actor: Training Administrator I Use Case Type: Detail, essential


Training Administrator - wants to define objects that learners enroll in and attend

Brief Description: This use case describes how to define schedule dates, times,

locations, and enrollment designation. Also, classes are further broken down to sessions

to specify different times and locations.

Trigger: Training Administrator have already created offerings and need to specify

instances of offerings.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator selects offerings that they want to create classes. It

should be at the third level and final level in the catalog hierarchy.

2. Training Administrator provides classes information to the system.

Subflows:


61

Table A.4. Create Leaming Object Use Case Description

Use Case Name: Create Leaming Object l ID: 1: l Importance Level: High



Training Administrator- wants to attach learning objects to online classes

Brief Description: This use case describes how to associate the learning object with

the physical content files that are located on content server.

Trigger: Training Administrator want to create offerings with online delivery mode.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator ensures that the physical content is available.

2. Training Administrator identifies required and optional fields.

3. Training Administrator put the Starting URL to specify the complete path

name of the content file.

Subflows:


62

Table A.5. Add Enrollment Use Case Description

Use Case Name: Add Enrollment J ID:~ J Importance Level: High

Primary Actor: Training Administrator J Use Case Type: Detail, essential


Training Administrator - wants to enroll learners to the class

Brief Description: This use case describes how to enroll learners with single

enrollment to classes which are not allowed self enrollment.

Trigger: Training Administrator receives a list of names from HR Client Service.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator ensures that class status is not Planned, the S-1:

check class status subflow is performed.

2. Training Administrator searches class information in order to add learners to

the class, and selects Enrolled status in enrollment status field.

3. After the enrollment, the system will create enrollment transactions as well

as the S-2: notify learner, the S-3: notify manager are performed.

Subflows:

S-1: Check Class Status

1. Training Administrator checks the class information, if status is

Planned then update the class status to Normal.

S-2: Notify Learner

1. The system will create notificatio:q transaction to inform learner whom

is enrolled in the class via Learner Self-Service.

2. Notification status will be Requested.

S-3: Notify Manager

1. The system will send requested notification to direct manager in order

to request enrollment approval via Manager Self-Service.


63

Table A.6. Enroll Class Use Case Description

Use Case Name: Enroll Class I ID: 2 I Importance Level: High

Primary Actor: Learner I Use Case Type: Detail, essential


Leamer - wants to enroll the class from Learner Self-Service

Training Administrator - manage class status in order that learner can enroll the class

Brief Description: This use case describes how to use self enrollment option from Leamer

Self-Service in order to request the enrollment.

Trigger: Leamer is interested in classes and want to request for enrollments approval.

Type: External

Relationships:

Association: Learner

Include:

Extend:

Generalization:


1. Training Administrator ensures that class status is not Planned, the S-1: check clas5

status subflow is performed.

2. Leamer logs on to Learner Self-Service and execute the Browse Class use case,

class enrollment lists will be shown for making enrollments.

3. After the enrollment, the system will create enrollment transactions as well as the

S-2: notify learner, the S-3: notify manager are performed.

Subflows:

S-1: Check Class Status

1. Training Administrator checks the class information, if status is

Planned then update the class status to Normal.

S-2: Notify Learner

1. The system will create notification transaction to inform learner whom is

enrolled in the class via Learner Self-Service.

2. Notification status will be Requested.

S-3: Notify Manager

1. The system will send requested notification to direct manager in order to

request enrollment approval via Manager Self-Service.


64

Table A.7. Approve Course Use Case Description

Use Case Name: Approve Course I ID: 1 I Importance Level: High

Primary Actor: Manager ) Use Case Type: Detail, essential


Manager - wants to approve the requested course

Brief Description: This use case describes how manager take approval actions from

Manager Self-Service in order to response the requested course.

Trigger: Manager receives the request course notification.

Type: External

Relationships:

Association: Manager

Include:

Extend:

Generalization:


1. Manager logs on to Manager Self-Service, the work lists will be shown with

notification details then take the Approved or Rejected action.

2. The system process; the S-1: update status and the S-2: notify learner

subflow is performed.

Subflows:

S-1: Update Status

1. The system will update the enrollment and notification status after

manager has taken actions.

S-2: Notify Leamer

1. The system will notify the course approval results to learner again via

Leamer Self-Service.


65

Table A.8. Attend Class Use Case Description

Use Case Name: Attend Class 'ID:~ I Importance Level: High

Primary Actor: Leamer j Use Case Type: Detail, essential


Leamer - wants to attend the class

Brief Description: This use case describes how to launch online offerings in the

player, whereas offline offerings are not launched within the application.

Trigger: Leamer is approved after learner enroll in the class.

Type: External

Relationships:

Association: Leamer

Include:

Extend:

Generalization:


1. Leamer logs on to Leamer Self-Service which can see the attendance lists

then learner will launch online classes in the player.

Subflows:


66

Table A.9. Browse Class Use Case Description

Use Case Name: Browse Class 'ID: 2 I Importance Level: High

Primary Actor: Leamer I Use Case Type: Detail, essential


Leamer - wants to see the enable classes that are self enrollment

Brief Description: This use case describes how to find the class that are self

enrollment.

Trigger: Leamer want to enroll the class.

Type: External

Relationships:

Association: Leamer

Include:

Extend:

Generalization:


1. Leamer logs on to Leamer Self-Service which can browse the class

enrollment lists.

Subflows:


67

Table A.10. Track Enrollment Use Case Description

Use Case Name: Track Enrollment 'ID: 10 I Importance Level: High

Primary Actor: Training Administrator Use Case Type: Detail, essential


Training Administrator - wants to see the enrollment transaction

Brief Description: This use case describes how to track the enrollment transaction.

Trigger: Training Administrator want to look up enrollment information.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator opens the enrollments and subscriptions menu.

2. Training Administrator puts the criteria such as class name, enrollment

status and so on ..

Subflows:


68

Table A.11. Search Course Use Case Description

Use Case Name: Search Course IID: 11 I Importance Level: High



Training Administrator - wants to search catalog information

Brief Description: This use case describes how to see the catalog hierarchy.

Trigger: Training Administrator want to display the specific catalog hierarchy.

Type: External

Relationships:


Include:

Extend:

Generalization:


1. Training Administrator opens catalog menu.

2. Training Administrator selects the level of hierarchy with the criteria word,

the result will be shown.

Subflows:


69

APPENDIX B

DATA DICTIONARY

Table B.1. Data Dictionary of Proposed system

Field Name Meaning

course code Course code

course name Course name

description Description information

start date Effective start date

end date Effective end date

offering_ id Offering identification definition

offering_ name Offering name

dm id Delivery mode identification definition

dm name Delivery mode name -

dm online Delivery mode online channel flag -

dm _synchronous Delivery mode synchronous type flag

obj_ id Leaming object identification definition

obj_ name Leaming object name

author Leaming object author

catalog Leaming object group

catalog_ number Catalog number of learning object

vers10n Leaming object version

content_ type Content access type; Content Server Access, URL Access

server name Content server name

server_ directory The server directory where store contents

initial file Content file name

starting_ url Uniform Resource Locator where content file store

70

Table B.1. Data Dictionary of Proposed system (Continued)

Field Name Meaning

class id Class identification definition

title Class title name

training_ center Training center name

location Classroom location

status Action status

start time Class effective start time -

end time Class effective end time -

duration Class duration number

unit Unit of measurement in class duration

enrollment start date Enrollment effective start date -

enrollment end date Enrollment effective end date -

min attendees Class minimum attendees -

max attendees Class maximum attendees -

self enrollment The enrollment type -

enrollment id Enrollment identification definition

enrollment date Date of enrollment

completion_ date Date of enrollment completion

notification id Notification identification definition

message_name Subject for the notification

action_ type Notification action type; approved, rejected

from id Employee ID of sender -

creation date Notification creation date -

71

Table B.l. Data Dictionary of Proposed system (Continued)

Field Name Meaning

due date Notification due date -

employee _id Employee identification definition

firstname Employee first name

lastname Employee last name

address Employee address

email Employee email

phone_ number Employee phone number

hire date Employee hire date -

salary Employee salary amount

job Job name

person_ type Person type

manager_id Manager identification definition

org_code Organization code

org_name Organization name

org_type Organization type

date from Organization effective start date -

date to Organization effective end date -

user id User ID -

user name User name -

user _password User password

last_ update_ date Date of last update the record

last_ logon _date Date of last logon to the system

72

Table B.1. Data Dictionary of Proposed system (Continued)

Field Name Meaning

resp_id Responsibility identification definition

resp_name Responsibility name

menu id Menu identification definition -

menu name Menu name -

page_name Page name of web page

73

APPENDIX C

CLASS-RESPONSIBILITY-COLLABORATION CARDS (CRC CARDS)

Table C. l. Course Class CRC Card

Front:

Class Name: Course IID: 1 Type: Concrete

Description: A training program that is used for skill Associated Use Case: 2

developments

Responsibilities Collaborators

Offering

Back:

Attributes:

course code end date

course name

description

start date

Relationships:

Generalization (a kind of):

Aggregation (has parts): Offering

Other Associations:

74

Table C.2. Offering Class CRC Card

Front:

Class Name: Offering IID: 2 Type: Concrete

Description: Specific instances of course that provides Associated Use Case: 3, 4, 5

more details about the delivery of the learning, as well

as, in the case of online course, linking to learning

objects


Delivery Mode

Leaming Object

Class

Back:

Attributes:

offering id

offering name

start date

end date

Relationships:


Aggregation (has parts): Delivery Mode

Leaming Object

Class

Other Associations:

-

75

Table C.3. Delivery Mode Class CRC Card

Front:

Class Name: Delivery Mode I ID: 3 Type: Concrete

Description: A mode of training delivery Associated Use Case: 2


Offering

Back:

Attributes:

dm id

dm name

dm online

dm synchronous

Relationships:


Aggregation (has parts):

Other Associations:

76

Table C.4. Leaming Object Class CRC Card

Front:

Class Name: Learning Object IID: 4 Type: Concrete

Description: The physical learning object address stored Associated Use Case: 2

on content server


loadContent Offering

Back:

Attributes:

obj id version

obj name content type

description server name

author server directory

catalog initial file

catalog number starting url

Relationships:



Other Associations:

77

Table C.5. Class Class CRC Card

Front:

Class Name: Class IID: 5 Type: Concrete

Description: A specific occurrence of an offering which Associated Use Case: 2, 6

identify different schedules and locations, also be related

to enrollments


updateStatus Offering

Enrollment

Back:

Attributes:

class id end time

title duration

training center unit

location enrollment start date

status enrollment end date

start date min attendees

end date max attendees

start time self enrollment

Relationships:



Other Associations: Enrollment

78

Table C.6. Enrollment Class CRC Card

Front:

Class Name: Enrollment llD: 6 Type: Concrete

Description: A process of training registration which Associated Use Case: 5, 7, 8

could be raised by learner or training administrator


updateStatus Class

sendNotification Notification

Employee

Back:

Attributes:

enrollment id

enrollment date

status

com12letion date

Relationships:



Other Associations: Class

Notification

Em12loyee

79

Table C.7. Notification Class CRC Card

Front:

Class Name: Notification 'ID: 7 Type: Concrete

Description: The message that will notify to learner and Associated Use Case: 6

manager in enrollment processes


updateActionType Enrollment

updateStatus

Back:

Attributes:

notification id action type

employee id from id

message name creation date

status due date

Relationships:




80

Table C.8. Employee Class CRC Card

Front:

Class Name: Employee I ID: 8 Type: Abstract

Description: An Individual that need to participate the Associated Use Case: 6, 9,

training 10,11,12


enroll Class Enrollment

receiveNotification Users

attend Class Organization

Training Administrator

Manager

[Back:

Attributes:

employee id hire date

firstname salary

Iastname iob

address person type

email manager id

phone number .

Relationships:




Users

Organization

81

Table C.9. Training Administrator Class CRC Card

Front:

Class Name: Training Administrator IID: 9 Type: Concrete

Description: An Individual who maintain the Training Associated Use Case: 8

Management System (TMS) and training tasks


addEnrollment

submitRe12ort

Back:

Attributes:

Relationships:

Generalization (a kind of): Em12loyee


Other Associations:

82

Table C.10. Manager Class CRC Card

Front:

Class Name: Manager IID: 10 Type: Concrete

Description: An Individual that need to response the Associated Use Case: 8

irequest notification course from direct subordinate


receiveNotification

armroveCourse

Back:

Attributes:

Relationships:

Generalization (a kind of): Employee

Aggregation (has parts): -~

Other Associations:

83

Table C.11. Organization Class CRC Card

Front:

Class Name: Organization I ID: 11 Type: Concrete

Description: An organization unit at Siam Commercial Associated Use Case: 8

Bank business group only


Em12loyee

Back:

Attributes:

org code date to

org name

org tme

date from

Relationships:



Other Associations: Em12loyee

84

Table C.12. Users Class CRC Card

Front:

Class Name: Users I ID: 12 Type: Concrete

Description: An Individual name that will be used to log Associated Use Case: 8, 13

on the system


Employee

Responsibility

Back:

Attributes:

user id last update date

user name last logon date

user password

creation date

Relationships:



Other Associations: Employee

Responsibility

85

Table C.13. Responsibility Class CRC Card

Front:

Class Name: Responsibility I ID: 13 Type: Concrete

Description: A group of operation roles Associated Use Case: 12, 14


Users

Menu

Back:

Attributes:

resp id

resp name

creation date

last update date

Relationships:



Other Associations: Users

Menu

86

Table C.14. Menu Class CRC Card

Front:

Class Name: Menu 'ID: 14 Type: Concrete

Description: A screen page that depends on the Associated Use Case: 13

responsibility access


Res2onsibility .,

!Back:

Attributes:

menu id last u2date date

menu name

page name

creation date

Relationships:



Other Associations: ResQonsibility

87

APPENDIX D

SEQUENCE DIAGRAM

An Actor: - is a person or system that derives benefit from and is external to the system

- Are placed across the top of the diagram - Participates in a sequence by sending and/or receiving messages

An Object: - Participates in a sequence by sending and/or receiving messages

- Are placed across the top of the diagram

A Lifeline: - Denotes the life of an object during a sequence - Contains an "X" at the point at which the class no longer interacts

An Execution Occurrence: - Is a long narrow rectangle placed atop a lifeline - Denotes when an object is sending or receiving messages

A Message: - Conveys information from one object to another one

- An operation call is labeled with the message being sent and a solid arrow, while a return is labeled with the value being returned and shown as a dashed arrow

anActor

anObject : aClass

aMessage() . Return Value-...,.. ________ _

Figure D. l. Element of Sequence Diagram

88


CreateCourse() aCourse:Course

Figure D.2. Sequence Diagram for Create Course Use Case

89

Courses:List Delivery Modes:List Leaming Objects:List


LookUpCourseO I

SelectDeliveryModeO I [Online Mode] SelectL eamingObjectO

CreateOfferingO

anOffering:Offering

I I

Figure D.3. Sequence Diagram for Create Offering Use Case

90

Offerings:List


....... ,....._

LookUpOffering() .... -

' ! CreateClass() i

I I - aClass:Class I

I ~

I I I

! I

!

Figure D.4. Sequence Diagram for Create Class Use Case

91


CreateLeamingObject() 1--------------1::.- aLeamingObject:LeamingObject

T i

j

Figure D.5. Sequence Diagram for Create Leaming Object Use Case

92

\0

w

A

Cla

sses

:Lis

t E

mpl

oyee

s:L

ist

AA

Tra

inin

g A

dmin

istr

ator

L

eam

er M

anag

er

~

Sel

ectC

lass

()

~

Sel

ectE

mpl

oyee

()

~

Cre

ateE

nrol

lmen

t()

~

anE

nrol

lmen

t:E

nrol

lmen

t

: ...L

Cre

ateN

otif

ic ca

tion

()

aNot

ific

atio

n :N

otif

icat

ion

-;- i : I

i N

otif

y()

: -

!

....,.

I

Not

ify(

) .

1

Fig

ure

D.6

. S

eque

nce

Dia

gram

for

Add

Enr

ollm

ent U

se C

ase

Classes:List

Leamer Manager

SelectClassO ;-

Enroll() . anEnrollment:Enrollment

I ,..L CreateNotificationO

. aNoti fication: Notification

i l

Notify() ~

Notify() f I

I ., I ! I I

Figure D.7. Sequence Diagram for Enroll Class Use Case

94

Notifications :List Enrollments:List

Manager Leamer

-'- ,..'- ' ! ReceiveNotification() l -

! I -

[Approved or Rejected] l

UpdateStatus() - ! - l [Approved or Rejected] UpdateStatusO --

_L

' Notify()

' -!

-T ! ! T ...,_ ! l

Figure D.8. Sequence Diagram for Approve Course Use Case

95

Attendances :List

Leamer

Attend Class()

Figure D.9. Sequence Diagram for Attend Class Use Case

96

Classes:List

Learner

LookUpClass()

Figure D.10. Sequence Diagram for Browse Class Use Case

97

Enrollments:List


LookUpEnrollment()

Figure D.11. Sequence Diagram for Track Enrollment Use Case

98

Courses:List Offerings:List Leaming Objects:List Classes:List


[Course criteria] ,... ,..!. i I LookUpCourseO

[Offering criteria] I i

I

,..!.

I LookUpOffering0 I ~

i !

[Leaming Object criteria] LtjokUpLeamingObject()1 J.

i I l [Class criteria] LookUpCJfiss()

- I I I -

Figure D.12. Sequence Diagram for Search Course Use Case

99

APPENDIX E

COMMUNICATION DIAGRAM

An Actor: - ~

- is a person or system that derives benefit from and is external to the system

- Participates in a collaboration by sending and/or receiving messages

anActor

An Object: - Participates in a collaboration by sending

anObject : aClass and/or receiving messages

- Are placed across the top of the diagram

An Association: - Shows an association between actors and/or

objects - Messages are sent over associations

An Execution Occurrence: - Conveys information from one object to another

one 1: a Message(~ - Direction is shown using an arrowhead - Sequence is shown by a sequence number

Figure E. l. Element of Communication Diagram

100

1: CreateCourse(~ aCourse:Course -


Figure E.2. Communication Diagram for Create Course Use Case

Courses:List 1: LookUpCourse(~

2: SelectDeliveryModeO-.. Delivery Modes:List

3: [Online Mode] SelectLeamingObject(~ Leaming Objects:List

4: CreateOffering(~

Training Administrator anOffering:Offering

Figure E.3. Communication Diagram for Create Offering Use Case

101

1: LookUpOffering(~ Offerings:List -

2: CreateClass(~

~1~~~a_c_1a_s_s_:c_1_as_s~----' Training Administrator

Figure E.4. Communication Diagram for Create Class Use Case

1: CreateLearningObject(~ aLearningObject:LearningObject


Figure E.5. Communication Diagram for Create Leaming Object Use Case

102

I: SelectClass~

-f 2: SelectEmployeeO---

A 3: CreateEnrollmentO---


5:Noti ~ Classes: List

Employees: List

anEnrollment:Enrollment

Figure E.6. Communication Diagram for Add Enrollment Use Case

I: SelectClassO---- Classes:List

2:Enroll~ anEnrollment:Enrollment

-s:NotifyO

Leamer

Figure E.7. Communication Diagram for Enroll Class Use Case

103

Leamer

3: [Approved or Rejected) UpdateStatus~ Enrollments: List

-1: ReceiveNotificationO ~ Notifications: List 4:Notify(~

2: [Approved or Rejected) UpdateStatus~

Leamer Manager

Figure E.8. Communication Diagram for Approve Course Use Case

1: [Course criteria] LookUpCourse()--+ Courses:List

2: (Offering criteria] LookUpOffering()~ Offerings:List

3: (Leaming Object criteria] LookUpLearningObject()--+ L . ob· L. earning ~ects: 1st

4: [Class criteria]LookUpCJass() ~

Training Administrator Classes:List

Figure E.9. Communication Diagram for Search Course Use Case

104

1: Attend Class(~ Attendances:List

Leamer

Figure E.10. Communication Diagram for Attend Class Use Case

1: LookUpClass(~ Classes:List

Leamer

Figure E.11. Communication Diagram for Browse Class Use Case

1: LookUpEnrollment(~ Enrollments:List


Figure E.12. Communication Diagram for Track Enrollment Use Case

105

APPENDIX F

DATABASE TABLES

......

0 O'I

Tab

le F

.l.

Cou

rse

Tab

le

Att

ribu

te N

ame

Dat

a T

ype

cour

se_ c

ode

(PK

) T

ext

cour

se n

ame

Tex

t

desc

ript

ion

Tex

t

star

t da

te

Dat

e

end

date

D

ate

Tab

le F

.2.

Del

iver

y M

ode

Tab

le

Att

ribu

te N

ame

Dat

a T

ype

dm_i

d (P

K)

Num

ber

dm

nam

e T

ext

dm o

nlin

e B

oole

an

dm _s

ynch

rono

us

Boo

lean

Len

gth

D

efau

lt V

alu

e

15

Uni

que

ID

280

Non

e

280

Non

e

Cur

rent

Dat

e

Non

e

Len

gth

D

efau

lt V

alu

e

Uni

que

ID

280

Non

e

Non

e

Non

e

runi

qut:

Nu

ll

Key

Typ

e F

orei

gn t

o T

able

y N

P

rim

ary

Key

O

ffer

ing

N

N

Att

ribu

te

N

y A

ttri

bute

N

N

Att

ribu

te

N

y A

ttri

bute

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

y N

P

rim

ary

Key

O

ffer

ing

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

Att

ribu

te

Tab

le F

.3.

Lea

min

g O

bjec

t Tab

le

Att

ribu

te N

ame

Dat

a T

ype

Len

gth

Def

ault

Val

ue

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

obj_

id (

PK

) N

umbe

r U

niqu

e ID

y

N

Pri

mar

y K

ey

Off

erin

g

obj_

nam

e T

ext

280

Non

e N

N

A

ttri

bute

desc

ript

ion

Tex

t 28

0 N

one

N

y A

ttri

bute

auth

or

Tex

t 28

0 N

one

N

y A

ttri

bute

-0 ca

talo

g T

ext

280

Non

e N

y

Att

ribu

te

-...

)

cata

log_

num

ber

Num

ber

Non

e N

y

Att

ribu

te

vers

10n

Num

ber

Non

e N

y

Att

ribu

te

cont

ent_

type

T

ext

80

Non

e N

y

Att

ribu

te

serv

er n

ame

Tex

t 80

N

one

N

y A

ttri

bute

serv

er_ d

irec

tory

T

ext

150

Non

e N

y

Att

ribu

te

init

ial

file

T

ext

150

Non

e N

y

Att

ribu

te

star

ting

_ url

T

ext

280

Non

e N

y

Att

ribu

te

.......

0 00

Tab

le F

.4.

Off

erin

g T

able

Att

rib

ute

Nam

e

offe

ring

_id

(PK

)

offe

ring

_ nam

e

star

t da

te

end

date

cour

se_ c

ode

(FK

)

dm_i

d (F

K)

obj_

id (

FK)

Dat

a T

yp

e

Num

ber

Tex

t

Dat

e

Dat

e

Tex

t

Num

ber

Num

ber

Len

gth

Def

ault

Val

ue

Uni

que

ID

280

Non

e

Cur

rent

Dat

e

Non

e

15

Non

e

Non

e

Non

e

Uni

que

Nul

l K

ey T

yp

e F

orei

gn t

o T

able

y N

P

rim

ary

Key

C

lass

N

N

Att

ribu

te

N

N

Att

ribu

te

N

y A

ttri

bute

N

N

For

eign

Key

N

y F

orei

gn K

ey

N

y F

orei

gn K

ey

.......

0 \0

Tab

le F

.5.

Cla

ss T

able

Att

ribu

te N

ame

clas

s _id

(PK

)

titl

e

trai

ning

_ cen

ter

loca

tion

stat

us

star

t da

te

end

date

star

t ti

me

end

tim

e

dura

tion

unit

enro

llm

ent

star

t da

te

--

enro

llm

ent

end

date

min

att

ende

es

max

att

ende

es

self

enr

ollm

ent

offe

ring

_id

(FK

)

Dat

a T

ype

Len

gth

Num

ber

Tex

t 28

0

Tex

t 15

0

Tex

t 15

0

Tex

t 20

Dat

e

Dat

e

Dat

e/T

ime

Dat

e/T

ime

Num

ber

Tex

t 20

Dat

e

Dat

e

Num

ber

Num

ber

Boo

lean

Num

ber

Def

ault

Val

ue

Uni

qm:

Nu

ll

Key

Typ

e F

orei

gn t

o T

able

Uni

que

ID

y N

P

rim

ary

Key

E

nrol

lmen

t

Non

e N

N

A

ttri

bute

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Nor

mal

N

N

A

ttri

bute

Non

e N

N

A

ttri

bute

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Cur

rent

Dat

e N

N

A

ttri

bute

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Fal

se

N

N

Att

ribu

te

Non

e N

N

F

orei

gn K

ey

Tab

le F

.6.

Not

ific

atio

n T

able

Att

rib

ute

Nam

e D

ata

Typ

e L

engt

h

Def

ault

Val

ue

Uni

que

Nu

ll

Key

Typ

e F

orei

gn t

o T

able

noti

fica

tion

_id

(PK

) N

umbe

r U

niqu

e ID

y

N

Pri

mar

y K

ey

empl

oyee

_ _id

N

umbe

r N

one

N

N

For

eign

Key

mes

sage

_ nam

e T

ext

300

Non

e N

N

A

ttri

bute

stat

us

Tex

t 30

O

pen

Not

ific

atio

n N

N

A

ttri

bute

- -ac

tion

_typ

e T

ext

20

Non

e N

N

A

ttri

bute

0

from

id

N

umbe

r N

one

N

N

Att

ribu

te

crea

tion

dat

e D

ate

Cur

rent

Dat

e N

N

A

ttri

bute

due

date

D

ate

Enr

ollm

ent E

nd D

ate

N

N

Att

ribu

te

enro

llm

ent_

id (

FK)

Num

ber

Non

e N

N

F

orei

gn K

ey

........

........

........

Tab

le F

.7.

Enr

ollm

ent T

able

Att

ribu

te N

ame

Dat

a T

ype

enro

llm

ent_

id (

PK

) N

umbe

r

enro

llm

ent

date

D

ate

stat

us

Tex

t

com

plet

ion_

date

D

ate

clas

s id

(FK

) N

umbe

r

empl

oyee

_id

(FK

) N

umbe

r

Len

gth

Def

ault

Val

ue

Uni

que

ID

Cur

rent

Dat

e

20

Non

e

Non

e

Non

e

Non

e

:Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

y N

P

rim

ary

Key

N

otif

icat

ion

N

N

Att

ribu

te

N

N

Att

ribu

te

N

y A

ttri

bute

N

N

For

eign

Key

N

N

For

eign

Key

.......

.......

N

Tab

le F

.8.

Em

ploy

ee T

able

Att

rib

ute

Nam

e D

ata

Ty

pe

empl

oyee

_id

(PK

) N

umbe

r

firs

tnam

e T

ext

last

nam

e T

ext

addr

ess

Tex

t

emai

l T

ext

phon

e_ nu

mbe

r T

ext

hire

dat

e D

ate

sala

ry

Num

ber

job

Tex

t

pers

on_ t

ype

Tex

t

man

ager

_id

(FK

) N

umbe

r

org_

code

(FK

) T

ext

Len

gth

D

efau

lt V

alue

Uni

que

ID

280

Non

e

280

Non

e

280

Non

e

280

Non

e

Non

e

Cur

rent

Dat

e

Non

e

150

Non

e

80

Non

e

Non

e

10

Non

e

Uni

qut=

N

ull

Key

Ty

pe

Fo

reig

n t

o T

able

y N

P

rim

ary

Key

E

nrol

lmen

t, U

sers

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y A

ttri

bute

N

y F

orei

gn K

ey

N

y F

orei

gn K

ey

-........ w

Tab

le F

.9.

Org

aniz

atio

n T

able

Att

ribu

te N

ame

Dat

a T

ype

org_

code

(P

K)

Tex

t

org_

nam

e T

ext

org_

type

T

ext

date

fro

m

Dat

e

date

to

Dat

e

Len

gth

10

280

80

Def

ault

Val

ue

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

Uni

que

ID

y N

P

rim

ary

Key

E

mpl

oyee

Non

e N

y

Att

ribu

te

Non

e N

y

Att

ribu

te

Cur

rent

Dat

e N

N

A

ttri

bute

Non

e N

y

Att

ribu

te

........

........ ~

Tab

le F

.10.

U

sers

Tab

le

Att

ribu

te N

ame

user

_id

(PK

)

user

nam

e

user

_pas

swor

d

crea

tion

dat

e

last

_ upd

ate_

date

last

_ log

on _d

ate

empl

oyee

_id

(FK

)

Dat

a T

ype

Num

ber

Tex

t

Tex

t

Dat

e

Dat

e

Dat

e

Num

ber

Len

gth

D

efau

lt V

alue

Uni

que

ID

15

Non

e

150

Non

e

Cur

rent

Dat

e

Non

e

Non

e

Non

e

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

y N

P

rim

ary

Key

U

sers

_Res

p

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

For

eign

Key

.......

.......

Vl

Tab

le F

.11.

R

espo

nsib

ilit

y T

able

Att

ribu

te N

ame

Dat

a T

ype

resp

_id

(PK

) N

umbe

r

resp

_nam

e T

ext

crea

tion

dat

e D

ate

last

_ upd

ate_

date

D

ate

Tab

le F

.12.

U

sers

_Res

p T

able

Att

ribu

te N

ame

Dat

a T

ype

user

_id

(PK

) (F

K)

Num

ber

resp

_id

(PK

) (F

K)

Num

ber

Len

gth

Def

ault

Val

ue

Uni

que

ID

280

Non

e

Cur

rent

Dat

e

Non

e

Len

gth

Def

ault

Val

ue

Non

e

Non

e

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

y N

P

rim

ary

Key

U

sers

_Res

p

N

N

Att

ribu

te

N

N

Att

ribu

te

N

N

Att

ribu

te

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

y N

P

rim

ary

Key

, For

eign

Key

y N

P

rim

ary

Key

, F

orei

gn K

ey

.......

.......

0\

Tab

le F

.13.

M

enu

Tab

le

Att

rib

ute

Nam

e D

ata

Ty

pe

men

u_id

(PK

) N

umbe

r

men

u na

me

Tex

t

page

_nam

e T

ext

crea

tion

dat

e D

ate

last

_ upd

ate_

date

D

ate

Tab

le F

.14.

R

esp_

Men

u T

able

Att

rib

ute

Nam

e D

ata

Typ

e

resp

_id

(PK

) (F

K)

Num

ber

men

u _id

(PK

) (F

K)

Num

ber

Len

gth

280

280

Len

gth

Def

ault

Val

ue

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

Uni

que

ID

y N

P

rim

ary

Key

R

esp_

Men

u

Non

e N

N

A

ttri

bute

Non

e N

N

A

ttri

bute

Cur

rent

Dat

e N

N

A

ttri

bute

Non

e N

N

A

ttri

bute

Def

ault

Val

ue

Uni

que

Nul

l K

ey T

ype

For

eign

to

Tab

le

Non

e y

N

Pri

mar

y K

ey,

For

eign

Key

Non

e y

N

Pri

mar

y K

ey, F

orei

gn K

ey

APPENDIX G

USER INTERFACE DESIGN


L()$;JiF1 Login Name

Password L~

Figure G. l. Login Form

117

su1mslnaw1ruHli $1AM COMMERCIAi. BANK Training Management System

Training Administrator Learner Self-Seryjce Manager Self-Servjce

Administrator

Course Administration Customer Enrollment Create Learning Object Submit Report

Learner

My Training Notification

Manager

Notification

Figure G.2. Main Menu Form

118

·~ isu,Fns1miw,rDm1 Training Management System ::::::::l:C.I SIAM COMMERCIAL BANK

Search I Course

Create I Cours.e

C ata.l()S.:t ..

W Commercial Loan Procedure Manual

r Jfl Loan Introduction ...

r i:t! Loan Procedu.re Manual-1

r Jf1 Commercial Loan Post-Test

Figure G.3. Catalog Form

119

su,ms1ntJw,rumI SIAM COMMERCIAL BANK

Create Course

General

•Course

Course Code

Description

• Start Date l2~c)u_n-2006 . ~ (>?>:.ample-: :iSL~h.m.2008)

End Date rm


Figure G.4. Create Course Form

120

~ su1mslnt:1w1rumi ~ SIAM COMMERCIAL- BANK Training Management System

Create Offering General

*Offering

' Learning Object

Course Commercial Loan Procedure Manual Course Start Dale 27.Jun-2006 Course End Dale

The offering start and end dales must fall within lhe course start and end dales.

*SlartDale [29:~~-":~.Q~ .. ~ End Date L_._____ ~ (e:cornple:29·jJn-XnJS)

Delivery Mode :

,Eleaming Self-Paced • No

.lnClass Scheduled Yes

lnClass Self-Paced No

Offline Self-Paced No

Figure G.5. Create Offering Form

121

~ su-m1slmmr1rum:i ~ SIAM COMMERCIAL BANK

g_re(lte Lea_rri.il'.1Jl 91'.>ie_ct__ General


*Identifier rj2500 _______ } ___ -_--_--_-----_----------------------------·---· _-------------------------

Content

*Name Description '!£1

Author

Catalog Catalog Number i------'--'--'--'-...;.;...;-'-'-"-

Version

Type I URL Access -- - _ }il __ _ Starting URL

Content Seiver I -~ Directory

Initial File

Figure G.6. Create Leaming Object Form

122

su,mslm:tw,rilua SfAM COMM&RCIAL BANK Training Management System

Create Class

General

Tille

Offering lnclass Commercial Loan Lab Offering Start Date 29.Jun-2006 Offering End Date

Training Center I_ fil Location ~L-.. -------:±:1~ .. *Status I Normal fil

Schedule

"Start Date I.. Start Time ,..,---

Duration

Enrollment

~ (E".>:fiffiple 29-JIJn-2006)

( E:.:.3mp!e 17:00)

J iJ·· .. ·.•. .~

End Date I_ . . ....... J ~ End Time (Example 17:00)

"Enrollment Start Date j29.Jun~2006 Enrollment End Date ,... . .. c .;} (e>ompl.o: 29-Jun-2008J

M in i mum A!tendees r--------- M ax i mum Attendees

r---------[1 Self Enrollment

Figure G.7. Create Class Form

123

~ su-imslm1w1rum:i ~ SIAM COMMERCIAL BANK Training Management System

Enrollments and Subscriptions Search

Class Name L .... ·······-···-·. Organization

Enrollment Number I._ Enrollment Status ,..., ---,.,,'.£]...,

Person Type fil @ (cteaiJ

r ·u1u 11fli'IUS~'iVltl u1fnt:f, Mr. Sakunprawit ,Navarax

Employee 'Analysts Unit,>AIM for iBRC I Business

· iRutchayothin i Flows 1 !

:u..;im w;,;i;~ ~~rn~ -/E;;:;pl~y;elciirporat;. ··[Coan :-rciu~1Jl'i, Miss ' I Sect cir 4 :Procedure jPornpen 1 1Manual-1 (!h:a.marutt,~:~~~n~ ! I

)u1J i'lfli'IY;_.m~- · · ·· l i::;;:;?i~;;;;Jst~ffing (liir.i"l Mrq· ,· ·.· .-.-.· !

Figure G.8.

1 - - __ \ ___ _

'Enrolled

Enrollments Form

124

isu1mslmiw1ruml SIAM COMMERCIAL BANK Training Management System

Add Enrollments

Search

Class Name

General

Course Name Commercial loan Procedure Manual

Course Code Offering Name loan Introduction Delivery Mode Elearning Self-Paced

Class Name Commercial loan Procedure Manual E-learning 54616

Class Status Normal Training Center

Enrollment Details

Enrollment Number 207001 Date Placed 30.Jun-2006

* Enrollment Status I ii{! Learner

"Learner I Test Simon, MR.

Figure G.9.

Class Start Date 27.Jun-2006 Class Start Time Class End Date Class End Time

Enrollment Start Date 27.Jun-2006 Enrollment End Date Minimum Attendees 0

Maximum Attendees 999999999

Add Enrollments Form

125

Search and Select: Learner

Search

To find your item, select a filter item in the pulldown list and enter a value in the text field, then select the "Go" button.

Search By l~~a.n1er ........ :BJ l~~lf\,1QNO!o . @

Results

(' Test Simon, MR.

(' TEST SIMON

Figure G.10. Select Leamer Form

126

Attendance

'Manual

Statutory ·compliance

l>U,ms1mmruilzn:i SIAM COMMERCIAL BANK

:1nCla~s is_che_du~ed __ _

Classes Enrollment


· Announcements

• You ha11e 3 new· notifications

• Class

Figure G.11. Learner Self-Service Fonn

127

r


You.have successfullyenrolle~in the da.s.s~om.rriercial Lo~n Procedure ManualE:Learning 54616.

Jest Simon Test Simon MR hascancelled an enrollment in_Commercial Loan Procedure Manual E·Le~rning 54616

• You h.avesucy.ssf.ully e_nrolle_d_i~the_d.ass_L.~ar!Pn;icedure wia_nual:1566_16.

Figure G.12. Notification Form

128

28-Jun-2006 i

l!IJ , - ;su1mslm1w1rum:i --- SIAM COMMERCIAL BANK

Details

From llfl«111Ja A~tt'lJ, Sakunkamol Pung bun

To llflilfi'i'>IJYl~A IJUH'i,, Sakunthammapong Monthira

Sent 30.Jun-2006 16:59:54 Due 30.Jun-2007 16:59:54

ID 1817006

Course Name Commercial Loan Procedure Manual

Course Code Offering Name Loan Introduction Delivery Mode Elearning Self-Paced

Class Name Commercial Loan Procedure Manual E-learning 54616

Class Status Normal Training Center


Class Start Date 27.Jun-2006 Class Start Time Class End Date Class End Time

Enrollment Start Date 27.Jun-2006 Enrollment End Date

Action jApprove

Figure G.13. Notification Message Form

129

f-m Microsoft Word

Figure G.14. Content Link Form

130

Figure G.15. Content Details Page

131

APPENDIX H

OUTPUT REPORTS


E11roH111e.rits an~Sll~~c_rip~~on~. Search

Class Name

Organization

Person Type

Enrollment Number

Enrollment Status

@D(CiW)

Select Enrollment: (u~~nro11) (oe1~~ef

--·-·~·l ~~·--·-·-- ~ . r ... ~:;-~ ~~~~~;~,;;,)· i Empl~y·;~[A;;~iy;ts u;i:)NMfo;-·- . '.u1foti, Mr. ; :BRC ; Business

·Enrolled

,Sakunprawit · :Rulchayothin Flows jNavarax , 1

·r:--~~Jn~~-~~~-;y s~1;,;··-tE;;,p1oy;:rCo-;;;~;;;-··iLoan ·~ --·-t 10WJ1·-

;foiunw!, Miss ! · I sector 4 'Procedure [Pornpen I \ lManual-1 ;Thamaruttanawong l

• o~."'~ • --{--.

r :u1J lffJ1'l41!1-n1 iEmployee!Staffing : ... nm"'I Mrc;:: ' t

it--0~~~i~~tit~~~~'j~~a.\•A .. -.~.,~.·~

-----1-------~-·- .. l ",. ··-------··--·-- ------~--- -···-- ---- -- ~ ;Cancelled

······)·····-··-··· Enrolled 'AU.A-level1-

'C:h•inn R•i

Figure H.1. Enrollments Tracking Report

132

-VJ VJ

Par

nmet

ets

Dat

e Fr

om :

i--

------

-D

ate

To

: I

11) (e

XM

!ple

. 2'f

i.J\.1

n-20

Ci&)

I Ce

o·)

Eu

rnllr

ne

nts

Su

mm

aiy

by

Cla

ss

_ l A

.dvo

nced

D~

top3

!

Sei

t l

. _

. \

lre:

chri

'

2006

12

! l

; i

' j..,

. .. """~".

...A'=-"

""'"-~".

'"'"~-,.

,,..,,..

~.,..,.,

._.,...,

,.,.'>"

.• ,·~·-·-'~

""""-'''""

'~'"'""""'

~•"'_,..,.

.,,.,,..,t

,_,..,.,..

.,_""'"''~

~-~Y«\•••\

<''""~"'=<

>·i••"h'·,

""·'""'''

'"''"''"'"

"'"""""''"

~m<......_

.,,.,,,_ ~

.. ~.•,.~ w

"Nn•W'~'

,.._~,..

..-,.,.,

.,,_~"-"

"·~~.•·L

..-,.r~,

,. ··•·""'

''""'"''"·

"""''"'i,'

"°'_,""""•

"'"~""""..

.-""""''4,

,~ ... ,.~ ··

·~ ···••

,,,,,,

, •. ,,,_,

,_,,,,~, ,,. .

... ., •.

,.,__,,,,s,

,.,.,,,.~,.,

,_.,ft"''

· "'

' ,,_~.,.,.

,~~_,,._,

I 2 i D~l

op T

oo

ls-

I D~l

:op2

! S

ell

l Sch

edl.A

e:d

I 2

0

l l

1 I

! ;

19

i

. ri

lnle

rmed

i:ed:

e:

-2(

)()61

1 •

1 '

' r

' ,.

1

t-ie

=:::

=:r~

~~~_

::r~

1~1~

~r~-

r~~-

:-~c

~o:=

r~-x

-~:

'. 4

I Dls

dplln

ery&

_

1 lrI

DG

1

Non

.Sei

t ! S

.Che

dl.d

ed

; 1

0

: .

' !

, 1

0

~ '

i~-~ ln

tervi~~-t~--~----~L,.,::=:r-'"4-----~-·---~~----~~~-~"~-"~~--·

--~-L-~~M-~-- --

.... -....... i

____ ," ____ ,

,_, .. , .....

...... ~_: ......

..............

. ·-----·-

------1

__ •_ !

-I ~l~ewng

, '

l ~!Jed

,, '

, I

, .

, ,

: -~l

~!;.s-

~---~-

---~, .

. J~~~

~~-~

~~--

~~J-

~---

,-~ .. ~

--·_·-----

-r!~-,~~

-~--L~

~--·--

~-J---

--------

--.. -~1

----~~

.. --~ j_·

..

-n

_

__

_ J_·

----~-

~-~~--

-L ... ___

__________

_ j ' P

erlo

mie

nce

1 i

i S

ched

uled

·

' i

1 1

' 11

I ·

. _

i P

etf'

21Xl

6/1

i N

on.S

elf

! ·

j 20

i

\ \

1 i

20

~ ~ M

ao&

g.el

n D

1

1 -

l 1

l !

i' !

1 1

,

rr1;tet~;;;-rsracoo.----T~--;:;,;;Tsctied~a··r----;~--

......... ~T--

-··---

----·-

---r--

--·---

.. ------

----~r

--·;-·

~-1··-

---·--

-~----

---·--

·---r·

------

-~;---

------

---r··

·--'--

-·----·i

~-~-

--"~

" t ~ ,

4----

·-----

+---"'

"·--+~

~--+--

--~!-'

-m"'"'

"-"'"*

"'"'--

"'-"'"

"'~""+

""""''

"-""'"

"""~"-

-'-'"'

"'""''

""-"'"

'~''~'

': L~-4

AfJ

A ~--

--· --~ L

eh,:!

.........

.. ..,

~-~.

:.he

b1 -4-~~-

L._2,!11~~-~---------1~--~-~1 .. _

....... ~---

-----.. --

~-----

-~·--·

·--~--

------

-l.---

------

---.. -..

......... L

.. ________

1_~-----

--"----~

--------

------! .

.... -.---

----1

i9

I !

N'"

"'·T

-'1

-!

i J

-i

' I

i J

' '

1 !N

ew

Te

ller

: · "'

" ~ ..

. !

Non~

Sell

i S

.Che

dtJe

d t

30

;

! !

; (

30

! ~

~ ~

~ 20

0611

~

~ ~

~ {

~ !;

I, t

' r--

-10 t' ,...

.,......,,"""'-""''"--.'"'"""""""~"--"'"""'."'"r-L ·--

-----,

_,,r-

----""

""""'"

"'t..,

,.....

.,. ...... ~

,,..,,,,,,.,.""."""'"·...-...T---·~·-.-"'·"""'""""'t"-

......... ,...,,

.,., . .,.,, . ._T~

-~-,=.

.,,··"

'''"''

"~~.,-

-,v·~r

,..,,,

......

~-"' ....

..........

,,,,_,

_._,1"

"'~"~~

~~,_.,

..,,,.

,,.,,,

_,.,,,

..."'"

'·=.''

f_· ,.,~

,,,..,,,

,,.,..,.

..,, .. """

"~~-

,---

,.;_

, ,._

~H~'

"'"'

"~-·

..,.

~,, ...

_,,,

l , C

omm

erd

af L

°"n

;

00

0

_ I

_ !

. !

~ i

1 i

; 1

! ! P

r---

...1

.-._

......

,,..,

'Pro

cedu

re

1 S

eit

t O

rin

e

l 2

5

' 1

! !

1 i

1 '

22

i

1 ...

..,...

.....,

.., '

",..

.,..

,.

I h4&

nual

-1

I I

I l

l l

; l

~<~<>~4.

,,,...,,

.,..,,,,

.,._.,.,

,>',,_""

'>"' .... ~-

-g""""

''<'"W

"'<'f"

""""'D

'''"'.

-fflt-

· _.,

.,,.

,._

,,--.,

.... ,,,

,_,,,

,,.,,.

.., .. tb

>'>";.

,,_~-*

>"""""

""'<> ...

. »~"f~"""

~'\O<.•n

<>''h~N"

•J"<""""

"~i"'"""

"""'"'""

-""-''A'

.''<>~\'

'"',_""'

°"f""''"

·"~""""'

°""'"°""

-J'i'"""

"'"<lf•~

.,_·;<-_

,,"1"W"'

'><'"4'"

-">""'''

""'"""""

-'''""17

·~·-?~'t

<""'"-'<

=<".j··

·~""'"''"'

'·""-"<(jo

''"'"'°'"'

"'''~'""""

'~'"'''~W"

'-'•~•~,«-

dJ....•.,,

;v...;,,.,

_.,_,,,,,.

,,.Y•>'."'

/''" " 1

1 '

' '

J .A

4M t

ir

! ;

! I

! ;

' l C~

merd

!J Lo

an to

l eu~

~s

I N

on-S

elf I Sc

hed~

d l

20

!

: 1

19

1 8

US

#l"

les$

;

FIO

Y!IS

!

i ;

: ,

i l

l 2(

)()61

1 I

! I

l ~

I ~-,., ..

... ,""

.-."'"

"""'""

'""'~~

..,...

,.,,,.

,,,.,,

.,"'"'

'· ,.,.,,,,,,_,_/•Y<'-""""""""'"''""'""'"~·"'-"

'"'"

"'-"

""""

"-""

·''"

' ......

"'''~"~""'"'~"''...,._.."',·~--,----.~ ..

,.,e.,

~""'''

""'~'»

·<>•<'

<''>-,

,.,,.,

..,,..

.,.,,.

.,.,,~

_.,,,

,,.. "

'"'·

·~-..

,,,.,.

_....,

..._.,

,,~·,.

.. ~,,-"""'~""'""'"'"'""'-"'"~~<'<>~•····>=~"'""'"-,,,.w'""'''"""'"·"'""'M'"''""

''~-

''•H

~., .

.. -...

.,,.,

•. ~-

-··-~·-"'•"'"

Fig

ure

H.2

. E

nrol

lmen

ts S

umm

ary

by

Cla

ss R

epor

t

APPENDIX I

COST ANALYSIS OF CANDIDATE SOLUTIONS

Tab

le I

.1.

Cos

t-B

enef

it A

naly

sis

of C

andi

date

1

4,65

8,50

0.0

598,

950.

00I

5 25

7 45

0.00

5

783

195.

00

20,0

92 3

42.5

51

3.86

7 03

4.53

4

012.

960.

3(

4.16

4 39

2.83

4.

321

539.

73

7.59

3.44

9.63

11

606

.409

.9'

15.7

70 8

02.8

2 20

092

342

.55

375,

000.

0 0

c 0

0 1,

850,

000.

0 0

c 0

0 75

,000

.0

01 2,

000,

000.

0 ~ QI

0 .....

... 1m

1e

mem

auon

,_,n

ar e

s 2,

150,

000.

0 ~

otal

Dev

elo

men

t Cos

ts:

6,45

0,00

0.0

50,0

00.0

0 50

,000

.0C

50

,000

.00

50,0

00.0

25

,000

.00

25,0

00.0

C

25,0

00.0

0 25

,000

.0

517,

000.

00

568,

700.

0C

625,

570.

00

688,

127.

00

592,

000.

00

643,

700.

0C

700,

570.

00

763,

127.

00j

er v

ear

215,

000.

00

215,

000.

0C

215,

000.

00

215,

000.

00]

807,

000.

00

858,

700.

00

915,

570.

00

978,

127.

00!

718.

227.

13

720

981.

08

725.

217.

20

730.

913.

39

11 7

77.4

14.2

71

9 60

0 30

2.60

10

.321

283

.68

11 0

46 5

00.8

7 11

777

414

.271

otal

Pro

iect

Ben

efits

-C

osts

: 5.

465,

000.

00

3,53

8,00

0.00

3,

920,

800.

00

4,34

1,88

0.00

4,

805,

068.

00

earl

yNP

V:

5,15

5,66

0.38

3,

148,

807.

40

3,29

1,97

9.28

3,

439,

175.

63

3,59

0,62

6.33

8,

314,

928.

28

iCum

ulat

ive

NPV

: 5.

155.

660.

38

2.00

6.85

2.97

) 1.

285.

126.

31

4.72

4,30

1.95

8.

314.

928.

28

etur

n on

Inv

estm

ent:

B

reak

-eve

n P

oint

: In

tam

!ibl

e B

enef

its:

,_D

ecre

ase

proc

essi

ng ti

mes

,_

Incr

ease

trai

ning

hou

rs

-G

ain

mor

e co

moe

titi

ve a

dvan

tage

s

.......

\,;.

) V

l

25,0

00,0

00.0

0 B

aht

20,0

00,0

00.0

0

15,0

00,0

00.0

0

I 0,0

00,0

00.0

0

5,00

0,00

0.00

1

-+

-P

V o

f All

Ben

efit

s:

-a-

PV

of A

ll C

osts

:

Yea

rs

2 3

4 5

Fig

ure

I.1.

B

reak

-Eve

n P

oint

of C

andi

date

1

Tab

le I

.2.

Cos

t-B

enef

it A

naly

sis

of C

andi

date

2

3,72

6,41

5.09

3.

726

415.

09

7 59

3 44

9.63

11

606

.409

.9<]

15

770

.802

.821

I

I 12

5,00

0 l

375,

000.

00

0 c

01 20

4,00

0.00

0

c 01

75

,000

.00

2,00

0,00

0.00

.....

.. 14

6,00

0.0

w

2,80

0,00

0.00

1 0

\

30,0

00.0

0 50

,000

.0C

50

,000

.0C

50

,000

.00

50,0

00.0

0 2,

250,

000.

00

25,0

00.0

C

25,0

00.0

C

25,0

00.0

C

25,0

00.0

0 47

0,00

0.00

51

7,00

0.0C

56

8,70

0.0C

62

5,57

0.00

68

8,12

7.00

2,

750,

000.

00

592,

000.

0(

643,

700.

0C

700,

570.

0(

763,

127.

00 !

erv

ear

I 13

2,70

0.00

13

2,70

0.00

13

2,70

0.00

13

2,70

0.00

13

2,10

0.00

1

5,68

2,70

0.00

72

4,70

0.0C

77

6,40

0.00

83

3,27

0.00

89

5,82

1.00

1 5.

361

037.

74

644.

980.

42

651.

880.

4 t

660

027.

89

669

414.

05

7.98

7.34

0.5

5.36

1.03

7.74

6.

006.

018.

1 ~

6.65

7.89

8.57

7.

317.

926.

45

7 98

7 34

0.50

otal

Pro

ject

Ben

efit

s -

Cos

ts:

I (1

732

,700

.00

3 62

0,30

0.00

4,

003

100.

00

4,42

4 18

0.00

4,

887,

368.

00\

'ear

lvN

PV

: I

<l,

634,

622.

64

3,22

2,05

4.1

l 3,

361,

079.

9:

3,50

4,36

4.94

3,

652,

125.

68

12, 1

05,0

02.0

1.

634.

622.

64)

l.58

7.43

1.47

4.

948,

511.

42

8.45

2,87

6.37

12

. 105

.002

.051

....... w

--..:i

25,0

00,0

00.0

0Bab

t

20,0

00,0

00.0

0

15,0

00,0

00.0

0

10,0

00,0

00.0

0

5,00

0,00

0.00

-11

1-P

V o

f All

Ben

efit

s:

PV

of A

ll C

osts

:

Yea

rs

2 3

4 5

Fig

ure

I.2.

B

reak

-Eve

n P

oint

of C

andi

date

2

........ w

00

Tab

le I

.3.

Cos

t-B

enef

it A

naly

sis

of C

andi

date

3

3,50

0,00

0.00

1 3,

850,

000.

0 45

0,00

0.00

49

5,00

0.0

3.95

0.00

0.00

1 4.

345.

000.

0 3.

726.

415.

091

3,86

7.03

4.53

3.

726.

415.

091

7.59

3.44

9.63

375,

000.

0 85

0,00

0.0

75,0

00.0

01

2,00

0,00

0.00

1 55

0,00

0.00

3,

850,

000.

0

30,0

00.0

2,

250,

000.

001

470,

000.

001

2,75

0,00

0.00

1

erv

ear

165,

000.

00

6,76

5,00

0.00

1 6.

382.

075.

47

6.38

2,07

5.47

1

otal

Pro

iect

Ben

efit

s -

Cos

ts:

2.81

5.00

0.00

3,

588,

000.

00

2,65

5,66

0.38

3,

193,

307.

23

Cum

ulat

ive

NPV

: 2.

655.

660.

38

537.

646.

851

Ret

urn

on I

nves

tmen

t:

12

0%

B

reak

-eve

n P

oint

: 1.

83 Y

ears

! fo

tan1

!:ib

le B

enef

its:

D

ecre

ase

oroc

essi

ng ti

mes

,_

Incr

ease

tra

inin

g ho

urs

,_ G

ain

mor

e co

moe

titi

ve a

dvan

tage

s

4,23

5,00

0.0

4,65

8,50

0.00

1 5,

124,

350.

00

544,

500.

0 59

8,95

0.00

1 65

8,84

5.00

4.

779.

500.

0 5.

257.

450.

00

5.78

3.19

5.00

4.

012,

960.

3 4.

164

.392

.83

4.32

1.53

9.73

11

.606

.409

.9

15, 7

70,8

02.8

2 20

.092

.342

.55'

50,0

00.0

01

50,0

00.0

0'

25,0

00.0

01

25,0

00.0

62

5,57

0.00

1 68

8,12

7.00

70

0,57

0.00

I 76

3,12

7.00

165,

000.

00

165,

000.

001

865,

570.

001

928,

127.

00

685.

612.

51

693.

550.

491

9.11

3.96

5.8

8.42

0.41

5.40

9.

113.

965.

891

4.39

1,88

0.00

4,

855,

068.

00

3,47

8,78

0.32

3,

627,

989.

241

10,9

78,3

76.6

61

7.35

0,38

7.42

10

.978

.376

.66

-w \0

25,0

00,0

00.0

0 B

aht

20,0

00,0

00.0

0

15,0

00,0

00.0

0

I 0,0

00,0

00.0

0

5,00

0,00

0.00

-m-

PV

of A

ll C

osts

:

Yea

rs

2 3

4 5

Fig

ure

I.3.

Bre

ak-E

ven

Poi

nt o

f Can

dida

te 3

BIBLIOGRAPHY

1. Whitten, Jeffery L., Lonnie D. Dentley and Kevin C. Dittman. System Analysis and Design Methods. Sixth Edition. McGraw-Hill, 2004.

2. O'Brien J. A. Management Information System: Managing Information Technology in the Internet worked Enterprise, Fourth Edition. USA: McGraw Hill, 1999.

3. Alan Dennis, Barbara Wixom, and David Tegarden. Systems Analysis and Design with UML Version 2.0. Second Edition. John Wiley & Sons, Inc., 2005.

4. Date, C.J. An Introduction to Database Systems, Seventh Edition. MA: Addison Wesley, 2000.

5. Information Technology Project Management, Jack T. Marchewka, Wiley, 2003, ISBN 0-471-39203-0.

6. Ron Weber. Information Systems Control and Audit. First Edition. Prentice Hall International, Inc., 1999.

7. 1 li Oracle Leaming Management Fundamentals, Student Guide

8. Http://www.scb.co.th.

140

training management system (tms) for siam commercial bank

Documents