UNIVERSIDAD TECNOLÓGICA GRAL.

MARIANO ESCOBEDO.

ALUMNO: Héctor Bernal Palma

MATRICULA: I301730159

GRADO: 7° Cuatrimestre GRUPO: A

MATERIA: Procesos de Desarrollo de Software

ACTIVIDAD: RA – Calidad y defectos de software

DOCENTE: Ing. O. Daniel Charles Hernández

TURNO: Vespertino

05 de agosto de 2019

INDEX

INTRODUCTION..................................................................................................................................1
SOFTWARE DEVELOPMENT PROCESSES..................................................................................2

QUESTIONS RA...................................................................................................................................3

CONCLUSION......................................................................................................................................7

BIBLIOGRAPHY...................................................................................................................................8
 INTRODUCTION

Defects are an important variable to measure software quality, can it be the most
significant? If we answer yes, we can think that with the detection of defects and we have
solved any problem, but more important than giving that answer is to first understand what a
defect is and what strategies are regularly adopted to detect them.

The concept of defect is traditionally associated with deviation from specifications or

functional requirements and errors. It is very common to find teams of test specialists who
received a test plan and run it along with a series of tests that are already cataloged to
perform the generic form in applications (a somewhat targeted exploratory test mode).
 SOFTWARE DEVELOPMENT PROCESSES

In Software Engineering, a software development process model can be seen as a

way to divide the work into different activities (or the product life cycle in different phases) with
the intention of achieving the best management and the best result for the project. These
models may include the prior definition of specific deliverables and other artifacts that are
created and completed by the team to design, code, test and maintain the software in
question.

The following describes some of the best-known management and development

projects and methodologies in the software world: cascade development, prototype
development, spiral development and agile development.

Phases of the process

All process models are mostly composed of different phases that vary, albeit slightly, from
model to model.

• Definition phase

 Software development project planning

 Requirements Engineering / Information Extraction

 Analysis (study) of those requirements

•Development phase

 Software design

 Code generation

 Software testing

• Maintenance phase

 Correction of errors and readjustments that sometimes come from new requirements
and involve repeating the activities of previous phases

2
 QUESTIONS RA

1. What is software quality?

Within the context of Software Engineering, the definition of quality in the software
proposed by the international standards organization (ISO / IEC DEC 9126) will be taken: All
the features of a software product that have the ability to meet explicit needs or implicit
Another quite complete definition of quality in the software is the one presented below [35]: It
can be said that the software has quality if it meets or exceeds user expectations regarding:

1. Functionality (that serves a purpose),

2. Execution (make it practical),

3. Reliability (do what you owe),

4. Availability (that works under any circumstances) and

5. Support, at a cost less than or equal to what the user is willing to pay.

In summary, we can say that software quality refers to: "The factors of a
software product that contribute to the complete and total satisfaction of the
needs of a user or organization."

2. Describe essential steps in time management.

3
a) Schedule management: it establishes the policies, procedures and documentation
that it is necessary to collect for the planning, execution and control of the project
programming. This process provides guidance and direction on how the project
schedule will be managed throughout its entire life cycle.

b) Definition of activities: with this step, we seek to identify and document the specific
actions that will be necessary to produce the project deliverables. It is time to, after
creating the work breakdown structure, to divide each package into the activities that
constitute the basis of the project.

c) Concatenation of activities: defines the relationships between the different activities of

the project, establishing for this the logical sequence of work that guarantees the
greatest efficiency, taking into account all the restrictions of the project.

d) Estimation of necessary resources for each activity: it is about making an

approximation, as precise as possible, of the type and amount of resources necessary
to carry out each activity. To complete this process, it is necessary to identify not only
the class and volume of resources that will be used, but also its main characteristics,
since this minimizes the risk related to the calculation of costs and duration.

e) Estimation of the duration of each activity: it offers a very clear vision of the number of
work periods necessary to complete the individual activities with the estimated
resources. These calculations provide enough information to know the amount of time
each activity requires to complete.

f) Development of the project schedule: which is carried out by analyzing each

sequence of activities, their durations, the requirements applicable to the resources
and, of course, also the restrictions. Once completed, you must show the planned
dates to complete all the activities of the project that are included in it.

