Many object-oriented information systems share an architectural style that emphasizes flexibility and run-time adaptability. Business rules are stored externally to the program such as in a database or XML files instead of in code. The object model that the user cares about is part of the database, and the object model of the code is just an interpreter of the users' object model. We call these systems "Adaptive Object-Models", because the users' object model is interpreted at runtime and canbe changed with immediate (but controlled) effects on the system interpreting it. The real power in Adaptive Object-Models is that they have a definition of a domain model and rules for its integrity and can be configured by domain exports external to the execution of the program.This paper describes the Adaptive Object-Model architecture along with its strengths and weaknesses. It illustrates the Adaptive Object-Model architectural style by describing a framework for Medical Observations (following Fowler's Analysis Patterns) that we built.
In this paper we present an architecture to manipulate object topologies and field-oriented data. We first show how to extend the object oriented model presented in [5] by defining an extended location micro-arquitecture; next we explain how we use extended locations to define a set of structures and operations to manipulate different kinds of vector based topologies such as Node and ArcNode topologies. We then present the object-oriented architecture for dealing with field data; we show how this architecture alIows us to decouple data belonging to a continuous field from corresponding samples, their implementations and the estimation methods used to calculate points in the corresponding field. We finally discuss present some further work on implementing this architecture.
In this paper we show the impact of Design Patterns in the generation of the software architecture underlying a GIS application. We first discuss the problem of adding spatial features to Iegacy object oriented applications, then we present three Design Patterns specific to this domain: Reference System, Roles and Appearances to illustrate our claims.We introduce Design Patterns as a conceptual tool both, to record design experience and to support evolvable design micro-architectures, and describe the previously mentioned patterns, exemplifying their use within the design of GIS applications. Finally, we discuss some further issues in our research. l-IntroductionThe complexity of the underlying domains of GIS applications, the variety of data types including spatial data and sophisticated relationships and the strong need of performance and accuracy in the final product, usually lead the GIS design task as a process closer to the implementation than to a software engineering process.However, expert GIS designers do not solve every problem from scratch. Most of the time they reuse previous solutions to solve similar problems. But this reuse of experiences is difficult to transmit to non-expert designers and therefore, lacking an adequate procedure to record experience, the sharing of knowledge is not effective in helping the designer to reason in term of GIS structures; critical design decisions, such as relationships between spatial features and conceptual ones remain hidden in the code or are poorly documented. Many other decisions cannot be even deduced from either code or documentation. These strategies of reuse are caged in the designer's mind.The problem of reusing design in GIS applications has become also a need because in the last times, more and more users are building GIS applications based on open systems instead of using a particular GIS product (like ARCInfo, GENAMAP, etc). The rapid growing of the WWW as a host for different kind of applications and the emergence of Java as an object-oriented programming language well suited for developing efficient, distributed applications, also shows us the need to find a systematic approach for reusing design experience in the context of GIS applications. This is particularly true when a designer must face hybrid applications dealing with conventional transactionbased systems and must be upgraded to incIude spatial features that are not built in the underlying software.Permission to mnke digital/hard copies ol'all or p:u~ ofthis material for personnl or clnssroom use is grmkd without fee provided that the copies are 1101 made or distributed liar prolit or comlcrcinl ndvantny. lhr copyright notice. the title ofthe publication and its date nppenr, and tloticu is given lhnt copyrighl is by pcnnissio~l ofthe ACM. Inc. To copy olhenvise, to republish. IO posl 011 swvcm or IO rcdislrihrlc to IisLx rcquiresspccific pernlissio~~ sndlor Ite. GlS 97 Lmvegl7s iveI'c7dr7 11,Y.l Copyright 1997 ACM I-5X113-017-l/97/1 l.XI.50Examples of solutions extending traditional applicat...
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.