Recording the reasons for design decisions
ICSE '88 Proceedings of the 10th international conference on Software engineering
CASE productivity perceptions of software engineering professionals
Communications of the ACM - Special issue: multiprocessing
A proposed perspective shift: viewing specification design as a planning problem
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Integrating multiple specifications using domain goals
IWSSD '89 Proceedings of the 5th international workshop on Software specification and design
Supporting Systems Development by Capturing Deliberations During Requirements Engineering
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Goal-directed requirements acquisition
6IWSSD Selected Papers of the Sixth International Workshop on Software Specification and Design
Inquiry-Based Requirements Analysis
IEEE Software
The changing roles of the systems analyst
Information Resources Management Journal
A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification
IEEE Transactions on Software Engineering
ConceptBase—a deductive object base for meta data management
Journal of Intelligent Information Systems - Special issue: deductive and object-oriented databases
Computer related risks
A meta-model for restructuring stakeholder requirements
ICSE '97 Proceedings of the 19th international conference on Software engineering
Supporting the negotiation life cycle
Communications of the ACM
Managing Requirements Inconsistency with Development Goal Monitors
IEEE Transactions on Software Engineering
Software Engineering Economics
Software Engineering Economics
Requirements and Specification Exemplars
Automated Software Engineering
Identifying Quality-Requirement Conflicts
IEEE Software
IEEE Software
CORE - a method for controlled requirement specification
ICSE '79 Proceedings of the 4th international conference on Software engineering
Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Using non-functional requirements to systematically support change
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
A Systematic Tradeoff Analysis for Conflicting Imprecise Requirements
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Goal-Based Requirements Analysis
ICRE '96 Proceedings of the 2nd International Conference on Requirements Engineering (ICRE '96)
Electronic Brokering for Assisted Contracting of Software Applets
HICSS '97 Proceedings of the 30th Hawaii International Conference on System Sciences: Information Systems Track—Internet and the Digital Economy - Volume 4
Managing Requirements Inconsistency with Development Goal Monitors
IEEE Transactions on Software Engineering
Requirements, domain and specifications: a viewpoint-based approach to requirements engineering
Proceedings of the 24th International Conference on Software Engineering
Requirements interaction management
ACM Computing Surveys (CSUR)
Discovering Multidimensional Correlations among Regulatory Requirements to Understand Risk
ACM Transactions on Software Engineering and Methodology (TOSEM)
Hi-index | 0.00 |
Systems requirements errors are numerous, persistent, and expensive. To detect such errors, and focus on critical ones during the development of a requirements document, we have defined Root Requirements Analysis. This simple technique is based on: generalizing requirements to form root requirements, exhaustively comparing the root requirements, and applying simple metrics to the resultant comparison matrix. Root Requirements Analysis is effective. In the case study described in this article, the technique finds that 36 percent of the case's root requirements interactions result in problems which require further analysis. Moreover, the technique provides a specific, operational procedure to guide the efficient iterative resolution of identified requirements conflicts. The process of Root Requirements Analysis itself is not specific to a particular methodology. It can be applied directly to requirements in a variety of forms, as well as to the documentation of requirements development. We took this later approach in the case study illustrating how Root Requirements Analysis can augment the Inquiry Cycle model of requirements development. Finally, the technique is amenable to support through collaborative CASE tools, as we demonstrate with our DEALSCRIBE prototype.