Creating methodological proposal to confirm

quality metric of completeness

Rodrigo Mercado Seplveda
Universidad Catlica del Maule
August, 2015
Abstract
Given the minimal importance of making requests, in contrast with the real importance, is that this
research is motivated, to create a new metodology, for developments small and medium. The
objective of this investigation is to determine the completeness the metodology capable of
establish a paralel between the feed of requisite (Natural Language) and the relational model or the
data base of the data selected. The methodology used to determine the quality (completeness) of the
software well be is(tiempo verbal en presente en todo el documento) the Lexical-Morphological
Analysis from the gathering of requeriments proposed by Navarro(insertar bibliografa). The results
obtained satisfy the purpose of this investigation, since 90% of the sample work done, indicate to
have obtained a better software after applying the methodology, but more importantly and that it
simplified a necessary process that previously was done, for the requeried time. The proposal we
may help to improve draw from this research is the development of new tools that allow the
measurement of other quality metrics, such as integrity, accessibility, in the software.
Keywords -- Requeriments, Metrics, Completeness, Relational Model, Methodology.
Verificar bien los objetivos con todas las acciones realizadas
1.-

Introduction

1.1

Context / Motivation

Given the limited importanco of documentatin in making requirements of

software development process (Faulk, 1992)(Lutz, 1993), is that, whit the
traceability that gives this model making a link with the database (physical
model), it has been estimated that this solution is a cornerstone when requiring
a change of software, maintaining adequate levels in the metric of
completeness for the estimation of de quality.
1.2

State of art

(Navarro, 2005) uses a lexical analyzer, where in the data source it is making
requests, generating with it, the metric of completeness, assuming that the
tool will have the ability to determine all software requirements. That
assumption is that which is considered successful, as making requests is one of
the stages of development, in complement with modeling (meeting with

experts) delivery all software requirements. For this, rejects the proposal
making requests as the sole source of data and adds the physical model as a
source of more refined data and greater detail.
Sommerville indicates the completion means no default service, restrictions or
actions to be performed by the software. Firesmith (Firesmith, 2005) deepens
further the concept of incompleteness indicating that there is incompleteness
in requirements model, this is, when a requirement is omitted completely, that
is to say, was not specified, there is also individually on each of the
requirements, where despite specify it, information needed for it to be
implemented no additional information.
The lexical language extended (LEL) is a glossary whith the connotation and
denotation of the terms used in the domain of the making requests. (Leite,
1993)
The physical model proposed by many authors (Navarro 2005, Leite 1993)
deliver to developers the communication tool to convey to the end user or
customer the generated model from making requests, allowing detect probably
needs undetected or initially described.
1.3

Methodology

Studies on the quality of decision requirements which are measured in metric

and completeness, readability, Correctness, minimality, expressiveness, selfexplanation, consistency, etc.
Estimating completeness intends, in a different way to that done in other
studies, since, in many of them it is performed a syntactic lexical analysis, on a
reality that, in most developments, it is unknown by programmers, therefore,
difficult to measure a priori. The proposed methodology performs a
measurement of the completeness with respect to a making requests in
addition to the physical model.
In the proposed methodology will be performed a lexical analysis, where the
user indicates the ratio of each word with the correspondence at physical
model. The idea is to make a visual mapping, making a link between the word
and the object representing an entity, attribute or cardinality.
The steps to obtain completeness were:

Perform making requests

Perform physical model
Generate correspondence between model and requirements
Calculating deliver bidirectional completeness.

1.4
In section one introducing occurs, in section two presented studies
related to the topic at hand, on which it intends to deliver an improvement or
at least a different point of view of the currently used to. In section tree present
the results obtained in this paper for end in section four with conclusions and
proposals for improvement and future work.

Methodology

2.1

Making requirements

Making two requirements are reviewed and implemented systems, where there
is already a physical model. Making requests is defined in meetings had with
customers. There were two groups of interviewers, Group One, formed by
internal analysts (belonging to the client) and outside analysts (belonging to
the developer company).
Three meetings were held with customers (managers or specialists areas
knowledgeable business model) where a set of questions was conducted, which
it increases as they move meetings.
An important part of making requests are substantive, indicating the possible
existence of an entity the physical model, this is why, using a reduced Spanish
dictionary they were previously identified possible entities, to facilitate the task
of the analyst. To the above was used lexical extended processing (LEL) (Litvak,
2012).
2.2

Reading the physical model

As in making requests, the physical model was in operation in systems where

the measurement was performed completeness, helping to verify the
subsequent calculation of the indicator.
2.3 To generate relationship between the physical model and the requirements.
Once we have the requirements and the physical model, we need to connect
both, identifying in a first step the name of the entities of the physical model in
the requirements taken, to show the possible entities, for the above, it was
carried out the following:

Indexing the collection of entities of the

physical model:
At this stage NPL techniques (natural language
processing ) were applied , generating the index
with the entity descriptions.
Indexing the set of requirements:
Here the same NPL techniques were applied,
generating an index with descriptions of the requirements. Therefore, once a
user enters a request, the system analyzes to parallelize user needs
(requirements) associating with similar characteristics in the physical model .

The results extracted from the proposed methodology are similar to making
substantive requirements and the physical model. First, the calculation is
performed with the requests made by Group 1, without taking into
consideration the physical model, same methodology for group 2. Then, the
completeness is calculated according to the requests sample made,
considering the physical model.

3
3.1

Results
To deliver bidirectional completeness calculation.

Once the physical model and the requests sample are linked by the comparison
function, we can determine the percentage of completeness of the system. In
previous studies it has been determined that the metric of completeness, in
best cases reached 50 % (Litvak, 2012), therefore, we consider successful an
increasement of this value, given that the calculation is performed at a later
stage of the study (once you have the physical model).

For comparison of metric, values of completeness of the same system were

taken,with and without physical model, and the results obtained are:
Analysis
without
the
physical
model
Group 1 28
Group 2 37
Groups
/
Analysi
s

Analysis
Level
of
Level
of
with the
Complete
Complete
physical
ness
ness
model
37%
43%

43
54

42%
54%

To have the physical model of the database increases the level of completeness
Another important aspect to consider, is that, having the physical model, a
greater number of parameters to be measured can be seen, which indicates
that the display model helps to better understand the case.

4.-

Conclusion

After applying the new methodology, it was obtained a better indicator of

completeness keeping an eye on the physicalmodel, this is independent to the
knowledge of the business model.
Also it can be concluded that having the physical model , more detail is
achieved in making requirements while increasing completeness indicator .
It would be a great future work, because the application would allow to modify
in real time the specific model, to have both tools and determine in higher
measure the completeness of the software. (impactanalysis).