The Requirements Apprentice: Automated Assistance for Requirements Acquisition
IEEE Transactions on Software Engineering
Representing and using nonfunctional requirements: a process-oriented approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Supporting Software Designers with Integrated Domain-Oriented Design Environments
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Process reuse using a template approach: a case-study from avionics
ACM SIGSOFT Software Engineering Notes
A case-study of requirements reuse through product families
Annals of Software Engineering
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Technology Transfer for Reuse: A Management Model and Process Improvement Framework
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Addressing requirements issues within a conceptual modeling environment
IWSSD '91 Proceedings of the 6th international workshop on Software specification and design
Using focus rules in requirements elicitation dialogues
IJCAI'99 Proceedings of the 16th international joint conference on Artifical intelligence - Volume 1
| Hi-index | 0.00 |
The Listener is an automated system that unintrusively performs knowledge acquisition from informal input. The Listener develops a coherent internal representation of a description from an initial set of disorganized, imprecise, incomplete, ambiguous, and possibly inconsistent statements. The Listener can produce a summary document from its internal representation to facilitate communication, review, and validation. A special purpose Listener, called the Requirements Apprentice (RA), has been implemented in the software requirements acquisition domain. Unlike most other requirements analysis tools, which start from a formal description language, the focus of the RA is on the transition between informal and formal specifications.