OSS Integration model

This goal model corresponds to the file oss integration_v2.1.istarml in the goal-model folder.

The OSS integration adoption strategy requires sharing and co-creation of OSS between the adopter and the OSS community (see Figure 3). This collaboration means a give and take to the benefit of all involved parties. For instance, the adopter might use existing OSS components that have been developed by the community, and pay back in terms of bug reports, patches, etc.

In this case, the adopter organization wants to benefit from co-creation (softgoal Benefit from co-creation taken); it is interested on being involved in the OSS community (softgoal OSS involvement) and on influencing it (softgoal OSS evolution influenced).

The task Integrate OSS Community is composed by the activities already required by the [acquisition strategy](OSS Acquisition model) complemented with additional activities that the adopter develops as part of its co-creation and collaboration with the community. These activities, grouped under the goal OSS Community Contributed, may be reporting bugs, developing and reporting patches or other forms of support such as sponsoring events. Dependencies stem out of these activities reflecting the collaboration with the community. For an advantageous co-creation, the contribution must be aligned to the OSS community culture, as represented by the softgoal According to OSS community practices. The activity Acquire management skills consisting on acquiring knowledge about the community contributes to it. A feature of the OSS integration adoption strategy is that the adopter organization relies partly on the successive releases of the OSS component for the maintenance of its product. Thus, the adopter organization might want to influence the community roadmap to ensure that successive releases of the OSS component follow its desired features. The softgoal OSS Comp Evolves towards Desired Features under the maintenance activity shows this dependency. The adopter organization defines its expectations for the evolution of the OSS component (Act-DECIDE-Wishlist). The community may eventually take this wishlist to decide its roadmap as represented by the dependency with dependum New feature request. The maintenance activity of the company also depends on the Quality of the evolved OSS component provided by the OSS community.