Employing a Horizontal Modeling View. The abstraction practice, also known as horizontal
practice, typically engages the cross-organization stakeholders that represent various silo operations
in the enterprise to collaborate on service-oriented modeling activities. Imagine how
beneficial it would be to involve representatives from different lines of business to discuss
how they can collaborate to foster asset reusability opportunities and to encourage functionality
redundancy and consolidation of future assets. They should also be able to identify mutual
organizational concerns and propose remedies that can be reused across the enterprise. Imagine
how advantageous it would be if these business and technological practitioners partner to meet
service interoperability challenges and to enable a holistic view of all modeling assets regardless
of their origin, geographic location, or empowering technologies.
Visualizing Abstraction Practice Process and Artifacts. Can the abstraction practice enable one
to visualize the activities and deliverables involved? Can concepts be visible? Indeed, concepts
are invisible entities. They originate from peoples??™ ideas and propositions. But the abstraction
process should be mechanical and well formulated, driven by a well-defined process and should
employ tools to enable visualization of intangible software assets. By ???mechanical,??? we mean that
the abstraction process employs conceptualization best practices that yield conceptual services,
which, despite their intangibility, are treated like the other valuable assets in an organization.
Pages:
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72