GRAY WATCH: An extended design process

0Citations
Citations of this article
4Readers
Mendeley users who have this article in their library.
Get full text

Abstract

The process of developing a software product must have mechanisms to verify the quality of the product and the process under development. Talking about the quality of the resulting software requires taking into account a series of parameters that allow defining the minimum levels that a software product must meet to be categorized of quality. Thus, quality concerns corresponds to properties that characterize an architectural solution. The GRAY WATCH (GW) method is framed in the development of business software under the component reuse paradigm. This method lacks mechanisms that allow obtaining a quality architecture and needs to be improved. In order to resolve this deficiency, this article proposes to define and incorporate the activities and products that allow to expand the design process of GW. The aim of the proposals is to consider the ISO/IEC 25010 product quality standard, which defines criteria to stipulate the quality requirements for a software product, their measurement criteria and evaluation. It take into consideration a quality model composed of characteristics and sub-characteristics. The extension is supported by the Domain Engineering process, based in Software Quality “InDoCaS” and the “InDoCaSE” process as the methodologies for the definition of all products and activities in the Design process.

Cite

CITATION STYLE

APA

Pérez-Medina, J. L. (2020). GRAY WATCH: An extended design process. In Advances in Intelligent Systems and Computing (Vol. 1137 AISC, pp. 179–188). Springer. https://doi.org/10.1007/978-3-030-40690-5_18

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free