NATIONAL LEARNING SERVICE

SIGN

IE-AP08-AA9-EV03-Determine-Compliance-Quality.

TECHNOLOGIST IN ANALYSIS AND DEVELOPMENT OF INFORMATION

SYSTEMS

PRESENTED BY
Neftali Zambrano Ramirez

SIGN

August2021
IE-AP08-AA9-EV03-Determine-Compliance-Quality

Characteristic Sub feature Metrics Requir Level Compliance level C:

ed level obtain Complies
ed NC: Does not meet
NR: I dont know
requires
1 Functionality Compliance with Functional 0.9 0.9 C
functionality compliance.
standards.
2 Reliability Maturity. Fault 0.8 0.1 NC
detection
3 Easy to use Ability to be Revision of 0.9 0.9 C
operated. the
validations
to the data
input.
Preparation of the quality metrics report.
Analysis of results

In the previous table, 3 quality metrics were applied to evaluate 3 sub-characteristics and 3
quality characteristics of the software. Of the 3 metrics applied, only two comply and one
does not meet the expected quality levels.

Analysis by characteristics

The following table groups the results by characteristics:

Characteristic Expected quality Quality obtained Level of compliance

Functionality 0.9 0.9 C

Reliability 0.8 0.1 NC

Easy to use 0.9 0.9 C

It can be seen that only the functional characteristic and the ease-of-use characteristic are
fulfilled, therefore, the reliability does not meet what is expected.

The functional subcharacteristic metric (Functional compliance), refers to one of the

functional requirements of the system "System with multiple forms functionality", the
expected quality is met since after the tests it is effectively functional, the required forms are
enabled, all in accordance to the deliverables and the test scenario that were carried out in
the Traceability Matrix.

The reliability sub-characteristic metric (Detention of failures), refers to one of the functional
requirements such as "System security", the quality is not met since the system is not safe, is
not finished and requires tests.

The ease-of-use sub feature metric (Review of input data validations), refers to one of the
functional requirements as "One ID for each user", the expected quality is met since after the
tests it is effectively functional, the system validates that it is indeed a ID for each user.
Improvement opportunities.

After having identified the characteristic that did not comply, an action plan is proceeded to
improve the metric of the quality requirements. The above will be done to identify what were
the causes that led to non-compliance in the quality metric. It is expected that the system can
be finished according to your safety, the pertinent tests must be carried out so that it complies
with what is expected.