Muutke küpsiste eelistusi

E-raamat: Process-Centric Architecture for Enterprise Software Systems

2.00/5 (2 hinnangut Goodreads-ist)
(Infosys, Bangalore, India)
  • Formaat: 333 pages
  • Sari: Infosys Press
  • Ilmumisaeg: 24-Jun-2010
  • Kirjastus: Taylor & Francis Inc
  • ISBN-13: 9781439816295
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 90,47 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Process-Centric Architecture for Enterprise Software SystemsSuurem pilt
  • Formaat: 333 pages
  • Sari: Infosys Press
  • Ilmumisaeg: 24-Jun-2010
  • Kirjastus: Taylor & Francis Inc
  • ISBN-13: 9781439816295
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

The increasing adoption of Business Process Management (BPM) has inspired pioneering software architects and developers to effectively leverage BPM-based software and process-centric architecture (PCA) to create software systems that enable essential business processes. Reflecting this emerging trend and evolving field, Process-Centric Architecture for Enterprise Software Systems provides a complete and accessible introduction explaining this architecture.

The text presents, in detail, the analysis and design principles used in process-centric architecture. Illustrative examples demonstrate how to architect and design enterprise systems based on the business processes central to your organization. It covers the architectural aspects of business process management, the evolution of IT systems in enterprises, the importance of a business process focus, the role of workflows, business rules, enterprise application integration, and business process modeling languages such as WS-BPEL and BPML. It also investigates:





Fundamental concepts of process-centric architecture style The PCA approach to architecting enterprise IT systems Business process driven applications and integration Two case studies that illustrate how to architect and design enterprise applications based on PCA SOA in the context of process-centric architecture Standards, technologies, and infrastructure behind PCA

