This is natural, given that often the potential
users of a DSM solution are competitors working in the same domain and producing
similar kinds of applications. Why would any organization want to help a competitor
create better quality products faster? Making aDSM solution available for others also
requires extra resources and knowledge, which is not initially available in a company
focused on improving its internal software development efforts.
There are some situations, though, where companies want to make their internally
developed DSM solutions publicly available. First, a company outsourcing its
34 BUSINESS VALUE
application development efforts usually wants its subcontractors to work with its
existing DSM solution and tools. While the DSM solution is shared, it is not usually
made available for changes. A second well-known situation for publishing a DSM
solution is when it makes using an underlying platform easier or more palatable for a
larger number of developers. For example, in the embedded area, it is very common
for hardware manufacturers to provide tooling to develop features on top of their
target platform.
A third case covers initiatives, usually inside a vertical domain, that create
standards in terms of metamodels. These are aimed at improving communication and
information exchange and lowering the cost of entry to create competition.
Pages:
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88