DIRECCIÓN ACADÉMICA
Formato de entrega de evidencias
FO-205P11000-14
División: (1) INGENIERÍA EN SISTEMAS COMPUTACIONALES Grupo: (2) 351-V
Fundamentos de Ingeniería de
Asignatura: (3) Docente: (4) M. en TI. Violeta Rocío Jiménez Olvera
Software
Nombre y número de control: (5) NAVARRO JIMÉNEZ CHRISTIAN RICARDO - No. DE CONTROL 193107009
Fecha de entrega: (6) 26-SEPTIEMBRE-2021
Descripción: Identifica y comprende el entorno de aplicación de la ingeniería de
Competencia No.: (7) 2
(8) software.
A) Describir los conceptos acerca de la Ingeniería del Software e identificar sus campos de
Indicador de alcance: (9)
aplicación, así como su aplicación.
Evidencia de aprendizaje: (10) Cuadro comparativo metodologías de desarrollo de software
Methodology Guy Definition Characteristics Stages Scheme
name
Waterfall Classical or Methodology in which the Its phases appear as a System engineering and
Methodology traditional stages are organized waterfall analysis: requirements of
methodology from top to bottom, hence The start of each stage all system elements
the name. The different should wait for completion Analyzing System
functions are developed At the end of each stage, Requirements:
in differentiated stages the model is designed to Understanding the Scope
and obeying a rigorous carry out a final review, of Software Information
order. Before each stage which is responsible for Design: focuses on data
the product should be determining if the project is structure, software
reviewed to see if it is ready to advance to the next architecture, procedural
ready to move on to the phase. detail and interface
next phase. we cannot expect that the characterization
initial specifications are Coding: passing the
correct and complete and design to code to make it
that the user can change his visible and functional
mind about one or another Testing: focuses on the
feature internal logic of the
software, and on external
functions, performing tests
that ensure that the
defined input produces the
results that are really
required.
Maintenance: The
software will undergo
changes after it is
delivered to the customer.
Changes will occur
because errors have been
found, because the
software must adapt to
changes in the external
environment
Prototyping Classical or It is based on the Creating a partial Collection and refinement
Methodology traditional construction of a software implementation of a system, of requirements
methodology prototype that is built for the explicit purpose of Modeling, fast design
quickly so that users can learning about system
Prototype Construction
test it and provide requirements
feedback. Thus, you can The prototype can be used Development, evaluation
fix what is wrong and as part of the requirements of the prototype by the
include other phase (determine client
requirements that may requirements) or just before Prototype refinement
arise. It is an iterative the requirements phase (as Engineering Product
model that relies on the a requirements
trial-and-error method to predecessor)
understand the It is a less formal method of
specificities of the development
product. focuses on a representation
of those aspects of the
software that will be visible
to the customer or end user.
The prototype is tested and
modified when necessary,
and the results are noted in
the review of the sketches
and drawings in operation.
Spiral Classical or It takes advantage of the Planning: in which the
methodology traditional cascade development initial requirements or
methodology model and the prototype new requirements to be
model by adding the added in this iteration are
concept of risk analysis. collected. Risk analysis:
It takes advantage of the based on the
cascade development requirements we decide
model and the prototype whether or not we are
model by adding the able to develop the
concept of risk analysis. software and the decision
is made to continue or not
to continue. Engineering:
in which a prototype is
developed based on the
requirements obtained in
the planning phase.
Customer evaluation: the
customer comments on
the prototype. If you are
happy with it, the process
is over, if the new
requirements are not
added in the next
iteration.
Incremental Classical or In this software It reduces risks as it Communication
methodology traditional development provides visibility into the Planning
methodology methodology, the final progress of new versions. Modeling (analysis,
product is built Provides feedback through design)
progressively. At each the displayed functionality. construction (code, test)
incremental stage, new It allows you to attack the Deployment (delivery,
functionality is added, greatest risks from the feedback)
allowing you to see beginning.
results faster compared Partial implementations can
to the cascading model. be made if you have
The software can be sufficient functionality.
started with even before it Testing and integration are
is fully completed and is constant.
generally much more Progress can be measured
flexible than other in short periods of time.
methodologies. It is easier to accommodate
changes by shortening the
size of increments.
You can plan based on the
functionality you want to
deliver first.
Due to its versatility, it
requires careful planning
both administratively and
technically.
Rapid Classical or This methodology allows It includes interactive Management modeling:
Application traditional you to develop high- development, prototyping What information drives
Design (RAD) methodology quality software in a short and the use of CASE the management
period of time. The costs (Computer Aided Software process? What
are much higher and the Engineering) utilities. information is generated?
development more Need for senior developers Data modeling: The flow
flexible, although it Demands a lot of user of information is refined
requires greater interactivity as a set of data objects
intervention from users. Difficulty within large-scale needed to support the
On the other hand, the projects enterprise
code may contain more Hybrid equipment Process modeling: The
errors, and its functions data objects defined in
are limited due to the little the data modeling phase
time available to develop are transformed to
them. The goal is to achieve the flow of
iterate as few times as information needed to
possible to get a implement a management
complete application function
quickly. Application generation:
Instead of creating
software with third-
generation programming
languages, the DRA
process works to reuse
existing program
components.
Proof of delivery: Reuse
is emphasized, this
reduces testing time.
Kanban Agile Work methodology It is based on the idea that Pending: Activity or tasks
Methodology methodologies invented by the Toyota work in progress should be that are still in the process
car company. It consists limited, and we should only of being performed
of dividing the tasks into start with something new Analysis: stage where
minimum portions and when a previous block of tasks are subject to
organizing them in a work work has been delivered or revision for further
board divided into has moved to another later development
pending, in progress and function of the chain. Development: Tasks are
completed tasks. In this Uses a visual control developed and separated
way, a very visual mechanism to track work as by tasks completed and
workflow is created it travels through the value done.
based on priority tasks stream Test: Testing of tasks to
and increasing the value Used on a panel or verify their functionality
of the product. whiteboard with sticky notes Deploy: Implementation
or an electronic panel of the results.
SCRUM Agile It is an incremental A set of good practices are Spring: Heart of SCRUM,
Methodology methodologies methodology that divides applied on a regular basis to container of the other
requirements and tasks work collaboratively, as a hitos of the process.
similarly to Kanban. It is team, and obtain the best Sprint planning: The
iterated on blocks of short possible result from a whole Scrum team
and fixed times (between project defines what tasks are
two and four weeks) to It is based on some going to be addressed
achieve a complete result controlled chaos, but and what will be the
in each iteration. The establishes certain objective of the sprint,
stages are planning mechanisms to control this what is going to be done
sprint, sprint, daily indeterminacy, manipulate in the sprint? How are we
meeting and sprint the unpredictable, and going to do it?
review. Each iteration control flexibility. Daily meeting: It is a daily
through these stages is It is especially suitable for meeting within the sprint
also called a sprint. projects in complex that lasts a maximum of 15
environments, where minutes. It must involve, if
results need to be obtained or if, the development
early, where requirements team and the Scrum
are changing or poorly master.
defined, where innovation, Sprint review: the review
competitiveness, flexibility, of the value that we are
and productivity are going to deliver to the
fundamental. client is done in this
meeting, at the end of
each sprint. Its duration is
4 hours for sprints of one
month.
Sprint retrospective: It
has a duration of 3 hours
for Sprints of one month
and is the team meeting in
which an evaluation is
made of how the Scrum
methodology has been
implemented in the last
sprint.
Extreme Agile It is a software It is based on 12 concepts: Programming
programming methodologies development simple design methodology: simple
methodology based on Testing, refactoring, and design, testing,
interpersonal Coding with standards refactoring, and coding
relationships, which are Collective ownership of the with standards.
considered the key to code Team methodology:
success. Its main Couples programming collective code
objective is to create a Continuous integration ownership, pair
good teamwork Weekly deliveries and programming, continuous
environment and that customer integrity integration, weekly
there is constant On-site customer deliveries, and customer
feedback from the client. Frequent deliveries integrity.
Planning. Process methodology: on-
site customer, frequent
deliveries, and planning.
Lean Agile It is set up for small, It consists of having a very Eliminate waste
Methodology methodologies highly skilled prepared, highly motivated, Extend learning
development teams to and close-knit team. Decide as late as possible
work out any task in no It is based mainly on React as quickly as
time. The most important constituting a strong and possible
assets are people and highly prepared team Empower the team
their commitment, thus capable of carrying out any Create integrity
relegating time and costs task in a short time. View all content
to the background.
Learning, quick reactions
and empowering the
team are fundamental.
References
https://www.becas-santander.com/es/blog/metodologias-desarrollo-software.html
https://repositorio.uca.edu.ar/bitstream/123456789/522/1/metodologias-desarrollo-
software.pdf
https://okhosting.com/blog/metodologias-del-desarrollo-de-software/
DIRECCIÓN ACADÉMICA
Guía estructurada de evaluación FO-205P11000-13
División: (1) Ingeniería en Sistemas Computacionales
Docente: (2) M en TI Violeta Rocío Jiménez Olvera
Asignatura: (3) Fundamentos de Ingeniería de Software
Nombre y número de control: (5) Christian Ricardo Navarro Jiménez Grupo: (6) 351V
Investiga las principales metodologías de la Ingeniería del software (IS): y elaborar
EVIDENCIA DE
un Cuadro Comparativo.
APRENDIZAJE: (7)
Criterios de evaluación:
CRITERIOS DE EVALUACIÓN SI NO OBSERVACIONES
HERRAMIENTA
El mapa se realiza en la
PARA LA
herramienta de su elección.
ELABORACIÓN.
Contiene el título principal
“Principales Metodologías de
Softwre”
1.- Elije 10 metodologías
2.- Las columnas deben ser las
siguientes:
a) Nombre de la Metodología
CONTENIDO b) Tipo
DEL CUADRO c) Definición
d) Características
COMPARATIVO
e) Etapas
f) Esquema
3.- No puedes repetir
metodologías.
Se anexa evidencia de la visita a la
biblioteca virtual.
Se entrega en formato de evidencia
y este se encuentra debidamente
ENTREGA requisitado.
El cuadro se entrega en la fecha y
hora indicada por el docente.
Contiene referencia bibliográfica
BIBLIOGRAFÍA
por concepto y se encuentran en
Y GRAMÁTICA formato APA.
ORTOGRAFÍA Se encuentra libre de errores
Y GRAMÁTICA ortográficos o gramaticales.
La calidad del trabajo entregado
CALIDAD DEL es realmente buena, cubre y
TRABAJO respeta todos los puntos
establecidos por el docente.
1ª oportunidad 2ª oportunidad
Puntuación
Alcanzada (10)