g) Control of the schedule: it lays the necessary bases to facilitate the monitoring and
control of the status of the project activities. In addition, it serves to update the
progress of the project and manage changes in the baseline of the schedule that allow
to gain adjustment with the provisions of the planning. The most important function of
this process is to provide the means to identify deviations prematurely, being able to
propose the necessary corrective or preventive actions.

3. What are software defects?

4
 Software defects are commonly known in developer slang as Bug (bug), and
corresponds to an error, imperfect or failure of a computer application that can cause an
unwanted result or breach of a requirement.

A defect is much more than an application error, a defect really covers the entire
productive process of software development and the artifacts it produces, that is, defects are
injected into the different stages of the Application Development Life Cycle and not only in the
development phase. A defect can be entered for example in a user manual that specifies a
functionality not available in the application, this finally remains a defect of the application if
we look at it not only as the program used by the client but as a whole package that includes
Several components, including documentation.

The following list lists some of the causes that generate defects in applications:

1. Communication problems Client - Supplier

2. Incorrect definition or absence of requirements

3. Deliberate deviation from the requirements (due to time pressure, progress

without authorization)

4. Design Errors

5. Coding errors

6. Breach of standards

7. Insufficient testing

8. Documentation Errors

4. What is the most important reason to review a program early?

5
 I. NEED FOR EVALUATION

a)  It is necessary to evaluate a system, to check

b) that its operation is correct, that is, the

c) expected.

d)  It is also necessary to evaluate when you want:

e)  Design a machine.

f)  Design a computer system.

g)  Select and configure a computer system.

h)  Plan the capacity of the computer system.

i)  Tune in or adjust a computer system.

II. THE OBJECTIVES OF PERFORMANCE EVALUATION ARE THE FOLLOWING:

a)  Compare different alternatives;

b)  Determine the impact of a new element or

c) feature in the system (for example: the addition of

d) a new hard drive);

e)  Tune in the system, that is, make functions

f) better from some point of view;

g)  Measure relative performance between different systems;

h)  Debugging benefits, that is, identify the

i) system failures that make it go slower (neck

j) of bottles).

6
 CONCLUSION

In this activity, it is understood the importance of knowing how to identify the defects in
a project, as well as that they should always be considered to be done with the best possible
quality. It is also very important to know how to manage our times to avoid unforeseen events
and work expressed.

We must always take into account the evaluation and self-analysis of our systems to avoid
failures or errors in them.

It is impossible to guarantee that a product has no defects, however, it is possible to improve

its process to produce products with very few defects, with a controlled defect rate.

The strategy is to identify the metrics that could indicate the possible number of defects
remaining in the final product and establish a standard that can be known by our customers,
according to which our product has an X number of defects that can become failures of the
system.

We must always define the best available and possible methodology for software
development management, taking into account the requirements and needs themselves, both
of the company or institution to which we will implement the system and both the work team
that will be the which will implement and design said system.

7
 BIBLIOGRAPHY

Los defectos y la calidad del software I. (2013, 15 septiembre). Recuperado 4 agosto, 2019,
de https://jummp.wordpress.com/2013/09/21/los-defectos-y-la-calidad-del-software-i/

Procesos de desarrollo software - Wikiversidad. (s.f.). Recuperado 4 agosto, 2019, de

https://es.wikiversity.org/wiki/Procesos_de_desarrollo_software

Calidad De Software. (s.f.). Recuperado 4 agosto, 2019, de http://www.eumed.net/libros-

gratis/2008a/351/Calidad%20de%20Software.htm

Etapas del plan de gestión del tiempo en un proyecto | OBS Business School. (s.f.).
Recuperado 4 agosto, 2019, de https://www.obs-edu.com/int/blog-project-
management/planificacion-de-las-actividades-y-tiempo-de-un-proyecto/etapas-del-plan-de-
gestion-del-tiempo-en-un-proyecto

Defectos del Software y sus Causas. (s.f.). Recuperado 4 agosto, 2019, de

http://desarrollandowebapps.blogspot.com/2013/02/defectos-del-software-y-sus-causas.html