Welcome!
To use the personalized features of this site, please log in or register.
If you have forgotten your username or password, we can help.
|
 |
Purpose: Between Types and Code
| |
|
Purpose: Between Types and Code
Natalia Romero6 , María José Presso6 , Verónica Argañaraz6 , Gabriel Baum6 and Máximo Prieto6 
| (6) |
LIFTA, Departamento de Informática, Universidad Nacional de La Plata C.C. 11, La Plata, Argentina |
Abstract
The quality of software architectures is highly related to the easiness of evolution and maintenance of the system. Meyer
says that ‘Those (quality factors) for which current software is most badly in need of better methods, and which the object-oriented
method directly addresses, are the safety-related factors correctness and robustness, together known as reliability, and the
factors requiring more decentralised software architectures: reusability and extendibility, together known as modularity’
[3]. Nevertheless, it still does not exist a set of precise rules to determine the quality of an object oriented design, but
there are some constructions that are known to have good characteristics. Polymorphic hierarchies, described by Woolf in [4]
show a number of these characteristics, ‘a polymorphic hierarchy encapsulates code that is highly reusable, flexible, extensible
and just plain good OO’. A rigorous definition of these constructions is useful to identify them in order to assess the quality
of a system.
Fulltext Preview (Small, Large)
 References secured to subscribers.
|
|
|
|
|
|