Carme Quer

DesCOTS: a software system for selecting COTS components

Selection of commercial-off-the-shelf software components (COTS components) has a growing importance in software engineering. Unfortunately, selection projects have a high risk of ending up into abandonment or yielding an incorrect selection. The use of some software engineering practices such as the definition of quality models can reduce this risk. We defined a process for COTS components selection based on the use of quality models and we started to apply it in academic and industrial cases. The need of having a tool to support this process arose and, although some tools already exist to partially support the involved activities, none of them was suitable enough. Because of this we developed DesCOTS, a software system that embraces several tools that interact to support the different activities of our process. The system has been designed taking into account not only functional concerns but also nonfunctional aspects such as reusability, interoperability and portability. We present in this paper the different subsystems of DesCOTS and discuss about their applicability.

Combined Selection of COTS Components

In this paper the problem of the combined selection of COTS components is analyzed in organizations of a specialized nature. This is currently a process of great interest: once many organizations have implemented recently ERP systems for supporting their central management areas, they need to select specialized components for other more particular business areas. We propose a model of combined selection of components based on the distinction of two levels. At the global level the combined selection process takes place, and it includes the initial planning, the enactment of the individual selection processes, the proposal of scenarios to evaluate and the final selection of COTS components. At the local level we locate all the individual selection processes of the different particular business areas, under the supervision of the process at the global level. The model presented here arises from the observation of an ongoing real case.

A Metamodel for Software Requirement Patterns

[Context and motivation] Software Requirement Patterns (SRP) are a type of artifact that may be used during requirements elicitation that also impact positively in other activities like documentation and validation. In our experiences, SRP show a great percentage of reuse for the non-functional requirements needed in call-for-tender requirement specifications. [Question / problem] We are facing the need of formulating the accurate definition of SRP for their use in call-for-tender processes to allow reasoning rigorously and know more about their semantics and applicability. [Principal ideas / results] In this paper we present a metamodel for SRP around three main concepts: 1) the structure of SRP themselves; 2) the relationships among them; 3) the classification criteria for grouping them. [Contribution] We provide a rigorous definition that shows the concepts that are of interest when defining and applying SRP.

PABRE: Pattern-based Requirements Elicitation

This paper presents our PABRE method for facilitating Requirements Elicitation on the basis of Requirement Patterns with the goal of saving time and reducing errors during this activity. The process presented applies for elicitation in Off-The-Shelf selection projects driven by call for tenders processes and uses a Requirement Patterns Catalogue. The process selects patterns from the catalogue that apply to the particular selection project, and convert them into the real requirements that finally configure the project Requirements Book. We show some benefits of the pattern approach for requirements engineers and IT consultants, as well as for customers. Finally we discuss the strengths and weaknesses of the proposal and identify some future work.

Characterization of a Taxonomy for Business Applications and the Relationships Among Them

In this paper we propose a taxonomy for classifying COTS business applications, i.e. products that are used in the daily functioning of all types of organizations worldwide, such as ERP systems and document management tools. We propose the identification of characterization attributes to arrange the domains which these products belong to, and also we group these domains into categories. We define questions and answers as a means for browsing the taxonomy during COTS selection. We show the need of identifying and recording the relationships among the domains and propose the use of actor-oriented models for expressing these relationships as dependencies. Last, we explore the definition of quality models for the domains, to be used in COTS selection, focusing on their reusability and stepwise definition downwards the hierarchy.

Managing Non-Technical Requirements in COTS Components Selection

The selection of COTS components is made not only by an analysis of their technical quality but also (and sometimes mostly) by considering how they fulfill those non-technical requirements considered relevant, which refer to licensing, reputation, and similar issues. In this paper we present an approach for managing nontechnical requirements during COTS selection. The proposal is based on extending the ISO/IEC 9126-1 catalogue of quality factors by adding factors related to non-technical issues, obtaining a cohesive and comprehensive framework for managing requirements during selection

COSTUME: a method for building quality models for composite COTS-based software systems

The use of quality models during the selection of commercial, off-the-shelf (COTS) products provides a framework for the description of the domains which the COTS products belong to. Descriptions of COTS products and user quality requirements may be translated into the quality concepts defined in the model, making selection more efficient and reliable. We propose a method for the construction of quality models for composite COTS-based software systems (CCSS), defined as systems that are composed by several interconnected COTS products. Selection processes carried out when procuring a CCSS require not a single COTS product to be selected but a set of them. As a consequence, instead of a classical quality model, we need a more elaborated one, defined as the composition of those models that belong to the domains of the COTS products that form the CCSS.

Towards a Quality Model for the Selection of ERP Systems

ERP systems are a category of COTS products that offers extensive support to the management of business processes in most kind of companies and organizations. Due to their increasing adoption and the risks coming from their incorrect selection, efforts towards effective and reliable selection methods should have a positive impact in the community. This chapter proposes the adoption of quality models as a means for structuring the description of the capabilities of such type of products. The ISO/IEC 9126-1 quality standard is chosen as a framework, and a methodology for tailoring it to this specific domain is followed. The chapter also shows the formalization of the quality model by using a formal language. Last, the use of the quality model for processing quality requirements is also addressed.

LEARN-SQL: Automatic Assessment of SQL Based on IMS QTI Specification

In this paper we present LEARN-SQL, a system conforming to the IMS QTI specification that allows on-line learning and assessment of students on SQL skills in an automatic, interactive, informative, scalable and extensible manner.

SYSTEMATIC CONSTRUCTION OF i STRATEGIC DEPENDENCY MODELS FOR SOCIO-TECHNICAL SYSTEMS

Goal- and agent-oriented models have become a consolidated type of artifact in various software and knowledge engineering activities. Several languages exist for representing such type of models but there is a lack of associated methodologies for guiding their construction up to the necessary level of detail. In this paper we present RiSD, a method for building Strategic Dependency (SD) models in the i* notation. RiSD is defined in a prescriptive way to reduce uncertainness when constructing the model. RiSD tackles three fundamental issues: (1) it tends to reduce the average size of the resulting models; (2) it defines some traceability relationships among model elements; (3) it provides some lexical and syntactical conventions. As a result, we may say that RiSD supports the construction process of goal- and agent-oriented models whilst increasing their understanding.