Information Technology Reference
In-Depth Information
- the third category concerns the use case for manipulation of the user profile:
manage the profile
,
visualize the profile
,
modify preferences and delete the profile
.
3.5.2.2.
Functional analysis of the personalized service
Starting from the use case diagram stemming from the capture of functional
needs, a static modeling of the business objects of the itinerary search service is
carried out (see Figure 3.6).
Preferences
+modify()
+delete()
+renderOutPut()
“Responsibility”
-- Display the profile of the user
-- Enable the profile to be handled
by the user
PerSyst
MASC
“Responsibility”
-- Transmit the user's choice
to PerSyst
“Responsibility”
-- Display the itinerary search
interface
-- Send the user's request
to PerSyst
Search
Choice
+search()
+renderOutPut()
+sendChoice()
“Responsibility”
-- Display all possible choices
-- Display the details of an itinerary
-- Display the itinerary
recommended by PerSyst
ResultSearch
+printAllRoutes()
+selectRoute()
+printDetailRoute()
Figure 3.6.
Class diagrams for the itinerary search services
The classes necessary to ensure the different responsibilities are defined. The
modules that are not part of the service (but are useful to it) are represented in the
form of
packages.
To refine the static model, a series of dynamic models was
established. For example, Figure 3.7 presents a scenario for the itinerary search by
giving details of the interactions between different objects of the service. After
connecting to the MASC, the user begins his request using the personalized itinerary
