We J2EE architects must care for simple architecture; few things might help do develop application which are long lasting and easy to accommodate future requirements.
For example; I tried with followings
1) Care for OO rather than standards/specifications
2) Create architecture against requirements in hand rather than technology specific
3) Do not distribute objects if requirements are not called for
4) Follow good architecture and design principles rather than just following patterns
5) Leverage on lightweight architecture like Spring centric which greatly helps in interface driven programming, container level capabilities, test strategies
6) Follow thought full analysis of business requirements and come up with list of high level components, its responsibilities and associated rationale
7) Follow whiteboard driven architectures to kick start the discussion
Care for executable architecture (RUP), spike resolution (XP) and vertical slicing to get confidence in the architecture
8) Come up with list of development standards, guidelines and implementation classes
Subscribe to:
Post Comments (Atom)
One new learning / day - however small it is
Read a blog / or article Watch TED talk Read a small self-help book (many free eBooks available with less than 100 pages/can be completed i...
-
It is often found that, many people adopt agile development process for quicker delivery. But it is thorough bad idea, with out understandin...
-
I underwent TOGAF 8.1.1/9 training and certification program in last week of sept'09. It was good experience and lot of knowledge gained...
-
What is the difference between software architecture and software design? In my view, software architecture is list of significant dec...
No comments:
Post a Comment