Location of Repository

From Documents to Applications via Frameworks: the Tools and Materials approach

By Martin Lippert, Stefan Roock and Heinz Züllighoven

Abstract

respondence between the model of core application concepts and the software architecture. This structural similarity enhances maintainability, extensibility and other aspects of quality. 3 A DOCUMENT-DRIVEN APPROACH To guide the developer through the process, we use several design metaphors: Tools, Materials, Automata and the Work Environment. They help us to analyze the application domain and build a bridge from the application domain via object-oriented design to the technical implementation of the software system. The approach is document-driven. Starting a new development cycle within an evolutionary process, we use a number of documents to analyze and mainly to understand the application domain. These documents are critically reviewed and revised in an author/critic cycle. Scenarios (corresponding to the Business Use Cases of the Unified Approach [4]) and glossaries are the documents of choice for describing the current work situation. A system vision (corresponding to Use Cas

Year: 2007
OAI identifier: oai:CiteSeerX.psu:10.1.1.19.4373
Provided by: CiteSeerX
Download PDF:
Sorry, we are unable to provide the full text but you may find it at the following location(s):
  • http://citeseerx.ist.psu.edu/v... (external link)
  • http://swt-www.informatik.uni-... (external link)
  • Suggested articles


    To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.