Download circumstantial knowledge management - e

Transcript
Chapter 5
Implementation
The aim of this chapter is to delve into the design of the system, thus providing enough
detail as required to serve as a guide for its implementation. This implementation must
satisfy the physical and functional needs listed in the previous chapter.
Section 5.1 describes some considerations regarding the system implementation, which
may be helpful to understand some implementation decisions of the later sections.
Moreover, sections 5.2 and 5.3 detail the implementation of the physical architecture
for the system and provide a low-level design of the functional architecture, respectively.
The contents of the latest one can be used directly for the system coding.
Finally, section 5.6 introduces the implementation of the data storages of the system.
5.1
Implementation Issues
This section describes some implementation considerations which may be helpful to understand some decisions carried out during system implementation.
The system implementation will follow an object-oriented approach. This turns out to
be a good option as the system is structured into classes, each of them having well defined
responsibilities. Moreover, it provides some features such as encapsulation, inheritance and
polymorphism, which can be really useful for our purposes:
• The principle of encapsulation allows a class to hide its own attributes. Instead,
public methods describes the functions which can be executed over an instance of the
class (also known as an object). This provides modularity, and allow to use classes
as black boxes, where nothing but its functionality is required to be known.
• The principle of inheritance allows to create a class hierarchy, where some classes
are childs of other classes. Often, these child classes provides some specialization
77