Information Technology Reference
In-Depth Information
Though work still needs to be carried out to merge the progress of human-
machine interface research in mainstream UML-based software design methods
[PAL 03], OO developers perceive UML as an approach that is intuitive and
effective to implement, particularly for use case diagrams and state diagrams
[AGA 03]. The developers that have more experience in OO analysis and design
techniques also perceive class diagrams and interaction diagrams as easy to use
[AGA 03]. In the case of IIS, certain works have already put forward ways for
improvement. For example, da Silva and Paton propose an extension of UML that
enables us to directly integrate the interface specifications by incorporating a new
notation in UML [DAS 03]. UML i enables us to express the relations between the
use case, tasks, views and particularly the relations that exist between tasks and the
data on which they act. More recently, Razali and his colleagues have shown in their
survey the benefit of using a method of formalization in UML that is based on a
cognitive framework which enables each player to share a notation and a common
formalism [RAZ 08]. The object modeling in RAMSES implies a dialog between
ergonomist and computing designer. It must be ensured by a designer who masters
the OO methods. It progresses according to two axes: a static modeling and a
dynamic modeling.
Staticmodeling or domain modeling describes the use and operating
environments of the IIS. The definition of the information flow diagram enables the
construction of a class diagram representing the elements of the problem. Each
element of the environment (place, media, operator, etc.) previously identified is
represented in the form of a class. Activity analysis enables us to exhibit the
components, which describe these elements. These components appear as the
attributes and methods of these classes. Thus, the ergonomic analysis of the previous
step has enabled us to define users' profiles. These profiles represent the instances
of a user class. Each user is an instantiated object based on this class. Similarly,
the media and resources have been described by the ergonomist in environments
of use and operation. These elements contribute to the definition of IIS classes
(classes, attributes and methods).
The classes were then linked by associations describing their interactions in the
process of production and diffusion of information between the system and the
users. The specification of the system at this step is to describe the functions
expected after the analysis of user needs. Based on these observations of an existing
system or scenarios of contexts, the ergonomist will be able to give the orientation
of the IIS functionalities to produce information that meets the user's needs and the
conditions to fulfill and guarantee the usability of this information in the
environment of use.
The second modeling axis concerns the dynamic aspects of users' activity. This
model explains the interactions of the user with the entities created in the static
Search WWH ::




Custom Search