|
ABSTRACT
One of the main reasons why the development of software does not meet the client's need is the lack of understanding of the software's real objective, and consequently, the tasks it should perform and how they should be performed. With this assumption, we have defined a structure to represent the task knowledge which supports software engineers in understanding problems starting from the understanding of the tasks which comprise these problems. This structure combines task ontologies and problem solving methods, providing the developer with the necessary task knowledge to guide him throughout the development process. This article shows how task knowledge is defined and used to help the development of software, presenting as an example, use cases modeling.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
|
| |
2
|
Oliveira, K. M., Rocha, A. R., Travassos, G. H., Menezes, C., 1999, "Using Domain-Knowledge in Software Development Environments", In: Proceedings of Software Engineering and Knowledge Engineering; pp 180-187, Kaiserlautern, Germany, Jun.
|
| |
3
|
|
| |
4
|
Oliveira, K. M., Rocha, A. R., Travassos, G. H., 1999, "A Domain-Oriented Software Development Environment for Cardiology", In: Proceedings of America Medical Informatics Association conference. pp 1113, Washington, D.C., Nov.
|
| |
5
|
Oliveira, K. M., Galotta, C., Rocha, A. R. et al., 1999, "Defining and Building Domain-Oriented Software Development Environments", In: 12th International Conference of Software & Systems Engineering and their ApplicationsICSSEA'99 --- CNAM, Paris, France, December.
|
| |
6
|
Villela, K., Zlot, F., Santos, G., et al, 2001, "Knowledge Management in Software Development Environments", 14th International Conference on Software & Systems Engineering and their Applications; Paris, France, December.
|
| |
7
|
Mizoguchi, R., Vanwelkenhuysen, J., Ikeda, M., 1995, Task Ontology for Reuse of Problem Solving Knowledge. N. J. I Mars, Ed. IOS Press 1995.
|
| |
8
|
|
| |
9
|
|
| |
10
|
Tautz, C., Althoff, H., 2000, A Case Study on Engineering Ontologies and Related Processes for Sharing Software Engineering Experience. SEKE 2000, pp.318-327.
|
| |
11
|
Chandrasekaran, B., Josephson, J. R., Benjamins, V., 1998, The Ontology of Tasks and Methods. In Proceedings of KAW' 98, Eleventh Workshop on Knowledge Acquisition, Modeling and Management, Alberta, Canada, April 1998.
|
| |
12
|
Mizoguchi, R., Sinitsa, K., Ikeda, M., 1996. Task Ontology Design for Intelligent Educational/Training Systems. Position Paper for ITS' 96 Workshop on Architectures and Methods for Designing Cost-Effective and Reusable ITSs, pp.l-21, 1996.
|
| |
13
|
Schreiber, G., Wielinga, B., Breuker, J., 1993, KADS: A Principled Approach to Knowledge-Based System Development, Academic Press, London.
|
| |
14
|
Marcus, S., 1988. SALT: A Knowledge Acquisition Tool for Propose-and-Revise Systems. In Marcus, S., editor, Automating Knowledge Acquisition for Expert Systems, pages 81-123. Boston: Kluwer Academic Publishers.
|
| |
15
|
Coelho, E., Lapalme, G., 1996, Describing Reusable Problem Solving Methods with a Method Ontology. In Gaines, B. R. & Musen, M. A., editors, Proceedings of the 10th Banff Knowledge Acquisition for Knowledge-Based Systems Workshop, pp. 3.1{3.20, Alberta, Canada. SRDG Publications, University of Calgary.
|
| |
16
|
|
|