Knowledge Representation as the Basis for Requirements Specifications

Borgida,; Greenspan,; Mylopoulos,

doi:10.1109/mc.1985.1662870

Cited by 194 publications

(1 citation statement)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The methodology that we present in this section (see also [18,19]) conibines the OOA, hierarchical structuring, stepwise refinement by specialization [20] and inforniation hiding with the use of tlie client-serverservice paradigm.…”

Section: The Methodologymentioning

confidence: 99%

A framework for object oriented design and prototyping of manufacturing systems

Menga

Morisio

Mancin³

Proceedings. 1991 IEEE International Conference on Robotics and Automation

View full text Add to dashboard Cite

Object Oriented Programming, through the use of a library of standard classes and their inheritance relationships, offers a consistent fraiiiework to specify, desigil and prototype the software architecture of coiiiplex discrete event control systems.This paper applies such a fraiiiework to Coiiiputer Integrated Manufacturing, proposing a unified view to represent the hierarchical control structure of a coiiimonly accepted reference model. The results are a library of classes (called G++ and based on the C++ prograiiiniing language) to express concurrency and to support aii extended client server paradigin, aiid a new design methodology.

show abstract

Section: The Methodologymentioning

confidence: 99%

A framework for object oriented design and prototyping of manufacturing systems

Menga

Morisio

Mancin³

Proceedings. 1991 IEEE International Conference on Robotics and Automation

View full text Add to dashboard Cite

show abstract

GSL: a requirements specification language for end‐user intelligibility

Wijayarathna¹,

Kawata²,

Santosa³

et al. 1998

Softw: Pract. Exper.

View full text Add to dashboard Cite

Software Requirements Specifications (SRS) have been used to fill the communication gap between systems analysts and the end‐users. SRSs should satisfy the needs of both systems analysts and end‐users. Non‐technical end‐users require intelligible SRSs while systems analysts need more precise, clear and concise SRSs. Object‐oriented methods cannot represent temporal relations between events precisely. However, object‐oriented principles are widely used in systems analysis and designing. Hence, there is a need for a software requirements specification language which supports object‐oriented analysis methods, represents temporal knowledge precisely and whose representation scheme resembles natural languages. The specification language presented in this paper, GSL, is designed to meet the above requirements. The language is based on First‐order Temporal Logic (FTL), which has temporal operators in addition to classical logical connectives and quantifiers. Since FTL cannot represent relative temporal knowledge and it inherits problems with point‐based time models, a new logical connective TAND and redefined AND connective are used to represent relative temporal knowledge and to solve the problems with FTL. The language employs object‐oriented principles: events, conditions, rules and activities can be represented as objects as well as attributes of an object. However, systems analysts can decide whether to use object‐oriented conceptual modeling or not. © 1998 John Wiley & Sons, Ltd.

show abstract

Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering

Mylopoulus

1996

Int. J. Intell. Syst. Acc. Fin. Mgmt.

View full text Add to dashboard Cite

One step towards a more systematic approach to the design of business processes is to develop models that provide appropriate representations of the knowledge that is needed for understanding and for reasoning about business processes. We present a modelling framework which uses goals, rules and methods to support the systematic analysis and design of business processes. The frame‐work consists of two main components—a Strategic Dependency model that describes a process organization in terms of intentional dependencies among actors, and a Strategic Rationale model that supports reasoning during process redesign. Formal representation of these models allows computer‐based tools to be developed as extensions to, and eventually integrated with, other tools for supporting information systems development.

show abstract

Knowledge Representation as the Basis for Requirements Specifications

Cited by 194 publications

References 6 publications

A framework for object oriented design and prototyping of manufacturing systems

A framework for object oriented design and prototyping of manufacturing systems

GSL: a requirements specification language for end‐user intelligibility

Using Goals, Rules and Methods to Support Reasoning in Business Process Reengineering

Contact Info

Product

Resources

About