Latest Requirements Buzz
Call for Papers: Requirements Engineering Education and TrainingThe 4th International Workshop on Requirements Engineering Education and Training (REET09)
Held in conjunction with the 17th International Requirements Engineering Conference (RE09). The workshop will be held in Atlanta, Georgia, USA on
August 31, 2009.
Requirements Gathering - Define Requirements AccuratelyThe requirements you capture must be stated in business terms, must be clearly stated, must be concise, and must be feasible. To ensure that requirements are clearly stated, you should have them proof read by someone external to the project (or at least someone not familiar with the requirements you've captured).
Identifying the Right Stakeholders to Contribute to RequirementsYour first step in the requirements gathering process should be to solicit requirements for your software development project from the stakeholders. The method and techniques you choose to employ for the purpose of requirements solicitation will require you to contact these stakeholders for the purpose of either gathering them together, meeting with them one on one, or communicating with them long distance. That first contact will require a contact list of key stakeholders.
12th Australian Workshop on Requirements Engineering2 Keys to Reduce Risk: Requirements Definition and Requirements ManagementGathering and managing requirements are fundamental challenges in project management. Most successful projects have high quality project requirements. Projects can fail due to poor requirements at any time during the project lifecycle without effective requirements management. The Project Manager needs to assess and understand the uniqueness of the requirements gathering process for his/her individual project.
What Is User Requirements Capture?A User Requirements Capture is a research exercise that is undertaken early in a project lifecycle to establish and qualify the scope of the project. The aim of the research is to understand the product from a user’s perspective, and to establish users’ common needs and expectations. The user requirements capture is useful for projects that have a lack of focus or to validate the existing project scope. The research provides an independent user perspective when a project has been created purely to fulfil a business need. The requirements capture findings are then used to balance the business g...
Requirements Gathering - Choosing the Right ToolsThe intent of this section is to offer you some insight into the various requirements gathering tools available and the factors you need to consider when choosing which to use for your project. You'll need to take training in the use of these tools before becoming proficient in their use.
The nature of the software application or web site your project will deliver will influence your decision on which requirements gathering tools to use. Other factors that will influence your decision are the number and type of business users, customer service reps, and maintenance people and their locations....
ROI Is Deceptive Without REAL Requirements and Quantified IntangiblesCommon presumed best practices for determining Return on Investment (ROI), advocated by almost all apparent authorities, in reality often undermine ROI’s very purposes.
ROI is supposed to provide a valid and reliably supportable objective basis for making decisions: the quantified dollar benefits of an approach versus its quantified dollar costs.
Requirements Visualization: A New Trend?The Problem With Defining Information RequirementsAs many of you know, I have been active in the Information Technology (IT) industry for a long time now. It's a strange business and, frankly, sometimes I wish I had never gotten involved with it. Nonetheless, there are a lot of problems associated with IT, such as computer performance, capacity planning, security, networking, disaster recovery, but probably the biggest problem is requirements definition. In other words, accurately defining the information needs of the end-user. The industry is actually quite good at designing and writing software, developing data bases, and acquiring hardware...