This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Automated Object Design: The Client-Server Case
February 1996 (vol. 29 no. 2)
pp. 62-66

As more enterprises move to client-server environments, object technology is gaining favor as a means of migrating legacy applications. The object paradigm is well suited for modeling real-world business processes and has the flexibility to integrate emerging technologies. However, the most difficult aspect of object-oriented applications development is not programming, but technical design. This activity involves an enormous amount of work and necessitates technical competence in development and in modeling. This article describes a methodology that formalizes and automates object-based technical design and is particularly useful in the domain of information management systems, which typically present technical designs susceptible to systematization. Developers using automated object design can continue to work at the conceptual level, with the best architectural choices being formalized by the rules and thus conditioning the methodology. This guarantees their systematic use by all developers, automates code production, and avoids having each developer repeat the difficult task of technical design. The methodology thus aims to promote strong productivity and maintainability, high-quality code, and systems independent of the underlying environment.

Citation:
Philippe Desfray, "Automated Object Design: The Client-Server Case," Computer, vol. 29, no. 2, pp. 62-66, Feb. 1996, doi:10.1109/2.485848
Usage of this product signifies your acceptance of the Terms of Use.