On the frame problem in procedure specifications

The paper provides examples of situations where formal specifications of procedures in the standard pre/postcondition style become lengthy, cumbersome and difficult to change, a problem which is particularly acute in the case of object oriented specifications with inheritance. We identify the problem as the inability to express that a procedure changes only those things it has to, leaving everything else unmodified, and review some attempts at dealing with this “frame problem” in the software specification community. The second part of the paper adapts a recent proposal for a solution to the frame problem in artificial intelligence-the notion of explanation closure axioms-to provide an approach whereby one can state such conditions succinctly and modularly, with the added advantage of having the specifier be reminded of things that she may have omitted saying in procedure specifications. Since this approach is based on standard predicate logic, its semantics are relatively straightforward. The paper also suggests an algorithm which generates syntactically the explanation closure axioms from the pre/postcondition specifications, provided they are written in a restricted language; it also suggests a model theory supporting it     

Exploring alternatives during requirements analysis

Goal-oriented requirements analysis techniques provide ways to refine organizational and technical objectives, to more effectively explore alternatives during requirements definition. After selecting a set of alternatives to achieve these objectives, you can elaborate on them during subsequent phases to make them more precise and complete. The authors argue that goal-oriented analysis complements and strengthens traditional requirements analysis techniques by offering a means for capturing and evaluating alternative ways of meeting business goals. They detail the five main steps that comprise goal-oriented analysis. These steps include goal analysis, softgoal analysis, softgoal correlation analysis, goal correlation analysis, and evaluation of alternatives. To illustrate the main elements of the proposed analysis technique, they explore a typical scenario that involves defining requirements for a meeting scheduling system     

Tropos: An Agent-Oriented Software Development Methodology

Our goal in this paper is to introduce and motivate a methodology, called Tropos,¹ for building agent oriented software systems. Tropos is based on two key ideas. First, the notion of agent and all related mentalistic notions (for instance goals and plans) are used in all phases of software development, from early analysis down to the actual implementation. Second, Tropos covers also the very early phases of requirements analysis, thus allowing for a deeper understanding of the environment where the software must operate, and of the kind of interactions that should occur between software and human agents. The methodology is illustrated with the help of a case study. The Tropos language for conceptual modeling is formalized in a metamodel described with a set of UML class diagrams.     

The Migration of Multi-tier E-commerce Applications to an Enterprise Java Environment

As technology evolves, many organizations face the problem of migrating legacy applications from one technology base to another. We report on a case study involving the migration of legacy code into the IBM® WebSphere® Commerce Suite product. Specifically, we focus on the problem of migrating applications that use traditional database access techniques to applications using the Enterprise JavaBean (EJB) programming model. Our results include a practical methodology that facilitates such migration, as well as a tool that supports this methodology. The tool has been released on IBM's alphaWorks site.     

Ontologies for Knowledge Management: An Information Systems Perspective

Knowledge management research focuses on concepts, methods, and tools supporting the management of human knowledge. The main objective of this paper is to survey basic concepts that have been used in computer science for the representation of knowledge and summarize some of their advantages and drawbacks. A secondary objective is to relate these techniques to information science theory and practice.The survey classifies the concepts used for knowledge representation into four broad ontological categories. Static ontologies describe static aspects of the world, i.e., what things exist, their attributes and relationships. A dynamic ontology, on the other hand, describes the changing aspects of the world in terms of states, state transitions and processes. Intentional ontologies encompass the world of things agents believe in, want, prove or disprove, and argue about. Finally, social ontologies cover social settings – agents, positions, roles, authority, permanent organizational structures or shifting networks of alliances and interdependencies.     

Simulation Modeling of Runoff,Groundwater Flow and Sediment Transport into Kastoria Lake,Greece

Kastoria Lake is located in northwestern Greece. The whole basin of the lake is about 253 km². For the computation of the surface water volume inflowing into the lake from the main streams of the sub-basins located around Kastoria Lake, a rainfall-runoff sub-model is used. A quasi-three-dimensional simulation model of the Kastoria basin aquifer is also realized, in order to estimate the groundwater contribution to the volumetric budget of the lake and the whole basin as well. For the computation of sediment load inflowing into the lake from the main streams of the sub-basins, the rainfall-runoff sub-model is combinedwith a soil erosion sub-model and a sediment transport sub-model for streams. A GIS was developed in the hydrologic basin with all data needed for parameter identification and model application. The data base was enriched by a series of on site measurements of water discharge made in all main streams for one whole hydrologic year. By means of the resulting mathematical sediment model, those sub-basins, which deliver most sediment load to the lake, are identified. On the basis of this identification, a series of control measures, for the reduction of sediment inflowing into the lake, at certain places of the above mentioned sub-basins is proposed.     

Making XML document markup international

In name and in practice, the World‐Wide Web (hereafter Web) is used around the World beyond English‐speaking areas. This creates a tremendous need to internationalize standard terminology used in the technologies that make the Web possible. Existing efforts on XML internationalization (i18n) and localization (i10n) have focused on the content of XML documents instead of the terms used in markup (annotations) such as elements and attributes. The SGML standard ISO 8879 supports the use of Unicode (ISO 10646) throughout a document, including markups. However, most elements and attributes of XML documents are still defined in English, thereby limiting their use among non‐English speakers. This paper presents an XSLT‐based method that can completely localize the markup of XML documents into different natural languages. We also describe how the proposed technique can be applied to translation problems in programming (e.g. C and Java) or documentation (e.g. LAT_EX or other formatting languages) so that a program or a document can be converted to and from an XML format. Copyright © 2004 John Wiley & Sons, Ltd.     

TORUS: A step towards bridging the gap between data bases and the casual user

This paper describes TORUS, a natural language understanding system that serves as a front end to a data base management system in order to facilitate communication with casual users. The system employs a semantic network to store knowledge about a data base of student files. This knowledge is used to find the meaning of each input statement, to decide what action to take with respect to the data base, and to select information that must be output in response to the input statement. A prototype version of TORUS has been implemented.