Case-method: a methodology for building large-scale case-based systems

Authors:
Hiroaki Kitano;Hideo Shimazu;Akihiro Shibata
Affiliations:
Case Systems Laboratory, NEC Corporation, Tokyo, Japan;C&C Information Technology Research Laboratories, NEC Corporation, Kawasaki, Japan;C&C Information Technology Research Laboratories, NEC Corporation, Kawasaki, Japan
Venue:
AAAI'93 Proceedings of the eleventh national conference on Artificial intelligence
Year:
1993

Citing 9
Cited 0

Structured systems analysis and design method: application and context

Structured systems analysis and design method: application and context
Managing the software process

Managing the software process
C4.5: programs for machine learning

C4.5: programs for machine learning
Strategic Information Systems

Strategic Information Systems
Inside Case-Based Reasoning

Inside Case-Based Reasoning
Applying Case-Based Reasoning to Autoclave Loading

IEEE Expert: Intelligent Systems and Their Applications
Case-based planning: an integrated theory of planning, learning and memory

Case-based planning: an integrated theory of planning, learning and memory
Design tool combining keyword analyzer and case-based parser for developing natural language database interfaces

COLING '92 Proceedings of the 14th conference on Computational linguistics - Volume 2
Retrieving cases from relational data-bases: another stride towards corporate-wide case-base systems

IJCAI'93 Proceedings of the 13th international joint conference on Artifical intelligence - Volume 2

Quantified Score

Hi-index	0.00

Visualization

Abstract

Developing large-scale systems are major efforts which require careful planning and solid methodological foundations. This paper describes CASE-METHOD, the methodology for building large-scale case-based systems. CASEMETHOD defines the procedure which managers, engineers, and domain experts should follow in developing case-based systems, and provides a set of supporting tools. An empirical study shows that the use of CASE-METHOD attains significant workload reduction in system development and maintenance (more than 1/12) as well as qualitative change in corporate activities.