By Topic

Latin America Transactions, IEEE (Revista IEEE America Latina)

Issue 3 • Date July 2008

Filter Results

Displaying Results 1 - 10 of 10
  • Iberoamerican workshop on requirements engineering and software environments, ideas 2008 [special issue introduction]

    Page(s): 237
    Save to Project icon | Request Permissions | PDF file iconPDF (259 KB)  
    Freely Available from IEEE
  • Refactoring to Requirements Documents: An approach Aspect Oriented

    Page(s): 238 - 243
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (524 KB)  

    Typical problems of a requirements document, regarding its contents and organization, involve deficient modularization where requirements artifacts may deal with too much information, duplication of requirements, scattering requirements, tangled problems, among other problems. In this paper we describe how to improve requirements documents by removing duplication of information using aspect-oriented refactoring. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The role of Foundational Ontologies for Domain Ontology Engineering: a case study in the Software Process Domain

    Page(s): 244 - 251
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (502 KB)  

    Foundational ontologies are theoretically well-founded domain independent systems of categories that have been successfully used to improve the quality of conceptual modeling languages and models. In this paper, we present the latest developments in the UFO ontology. Moreover, we elaborate on the relevance of these foundational ontologies in the development of domain ontologies by showing a case study in the software process domain. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Evaluation of software development through an MDA tool: a case study

    Page(s): 252 - 259
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (440 KB)  

    Model Driven Architecture (MDA) was born as a standard of Model Driven Development (MDD) to increment the productivity in the software industry. Actually, there exist different models based tools to get an acceptable degree of automation in the applications generation. Many of those tools allow users to build software with high productivity in their respective domains. According their authors, the very challenge of MDA approach and tools is to put emphasis in a satisfactory degree of productivity and, at the same time, increasing others important software qualities such as portability, interoperability, reusability and maintainability. This paper intends to verify the effectiveness of such benefits analyzing the development of a real application using a MDA tool compared with a traditional approach. For analysis purpose, a series of metrics that can help to evaluate the different aspects related to the benefits of MDA was adopted. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Architectural requirements as basis to quality of software engineering environments

    Page(s): 260 - 266
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (884 KB)  

    In the last years, a proliferation of tools and software engineering environments (SEEs) can be noticed, impacting positively in software production. Although the reuse is focus of research in software development, tools and SEEs have been sometimes individually build, without attention in reusing development efforts. Besides that, the architectures of these tools and environments, as well as the establishment of reference architectures, have not been broadly investigated. This fact can make difficult integrating and evolving these environments. Thus, this paper aims at presenting a set of architectural requirements of SEEs. These requirements were the basis to establishment of a reference architecture of SEEs. Partial results have showed the viability of this architecture providing basis to incremental development of evolvable SEEs. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Unifying Models of Test Cases and Requirements

    Page(s): 267 - 274
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (889 KB)  

    In industry, due to market pressures, it is common that the system requirements are out of date or incomplete for certain parts of the system. Nevertheless, we can always find up to date test cases which implicitly complements the related requirements. Therefore, instead of simply using test cases to detect software failures, in this paper we present an approach to update requirements using test cases. To accomplish this, we first assume that both requirements and test cases are formally documented; we reuse previous works that provide such models automatically as CSP formal specifications. Thus, we formally define a merge operation using the operational semantics of CSP. Finally, we use part of a real case study to experience the proposed approach. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Em Busca de Agilidade na An??lise de Impacto: O Artefato FIR

    Page(s): 275 - 281
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (683 KB)  

    Requirements management uses traceability information to maintain the consistency between requirements and between requirements and other software artifacts. Accordingly, the impact analysis technique depends on traceability information for an agile estimative of the implications of requirement changes. The need to be agile imposes specific demands on traceability that may bring difficulties for the management of requirements. This paper presents FIR (functionality-information-rule), an artifact that supports traceability by means of more specialized links, in order to accommodate such demands. A simple example illustrates the applicability of the FIR artifact and is used to discuss some of its benefits and challenges . View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • An approach based on i* for security requirement analysis in data warehouses

    Page(s): 282 - 289
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (839 KB)  

    Requirement analysis approaches for data warehouse (DW) systems are only focused on information needs of decision makers, without considering other kind of requirement such as security or performance. However, modeling these issues in the early stages of the development is a cornerstone for building a DW that satisfies user expectations. In this paper, we define the two kinds of requirements for DWing as information and quality-of-service requirements. These requirements are defined within the MDA (Model Driven Architecture) framework, which allows their traceability towards the subsequent conceptual and logical design phases. It is worth mentioning that this paper focuses on proposing a requirement model for security (as a concrete kind of quality-of-service requirement), and a three-step process for modeling together information and security requirements. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • A Strategy for Automatic Conformance Testing in Embedded Systems

    Page(s): 290 - 297
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1011 KB)  

    Software testing is an expensive and time-consuming activity; it is also error-prone due to human factors. But, it still is the most common effort used in the software industry to achieve an acceptable level of quality for its products. An alternative is to use formal verification approaches, although they are not widespread in industry yet. This paper proposes an automatic verification approach to aid system testing based on refinement checking, where the underlying formalisms are hidden from the developers. Our approach consists in using a controlled natural language (a subset of English) to describe requirements (where it is automatically translated into the formal specification language CSP) and extracting a model directly from a mobile phone using a developed tool support; these artifacts are normalized in the same abstraction level and compared using the refinement checker FDR. This approach is being used at Motorola; the source of our case study. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Applying a Security Domain Requirements Engineering Process for Software Product Lines

    Page(s): 298 - 305
    Save to Project icon | Request Permissions | Click to expandQuick Abstract | PDF file iconPDF (1323 KB)  

    Security requirements management is especially important in software product lines, given that a weakness in security or a security breach can cause problems throughout all the products of a product line. The main contribution of this work is that of illustrating, by describing part of a real case study, a guided, systematic and intuitive way of dealing with security requirements from the early stages of the product line lifecycle by applying our proposed process of security requirements engineering for software product lines (SREPPLine), which makes it easier the variability and reusability management as well as the traceability relations of the security requirements in the product line. It is based on the use of the latest security requirements techniques, together with the integration of the Common Criteria (ISO/IEC 15408) and ISO/IEC 27001 controls, so that it facilitates the conformance of the product line and its products to the most relevant security standards with regard to the management of security requirements, such as ISO/IEC 27001 and ISO/IEC 15408. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.

Aims & Scope

IEEE Region 9 provides IEEE Latin America Transactions to enable the publication of non-published and technically excellent papers from Latin American engineers, in Spanish or Portuguese languages.

Full Aims & Scope

Meet Our Editors

Editor-in-Chief
José Antonio Jardini (Brasil)
IEEE Fellow Member