Domain-Specific Automatic Programming
IEEE Transactions on Software Engineering - Special issue on artificial intelligence and software engineering
A requirements modeling language and its logic
On knowledge base management systems: integrating artificial intelligence and d atabase technologies
Proc. of the IFIP WG 8.1 working conference on Information systems design methodologies: improving the practice
A plan-based intelligent assistant that supports the software development
SDE 3 Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
Domain analysis: from art form to engineering discipline
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
A proposed perspective shift: viewing specification design as a planning problem
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Automated Acquisition of Evolving Informal Descriptions
Automated Acquisition of Evolving Informal Descriptions
On formal requirements modeling languages: RML revisited
ICSE '94 Proceedings of the 16th international conference on Software engineering
ACME/PRIME: Requirements Acquisition for Process-Driven Systems
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
| Hi-index | 0.00 |
This paper takes the position that research on how to formalize informal requirements information is not enough. One must actually identify what tasks the requirements analyst is undertaking, identify the types of knowledge that are being interrelated, and work out the desired relationships, or correspondences, between the various views. To do this, a conceptual modeling environment (ACME) is needed to define the various modeling viewpoints. An example is the definition of functional and architectural requirements and the assertion/retraction of design decisions that assign functions to components.