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 first published in June 2009

Dig deeper on SOA data services and architecture

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

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.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

SearchBusinessAnalytics

SearchAWS

SearchContentManagement

SearchOracle

SearchSAP

SearchSOA

SearchSQLServer

Close