| 1. |
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
|
| 2. |
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
|
| 3. |
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
|
| 4. |
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
|
| 5. |
SCE Leaders Partner To See Beyond Their Portfolio Part Three: Challenges and User Recommendations (3 Pages)
by P.J. Jakovljevic
May 21, 2003
Abstract : One of the biggest challenges facing IT departments today is still unlocking data and processes from a plethora of heterogeneous applications running on different technologies and platforms, from mainframe to Web application servers. Since most SCE solutions involve a complex flow of transactions across a company's information systems network, users need simple to use, graphical tools to help them manage these transaction flows and quickly respond to problems.
Type: Article
|
| 6. |
Enterprise Application Integration - Where Is It Now (And What Is It Now)? Part 2: Where Is It Now? by Michael F. Reed
Sep 6, 2001
Abstract : Enterprise Application Integration has changed massively in the past two years. Where is the market, and what vendors are left in the game?
Type: Article
|
| 7. |
Enterprise Application Integration - the Latest Trend in Getting Value from Data (6 Pages)
by M. Reed
Feb 1, 2000
Abstract : Enterprise Application Integration (EAI) is one of the hot-button issues in IT for the Year 2000. Information Week Research's survey of 300 technology managers showed nearly 75% of respondents said EAI is a planned project for their IT departments in the coming year. According to a survey conducted by Bank Boston, the market for EAI is expected to be $50 Billion USD by 2001. However, successful EAI requires a careful combination of a middleware framework, distributed object technologies, and custom consulting.
Type: Article
|
| 8. |
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
|
| 9. |
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
|
购物车 
