During the last two decades, application of Goal-Oriented Requirements Engineering has increased in software projects, mainly because this approach is useful during requirements analysis process and supports realization tasks such as elaboration, validation, planning, can be used part system life cycle, e.g. architecture design behavioral processes, coding, testing, monitoring, adaptation evolu...

As several mature implementations of data warehousing systems are fully operational, a crucial role in preserving their up-to-dateness is played by the ability to manage the changes that the data warehouse (DW) schema undergoes over time in response to evolving business requirements. In this paper we propose an approach to schema versioning in DWs, where the designer may decide to undertake som...

The Variations/FRBR project at Indiana University is experimenting with implementing the Functional Requirements for Bibliographic Records (FRBR) conceptual model in order to further research on next-generation library catalogs and promote the re-usability and interoperability of FRBR-based metadata. This paper describes the use of FRBR in some system implementations, discusses the first steps ...

Writing requirements is a two-way process. In this paper we use to classify Functional Requirements (FR) and Non Functional Requirements (NFR) statements from Software Requirements Specification (SRS) documents. This is systematically transformed into state charts considering all relevant information. The current paper outlines how test cases can be automatically generated from these state char...

The notion of Non Functional Requirement (NFR) of software system is not homogeneous. There is lack of consensus to answer questions as: What are they? How do they classify within the software development context? Also, knowing, how there are classified in the Web application development? In [1] we compared six Methodological approaches used for the development of Web applications in order to a...

The FRBR model is by many considered to be an important contribution to the next generation of bibliographic catalogues, but a major challenge for the library community is how to use this model on already existing MARC-based bibliographic catalogues. This problem requires a solution for the interpretation and conversion of MARC records, and a tool for this kind of conversion is developed as a p...

An increasing number of developers of virtual classrooms offer keyboard support and additional features for improving accessibility. Especially blind users encounter barriers when participating in visually dominated synchronous learning sessions. The existent accessibility features facilitate their participation, but cannot guarantee an equal use in comparison to non-disabled users. This paper ...

We use the term requirements to denote what are often called functional requirements. Requirements are located in the environment, which is distinguished from the machine to be built. A requirement is a condition over phenomena of the environment. A specification is a restricted form of requirement, providing enough information for the im-plementer to build the machine (by programming it) witho...

In 1998, the Functional Requirements for Bibliographic Records (FRBR) model which is composed by four entities (work, expression, manifestation and item) and their associative relationships ( primary, responsibility and subject ) , was proposed by the International Federation of Library Associations and Institutions (IFLA). The FRBR model can be deployed as a logical framework for proceeding me...

The FRBR model has the potential for new services and discovery techniques for cultural items such as books, movies and music. In this paper, we present an approach to interpret descriptions found in Web resources and identify the FRBR entities these pertain to. To verify the resulting set of FRBR entities, we have used the Linked Open Data and the veri cations have been validated by a group of...