| 1. |
How Many Napkins Have to Die Needlessly? A Case for Business Architecture ( Pages)
by J. Dowling
Apr 5, 2000
Abstract : Architecture is a description of how things go together. Once we know what our Business Architecture is, we can design an Information Technology Architecture to compliment it. Without a clearly stated architecture, there is a good chance that things will be put together wrong.
|
| 2. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part II - The Architecture Process ( 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.
|
| 3. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part I - Introduction to Software Architecture ( 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.
|
| 4. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part III - Steps in the Architecture Process ( 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.
|
| 5. |
Architecture Evolution: From Mainframes to Service-oriented Architecture ( Pages)
by P.J. Jakovljevic
Sep 18, 2006
Abstract : Product architecture is going to do much more than simply provide the technical functionality, the user interface, and the platform support. It is going to determine whether a product is going to be able to accommodate increasingly evolving user requirements.
|
| 6. |
Architecture Evolution: From Web-based to Service-oriented Architecture ( Pages)
by P.J. Jakovljevic
Sep 19, 2006
Abstract : Traditional enterprise systems have proven difficult to change and extend. The inherent problem of old core code and business logic duplication is part of the reason traditional enterprise resource planning systems have not readily taken to e-commerce.
|
| 7. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part V - Applying the Methodology ( 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.
|
| 8. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part IV - Moving From Planning to Implementation ( Pages)
by Glen B. Alleman
Sep 13, 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.
|
| 9. |
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.
|
CART 
