Process-Based Knowledge Management Support for Software by Harald Holz

By Harald Holz

Show description

Read Online or Download Process-Based Knowledge Management Support for Software Engineering PDF

Similar management information systems books

Outsourcing Management Information Systems

This booklet balances the confident results of outsourcing, that have made it a favored administration approach with the destructive to supply a extra inclusive determination; it explores threat elements that experience no longer but been broadly linked to this procedure. It makes a speciality of the conceptual "what", "why", and "where" elements of outsourcing in addition to the methodological "how" facets"

Design of Sustainable Product Life Cycles

Product lifestyles cycle layout – producing sustainable product lifestyles cycles explains the significance of a holistic long term making plans and administration method of attaining a greatest product gain over the full lifestyles cycle. The paradigm of pondering in product lifestyles cycles helps brands in shaping winning items.

Additional resources for Process-Based Knowledge Management Support for Software Engineering

Example text

As opposed to handling standard business processes), and 2. the inherently knowledge-intensive, creative nature of software development activities. g. g. PSL [SGT+00]) do not take this issue into account. 3 Shortcomings of SE Knowledge Management Approaches In particular, most existing approaches lack the concept of situation-specific information delivery. g. by the Experience Factory) or outside the organization in order to successfully perform their activities. g by providing process performers with to-do lists, and notifying them when new activities have been assigned to them, or when changes in products have occurred.

1). 3 Shortcomings of SE Knowledge Management Approaches Learning (QIP 5-6) Past experience Process requirements Process engineering Process model Project requirements Product requirements Project planning Project management & Software engineering (QIP 1-3) (QIP 4) Project plan Product Fig. 7: Dataflow between the three areas supported by a PSEE (adapted from [GJ96]). An initial process model is created during process engineering; this process model is supposed to be independent of particular projects.

If, however, a change in the project plan results in the substitution of RMI with another technology during the implementation activity, the information on RMI should no longer be offered to the performer, but should be replaced by information on the new technology. In particular, any information about known conflicts between the new technology and Serialization should be offered now to the programmer. An analysis of the shortcomings identified for Experience Bases and Process-Centred Software Engineering Environments reveals the possibility to address them by an appropriate integration of both approaches.

Download PDF sample

Rated 4.52 of 5 – based on 40 votes