better identification of critical factors that will lead
to the development of successful software systems
running on the Web. In our case, success is assumed
when the RS is able to provide information
suggestions that are very close to the user interests,
characteristics and expectations at the time of
accessing particular portions of Web information.
The model categorizes system requirements in three
main axons: The Country Characteristics, the User
Requirements, and the Application Domain axon
(fig. 1).
Figure 1: The SpiderWeb Model.
Each axon includes certain components, which are
directly connected and interrelated. The SpiderWeb
axons are also interdependent, allowing the sharing
of same, similar, or different characteristics among
each other.
The analysis of the axon components of the
SpiderWeb model presented in the previous part
aimed primarily at providing the basic key concepts
for collecting proper system requirements. These
concepts are to be used as guidelines for gathering
critical information that may affect the functional
and non-functional behavior of the RS under
development. A form of small-scale ethnography
analysis is conducted for collecting and analyzing
information for the three axons described before.
Our method includes focus questions produced
in the form of questionnaires. These questions are
distributed among the targeted group or are used as
part of the interviewing process, and the answers are
recorded, analyzed and evaluated.
The SpiderWeb methodology is integrated with
the WebE process (Pressman, 2000), the latter being
used for the development of Web applications.
As previously mentioned, the SpiderWeb model
is utilized to guide the creation of the
recommendation engine so as to provide the right
recommendations. The engine employs both offline
and online data gathering and processing procedures
as follows:
Offline Operation Procedures
During the Analysis Phase the following offline
operation procedures are used:
Step 1 – Administer focus questions to groups of
users and collect HSCO information on country
characteristics, user requirements and the RS
itself.
Step 2 – Estimate the preferences’ priorities (e.g.
purchasing decisions or searching patterns)
according to the user groups and the type of the
application
Step 3 – Compute similarity measures between
user groups
Step 4 – Derive the possibility measures
Online Operation Procedures
Step 1 – Set up basic parameters by establishing
an initial dialogue with users to collect HSCO
information (e.g. age, gender)
Step 2 – Record on-click and identify users’
interests and preferences patterns
Step 3 – Analyze search and browse patterns,
build categories
Step 4 – Match related content with categories
Step 5 – Provide recommendations
First, historical data are selected and added into
datasets. For every search, if frequently occurring
patterns (classifiers) are found then those of good
quality are used for recommendations. When new
information is requested, the system identifies the
corresponding class labels using multiple classifiers.
Finally, the performance of the RS is evaluated by
investigating the accuracy of the recommendations
offered.
Typically, a client is accessing the RS through
her/his Web browser where she/he can search and
retrieve information (fig. 2). The Web server will
receive her/his request and information and then
process the data. The requirements pre-processing
subsystem will receive the request and search the
semantic rule database and if there is a relationship
then there is a match to the original requirements.
Offline classifiers are built and stored in the
classifier rule database for new classifications. For
every new customer requirements, the server will
find all the classifiers that meet the conditions of
these requirements by searching the classifier rule
database and the new recommendations are
provided.
Country
Characteristics
User
Re
uirements
Application
Domain
1 2 . . .
c
2
1
1
2
…
r
…
ICEIS 2011 - 13th International Conference on Enterprise Information Systems
212