Skip to main content
Home / Failure and Lessons Learned in Information Technology Management, Volume 1, Number 2

Domain-Oriented Design Environments: Knowledge-Based Systems for the Real World

Buy Article:

$30.00 + tax (Refund Policy)

Over the last 10 years we have created a theoretical framework for domain-oriented design environments (DODEs), developed several prototypes and assessed them in real-world settings. DODEs are knowledge-based systems that emphasize a human-centered and domain-oriented approach. Used as intelligent support systems, they facilitate collaboration and communication among humans as well as between humans and their computational environments to create more useful and usable artifacts. In this article we discuss a component architecture (the multifaceted architecture) and a process model (the seeding, evolutionary growth, reseeding model) underlying DODEs by focusing specifically on their support for evolution. We describe two of the applications developed for voice dialogue and computer network design, and we discuss our experience with the DODE approach derived from real-world uses in collaboration with companies and communities of practice.

Keywords: DOMAIN-ORIENTED DESIGN; DOMAIN-ORIENTED DESIGN ENVIRONMENTS; END USER MODIFICATION; EVOLUTION; ORGANIZATIONAL LEARNING AND ORGANIZATIONAL MEMORY

Document Type: Research Article

Publication date: 01 June 1997

More about this publication?
  • Most people learn more from failures than from successes. In information technology management, many lessons have been learned over the years "the hard way" through failed implementations, poor management practices, technology limitations, and the like. Failure & Lessons Learned in Information Technology Management is devoted to addressing failures of and lessons learned from information technology projects in business, universities, government, and the military that did not succeed due to technology, management, organizational, social, cultural, and other issues. The goal is to learn from these cases and understand the basis of decisions made in order to not recreate the same mistakes or "reinvent the wheel." The organizational names in the articles can be protected by using pseudonyms.

Share Content

  • Access Key
  • Free content
  • Partial Free content
  • New content
  • Open access content
  • Partial Open access content
  • Subscribed content
  • Partial Subscribed content
  • Free trial content