Information Technology Reference
In-Depth Information
It is important to note here that this categorization, which is based on a field
study, is only a heuristic vision of the issue. Thus, the choice of the number of
categories, as well as the definition of each category, was done in order to be able to
identify as many common behaviors as possible. The use of such an approach, if it
enables the issue to be simplified, also implies the existence of a grey area at the
boundaries between the different categories.
It does not enable us,
in theory
,
to be able to ensure a certain and unambiguous
identification of which category the user belongs to. That being said, it represents an
initial approach to the issue of considering the notion of time use during travel by
users of public transport.
9.3. Specificities in the field of transport in the framework of a method of
modeling personalized interactive applications
9.3.1.
Introduction
To take into account the travel time experience of the user in application models,
it is first essential to be able to correctly identify the activities associated with each
category. Then, it is necessary to define how we can know, at any time, in which
category the user is. Finally, it is necessary to be able to take into account this notion
of category of travel time experience by the traveler in the application models,
particularly the conceptual models.
9.3.2.
A different approach to the analysis of needs
In the classical methods of analysis proposed in the context of systemic-type
approaches, such as Merise [NAN 01], Cartesian, such as SADT (Structured
Analysis and Design Technique) or IDEF0 (Integration Definition for Function
Modeling) [ANG 99], object-oriented, such as UP (Unified Process) [JAC 99], RUP
(Rational Unified Process) [KRU 00] or 2TUP (Two Track Unified Process)
[ROQ 07], the organization of tasks only considers a functional logic centered
around a goal to be reached and only marginally takes into account the user. We
propose adding a new stage to the different analysis stages of these methods; see
Figure 9.3. Initially, once all the tasks have been identified, it will consist of
grouping them together into business processes; i.e. an ensemble of tasks enabling
us to determine a business goal from the point of view of the user and/or the point
field of business in which the application is used (a business process can call on
several users).
