Joint application development (2nd ed.)
Joint application development (2nd ed.)
Software project management
Harvard Business Review on Knowledge Management
Harvard Business Review on Knowledge Management
Surfacing Tacit Knowledge in Requirements Negotiation: Experiences Using Easy Win Win
HICSS '01 Proceedings of the 34th Annual Hawaii International Conference on System Sciences ( HICSS-34)-Volume 1 - Volume 1
Collecting commonsense experiences
Proceedings of the 2nd international conference on Knowledge capture
Collecting commonsense experiences
Proceedings of the 2nd international conference on Knowledge capture
Knowledge-Sharing Issues in Experimental Software Engineering
Empirical Software Engineering
The Tyranny of Tacit Knowledge: What Artificial Intelligence Tells us About Knowledge Representation
HICSS '05 Proceedings of the Proceedings of the 38th Annual Hawaii International Conference on System Sciences - Volume 08
Generating testable hypotheses from tacit knowledge for high productivity computing
Proceedings of the second international workshop on Software engineering for high performance computing system applications
Knowledge Management Revisited
IEEE Intelligent Systems
Capturing software-engineering tacit knowledge
ECC'08 Proceedings of the 2nd conference on European computing conference
Software Engineering: A Practitioner's Approach
Software Engineering: A Practitioner's Approach
A Model of Tacit Knowledge and Action
CSE '09 Proceedings of the 2009 International Conference on Computational Science and Engineering - Volume 04
IEEE Transactions on Information Technology in Biomedicine
| Hi-index | 0.00 |
Software maintenance represents one of the most challenging tasks for software engineers. This can be attributed to many problems related to how software applications are built. However, the lack of enough historical knowledge about legacy software projects is a major software maintenance issue. Though software documentation is heavily used to guide maintainers tasks, but it only cater for documented experience knowledge in the form of diagrams, code, test cases, etc. On the other hand valuable experience knowledge can not be recalled simply because it is implicitly embedded in the minds of expert software engineers. This includes views, assumptions, and observations made as part of managing legacy software projects. The lack of such valuable experience knowledge during software maintenance would certainly lead to misinterpretations and wrong assumptions about the software being maintained. Within the software lifecycle, software requirements phase accommodates extensive expert deliberations. This represents a major source of software tacit or undocumented knowledge. Capturing tacit knowledge in the form of requirements rationale is expected to provide greater help for software maintainers to understand the complexity of the software application being maintained. This paper presents an approach for capturing experts' tacit knowledge. It is aimed to provide the ability to capture requirements tacit knowledge resulted from the collaborative requirements verification and validation.