Fast, Cheap Requirements: Prototype, or Else!
IEEE Software
Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
The unified software development process
The unified software development process
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Specification-based prototyping for embedded systems
ESEC/FSE-7 Proceedings of the 7th European software engineering conference held jointly with the 7th ACM SIGSOFT international symposium on Foundations of software engineering
Graphical animation of behavior models
Proceedings of the 22nd international conference on Software engineering
Writing Effective Use Cases
Software Requirements Engineerings, 2nd Edition
Software Requirements Engineerings, 2nd Edition
ICCBSS '02 Proceedings of the First International Conference on COTS-Based Software Systems
SCR*: A Toolset for Specifying and Analyzing Software Requirements
CAV '98 Proceedings of the 10th International Conference on Computer Aided Verification
Agile and Iterative Development: A Manager's Guide
Agile and Iterative Development: A Manager's Guide
Scenario-Based Requirements Engineering
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Goal-Oriented Requirements Animation
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Research Directions in Requirements Engineering
FOSE '07 2007 Future of Software Engineering
Cmmi® distilled: a practical introduction to integrated process improvement, third edition
Cmmi® distilled: a practical introduction to integrated process improvement, third edition
Generating systems requirements with facilitated group techniques
Human-Computer Interaction
Hi-index | 0.00 |
A new synthesis of software requirements models called pseudo software is proposed with the aim to cut requirements-related errors. Pseudo software achieves this aim by serving as a mediating instrument to empower stakeholders to participate in requirements elicitation and validation through model construction and manipulation, and to provide guidance to the development team to correctly interpret the requirements in the downstream development activities. Pseudo software obtains its traits as a mediating instrument through the choice of requirements information bits and the use of multimodal representations with tool support to integrate the requirements. Using historical data of fifty projects in the enterprise computing domain, pseudo software is shown to effectively cut the requirements-related errors committed by both the customer and the development team.