Abstract
AbstractIn the complex world of developing requirements and eliciting user needs, engineers build billions of dollars of products that are wrong on delivery, because they solved the wrong problem. The problem statement does change, because the environment (i.e., schedule, technology, people, or politics) changes. The Continuous Early Validation (CEaVa) refinement method will stabilize the problem statement (i.e., critical requirements or KPPs), which will enhance the probability of building the right product. We will highlight the second application on a billion dollar Army Information Technology system case study that utilized the CEaVa method.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
