Capturing needs
Web application modeling and design
Article REF: H7230 V1
Capturing needs
Web application modeling and design

Author : Gustavo ROSSI

Publication date: November 10, 2006 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

4. Capturing needs

4.1 Identify the players

In OOHDM, we build a different navigation model for each user profile. In the example application, we clearly have two orthogonal user profiles: the customer (who is looking for a movie to buy or just to consult information) and the administrator (who maintains the movie database); we discuss here the application corresponding to the customer. Once the actors have been identified, we need to identify the tasks they will perform to obtain usage scenarios. A subset of the most important tasks for the "customer" user profile of our application is as follows:

  • given a title, find the corresponding film;

  • given the name of one of the actors, find the film;

  • ...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Article included in this offer

"Digital documents and content management"

( 71 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details