At Extreme 2003 a “late breaking” presentation by members of the UIUC/GSLIS Electronic Publishing Research group argued that XML Documents could not be assigned to either of the two plausible FRBR entity classes, manifestation or expression, since XML Documents appear to both have and lack some characteristics of each class. A “double aspect” theory was proposed where a single XML Document can ...

This paper attempts to shed light on the relationships between the concerns of sustainability and longevity in software and requirements engineering. Disciplines related to longevity of information and of systems can bring interesting ideas and perspectives to the discussion of sustainability. At the same time, sustainability clearly is a crucial component and critical success factor in determi...

A system cannot have high assurance if it has poor security, and thus, requirements for high assurance systems will logically include security requirements as well as availability, reliability, and robustness requirements. Unlike typical functional requirements, security requirements can potentially be highly reusable, especially if specified as instances of reusable templates. This paper discu...

This paper outlines the adaptation of IFLA's Functional Requirements for Bibliographic Records (FRBR) for development of a metadata scheme to represent palm leaf manuscripts (PLMs) and facilitate their retrieval in digital collections. The FRBR model uses a structured, four-level hierarchy to represent an intellectual work with multiple titles, editions or formats. Because FRBR focuses on repre...

Use cases are a popular way of specifying functional requirements of computer-based systems. Each use case contains a sequence of steps which are described with a natural language. Use cases, as any other description of functional requirements, must go through a review process to check their quality. The problem is that such reviews are time consuming. Moreover, effectiveness of a review depend...

In Requirements Engineering structural and functional requirements for a new software system are gathered, analyzed, and manifested. Unfortunately the connection between these aspects gets lost in the standard object oriented methodology and has to be re-established later on. Not only is this tedious work but the detection of conflicts and inconsistencies in early phases is hindered by the sepa...

In this paper, we describe the Probado music repository which is currently set up at the Bavarian State Library, Munich, as part of the larger German Probado digital library initiative. Based on the FRBR approach, we propose a novel work-centric metadata model for organizing the document collection. The primary data contained in the repository currently consists of scanned sheet music and digit...

The classification of NFRs brings about the benefits that NFRs with respect to the same type in the system can be considered and implemented aggregately by developers, and as a result be verified by quality assurers assigned for the type. This paper conducts an empirical study on using text mining techniques to classify NFRs automatically. Three kinds of

Introduction. To provide valuable services in the future, libraries will need to create better information systems and set up an infrastructure more in line with the current technologies. The Functional Requirements for Bibliographic Records conceptual model provides a basis for this transformation, but there are still a number of unresolved issues connected to its actual implementation. Method...

Non-functional requirements (NFR) have a crucial role in the software development process because they correspond to the characteristics and restrictions on which the software must running and represent factors that influence the time and cost of software development. Nevertheless, many organizations do not perform these requirements elicitation properly. This paper presents an approach to crea...