Back to homepage
| Bacolod | Baguio | Cagayan de Oro | Cebu | Davao | Dumaguete | General Santos | Iloilo | Manila | Pampanga | Pangasinan | Zamboanga |

  Business
Tax changes cause drop in RP auto sales
Cebu City inflation at 5.1%
Government district offices set to go electronic in procurement
Toral: Managing requirements
Prepaid Internet credits bought, passed thru phone
Ng: Knowing real score
International data storage firm targets Cebu

Thursday, June 10, 2004
Toral: Managing requirements
By Janette Toral
Digital Filipino


FAILURE. A lot of software development projects by organizations, whether large or small, fail, because of poor requirements management.

Here is a checklist you can follow should you decide to start outsourcing or developing your
in-house applications.

l Get trained. Understanding how the software development life cycle takes place will make you sensitive to the realities of this process. Untrained project proponents often have unrealistic expectations and are primary causes of project failures.

Getting software process improvement knowledge beforehand will make you confident as well in dealing with vendors and able to discern which entity can deliver the expectations in your software project based on their competency and process maturity.

l Document your requirements. Make sure all requirements stated in your software project are documented.

Before the creation of a project plan, three documents must be prepared and approved: the vision/scope, customer requirements, and product requirements.

These documents shall serve as the basis for project planning, testing, and customer acceptance.

l Identify your success criteria. Each feature or component of your requirements was included for a reason.

Its reason must be cited, and the goals or success criteria must be stated. This is the only way you can measure whether you have met your objectives.

Success criteria can be a business statement like “decrease the number of days for order processing from five to three days” to a technical statement like “complete monthly sales report generation in 30 minutes.”

l Assign responsibility to stakeholders. Most projects fail due to the lack of or poor participation of stakeholders.

All identified actors in the project must be given appropriate responsibility. They should be made responsible for non-cooperation in the software development project.

One factor that results in this poor cooperation is the lack of knowledge about the software development life cycle.

That is why it is important to have a workshop at the start of the project to level the knowledge among project participants and relevant stakeholders.

(e-mail: janette@digitalfilipino.com.)

(June 10, 2004 issue)
Write letter to the editor.Click here.
Join the Sun.Star message board.Click here.





ENETWORK HEADLINE
Poe overtakes Arroyo; 55 COCs canvassed

ENETWORK NEWS
Typhoon brings a lot of rain; people stranded
US terror tag on MILF remains a possibility
2 lady dentists killed in Benguet


[return to top] [home] [network page]






Sun.Star Network Online

LOCAL NEWS
BUSINESS
OPINION
SPORTS
LIFESTYLE
FEATURE

SUPERBALITA
WEEKEND

Classified Power Ads

Past Issues

Click to find out more

I © Copyright 2002 - 2004 Sun.Star Publishing, Inc. I Contact the website at online_desk@sunstar.com.ph I