The Art And Science Of IT Architecture Design
| by J. Dowling |
... ÿþThe Art And Science Of IT Architecture Design J. Dowling - June 3, 2002 1.
Introduction. 2. The Art
of Architecture Design. ... The Art of Architecture Design. ...
|
|
| http:/.../Research/ResearchHighlights/ExecutiveView/2002/06/research_notes/MI_EV_JFD_06_03_02_1.asp - 14k - 2002-06-03 |
| Summary: To assure flexibility and lasting value, information system designs and product selection must be guided by an architectural
plan for infrastructure and applications systems. The Art of architecture design is in extracting business requirements;
the Science is translating them into technology solutions.
|
|
Architecture-Centered Information Systems In The Manufacturing ...
| by Glen B. Alleman |
... ÿþArchitecture-Centered Information Systems In The Manufacturing Domain - Part II -
The Architecture
Process Featured Author - Glen B. Alleman - September 6 ...
|
|
| http:/.../Research/ResearchHighlights/ExecutiveView/2002/09/research_notes/GA_EV_GBA_09_06_02_1.asp - 19k - 2002-09-06 |
| Summary: 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
|
|
Tentative Unification in Server I/O Architecture Battle
| by R. Krause |
... ÿþTentative Unification in Server I/O Architecture Battle RA Krause -
September 3rd, 1999 Event Summary.
The Next Generation I/O ...
|
|
| http:/.../Research/ResearchHighlights/HardwareOS/1999/09/news_analysis/NA_HW_RAK_9_3_99_2.asp - 4k - 1999-09-03 |
| Summary: The Next Generation I/O (NGIO) and Future I/O groups have agreed to unify their efforts to develop the next I/O architecture.
|
|
Great Product: Too Bad The Architecture Doesn’t Fit
| by M. Reed |
... ÿþGreat Product: Too Bad The Architecture Doesn't Fit M. Reed - November
29, 2003 1. Introduction.
2. Subject. 3. Audience. Complete ...
|
|
| http:/.../Research/ResearchHighlights/DataWarehousing/2003/11/research_notes/TU_DW_MFR_11_29_03_1.asp - 14k - 2003-11-29 |
| Summary: During the process of product selection a great deal of attention is given to the functional capabilities of the software
being evaluated. While this aspect is obviously important, ignoring the technical mechanisms by which the software actually
operates can be fatal to a project. In this document we e
|
|
Architecture Evolution: From Mainframes to Service-oriented ...
| by P.J. Jakovljevic |
... ÿþ Architecture Evolution: From Mainframes to Service-oriented Architecture
PJ Jakovljevic -
September 18, 2006. Software architecture ...
|
|
| http:/.../Research/ResearchHighlights/ERP/2006/09/research_notes/TU_ER_PJ_09_18_06_1.asp - 18k - 2006-09-18 |
| Summary: 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.
|
|
Product Architecture for Product Endurance?
| by P.J. Jakovljevic |
... ÿþ Product Architecture for Product Endurance? PJ Jakovljevic - September 30, 2005.
1. LANSA Target
Market. 2. LANSA 2005. 3. User Recommendations. ...
|
|
| http:/.../Research/ResearchHighlights/ERP/2005/09/research_notes/TN_ER_PJ_09_30_05_1.asp - 16k - 2005-09-30 |
| Summary: Product architecture can ensure product scalability, endurance, and the incorporation of emerging technologies. Consequently,
LANSA 2005 offers Web Application Modules (WAM), to give developers a shorter learning curve and lower development costs to
produce browser-based commercial enterprise application
|
|
Delivery Architecture - What it Means...
| by Lucy West |
... ÿþ Delivery Architecture - What it Means... Featured ... Performance. These will
be prerequisites
for understanding the delivery architecture. ...
|
|
| http:/.../Research/ResearchHighlights/Scm/2005/06/research_notes/TN_SC_XLW_06_28_05_1.asp - 19k - 2005-06-28 |
| Summary: Once we cross the border of the enterprise, traditional enterprise-centric systems fail to provide visibility or a way to
understand and act, all in sync with our supply chain partners. This is why the delivery architecture of an application is
critical, especially for addressing multi-enterprise intera
|
|
Architecture-Centered Information Systems In The Manufacturing ...
| by Glen B. Alleman |
... ÿþArchitecture-Centered Information Systems In The Manufacturing Domain - Part V -
Applying the Methodology
Featured Author - Glen B. Alleman - September 19 ...
|
|
| http:/.../Research/ResearchHighlights/ExecutiveView/2002/09/research_notes/GA_EV_GBA_09_19_02_1.asp - 31k - 2002-09-19 |
| Summary: 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
|
|
Architecture-Centered Information Systems In The Manufacturing ...
| by Glen B. Alleman |
... ÿþArchitecture-Centered Information Systems In The Manufacturing Domain - Part IV -
Moving From Planning
to Implementation Featured Author - Glen B. Alleman ...
|
|
| http:/.../Research/ResearchHighlights/ExecutiveView/2002/09/research_notes/GA_EV_GBA_09_13_02_1.asp - 30k - 2002-09-13 |
| Summary: 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
|
|
Architecture Evolution: From Web-based to Service-oriented ...
| by P.J. Jakovljevic |
... ÿþ Architecture Evolution: From Web-based to Service-oriented Architecture PJ
Jakovljevic - September
19, 2006. Extending Applications to the Web. ...
|
|
| http:/.../Research/ResearchHighlights/ERP/2006/09/research_notes/TU_ER_PJ_09_19_06_1.asp - 22k - 2006-09-19 |
| Summary: 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.
|
|
CART 
