A framework for analyzing and testing requirements with actors in conceptual graphs

Authors:
B. J. Smith;Harry Delugach
Affiliations:
Computer Science Department, University of Alabama in Huntsville, Huntsville, AL;Computer Science Department, University of Alabama in Huntsville, Huntsville, AL
Venue:
ICCS'06 Proceedings of the 14th international conference on Conceptual Structures: inspiration and Application
Year:
2006

Citing 5
Cited 2

Conceptual structures: information processing in mind and machine

Conceptual structures: information processing in mind and machine
Software requirements: objects, functions, and states

Software requirements: objects, functions, and states
An approach to conceptual feedback in multiple viewed software requirements modeling

ISAW '96 Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96) on SIGSOFT '96 workshops
Capture, Integration, and Analysis of Digital System Requirements with Conceptual Graphs

IEEE Transactions on Knowledge and Data Engineering
Acquiring Software Requirements As Conceptual Graphs

RE '01 Proceedings of the Fifth IEEE International Symposium on Requirements Engineering

A Framework for Analyzing and Testing Overlapping Requirements with Actors in Conceptual Graphs

ICCS '07 Proceedings of the 15th international conference on Conceptual Structures: Knowledge Architectures for Smart Applications
Another Reason Why Conceptual Graphs Need Actors

ICCS '09 Proceedings of the 17th International Conference on Conceptual Structures: Conceptual Structures: Leveraging Semantic Technologies

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software has become an integral part of many people's lives, whether knowingly or not. One key to producing quality software in time and within budget is to efficiently elicit consistent requirements. One way to do this is to use conceptual graphs. Requirements inconsistencies, if caught early enough, can prevent one part of a team from creating unnecessary design, code and tests that would be thrown out when the inconsistency was finally found. Testing requirements for consistency early and automatically is a key to a project being within budget. This paper will share an experience with a mature software project that involved translating software requirements specification into a conceptual graph and recommends several actors that could be created to automate a requirements consistency graph.