Explaining how to architect enterprise systems using a BPMS technology platform, J2EE components, and Web services, this forward-looking book will empower you to create systems centered on business processes and make todays enterprise processes successful and agile.
Preface xv
Acknowledgments xvii
Author xix
PART I THE PROCESS-CENTRIC ARCHITECTURE PARADIGM
1 Introduction
3(14)
1.1 Objectives
3(1)
1.2 Enterprise Software Systems
3(1)
1.3 Architecture for Systems
4(3)
1.3.1 IT Architecture
4(1)
1.3.2 IT System Architecture
5(1)
1.3.3 Architectural Styles and Patterns
5(2)
1.4 Introduction to Business Processes
7(1)
1.5 Activities in Business Processes
8(1)
1.6 Types of Activities
9(1)
1.6.1 Manual
9(1)
1.6.2 System
10(1)
1.7 Importance of Business Processes to Enterprise
10(3)
1.7.1 Processes Are Unique
12(1)
1.7.1.1 Work Culture
12(1)
1.7.1.2 Change
12(1)
1.7.1.3 Employees/People
12(1)
1.7.1.4 Systems
12(1)
1.7.1.5 Vision and Mission
13(1)
1.7.2 Processes Are Organization Wide
13(1)
1.8 Process-Centric Architecture---A Quick Introduction
13(2)
1.8.1 Background
13(1)
1.8.2 Concept
14(1)
1.8.3 Benefits
15(1)
1.8.4 The Book
15(1)
1.9 Exercise Questions
15(2)
2 Evolution of IT Architecture
17(20)
2.1 Objectives
17(1)
2.2 Historical Perspective on Enterprise Computing Architectures
17(10)
2.2.1 The 1960s
18(1)
2.2.2 The 1970s
19(1)
2.2.3 The 1980s
20(2)
2.2.4 The 1990s
22(3)
2.2.5 The 2000s
25(2)
2.3 Traditional Ways of Supporting Business
27(2)
2.4 Workflows
29(1)
2.5 Packages
30(1)
2.6 Integration
31(2)
2.7 Business-IT Gap
33(2)
2.8 Exercise Questions
35(2)
3 Concept of Process-Centric Architecture
37(30)
3.1 Objectives
37(1)
3.2 The Case for a New Approach
37(1)
3.3 What Is Process-Centric Architecture?
38(1)
3.4 Process Logic Abstraction
39(4)
3.5 Qualities Addressed
43(1)
3.6 Structure
44(3)
3.6.1 Business Process Model
45(1)
3.6.2 Process Layer
45(1)
3.6.3 Business Logic Elements
45(1)
3.6.4 UI Application Layer
46(1)
3.6.5 Clients
46(1)
3.6.6 Business Rules Layer
46(1)
3.7 Dynamics
47(1)
3.8 Principles
48(13)
3.8.1 Business Process-Driven System
48(1)
3.8.2 Highly Abstracted Components
49(1)
3.8.3 Automated Processes
50(1)
3.8.4 Process Thinking Oriented
51(1)
3.8.5 Explicit Processes
52(1)
3.8.6 Flexible Processes
52(1)
3.8.7 Service-Based Activities
53(1)
3.8.8 Implementation-Isolated Processes
54(1)
3.8.9 Executable Process Specifications
55(2)
3.8.10 Interacting Processes
57(1)
3.8.11 Business Controlled System
57(1)
3.8.12 Reusable Processes
57(1)
3.8.13 Mobile Processes
58(1)
3.8.14 Process-Level Programming
59(1)
3.8.14.1 New Programming Abstraction
59(1)
3.8.14.2 Minimized Coding
60(1)
3.8.15 Composable Processes
60(1)
3.8.16 Autonomous Processes
60(1)
3.9 Integration Concept as Handled in PCA
61(1)
3.10 Workflow in PCA
62(1)
3.11 Holistic View in Architecture
62(1)
3.12 Similar Approaches
63(2)
3.13 PCA in the Context of Other Architectures
65(1)
3.14 Exercise Questions
66(1)
4 Business Process Management
67(14)
4.1 Objectives
67(1)
4.2 What Is BPM?
67(4)
4.3 PCA and BPM
71(1)
4.4 Business Process Life Cycle
72(2)
4.4.1 Process Design
72(1)
4.4.2 Process Modeling
72(1)
4.4.3 Process Simulation
73(1)
4.4.4 Process Design-Time Optimization
73(1)
4.4.5 Process Deployment
73(1)
4.4.6 Process Execution
74(1)
4.4.7 Process Monitoring
74(1)
4.4.8 Process Analysis
74(1)
4.4.9 Process Optimization
74(1)
4.5 Six Sigma
74(1)
4.6 Lean
75(1)
4.7 Process Redesign
76(1)
4.8 Process Automation
77(1)
4.9 BPMS Products
77(1)
4.10 BPM Landscape
78(1)
4.11 Exercise Questions
79(2)
5 Components of PCA
81(24)
5.1 Objectives
81(1)
5.2 The Business Process Model
81(13)
5.2.1 Structure
82(2)
5.2.2 Relationships
84(1)
5.2.2.1 Business Logic Elements
84(1)
5.2.2.2 The Process Layer
84(1)
5.2.3 Properties of Processes
85(3)
5.2.4 Levels of Models
88(1)
5.2.4.1 High-Level Business Process Model
88(1)
5.2.4.2 Executable Process Model
89(5)
5.3 Process Layer
94(5)
5.3.1 Responsibilities
94(2)
5.3.2 Interrelationships
96(1)
5.3.2.1 Process Model
96(1)
5.3.2.2 Business Logic Elements
97(1)
5.3.2.3 UI Application Layer
97(1)
5.3.2.4 External Process Systems or Other Processes
98(1)
5.3.3 Structure
98(1)
5.4 Business Logic Elements
99(2)
5.4.1 Principles
100(1)
5.5 User Interface Application Layer
101(1)
5.6 Exercise Questions
102(3)
6 Process Execution
105(24)
6.1 Objectives
105(1)
6.2 Deployment
105(1)
6.3 Execution
106(15)
6.3.1 System Participation
107(1)
6.3.1.1 Solicit-Response
107(1)
6.3.1.2 Notification
108(1)
6.3.1.3 Request-Response
108(1)
6.3.1.4 One-Way
109(1)
6.3.2 Critical Aspects at Run-Time
110(1)
6.3.2.1 Errors
110(2)
6.3.2.2 Transactions
112(3)
6.3.2.3 Compensation
115(1)
6.3.2.4 Correlation
116(1)
6.3.3 Human Participation
117(1)
6.3.3.1 Allocation
118(1)
6.3.3.2 Execution
119(1)
6.3.3.3 Notification
119(1)
6.3.4 Life-Cycle Stages
120(1)
6.4 Addressing Integration
121(3)
6.5 Workflow
124(2)
6.6 Business Rules
126(1)
6.7 Flows Handled in a Process
127(1)
6.8 Exercise Questions
128(1)
7 Benefits of Process-Centric Architecture
129(14)
7.1 Objectives
129(1)
7.2 Business Benefits
129(4)
7.2.1 Business-IT Alignment
129(1)
7.2.2 Better Control for Business
130(1)
7.2.3 Reuse
130(1)
7.2.4 Central Store of Processes
131(1)
7.2.5 Process Management
131(1)
7.2.6 Mergers and Acquisitions
131(2)
7.3 Benefits to IT Systems
133(1)
7.3.1 Flexibility
133(1)
7.3.2 Agility
133(1)
7.3.3 Interoperability
133(1)
7.3.4 Scalability of the IT System Is Improved
134(1)
7.3.5 Maintainability
134(1)
7.4 Scalability of the PCA Style and Approach
134(2)
7.5 Complexity versus Manageability
136(1)
7.6 Raised Level of Abstraction for the IT System
137(2)
7.7 Exercise Questions
139(4)
PART II ARCHITECTING IT SYSTEMS, THE PROCESS-CENTRIC STYLE (DESIGNING PCA)
8 The Approach
143(22)
8.1 Objectives
143(1)
8.2 A Typical Manifestation of Process-Centric Architecture
143(7)
8.2.1 The Architecture
143(2)
8.2.1.1 Process Engine
145(1)
8.2.1.2 Process Repository
146(1)
8.2.1.3 Applications
146(1)
8.2.1.4 Application Server
147(1)
8.2.1.5 Adapter Layer
147(1)
8.2.1.6 Business Rules Engine
148(1)
8.2.1.7 Web Server
148(1)
8.2.2 Legacy Components
149(1)
8.3 Architectural Design in PCA
150(10)
8.3.1 When to Apply?
150(1)
8.3.2 How to Apply?
151(1)
8.3.2.1 Modeling Business Processes---Prerequisites
151(1)
8.3.2.2 Top-Down Approach (or Leaned to Top Approach)
152(4)
8.3.3 Levels of Models
156(1)
8.3.3.1 High-Level Business Process Modeling
156(2)
8.3.3.2 Executable Business Process Modeling
158(2)
8.4 Re-Architecting an Existing IT System for PCA
160(2)
8.4.1 A Scenario
160(1)
8.4.2 Approach
161(1)
8.4.2.1 Justification
161(1)
8.4.2.2 Re-Architecture
161(1)
8.5 Addition of an IT Subsystem to an Existing IT System
162(2)
8.6 Exercise Questions
164(1)
9 SOA for Services
165(10)
9.1 Objectives
165(1)
9.2 Services
165(1)
9.3 Service-Oriented Architecture
166(1)
9.4 Bottom-Up Approach
167(1)
9.5 Need for SOA in PCA
168(2)
9.6 Complementary Approach to Architectural Design
170(3)
9.6.1 Context
170(1)
9.6.2 Top-Down
170(1)
9.6.3 Design of Services in the Context of PCA
171(1)
9.6.4 Leverage What Is Available
172(1)
9.6.5 Binding
172(1)
9.6.6 Complementary
173(1)
9.7 Exercise Questions
173(2)
10 Standards and Technologies
175(18)
10.1 Objectives
175(1)
10.2 Standards
175(1)
10.3 Process Modeling Standards
176(2)
10.3.1 BPMN
176(2)
10.3.2 XPDLtm
178(1)
10.4 Process Execution Standards
178(9)
10.4.1 WS-BPEL
179(1)
10.4.1.1 A Combination of Interoperability Standards
179(1)
10.4.1.2 Structure
179(4)
10.4.1.3 Bindings
183(1)
10.4.1.4 Extensions
183(1)
10.4.2 BPML
183(4)
10.5 Inter-Process Layer Interactions
187(1)
10.6 Business Logic Interaction Standards
187(1)
10.7 Technologies and Tools
188(2)
10.7.1 Process Component and Process Layer
188(1)
10.7.2 Adapter Layer or Collaboration Layer
188(1)
10.7.3 Implementation of Business Logic
188(1)
10.7.4 Server Components
189(1)
10.7.5 Design-Time Component
190(1)
10.7.6 Operations and Administration
190(1)
10.8 Implementation Options
190(2)
10.9 Exercise Questions
192(1)
11 Case Study---Architectural Design Applying PCA
193(92)
11.1 Objectives
193(1)
11.2 Case Study I
193(42)
11.2.1 Modeling of the Business Process
194(2)
11.2.1.1 Design Rationale
196(1)
11.2.2 Detail-Level Business Process Modeling
197(29)
11.2.3 Logical Architecture
226(6)
11.2.4 Services
232(3)
11.3 Case Study II
235(48)
11.3.1 The Process
236(1)
11.3.2 Background Context
236(1)
11.3.3 The Current System
236(1)
11.3.3.1 Applications
237(1)
11.3.3.2 Flow Support
238(1)
11.3.3.3 Issues
239(1)
11.3.4 The New System
239(1)
11.3.4.1 The Business Process Model
239(3)
11.3.4.2 Detailed Process Model
242(2)
11.3.4.3 Services Design
244(17)
11.3.4.4 User Activities
261(2)
11.3.4.5 Executable Process Definition
263(20)
11.3.4.6 Embodiment
283(1)
11.4 Exercise Questions
283(2)
12 Implementation Considerations
285(20)
12.1 Objectives
285(1)
12.2 Types of Business Processes
285(4)
12.2.1 Rules-Centric
286(1)
12.2.2 Workflow Oriented
287(1)
12.2.3 STP Oriented
287(1)
12.2.4 EAI Oriented
288(1)
12.3 Process Infrastructure
289(3)
12.3.1 Legacy BPMSs
289(1)
12.3.1.1 Application Server Legacy
290(1)
12.3.1.2 Workflow Legacy
290(1)
12.3.1.3 EAI Legacy
290(1)
12.3.1.4 Rule Engine Legacy
291(1)
12.3.1.5 DMS Legacy
291(1)
12.3.1.6 Package Legacy
291(1)
12.3.2 Pure-Play BPMSs
292(1)
12.4 Best Practices
292(3)
12.5 Practicalities in Architectural Design
295(9)
12.5.1 Some Common Situations
295(1)
12.5.1.1 Recurrent Tasks
295(1)
12.5.1.2 Making Task Nodes Work
296(1)
12.5.1.3 Audit Data Capture
297(1)
12.5.1.4 Batch Processing Platform
297(1)
12.5.1.5 Workflow Application
298(1)
12.5.1.6 Third-Party Data Integration
299(1)
12.5.1.7 Business Activity Monitoring Application
300(1)
12.5.1.8 Splitting the Responsibilities between the Specific Application and the Process Layer/BPMS
300(1)
12.5.1.9 Existing System with a Process Engine
301(1)
12.5.2 Anti-Patterns
302(1)
12.5.2.1 Screen Chaining
302(1)
12.5.2.2 Huge Data Transfer
303(1)
12.5.2.3 Batch Integration with Legacy
304(1)
12.6 Exercise Questions
304(1)
Bibliography 305(4)
Index 309
Parameswaran Seshan is a Principal (Education and Research) with Infosys Technologies Ltd., Bangalore, India. At Infosys, he is part of the E-comm Research Labs. He has around 14 years of work experience in the Information Technology (IT) industry as a researcher, educator, architect, and programmer. Before joining Infosys in 2001, he worked as an Advisory Systems Analyst with APL (American President Lines Ltd.), Oakland, California, U.S.A. Parameswaran has also worked as a software engineer with Case Consult (I) Pvt. Ltd., Thiruvananthapuram, India. He holds a Bachelor of Technology (B.Tech) degree in Computer Science and Engineering from the University of Calicut (in 1995). His work experience in the IT industry involved research, programming, architecture, and design.

At Infosys, Parameswaran has been doing research work in the area of Process-centric Architecture, Business Process Management (BPM) , Software architecture, and new computing models/paradigms. He has also been teaching architecture and high-end technology courses at Infosys. He was the lead architect for the home-grown Business Process Management System (BPMS) from Infosys and was also actively involved in its design and development. Parameswaran has architected, designed, programmed and supported a number of IT systems over his career as a computer software professional.

Parameswaran is an active researcher. He has published papers at international conferences and other forums. He has worked on joint research works with Microsoft Research India and Researchers from Universities such as Copenhagen University and University of Melbourne in the areas of BPM and Agent-oriented software engineering.

Parameswaran has designed, developed and supported IT systems involving various technologies, at APL. He programmed system tools to automate operations. He also led a team in software development and support projects at APL. Parameswaran programmed system tools based on REXX to automate conversion of programs from one programming environment to another, at Case Consult.

Parameswaran's areas of research interest include software architecture, process-centric architecture, new computing models, intelligent software agents and intelligent systems.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97814398162952e.html
Märksõnad: