This paper presents the AGENT method, a systematic test-case generation method for functional testing. AGENT consists of two steps. In the first step, a functional specification of a program is described with a formalized notation called a function diagram (FD). An FO consists of two components, a state transition which is described with a state transition diagram, and a set of boolean function...

the code for bibliographic description that replaces the Anglo-American Cataloging Rules (AACR2), is in use as of March 31, 2013. This code is based on the Functional Requirements for Bibliographic Records (FRBR), an entity-relationship model. This does not only affect bibliographic records: as of the same date, the Library of Congress and other national libraries will be producing authority re...

Recently, it has been pointed out that the majority of the requirements engineering methods do not take into account non-functional requirements (NFRs) [10][11]. Consequently, we have been experiencing serious problems during the development of software systems, such as cost and schedule overruns. In order to diminish this negligence of NFRs and its consequences, this work proposes a strategy (...

Using an interface displacement model derived from a microscopic density functional theory we investigate thin liquidlike wetting layers adsorbed on flat substrates with an embedded chemical heterogeneity forming a stripe. For a wide range of effective interface potentials we find first-order phase transitions as well as continuous changes between lateral interfacial configurations bound to and...

A normal form object-oriented entity relationship (OOER) diagram is presented to address a set of 00 data modelling issues, viz. the inability to judge the quality of an 00 schema, the presence of inheritance conflicts in ISA hierarchies, the lack of explicit support for different relationship types (m;n, n-ary, recursive etc.) in some 00 data models and the lack of general and flexible support...

Software inspections have attracted much attention over the last 25 years. It is a method for static analysis of artefacts during software development. However, few studies look at inspections of entity-relationship diagrams (ER-diagrams), and in particular an evaluation of the number of defects, number of false-positives and the types of defects that are found by most reviewers. ER-diagrams ar...

This paper presents mapping rules to conceptually model an Entity Relationship (ER) diagram and Extended Entity Relationship (EER) diagram from OWL by identifying ER and EER constructs in OWL. OWL has been designed for the semantic web, but data in OWL format is not easy to manipulate or query. The conceptual view of OWL presented in this paper is necessary to understand OWL and OWL data, and w...

To develop distributed applications requires to consider not only functional requirements but also nonfunctional requirements such as distributions, synchronizations, and scheduling policies. Specifying such non-functional requirements is necessary for supporting on-line capabilities of Autonomous Decentralized Systems (ADS). However, the existing design notations and methods do not address suc...

Without a formal methodology extracting entities from business descriptions, a business requirement in the real world cannot be abstracted correctly into an entity-relationship schema. Once core entities are discovered, we can obtain an Entity-Relationship Diagram (ERD) by inserting relationships between/among the relevant entities and by aggregating some attributes into one of the entities or ...

DEFINITION The extended entity-relationship (EER) model is a language for definition of structuring (and functionality) of database or information systems. It uses inductive development of structuring. Basic attributes are assigned to base data types. Complex attributes can be constructed by applying constructors such as tuple, list or set constructors to attributes that have already been const...