BCA/MCA - Software Engineering - RISKS ASSOCIATED WITH SOFTWARE DEVELOPMENT (#ipumusings)(#softwaredevelopment)
RISKS ASSOCIATED WITH SOFTWARE DEVELOPMENT
Software development fails to deliver, and fails to deliver value. This failure has massive monetary and human impact. We want to find a new ways to develop software applications.
The basic problem of software development is risk. Here are some examples of
risk:
Schedule slips
—the day for transport comes, and you have to tell the purchaser that the software program won't be equipped for some other six months.
Project canceled
—after several slips, the assignment is canceled without ever going into production.
System is going sour
—the software is efficaciously put into production, but after more than one years the fee of creating changes or the defect rate rises a lot that the gadget ought to be replaced.
Defect Price
—the software program is placed into production, but the illness price is so excessive that it isn't used.
Business misunderstood
—the software program is placed into production, but it does not remedy the enterprise trouble that was at the beginning posed.
Business Model changes
—the software program is placed into production, but the business trouble it was designed to solve was changed six months in the past by way of some other, greater pressing, enterprise problem.
False feature List (No Value Add)
—the software has a host of probably thrilling functions, all of which had been a laugh to application, however none of which makes the consumer lots cash.
Staff turnover
—after two years, all of the accurate programmers on the task start to hate the program and depart.
Schedule slips
—the day for transport comes, and you have to tell the purchaser that the software program won't be equipped for some other six months.
Project canceled
—after several slips, the assignment is canceled without ever going into production.
System is going sour
—the software is efficaciously put into production, but after more than one years the fee of creating changes or the defect rate rises a lot that the gadget ought to be replaced.
Defect Price
—the software program is placed into production, but the illness price is so excessive that it isn't used.
Business misunderstood
—the software program is placed into production, but it does not remedy the enterprise trouble that was at the beginning posed.
Business Model changes
—the software program is placed into production, but the business trouble it was designed to solve was changed six months in the past by way of some other, greater pressing, enterprise problem.
False feature List (No Value Add)
—the software has a host of probably thrilling functions, all of which had been a laugh to application, however none of which makes the consumer lots cash.
Staff turnover
—after two years, all of the accurate programmers on the task start to hate the program and depart.
