Re-usability and simplicity compliment each other to a certain level of granularity within the organization.
1 Re-usability will bring in required simplicity at an Enterprise level. When it comes to systems level, it becomes more tactical.
2 Re-usability and simplicity compliment each other to a certain level of granularity within the organization.
3 Knows when to reuse and when not to reuse: where it may be bad, where there may be risks, but also where, if appropriately mitigated the reuse could be good.
4 Reuse is about creating simple building blocks that can be applied over and over to minimize design cost and maximize value over the Lifecycle.
5 If we want to build reusable component, we must define all the reuse cases at the design level and build this component based on it, focused on real reusable cases instead of building something in a generic way and hoping that it could be reused later.
6 Architecture needs to play a significant role in orchestrating reusability, agility and flexibility, to craft more cohesive business capabilities, value/cost/risk analysis needs to be done more coherently.
7 Reuse of existing people, processes, locations, systems, services, data, applications and technology will always be considered first in the provision of any service to the Business Rationale.
8 Reuse is useful, but it must be done intelligently. To be effectively used, one must also learn from the past. Not only should we question the applicability of a component for re-use, but we need to capture and analyze the lessons learned from the previous applications of the component.
9 The art of reusability is about architectural design thinking and strategic planning; the science of reusability is related to governance and in-depth analysis & calculation, to achieve business results such as cost effectiveness & productivity, and good for business' long term development.
0 comments:
Post a Comment