Peer Review for material titled "Software requirements analysis, and why it doesn't work"
eTextbook Reviews for material titled "Software requirements analysis, and why it doesn't work"
User Rating for material titled "Software requirements analysis, and why it doesn't work"
Member Comments for material titled "Software requirements analysis, and why it doesn't work"
Bookmark Collections for material titled "Software requirements analysis, and why it doesn't work"
Course ePortfolios for material titled "Software requirements analysis, and why it doesn't work"
Learning Exercises for material titled "Software requirements analysis, and why it doesn't work"
Accessibility Info for material titled "Software requirements analysis, and why it doesn't work"
Please enter a Bookmark title
Please limit Bookmark title to 65 characters
Please enter a description
Please limit Bookmark title to 4000 characters
A Bookmark with this title already existed.
Please limit a note about this material to 2048 characters
Search all MERLOT
Select to go to your profile
Select to go to your workspace
Select to go to your Dashboard Report
Select to go to your Content Builder
Select to log out
Search Terms
Enter username
Enter password
Please give at least one keyword of at least three characters for the search to work with. The more keywords you give, the better the search will work for you.
Select OK to launch help window
Cancel help

MERLOT II

Advanced Search



        

Search > Material Results >

Software requirements analysis, and why it doesn't work

        

Software requirements analysis, and why it doesn't work

Logo for Software requirements analysis, and why it doesn't work
This is a great discussion of why software projects fail. Is it because of the requirements gathering process? Well this is the discussion, and quite interesting.
Go to material
Material Type: Reference Material
Technical Format: HTML/Text
Date Added to MERLOT: April 25, 2003
Date Modified in MERLOT: February 24, 2015
Author:
Submitter: Nagel

Quality

  • Reviewed by members of Editorial board for inclusion in MERLOT.
    Editor Review (not reviewed)
  • User review 4 average rating
  • User Rating: 4 user rating
  • Discussion (2 Comments)
  • Learning Exercises (none)
  • Bookmark Collections (1)
  • Course ePortfolios (none)
  • Accessibility Info (none)

  • Rate this material
  • Create a learning exercise
  • Add accessibility information
  • Pick a Bookmark Collection or Course ePortfolio to put this material in or scroll to the bottom to create a new Bookmark Collection
    Name the Bookmark Collection to represent the materials you will add
    Describe the Bookmark Collection so other MERLOT users will know what it contains and if it has value for their work or teaching. Other users can copy your Bookmark Collection to their own profile and modify it to save time.
    Edit the information about the material in this {0}
    Submitting Bookmarks...

About

Primary Audience: Graduate School, Professional
Mobile Compatibility: Not specified at this time
Language: English
Cost Involved: no
Source Code Available: no
Accessibility Information Available: no
Creative Commons: unsure

Connections



QR Code for this Page

Users who viewed this material also viewed...

Discussion

Discussion for Software requirements analysis, and why it doesn't work

Log in to participate in the discussions or Sign up if you are not already a MERLOT member.

Return to Top of Page
Avatar for Benjamin Rice
12 years ago

Benjamin Rice (Student)

It took me about five minutes to read thru this short article. What it lacked
in length, it more than made up for in impact. Though it didn?t provide any
?how-to? for a learning environment, it did serve as an effective wake-up call
for anyone attempting requirements elicitation. This is a good quick read to
ground anyone attempting the deceivingly difficult task.
Used in course

Avatar for Chris Ellis
13 years ago

Chris Ellis (Student)

This site presented several possible causes of project failure. It served as a
good reference tool.