Q

Should we consider a custom system architecture design?

A custom system design can pose unique challenges. Learn why and and find out the difference between a customized and non-customized system architecture design in this tip.

Does architecture matter when crafting a project plan?
Absolutely. "Vanilla" or non-customized system architecture design approaches are much easier to configure, test and ultimately deploy. Creative configurations that call for " spaghetti architecture" (such as two of the case studies in my book Why New Systems Fail: Theory and Practice Collide) are much more costly, difficult to test and likely to have unforeseen consequences and issues. As a general rule, increasing the number of customizations in a system architecture design increases the time and/or resources needed for the project to be successful.
This was last published in June 2009

Dig Deeper on SOA data services and architecture

PRO+

Content

Find more PRO+ content and other member only offers, here.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchAWS

SearchContentManagement

SearchOracle

SearchSAP

SearchSOA

SearchSQLServer

Close