Professional Documents
Culture Documents
CRIA Les3 Structure (Deel 01)
CRIA Les3 Structure (Deel 01)
CRIA Les3 Structure (Deel 01)
Interaction designers strive to create useful and usable products and services. Following the fundamental tenets of user-centered design, the practice of interaction design is grounded in an understanding of real userstheir goals, tasks, experiences, needs, and wants. Approaching design from a user-centered perspective, while endeavoring to balance users needs with business goals and technological capabilities, interaction designers provide solutions to complex design challenges, and define new and evolving interactive products and services.
Learning aims
You know the techniques which can (will) be used in the Structure phase You know the difference between high-level and expanded use cases You know the difference between essential and real use cases You know the assignment for the next lesson
Contents
Use Cases
High level & Expanded Essential en Real Work on a UseFace example
Assignment
Design overview
In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system. A use case in software engineering and systems engineering is a description of a systems behavior as it responds to a request that originates from outside of that system. In other words, a use case describes who can do what with the system in question. The use case technique is used to capture a systems behavioral requirements by detailing scenario-driven threads through the functional requirements.
Use cases
High-level use cases In the phase of analysis is a global view of each task enough - which tasks will our system support? - are the requirements in the MOSCOW-list covered by the Use cases?
Expanded use cases In the design we need a detailed view of how each task is performed;
Actors:
Purpose: Overview:
List of actors
Purpose of the task Short description of the use case
Note: A Use case covers one or more requirements. The requirements are inventorised and listed in the Strategy and Scope document.
Use Case (diagram) Contains all Use cases which will be supported by the designed system, system under construction (see youre Moscow analyses).
Two levels of use cases Essential use cases Free of implementation details Used in the analysis phase
Real use cases Specific for the design under construction Contains user interface descriptions Used in the design phase
In this course we work with Real use cases
Overview Prepare a new mathematical exercise starting with the registration of the exercise name and the exercise assignment. Additional information about the exercise assignment can be registered.
All clear???
Write down the HighLevel Use Cases which are shown (or you can use after clicking on Maak een pagina. 1. How many Use cases do you see on this page?
In FaceBook is the possibility to reset your password once youve lost it (or forgot it). 2. Create a Real Use case for the FaceBook functionality Je wachtwoord vergeten.
You can work in groups on this Real Use case. Use the format presented on the next slide.
Beware of the details!
Assignment Opdracht 1 In a nutshell: 1. Look in the Studyguide for assignment-03; 2. All necessary documents are on Online; 3. Work on the parts 1 and 2 (assignment-03) and put them in the Structure Document; 4. Use the Facebook example 4. Use youre creativity!