9/16/2015ingeniería de requisitos1 ingenieria de requisitos carlos mario zapata j
TRANSCRIPT
04/21/23 Ingeniería de Requisitos 1
INGENIERIA DE REQUISITOS
Carlos Mario Zapata J.
04/21/23 Ingeniería de Requisitos 2
Área de Trabajo
Educción de Requisitos de Software
Ingeniería de Requisitos
Ingeniería de Software
UNA PROPUESTA CONSISTENTE
04/21/23 Ingeniería de Requisitos 3
UNA PROPUESTA CONSISTENTE
04/21/23 Ingeniería de Requisitos 4
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 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 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".
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 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 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
LA ESENCIA DE LA INGENIERÍA DE SOFTWARE
04/21/23 Ingeniería de Requisitos 5
LA ESENCIA DE LA INGENIERÍA DE SOFTWARE
04/21/23 Ingeniería de Requisitos 6
UNC-METHOD EN LA ESENCIA
04/21/23 Ingeniería de Requisitos 7
04/21/23 Ingeniería de Requisitos 8
04/21/23 Ingeniería de Requisitos 9
04/21/23 Ingeniería de Requisitos 10
04/21/23 Ingeniería de Requisitos 11
DIÁLOGO CONTROLADOAnalyst: 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.
04/21/23 Ingeniería de Requisitos 12
DIÁLOGO CONTROLADOAnalyst: 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.”
04/21/23 Ingeniería de Requisitos 13
DIÁLOGO CONTROLADOAnalyst: 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.”
04/21/23 Ingeniería de Requisitos 14
DIÁLOGO CONTROLADOAnalyst: 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.
04/21/23 Ingeniería de Requisitos 15
TARJETAS DE EDUCCIÓN
04/21/23 Ingeniería de Requisitos 16
TARJETAS DE EDUCCIÓN
04/21/23 Ingeniería de Requisitos 17
TARJETAS DE EDUCCIÓN
04/21/23 Ingeniería de Requisitos 18
MODELO DEL DOMINIO
04/21/23 Ingeniería de Requisitos 19
04/21/23 Ingeniería de Requisitos 20
ORGANIGRAMA
04/21/23 Ingeniería de Requisitos 21
04/21/23 Ingeniería de Requisitos 22
04/21/23 Ingeniería de Requisitos 23
ESQUEMAS PRECONCEPTUALES
No. 350 - Clarita
<30 litros
04/21/23 Ingeniería de Requisitos 24
ESQUEMAS PRECONCEPTUALES
<30 litros
04/21/23 Ingeniería de Requisitos 25
ESQUEMAS PRECONCEPTUALES
<30 litros
04/21/23 Ingeniería de Requisitos 26
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 27
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 28
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 29
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 30
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 31
ESQUEMAS PRECONCEPTUALES
04/21/23 Ingeniería de Requisitos 32
ESQUEMAS PRECONCEPTUALES
ESQUEMA PRECONCEPTUAL
04/21/23 Ingeniería de Requisitos 33
ESQUEMA PRECONCEPTUAL EJECUTABLE
04/21/23 Ingeniería de Requisitos 34
04/21/23 Ingeniería de Requisitos 35
04/21/23 Ingeniería de Requisitos 36
TABLA DE TRAZABILIDAD DOCUMENTAL
04/21/23 Ingeniería de Requisitos 37
Original sound/image/text Source Location Element Kind of element ObservationsZenPhoto: The simpler media website content management system
Contents are included in albums
Textwww.zenphoto.org
Manages album Responsibility
Even though the word “management” is a noun, the existence of the system leads to the responsibility “manage.”
The amount of users is one of the challenging situations of modern CMS
TextCMS and beyond, page 15
There are few users
Problem
The adjective “few” is implicit in the context, since the “amount of users” as a challenging situation is related to few users.
Some information should be gathered for the images: location, height, width, and owner
TextZenPhoto user guide
Image has locationImage has heightImage has owner
Structural triads
We want to foster the usage of files and permits associated with them
SoundInterview with the stakeholder, 10:30-10:33
Fostering fileGoal
ImageScreenshot # 15 provided by the stakeholder
Album has titleGallery has albumAlbum has comment
Structural triads
Previous interviews with the stakeholder give us the possibility to complement the information based on the image.
ImageScreenshot # 15 provided by the stakeholder
Image has size (to be agreed)
Structural triad
Even though there is no explicit size associated with the files in the image, we know that the file needs this attribute.
04/21/23 Ingeniería de Requisitos 38
TABLERO KANBAN
04/21/23 Ingeniería de Requisitos 39
REPORTE DE AVANCE DE LOS ALFAS
04/21/23 Ingeniería de Requisitos 40
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
04/21/23 Ingeniería de Requisitos 41