QUALITY IN SOFTWARE DEVELOPMENT

Jairo Mendoza Tamara - 9176459

Activity 3

The company SoftSena, specialized in software development, has been requested

for a health clinic, which has requested the development of a
traditional information system (desktop), where the
medications delivered to patients, those prescribed by doctors and
those that are purchased from suppliers.
Likewise, the company needs to know the inventory status of the
medications by laboratory. The system must allow generating all the
necessary reports according to daily, weekly and
monthly. For this reason, the advice of a professional in this is requested.
field.
The technical group for the construction of the project is already formed. Without
embargo, faces the decision of choosing the software model that will guide
the design and construction and at the same time, the tests to be applied, according to the model of
chosen software life cycle.

1. Evidence the model according to the chosen life cycle.

The chosen model was the Extreme Programming (XP) Model because it is a
agile methodology is based on continuous feedback between the client and the team
development, continuous communication among all participants, simplicity in
the implemented solutions and ease of facing changes.
This methodology will allow us to develop the software that the entity needs.
hospital-based, and because it is focused on the health aspect, it denotes a great
responsibility therefore the XP methodology will provide us with the tools
you would need to achieve the best results with the quality it deserves.
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara
Activity 3

To meet the established requirements, a system will be implemented.

desk, divided into modules called 'Health Information System' (SIS),
that allow dividing the tasks to be performed and that can in turn be executed from
individual form but working in an integrated way based on the same
information. The first module will be administration, Hiring,
Medications and Supplies, Providers, Medical History, and Nursing. All
these modules will handle the information of an integrated database called
BDSIS and a test database called PBDSIS.

2. Determine the scope of the test.

The testing plan for this project aims to detect errors from the
same start of development and sequentially provide feedback and resolve them,
applying all tests in each of the phases.
Software testing has limitations, both theoretical and practical. From the
from a theoretical point of view, the problem is what we call undecidable; this
it implies, roughly speaking, that we cannot write a program that tests the
programs without human intervention. However, as we mentioned
Previously, the test is indeed automatable in many aspects.
From a practical standpoint, the number of possibilities to try
exhaustively a system is simply unmanageable; it is necessary then
use appropriate techniques to maximize the number of significant failures
found with the assigned resources. Next, we will show a
test summary.
Modules to be Tested Modules:
Management
Hiring
Medications and Supplies
Suppliers
Medical History
Nursing.
Objectives of the Test Visualization of entered data or
modified.
The operation of the prepared services
to respond to the products of the
SIS system.
The answers and completion of the
transactions of each module.
That the states of the activities and
documents generated in the system are
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara - 9176459
Activity 3

reflect according to the logical sequence

requested by the user.
The logical sequence of the functionalities and
transactions.
Execution Order Details The modules for your first execution are
of the modules You must open the module of:
Administration
2. Hiring
3. Suppliers
4. Medications and supplies

Next, you can open any of the

modules in the order you wish.

Clinical History and Nursing

After the first run, the modules

they will be able to act individually without any
problem without ceasing to be integrated in a
same system

Burden of Proof The tests are the responsibility of Testng.

Operational of the project team, who in
together with the user, they must select the tests
that ensure the effectiveness of the system.

3. Relate the types of tests to apply.

A series of automated tests must be continuously performed based on

the client's requirements to ensure that everything works correctly. These
they must be done periodically and automatically.
The aforementioned planning includes the deliveries at the end.
from each iteration, these will always be with the tested and functioning software
correctly and will be provided to the customer, who can use it for any
purpose, even for the end user. The types of tests to be conducted are:
Unit tests: In unit tests, the
individual operation of each module, writing test cases
for each functionality or method in the module, in such a way that it is determined
the integrity of it (Mayorga & Arce, 2013, p.32).
Integration tests: Integration tests aim to verify
that the set of modules of a system works properly
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara
Activity 3

(Mayorga and Arce, 2013). They are aimed at: 1. Identifying errors
introduced by the combination of unit-tested programs; 2.
Verify that the interfaces between external entities (users) and the
applications work correctly; 3. Test that the specifications
design goals are met and 4. Determine the approach to move forward from
a level of integration of the following components (Abad, 2005).
Smoke test: Its purpose is focused on testing the system.
constantly looking for it to "smoke" or fail. In some projects,
this type of test goes along with functional testing. It allows detecting
problems that are usually not detected in normal tests.
Sometimes, if the tests occur in later stages, this will be a
a way to ensure proper development. Smoke tests are not
exhaustive, but they go from one end to the other of the application (Abad, 2005).
Validation tests for custom systems Abad (2005), comments
A list of validation tests for applications must be presented.
custom systems, which are oriented towards validation of the
functioning of software tailored to the business model.
GUI or interface test: This test verifies the
user interaction with the software. The goal will be to ensure that the
the interface provides adequate navigation through different
features. In addition, it ensures that the interface objects
that are going to be adopted are within industry standards.
Configuration test: With this type of tests, it is possible to verify the
operation of the system in different hardware configurations and
software. The specifications for the workstations, equipment of
network and servers can show variations in most of the
production environments.
Style test: Check that the application follows the standards of
client-specific styles, such as window formats, colors
corporate, fonts, among others.
Acceptance test: This test is intended to confirm that the
product is ready for operational use. It is usually a subset of the
system tests are executed before the application is installed inside
from a production environment. Its execution is carried out by the client,
or by a specialist of the application.
Installation test: It is aimed at verifying and validating that the system
it is properly installed on each client computer, under these
conditions:
New facilities, new machines that have never been used.
the system installed.
Update previously installed machines with the system.
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara
Activity 3

