Collaborative problem solving and groupware for software development

Abstract When a group is working together toward a common goal, communication and collaboration are key. Access to Document Link to publication in Scopus. Link to citation list in Scopus.

Fingerprint Dive into the research topics of 'Collaborative problem solving and groupware for software development'. Together they form a unique fingerprint. View full fingerprint. AB - Teamwork is always challenging. Collaborative software development: A discussion of problem solving models and groupware technologies.

Overview Fingerprint. Abstract Teamwork is always challenging. Access to Document Link to publication in Scopus. Link to citation list in Scopus. Fingerprint Dive into the research topics of 'Collaborative software development: A discussion of problem solving models and groupware technologies'. SOLVEIT provides a set of tools geographically separated users to work that are associated with a six-stage process for problem together on a large programming project [31]. The primary goal of the system is to allow beginning programmers to collaborate when 4.

Group Cognition and Psychology designing software. Requirement elicitation is the context used to teach collaboration, the Group Cognition and Psychology need to be objective being to develop a requirements considered when developing any type of groupware or document for a software problem.

There are VTS. A groupware system should use automation to four shared tools: Procedural activity, to accelerate collaborative thinking, consensus building, establish operating procedures via a voting decision making, and planning [21] [22]. Cognitive processes are a major attribute of establishment, to enter criteria for individual problem solving and program development requirements; and solution activity, to [3].

Group problem solving also needs to take into establish a priority for requirements via the consider the human cognitive activities involved in voting tool.

Cognitive activities within a group The Evolving Artifact EVA is a are different and more involved than the cognitive collaborative tool that supports software activities of one individual solving a problem alone development. Developers use this system to [11]. This is because one must consider not only the understand problems and develop solutions. Stacy and Macmillian have studied This system uses a hypertext environment cognitive biases in the area software engineering. Their the belief being that access to a combination findings suggest the following three recommendations of prototypes and documentation increases to eliminate common failure among software engineers: problem understanding.

Nosek also It emphasizes integration of the semantics of explored this research area and developed a theory of the software development domain with group cognition. Analysis Zhang indicates that collaborative problem solving should not have explicit steps and thus This section provides an analysis of the methodology highlights four steps that must be the models and tools presented earlier.

The included when collaboratively solving problems. These models will be evaluated to determine the steps are similar to what other models already include, kind of collaborative skills and knowledge such as breaking the problem down into individual they require for the tasks of group problem representations.

However, coordination among group solving. The tools will then be evaluated to members is also not emphasized here. Lack of examine their support for collaborative coordination could lead to failure in integrating the problem solving and, where appropriate, their modules developed by each team member [17].

Additionally, all of the reviewed models emphasize the importance of developing and monitoring the group 5. Methodology dynamics. The next section examines the tools we have reviewed. Coordination in that assists in the kind of coordinated problem solving software development is where a group of efforts required in software development.

However, developers agree to a common definition of collaborative software development requires specific what they are building, share information, problem solving support including features or and integrate their activities [17]. Conflict guidelines that enhance group cognitive activities for resolution mechanism is also missing in this collaborative solving problems, and explicit guidance model.

This would involve the negotiation of and tools for the problem solving and program activities when determining solution development process, which Groove was not intended alternatives. Setting specific guidelines for to explicitly support. For example, the brainstorming team interaction in collaborative problem tool provided in Groove allows users to rank ideas, but solving is important.

When group activities does not provide an explicit mechanism for voting or are not properly channeled and coordinated, other methods or tools for facilitation consensus.

But this method is also lacking tools for real time or asynchronous collaboration a framework for coordination of activities activities. The coordinating features only assist in the between the group members as well as problem solving and design efforts of software stressing the iterative process involved in development. More collaboration tools are necessary problem solving. Team interaction is not to successfully collaborate when problem solving in the taken into consideration either in this model.

This method, for example, activities for collaboratively solving problems. In recognizes that there is a need to account for addition, explicit guidance and tools are needed for the the fact that group communication changes group problem solving and program development every time a member is added to the team.

Additional tools to facilitate explicit group problem solving process since activities such as brainstorming, voting, task Hohmann indicates that the individual identification, task distribution, etc are needed. GroupSystems is an excellent collaborative Conflict resolution is also not apparent in this tool. Its main goal is to support mission-critical model. Managing requirements can help to features required to collaboratively solve a minimize these kinds of problems.

Requisite pro is an software problem. For example, it has a extensive application to manage project requirements. Obviously there is not a step-by- asynchronous communication capabilities but only step process to guide the team through some include synchronous communication features. The development tasks but all of the tools needed asynchronous mode allows group members to join a to facilitate each aspect of collaborative problem solving session at various times, either by problem solving and software development design or necessity, and because of archived entries be process is certainly available in the able to develop an understanding and familiarity with GroupSystems tool.

Comparing it to other the progress. Of course, having both modes seems feature, calendar, web browsing, and a task most beneficial. We-Met is one tool supporting list. However, the features contained in synchronous interactions but supports only a limited GroupSystems have much more of an impact range of collaborative features: meeting discussions, on the collaborative problem solving and brainstorming, and collaboration archiving.

Though it software development process then the has been used as a problem solving tools, it does not features it is missing. DCSS, on Rose is a good development tool that the other hand, provides an interesting problem solving has a main focus of visual modeling.

But the Rational claims that visual modeling shortens system does not support conflict resolution among the development life cycle as well as group members, such as might occur during increases productivity, improves software consideration of design alternatives. Like We-Met, quality and team communication.

Team DCSS provides no overall problem solving framework communication could very well be increased and neither was developed to support software but only by team members sharing various development tasks. In other Some of the tools we reviewed provide words, team communication is increased specific support for software development. CSCT is a because of using a common modeling collaborative tool that features synchronous language.

There is no provision to communication, with the main objective being to communicate via the tool. Hence there are no facilitate requirement elicitation for software messaging, brainstorming, voting tools development. This tool does not provide any other integrated into the Rose tool.

Therefore, it facilities to support the rest of the software process. In is already assumed that the initial problem addition, the absence of an asynchronous solving stage is complete when Rose is used. The main implementation stage of development.

Problem solving groupware application for requirement facilities are not included. In other words, the user is forced development process documentation. Even though, this to either have exclusive rights to modify tool does not assist in solving problems or developing entire project or just read only access.

The software, it provides suggestions based on a repository feature that positively balances the exclusive of designs. CoNeX is a very rich environment for rights problem is the discussion tool.