| 1. |
Business Process Management Notations within Business Process Management (4 Pages)
by Hans Mercx
Nov 7, 2006
Abstract : Business process management notation (BPMN) is an initiative to increase standardization within process modeling. What are the principles of BPMN, and what is the value of BPMN to vendors and organizations using business process modeling?
Type: Article
|
| 2. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part II - The Architecture Process (7 Pages)
by Glen B. Alleman
Sep 6, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
Type: Article
|
| 3. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part III - Steps in the Architecture Process (14 Pages)
by Glen B. Alleman
Sep 11, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architectureﾖcentered methodologies must be an intentional step in the process of deploying information systems ﾖ not an accidental byﾖproduct of the software acquisition and integration process.
Type: Article
|
| 4. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part V - Applying the Methodology (11 Pages)
by Glen B. Alleman
Sep 19, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems - not an accidental by-product of the software acquisition and integration process.
Type: Article
|
| 5. |
Architecture–Centered Information Systems In The Manufacturing Domain – Part V – Applying the Methodology (11 Pages)
by Glen B. Alleman
Aug 23, 2000
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture–centered methodologies must be an intentional step in the process of deploying information systems – not an accidental by–product of the software acquisition and integration process. Part V – Applying the Methodology.
Type: Article
|
| 6. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part I - Introduction to Software Architecture (15 Pages)
by Glen B. Alleman
Sep 4, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
Type: Article
|
购物车 
