Service- and Component-based Development: Using Select Perspective™ and UML
by Hedley Apperly, Ralph Hofman, Steve Latchem, Barry Maybank, Barry McGibbon, David Piper, Chris Simons
Acquire component
So what components and services will be useful? Where will they be acquired? The task of identifying business needs that can be fulfilled by components is essential prior to any acquisition; a good starting point for this identification is a review of current and future project needs in terms of:
common UI aspects across solutions;
recurring technical architecture themes, such as error handling;
specific business domains for common business concepts; and
commonality across business domains.
During this exercise a basic component classification, i.e. categorization of component types, is being established, e.g. user interface 'widget', technical, or business-specific such as human resources. To implement this basic classification ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access