Critical requirements engineering issues & their solution

Proceedings - 2009 International Conference on Computer Modeling and Simulation, ICCMS 2009

Volumn , Issue , 2009, Pages 218-222

  Naz, Humaira ^a   Khokhar, Muhammad Nadeem ^a  

^a SHAHEED ZULFIKAR ALI BHUTTO INSTITUTE OF SCIENCE AND TECHNOLOGY   (Pakistan)

Author keywords

Component; Requirements engineering; Requirements management

Indexed keywords

COMPONENT; INTERNATIONAL RESEARCHES; REQUIREMENTS GATHERINGS; REQUIREMENTS MANAGEMENT; RESEARCH STUDIES; SOFTWARE INDUSTRIES; SOFTWARE PROJECTS;

COMPUTER SIMULATION; COMPUTER SOFTWARE;

REQUIREMENTS ENGINEERING;

EID: 64849105631     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICCMS.2009.50     Document Type: Conference Paper

References (9)

1. Bauer, Martin. Requirements Gathering Essentials. January 12th 2005.
2. Bahill, A.T.; F.F. Dean.Research to recycle - Discovering System Requirements. Retrieved on 2006-05-03., from the abstract: "Customer dissatisfaction and cost overruns are often caused by poor requirements that are produced by people who do not understand the requirements process. ⋯ System requirements, however, are seldom stated by the customer." Copyright © 1996 and 1997
3. Wikipedia. Requirements analysis. 2006.
4. Wiegers, Karl. 10 Requirements Traps to Avoid. January/February 2000, published in Software Testing & Quality Engineering.
5. McConnell, Steven. Rapid Development: Classic Mistakes Enumerated. 1996, 1st ed., Redmond, WA: Microsoft Press. ISBN 1-55615-900-5.
6. Rothman, Johanna. Successful Engineering Management: 7 Lessons Learned. 1999. Presented at Electro '99, June 16.
7. McConnell, Steven. Survival Crib Notes. From book "Software Project Survival Guide". 1997-1998.
8. Dr. Dorsey, Paul. Top 10 Reasons Why Systems Projects Fail. 2000.
9. Leffingwell, Dean & Don Widrig. Managing Software Requirements. 2004, Second Edition.