● Install old versions on previously installed machines with the

system.
Functional test: Test aimed at ensuring the appropriate analysis of
the functional requirements, including navigation, data input,
processing and obtaining results. In this sense, this type of
tests focus on functional requirements, they can be based
directly in the use cases, functions, and business rules.
Documentation test: and procedure It focuses on evaluating the
accuracy and clarity of user documentation and determines whether the
The procedure manual will operate correctly as an integral part of the
system.
Usability test: Its purpose is to determine usability.
of the system. In this sense, it seeks to measure how easy it will be for the user to use and
understand the application, trying to identify the design areas that
they hinder the use of the system by the user.
Field test: This test is aimed at running the system in a
real environment to find errors and validate the product against its
original specifications. In this regard, it determines the tests of
systems that will be run to validate the system in production.
[Link] testing strategies.

Certification is required from both the development team and the user for
productSIS - Health Information System, in two stages, that manages
and manage the medications and supplies applied to the patients. Therefore, it
you must verify:
1st Stage: For the functionalities of the Administration modules,
Hiring, Suppliers and Medicines and Supplies that are the ones
they must be executed in order to feed them with information
necessary for the operation of the other modules
2nd Stage: That the integrated functionalities of the modules are
capable of functioning individually and meeting the requirements.
Together, the sub-objectives for the 6 modules are summarized as follows
form:
The creation and entry, editing and updating of the entity's data
(Corporate name, identification, certification code, etc).
The creation, entry, editing, modification, and deletion of users,
providers, stables, patients, etc.
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara
Activity 3

The creation, entry, editing, modification, and deletion of medications

and Inputs.
the visualization, modification and deletion of administrative data
activities generate their corresponding status in the system.
It will be necessary to indicate as an objective to carry out the tests of the modules for the
management and administration of the medications and supplies applied to the
patients.
This refers to verifying and validating the results or outputs generated. An objective
the use of formal software testing techniques is important
Specification: This type of test includes testing the application against the
Documentation that was done before, for example, that the processes align with
the algorithms made on paper, or that the application has all the functions that
they had planned.
Usability: This type of test refers to ensuring that the user interface
(the GUI) should be intuitive, user-friendly, and function correctly.

Unit: This type of test only applies to large projects. The project is divided
to units and each unit is tested individually.
Integration: Test several units together to ensure they work well.
It also ensures that the new applications integrate with applications.
old or complementary applications.
Regression: This test includes all the previous tests in case you are
make some change to some module after it has been placed in the environment of
production.
Verification and validation: Software testing is an element of a topic
broader than what is usually referred to as verification and validation.

Verification: It is the set of tasks that ensure that the software

correctly implement a specific function
Are we building the product correctly?
Validation: It is a different set of activities that ensure that the
software that is built follows the client's requirements
Are we building the right product?

Alpha and Beta Tests:

 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara
Activity 3

The alpha test: is conducted by a system administrator, a doctor, a

nurse and a patient in the development site. The software is used in a way
natural, with the development manager 'looking over the shoulder' of
"user" and recording errors and usage problems. Alpha tests are conducted in
cable in a controlled environment, simulating the implementation of the software.

The beta test: it is carried out in one or more customer locations by the users
software finals. Unlike alpha testing, the development manager,
usually, it is not present. The beta test is a 'live' application of the
software (In the hospital entity) in an environment that cannot be controlled
by the development team. The client logs all issues (real or
imaginary) that it finds and reports them at regular intervals. As a result,
the development team is making modifications and thus prepares a version of
product for the entire customer base.

5. Present exit criteria and any additional aspects you consider.

necessary to take into account.

Among the parties involved in the process, it is formally defined under what
conditions can be considered that a testing activity has been completed. The
Exit criteria must be defined for each level of testing to be executed. Some
Examples of exit criteria that can be used include: percentage of
high-risk functionalities successfully tested, number of critical defects and/or
accepted adults, etc.

Other aspects: just as it is done in any project plan, it should be included

an estimate of the times, the roles and/or resources that will be part of the process, the
preparation of the testing environment, baseline schedule, etc.

Order of test execution

The tests will be conducted as follows:
Step-by-step sequences for Configuration
1. Configuration of Client Equipment and the Application Server
desktop and database.
Step sequences for generating files for the 6 modules.
1. Execution of process (manual) for generating input files with the
entity information, contracting, suppliers, medications and
 QUALITY IN SOFTWARE DEVELOPMENT
Jairo Mendoza Tamara - 9176459
Activity 3

supplies, patients, and users to feed the SIS system and the database.
BDSIS data.
Step sequences for data generation for the 6 modules.
1. Execution of the (manual) data generation process, where the tables and
fields to be used will be filled in manually (Entity data, Suppliers,
users and Contracts) in mass (patients).