ACME/PRIME: Requirements Acquisition for Process-Driven Systems

Authors:
Mark Feblowitz;Sol Greenspan;Howard Reubenstein;Robert Walford
Affiliations:
GTE Labomtories Incorporated, Computer and Intelligent Systems Lab, 40 Sylvan Road, Waltham, Massachusett;GTE Labomtories Incorporated, Computer and Intelligent Systems Lab, 40 Sylvan Road, Waltham, Massachusett;GTE Labomtories Incorporated, Computer and Intelligent Systems Lab, 40 Sylvan Road, Waltham, Massachusett;GTE Telephone Gperation, Tampa, Florida
Venue:
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Year:
1996

Citing 6
Cited 3

A requirements modeling language and its logic

Information Systems
Knowledge representations as the basis for requirements specifications

Readings in artificial intelligence and software engineering
The Requirements Apprentice: Automated Assistance for Requirements Acquisition

IEEE Transactions on Software Engineering
On formal requirements modeling languages: RML revisited

ICSE '94 Proceedings of the 16th international conference on Software engineering
The Three Dimensions of Requirements Engineering

CAiSE '93 Proceedings of Advanced Information Systems Engineering
Addressing requirements issues within a conceptual modeling environment

IWSSD '91 Proceedings of the 6th international workshop on Software specification and design

Conflicts in Policy-Based Distributed Systems Management

IEEE Transactions on Software Engineering
CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements

Automated Software Engineering
Two Rule-Based Natural Language Strategies for Requirements Discovery and Classification in Open Source Software Development Projects

Journal of Management Information Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper discusses a requirements gathering methodology and tool support for a class of systems we term service-oriented systems. The requirements acquisition methodology that our tools support is, not surprisingly, a process centered methodology, since the processes of the system map to the services provided by our organization. The ACME/PRIME tool to support this methodology is built upon a conceptual modeling platform (ACME) that traces its roots to RML. The paper will discuss our approach to one of the fundamental problems of requirements engineering, i.e., dealing with over and under specification of requirements. We also provide some lessons learned from deploying the ACME/PRIME tool in our corporate requirements office.