| |
Decision Support Systems, Vol. 45, No. 1. (2008), pp. 164-179.
Abstract
Knowledge management at an organisational level can only be brought into practice if a corporate memory is defined. Unfortunately, at this moment there is no complete and procedural specification on how to build it. This paper presents a complete and generic knowledge representation scheme that makes it possible to conceptualise/represent the knowledge of any domain in a systematic way, guiding the definition of a corporate memory and allowing us to reach a more procedural level in knowledge management discipline. The conclusions ...
|
| |
Reliability Engineering & System Safety, Vol. 92, No. 7. (July 2007), pp. 902-913.
Abstract
Failure can be a major driver for the advance of any engineering discipline and Software Engineering is no exception. But failures are useful only if lessons are learned from them. In this article we aim to make a strong defence of, and set the requirements for, lessons learned systems for safety-critical software. We also present a prototype lessons learned system that includes many of the features discussed here. We emphasize that, apart from individual organizations, lessons learned systems should target industrial ...
|
| |
Information and Software Technology, Vol. 46, No. 10. (August 2004), pp. 635-649.
Abstract
The first step towards developing quality software is to conceptually model the problem raised in its own context. Software engineering, however, has traditionally focused on implementation concepts, and has paid little or no attention to the problem domain. This paper presents a generic methodological framework to guide conceptual modelling, focusing on the problem within its domain. This framework is defined considering aspects related to a generic conceptualisation, and its application to software engineering--illustrated using the IFIP Case--achieves the called-for problem-sensitivity. ...
|
| |
Journal of Research and Practice in Information Technology, Vol. 36, No. 4. (Nov 2004), pp. 295-315.
|
| |
Knowledge-Based Systems, Vol. 11, No. 2. (12 October 1998), pp. 87-104.
Abstract
After many years of stressing the importance of the product and the process in software development, emphasis has now switched to the role played by the person. This paper, however, underlines the importance of understanding and modelling the problem, as this is a necessary, and often sufficient, condition for developing good quality software. Firstly, a formal definition is given of what the problem is and how it can be classified. In view of the confusion in the field of software development, ...
|
| |
Information and Software Technology, Vol. 48, No. 7. (July 2006), pp. 517-531.
Abstract
A conceptual modelling language should provide constructors that can be used to represent the conceptualisation of a problem considering the problem domain. However, software engineering has traditionally focused on implementation concepts.This paper considers the appropriate generic conceptualisation theoretical aspects to identify the conceptual elements for which constructors have to be provided in a problem-sensitive conceptual modelling language. These elements match the formal definition of any conceptualisation and are derived from natural language. By looking at these elements, we have defined a ...
|
| |
|
| |
In Knowledge Engineering and Knowledge Management. Lecture Notes in Artificial Intelligence 2473 (2002), pp. 102-107.
|
| |
Int. Journal of Human-Computer Studies, Vol. 51 (1999), pp. 757-781.
|
| |
IEEE Transactions on Software Engineering,, Vol. 30, No. 5. (2004), pp. 282-294.
Abstract
To solve any nontrivial problem, it first needs to be conceptualized, taking into account the individual who has the problem. However, a problem is generally associated with more than one individual, as is usually the case in software development. Therefore, this process has to take into account different viewpoints about the problem and any discrepancies that could arise as a result. Traditionally, conceptualization in software engineering has omitted the different viewpoints that the individuals may have of the problem and has ...
|