What is a Requirement?
\n\nSoftware is everywhere in our lives today. From your online banking system to your microwave oven, software applications play a vital role in everyday life. Why do we rely so heavily onÂ software applications? The reason is that they achieve a goal or solve a problem for us. In other words, they have properties that fill a need for the user.\n\nA Requirement is the description of the properties of a product that satisfy the consumer\'s need.
\n\nPut a different way: A Requirement is a condition or capability needed by a stakeholder to solve a problem or achieve an objective
(IIBA, 2008)\n\nWhat is Requirements Analysis?
\n\nRequirements Analysis consists of the activities that are performed for the purpose of structuring the requirements that have been elicited from stakeholders during the requirements elicitation phase. After requirements have been gathered or elicited, the following requirements analysis activities should be performed:\n
- Categorizing the Requirements\n
- Evaluating Requirements for Feasibility\n
- Prioritizing Requirements\n
- Context Diagramming\n
- Modeling (Presenting the Requirements in Various Formats)\n
\nHow to Document and Present Requirements
\n\nA Requirement can be documented and presented in many different ways.\nIt can be documented as a sentence, a business rule, a model, a prototype, a diagram, a table, a spreadsheet or any other mode that communicates the user or stakeholders\' need.\n\nIt is a good practice to define requirements using a combination of textual statements and diagrams or models (use cases, actors etc.) This makes the process of defining requirements more engaging to your users. It also helps clarify your requirements by revealing any holes in the requirements.\n\nCharacteristics of Excellent Requirements:\n
- Correct: Requirements should accurately represent the real needs of the users and stakeholders.\n
- Complete: Requirements must include all of the needed elements required to create the solution. This will include descriptions of functionality interfaces, quality attributes, constraints etc.\n
- Clear: They can be understood in the same way by all stakeholders without requiring additional explanation.\n
- Concise: They are stated simply in the minimal possible way to be understandable.\n
- Consistent: Requirements should not conflict with other requirements.\n
- Relevant: They are required to meet a business or user need or objective.\n
- Feasible: They are possible to implement.\n
- Verifiable: It should be possible to determine whether the requirement has been satisfied.\n
\nWho Should Handle Requirements Analysis?
\n\nThe typical job title for a person who handles Requirements Analysis is Business Analyst or Requirements Analyst. However, there are many individuals who manage requirements, yet work under other job titles. Software developers, project managers, business managers, process analysts and many more other titles describe people who work with Requirements Analysis everyday.\n\nRequirements Analysis is a process that requires a lot of skill and experience to master. There are many tools and techniques available to individuals who are involved in Requirements Analysis today. Not every tool or technique will apply in every situation.\n\nTo successfully analyze requirements,Â you will need to be trained on how to master and work with many different analysis techniques and different types of stakeholders. This way you can choose the right techniques for every requirements situation that you face.\n\nGet More Information
\nThis article is part of a series of articles on Requirements Analysis. Other articles in the series are:\n\nPart Two -Types of Requirements: Business, User, Software, Functional, Non-Functional\nPart Three - Requirements Elicitation Tools and Techniques\nPart Four - Challenges with Requirements Analysis\nPart Five - Best Requirements Analysis Practices\n
To receive the rest of the requirements analysis article series free, click here to request more information.