Transcript Ingeniería de Requisitos

INGENIERIA DE
REQUISITOS
Carlos Mario Zapata J.
4/13/2015
Ingeniería de Requisitos
1
Área de Trabajo
Ingeniería de Software
Ingeniería de Requisitos
Educción de Requisitos de Software
4/13/2015
Ingeniería de Requisitos
2
UNA PROPUESTA
CONSISTENTE
4/13/2015
Ingeniería de Requisitos
3
UNA PROPUESTA
CONSISTENTE
Seis hombres ciegos del Indostán
a los que les gustaba estudiar
fueron a ver a un elefante.
Y, como no lo podían avistar,
se pusieron a tocar y a intentar adivinar.
El cuarto hombre abrazó del elefante una pata,
y palpando la zona del medio
aseguró de forma inexacta:
"¡el elefante es como un madero
y con diez se hace un velero!"
El primero se aproximó
y, palpándole el flanco al bicho,
acto seguido exclamó:
"Oh, Dios mio, ¿qué es esto que cincho?
Ah, ya se, ¡es como un muro!
estoy casi seguro".
El quinto hombre, al tocar del animal la oreja,
con ojos risueños de chico
aseguro con sabiduría vieja:
"¡es plano como un abanico
y da más aire que una abeja!"
El segundo, haciendo de un colmillo presa,
raudo declaró sin duda:
"redondo,largo y de punta,
no me asusta decir de esa
que es como una lanza o como una vara de yunta."
El tercero se acercó
y puso manos a la obra.
La larga trompa palpó
y con certeza declaró:
"Sin duda y sin zozobra
declaro que es como una cobra".
4/13/2015
El sexto hombre agarró del enorme bicho el rabo
y sin mas pensar declaró:
"ya se, misterio acabado,
el elefante es como un nabo.
No importa visto de qué lado".
Y he aquí la moraleja amigos,
pues aquellos seis hombres ciegos
a pensar de tener razón en parte
no tenían, en realidad,
el arte de oir más allá de sus propios gorjeos
John Godfrey Saxe 1816-1887
Ingeniería de Requisitos
4
LA ESENCIA DE LA
INGENIERÍA DE SOFTWARE
4/13/2015
Ingeniería de Requisitos
5
LA ESENCIA DE LA
INGENIERÍA DE SOFTWARE
4/13/2015
Ingeniería de Requisitos
6
4/13/2015
Ingeniería de Requisitos
7
4/13/2015
Ingeniería de Requisitos
8
4/13/2015
Ingeniería de Requisitos
9
UNC-METHOD EN LA ESENCIA
4/13/2015
Ingeniería de Requisitos
10
ENTREGABLE 1
•
•
•
•
•
•
•
•
•
Diálogo controlado
Tarjetas de educción
Organigrama
Tabla de trazabilidad documental
Esquema preconceptual
Esquemas preconceptuales ejecutables (mínimo cinco)
Modelo del dominio
Tablero Kanban
Reporte de avance de los alfas
4/13/2015
Ingeniería de Requisitos
11
DIÁLOGO CONTROLADO
Analyst: Good morning. With this interview, we aim to clarify the information
concerning the problem domain in which we will work. Please answer the
questions in the clearest way possible.
Stakeholder: O.k. Let’s start.
Analyst: What is the name of this organization?
Stakeholder: ZenPhoto™.
Analyst: Please, list the internal/external actors linked to the activities of your
organization.
Stakeholder: We have administrators and users.
Analyst: Who can play the role of a user?
Stakeholder: An administrator.
Analyst: Would you please mention some characteristics of users?
Stakeholder: They have custom_data, pass, name, e-mail, right, name_user, valid,
group, access, and id.
4/13/2015
Ingeniería de Requisitos
12
DIÁLOGO CONTROLADO
Analyst: Please list the main functions of the users.
Stakeholder: He/she uploads and deletes files; publishes albums and uploads
images; creates, edits, deletes, and unpublishes albums; enables and
disables comments; assigns tags; resets hitcounters; adds, renames, and
deletes tags; deletes, approves, disapproves, and edits comments; edits
and deletes images; adds comments.
Analyst: Are these functions gathered in some sort of responsibility?
Stakeholder: Yes. Uploads and deletes files are gathered as “edits files;”
publishes albums and uploads images are gathered as “creates galleries;”
creates, edits, deletes, and unpublishes albums, enables and disables
comments, assigns tags, and resets hitcounters are gathered as “manages
albums;” adds, renames, and deletes tags are gathered as “edits tags;”
deletes, approves, disapproves, and edits comments are gathered as
“manages comments;” edits and deletes images edits and deletes images,
enables and disables comments, assigns tags, and resets hitcounters are
gathered as “manages images;” creates, edits, and deletes users are
gathered as “manages users.”
4/13/2015
Ingeniería de Requisitos
13
DIÁLOGO CONTROLADO
Analyst: Would you please mention some features of the files?
Stakeholder: Each file has a readable_status, a writable_status, a file_type, a
creation_date, a modification_date, a name, and a file_size.
Analyst: Which objects can we categorize and what is the name of the
category?
Stakeholder: Subalbums can be categorized under albums.
Analyst: Which of the mentioned features have features themselves?
Stakeholder: Each right has a permit, a description right, and an id. Each
access has a unique user and a unique album.
Analyst: Which values or instances can be associated to which feature?
Stakeholder: Admin, Manage all albums, Albums, Files, Tags, Comments, and
Upload are instances of description right.
Analyst: What does the user need in order to accomplish the file edition?
Stakeholder: He just need to have description right=“Admin” and description
right=“File.”
4/13/2015
Ingeniería de Requisitos
14
DIÁLOGO CONTROLADO
Analyst: Would you please establish some sort of sequence in the functions
and responsibilities you have just described?
Stakeholder: In the file editing, the user first uploads the file and then deletes
the file; in the gallery creation, the user first uploads the image and then
publishes the album; in the album management, the user first creates the
album and then edits and deletes the album; in the tag edition, the user first
adds the tag and then renames and deletes the tag; in the user
management, the administrator first creates the user and then edits and
deletes the user.
Analyst: What are the goals and problems associated with the function
“creates users”?
Stakeholder: The goals are “increasing the users”, “assuring the access has
albums,” and “fostering the permits.” The problems are “access has many
restrictions for new users” and “rights are difficult to be granted after a user
is created”.
Analyst: Thank you for your valuable information. We will be in contact in order
to clarify any doubts that may arise in this process.
Stakeholder: Thank you. I’ll be in touch.
4/13/2015
Ingeniería de Requisitos
15
TARJETAS DE EDUCCIÓN
4/13/2015
Ingeniería de Requisitos
16
TARJETAS DE EDUCCIÓN
4/13/2015
Ingeniería de Requisitos
17
TARJETAS DE EDUCCIÓN
4/13/2015
Ingeniería de Requisitos
18
ORGANIGRAMA
4/13/2015
Ingeniería de Requisitos
19
TABLA DE TRAZABILIDAD DOCUMENTAL
Original sound/image/text
ZenPhoto: The simpler media website
content management system
Source Location
Text
Contents are included in albums
The amount of users is one of the
challenging situations of modern CMS
Some information should be gathered for
the images: location, height, width, and
owner
We want to foster the usage of files and
permits associated with them
4/13/2015
Element
Kind of element Observations
Even though the word
www.zenphoto.or
“management” is a noun, the
Manages album Responsibility
g
existence of the system leads to
the responsibility “manage.”
Text
CMS and
There are few
beyond, page 15 users
Text
ZenPhoto user
guide
Problem
The adjective “few” is implicit in
the context, since the “amount of
users” as a challenging situation is
related to few users.
Image has
location
Structural triads
Image has height
Image has owner
Interview with the
Fostering file
Sound stakeholder,
10:30-10:33
Goal
Album has title
Screenshot # 15 Gallery has
Image provided by the album
stakeholder
Album has
comment
Previous interviews with the
stakeholder give us the possibility
Structural triads
to complement the information
based on the image.
Screenshot # 15
Image has size
Image provided by the
(to be agreed)
stakeholder
Even though there is no explicit
size associated with the files in the
Structural triad
image, we know that the file needs
this attribute.
Ingeniería de Requisitos
20
ESQUEMAS PRECONCEPTUALES
No. 350 - Clarita
<30 litros
4/13/2015
Ingeniería de Requisitos
21
ESQUEMAS PRECONCEPTUALES
<30 litros
4/13/2015
Ingeniería de Requisitos
22
ESQUEMAS PRECONCEPTUALES
<30 litros
4/13/2015
Ingeniería de Requisitos
23
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
24
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
25
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
26
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
27
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
28
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
29
ESQUEMAS PRECONCEPTUALES
4/13/2015
Ingeniería de Requisitos
30
ESQUEMA PRECONCEPTUAL
4/13/2015
Ingeniería de Requisitos
31
ESQUEMA PRECONCEPTUAL EJECUTABLE
4/13/2015
Ingeniería de Requisitos
32
MODELO DEL DOMINIO
4/13/2015
Ingeniería de Requisitos
33
TABLERO KANBAN
4/13/2015
Ingeniería de Requisitos
34
REPORTE DE AVANCE DE LOS ALFAS
4/13/2015
Ingeniería de Requisitos
35