• Summary
• Related Documents
  • Active Bibliography
  • Co-citation
• Version History

Abstract:

(2) In Merlin a workspace represents a personal view of a specific developer on a common repository, which stores the entirety of all software objects in a software development project. Depending on the users identity, role and access rights his/her workspace includes all documents and relations that are necessary to perform his/her specific task. In Merlin a workspace is represented to the user in a hypertext-like manner. (3) The notion of a view implies that a software object may appear in workspaces of different users at the same time. Modifications are immediately propagated to all other users with the modified object in their workspaces. This is in contrast to other approaches (e.g. COO, ADELE) which implement workspaces as subordinate databases using check out and check in functionality (cf. Section 5.4.). (4) However, if two or more developers need to access the same software object concurrently in isolation different versions of this object are created. The Merlin Version Management component offers means to merge different versions to reobtain a new common version of the particular software object. (5) Transactions may be initiated by a user in correspondence to his/her workspace, e.g. the user may start a working context transaction (wcCP) 1 to control all activities performed to 1. Cf. the definition of process transaction and cooperation patterns in Section 5.9.2.2

Citations