Professional Documents
Culture Documents
ii
iii
iv
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
vi
ERP
Information
System
Success
ERP ERP
ERP
ERP
ERP
vii
Summary
In an era of knowledge economy, it is necessary to promote the
efficiency of business. However, when a corporation decides to use an
enterprise resource planning (abbreviated as ERP) system, it
becomes a gigantic problem to choose either developing the system by
themselves or buying a suit ERP software. At present, the maturity of
ERP software on the market is able to fulfill the general demand of
business. But enterprises in general need to face the situation that the
procedure revises when having special demands. The suit ERP
software on the market, will divide the system into several main
module at present, usually can include financial management, stock
control, sale management, procurement management, production
management, human resource management.
The suit ERP software on the current market, the major problem
stems from three causes. They are process-oriented, structured
method, and object-oriented. We call them non architecture oriented
finance management ERP model (NAOFMERPM)
This research develops an architecture oriented finance
management ERP model (AOFMERPM) which solves the problems
generated by NAOFMERPM. To validate this expression, we use the
information system success model (abbreviated as IS Success Model)
three factors, information quality, system quality, service quality to
prove AOFMERPM is better than NAOFMERPM .
Keyword: non architecture oriented finance management ERP,
architecture oriented finance management ERP, enterprise resource
planning, Information System Success Model.
viii
1
1
2
2
ERP
3
3
3
3
5
7
ERP
11
11
13
ERP
AOFMERP
AOFMERP
14
14
16
ERP ERP
46
46
49
52
52
52
52
53
53
53
ix
3-1
12
4-1
15
4-2
WorkFlow ERP
19
4-3
AOFMERP
20
4-4
26
4-5
35
4-6
36
4-7
36
4-8
37
4-9
37
4-10
38
4-11
38
4-12
39
4-13
39
4-14
40
4-15
40
4-16
41
4-17
41
4-18
42
4-19
42
4-20
43
4-21
43
4-22
44
4-23
44
4-24
45
5-1
ERP
46
5-2
ERP
47
5-3
48
5-4
50
5-5
ERP
50
5-6
51
5-7
51
1-1
ERP
2-1
MRPII
4-1
AOFMERP_Simple_ClientServer_Diagram in Acme
15
4-2
25
4-3
34
xi
ERP
ERP
ERP
AOERPFMS
ERP
ERP 1-1
1-1 ERP
30
27
27
3
1
2
96.8
87.1
76.1
9.7
3.2
6.5
ERP
1999
ERP
ERP ERP
ERP ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
ERP
(Coguen,1975)[13]
(ANSI/IEEEStd 1471,2000)[21]
()
1960 EW
1990 Rational Software Corporation
Microsoft
(ADL)
Wright ()Acme ()
C2 ( UCI ) Darwin ()ADL
ERP
ERP
90 ERP
ERP
ERP MRPMRP
ERP
ERP ERP
MRPMRPAPICS
1995
ERP
ERP MRP
GUI
client/servo
open system
1ERP
2ERP
3ERP
MRP
4ERP 90
ERP Gartner Group 90
http://www.anser.com.tw/erp/erparticle6.htm
6
ERP
90 ERP
1970 MRP1980 MRP
2-1
2-1 MRPII
MRP
MRP
ERP
http://www.anser.com.tw/erp/erparticle6.htm
http://www.cyut.edu.tw/~ce/department/department/hwaiuj/3436-01.pdf
ERP
ERP
ERP
ERP
Alan Kay
Kay
Smalltalk
http://eteacher.mljh.ylc.edu.tw/harrison/viewthread.php?tid=352
RAD(Rapid Application
Development)
ttp://eteacher.mljh.ylc.edu.tw/harrison/viewthread.php?tid=352
10
(argument)
ERP(AOFMERP)ERP
(concept)
ERP
ERP
-AOFMERP
AOFMERPERP
AOFMERP
11
3-1
12
ERP
ERP
AOFMERP
AOFMERP ERP
ERP
SAP Oracle
13
ERP
ERP(AOFMERP)
AOFMERPClient-Server
AOFMERP
ERP
AOFMERP
(Architecture-Oriented Finance Management
ERPAOFMERP)
AOFMERP(ERP
)AOFMERPClient-Server
Client call-cServer
call-s4-1
14
Client-Server Acme
AOFMERP_Simple_ClientServer_Diagram in Acme
AOFMERP simple_CS=
{
AOFMERP_StructureElementClient = {
Port send-request;
};
AOFMERP_StructureElementServer = {
Port receive-request;
};
Interation = {
Role {call-c, call-s}
};
Behavior = {
Client.send-request to interact.call-c;
Server.receive-request to Interact.call-s;
}
}
4-1
AOFMERP_Simple_ClientServer_Diagram in Acme
15
AOFMERP
Client-Server AOFMERP
AOFMERP :
1995
ERP
ERP
16
95
1
17
10
11
12 ()
13
14
15
16
18
WowrkFlow ERP
4-2
4-2
WorkFlow ERP
http://www.dsc.com.tw/product/workflow/workflow2.htm
19
ERP
ERP
4-3
4-3
AOFMERP
20
XX XX
Invoice Invoice
21
Invoice
22
95
23
1995
ERP
ERP MRP
GUI
client/servo
open system
ERP
24
4-2
4-2
25
4-2
4-4
26
ERPClient-Server
AcmeBehavior = {Client.send-request to
interact.call-c;Server.receive-request to Interact.call-s;}
Behavior
27
28
29
30
31
32
4-3
33
4-3
34
4-5
4-5
35
Client-Server
4-6
4-7
36
4-8
4-9
37
4-10
4-11
38
4-12
4-13
39
4-14
4-15
40
4-16
4-17
41
4-18
4-19
42
4-20
4-21
43
4-22
4-23
44
4-24
4-24
45
ERP ERP
ERP ERP
ERP
ERP
ERP ERP
5-1
5-1 ERP
2000 P275-P282
46
ERP
ERP
ERP
5-2
5-2 ERP
47
ERP ERP
ERP
ERP 60.4%(
,2005)
ERP
ERP
ERP 5-3
ERP
5-3
48
ERP ERP
ERP
ERP
ERP
ERP
ERP
(ERD) DFD Hierarchical Input
Process OutPut HIPO (:)
:
(:)
ERP ERP
49
5-4
5-4
ERP
5-5
5-5 ERP
50
ERP ERP
ERP
5-6 ERP
5-6
5-7
5-7
51
ERP
ERP
ERP
ERP ERP
ERP
ERP
ERP
52
1 Steve McConnel
2005
2 SA UML/MDA 2007
3 2004
4 2005
5 ERP
1999
6 1995
7 ERP
53
5 Hevner, A. R.; March, S. T.; Park, J.; Ram, S.: Design Science in
InformationSystems Research. MIS Quarterly 28(1), 2004: pp.
75-105.
6 Kindler, E.: On the Semantics of EPCs: A Framework for Resolving
the ViciousCircle. In: Proceedings of the Business Process
Management: Second InternationalConference (Lecture Notes in
Computer Science, Vol. 3080 / 2004). Springer: PotsdamGermany,
2004, pp. 82-97.
7 Markus, M. L.; Petrie, D.; Axline, S.: Bucking the Trends: What the
Future MayHold for ERP Packages. Information Systems Frontiers
2(2), 2000: pp. 181-193.
8 Markus, M. L.; Tanis, C.; van Fenema, P. C.: Multisite ERP
implementations.Communications of the ACM 43(4), 2000: pp.
42-46.
9 Merriam-Webster: Merriam-Webster's Collegiate Dictionary (online
versionavailable under http://www.m-w.com). 11th ed.
Merriam-Webster: Springfield, MA,USA, 2003.
10PROVOX plus Instrumentation System: System overview, 1989.
11D. Harel, Statecharts: A visual formalism for complex systems,
Science of ComputerProgramming, vol. 8, pp. 231-274, 1987.
54
55