Think Holistically - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Government // Enterprise Architecture
Commentary
8/31/2008
12:00 AM
Commentary
Commentary
Commentary
50%
50%

Think Holistically

Software architecture is not a three-layer diagram -- UI/Business logic/Data. As an architect, you need to consider the project/solution at hand from a lot of different angles and take care for all sorts of concerns from the technical, team, managerial, and event esoteric ones.

Software architecture is not a three-layer diagram -- UI/Business logic/Data. As an architect, you need to consider the project/solution at hand from a lot of different angles and take care for all sorts of concerns from the technical, team, managerial, and event esoteric ones.

  • Technical- you need to consider things like threading models, data flow data structure, testability, security , user interface. A solution is only as strong as its weakest link. If the UI is great but the system is not stable, you will fail. If the system scales well but the security is flawed,  you will fail.
  • Team - You have to understand the limitations and capabilities of your teams and thier structure. If everybody knows Cobol, maybe Rails is not a good option. if the teams are spread out geographically, you need to make sure you partition the system into chunks that will allow them to progress independently as possible.
  • Managerial - brings to the forefront things like "What's the budget for the project?", "How much time do we have?" so can you really plan on using a rule engine if it eats 80% of your budget (maybe ?). Can you plan a cool piece of infrastructure if it will take four months to build?
  • Esoteric - Sometimes you even need to consider the less than common stuff. There aren't general examples here since its, well, esoteric. A couple of examples I've seen include a project where we had to see how much power the hardware we use needs (since it was to be deployed on a truck) or on another project where we designed a multi-monitor UI we had to figure out if it is better to design the UI for side-by-side or one atop the other
You should note that most probably you will not be able to be master of all the needed domains. you do need to be aware that they exist and work with other experts to cover the other bases of the solution.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

Commentary
New Storage Trends Promise to Help Enterprises Handle a Data Avalanche
John Edwards, Technology Journalist & Author,  4/1/2021
Slideshows
11 Things IT Professionals Wish They Knew Earlier in Their Careers
Lisa Morgan, Freelance Writer,  4/6/2021
Commentary
How to Submit a Column to InformationWeek
InformationWeek Staff 4/9/2021
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
Successful Strategies for Digital Transformation
Download this report to learn about the latest technologies and best practices or ensuring a successful transition from outdated business transformation tactics.
Slideshows
Flash Poll