Browse Prior Art Database

Building a Personalized Project Knowledge Portfolio using a Knowledge Acquisition Tool Disclosure Number: IPCOM000240865D
Publication Date: 2015-Mar-06
Document File: 6 page(s) / 124K

Publishing Venue

The Prior Art Database


Disclosed is a Knowledge Acquisition Tool that offers an efficient system to provide software development team members with personalized project knowledge portfolios that contain requisite information related to a project. Use of the portfolio accelerates the user’s ability to acquire project-specific knowledge and contribute to the project in a technical capacity with minimal initial support.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 30% of the total text.

Page 01 of 6

Building a Personalized Project Knowledge Portfolio using a Knowledge Acquisition Tool

Software development projects contain a proliferation of information that is scattered across knowledge artifacts. These knowledge artifacts include, but are not limited to, project management stories and tasks that might reside in a database associated with a project tool, source code and comments, engineering specification and internal documents, project information on wikis, and open source code and other documentation located on various websites.

Currently, team members (e.g., new hires, current staff, interns, etc.) assigned to a software project either do not have access to a software development project's knowledge artifacts or these knowledge artifacts are scattered, preventing team members from efficiently acquiring the necessary knowledge. This makes team members less effective in providing technical contributions to a software project and increases the time needed to become familiar with the project.

In one example of problems with the current state of the art, a new technical writer is assigned to a software development project that uses Java* to develop the product. The technical writer has access to the software development environment's knowledge artifacts, which include wikis, source code, engineering specifications, Agile stories and tasks, and more. However, the knowledge artifacts are so scattered that it is difficult for the technical writer to acquire the understanding necessary to effectively write the documentation for the different topics. In addition, the technical writer requires a significant amount of time to acquire this understanding, which can inhibit progress. Other project team members are busy with respective assigned tasks, and do not have time to direct the technical writer to all of the knowledge artifacts required to technically contribute to the product in development. For example, the technical writer, due to this scattered information, misses the connection between the product's delivering of a log4j properties file and the

fact that log4j is a Java-based logging utility originally written by Ceki Gulcu and is now a project of the Apache Software Foundation. Not having this bit of knowledge, the writer cannot even pose relevant questions to the developers. Lacking this understanding causes the technical writer to be less effective at communicating the log4J properties file created by the software development team for the product in development. In addition, the time taken to perform the appropriate background work to acquire this knowledge increases the time between learning and technical contribution.

For a company that develops complex software products, an efficient system is needed to convey requisite information to project staff with minimal support.

The disclosed system relates to the field of knowledge discovery. The novel contribution is a Knowledge Acquisition Tool that provides team members wit...