Wawanesa Insurance

Requirements are not really about requirements. Requirements are what the product or service you are building is meant to be and to do. Requirements always exist, and a product can never be right unless it conforms to these requirements. Requirements are not just for the sake of writing them down in a document, they focus on a business problem and solve it. The product or service being created is meant to solve a problem, and requirements are there to tell what how to create the product right. SO, in essence, requirements are not about written requirements as such, but rather an uncovering of the problem to be solved. You, the business analyst, will change the way the user thinks about his problem, either now or later. When a business analyst understands the requirements after consultation with the different stakeholders, he starts to establish a concept of it. He works in synchronization with all the stakeholders to find the essence of work, put together...

Strategy defines the most effective way to apply the capabilities of an enterprise in order to reach a desired set of goals and objectives. Strategies may exist for the entire enterprise, for a division, department or region, and for a product, project, or iteration.  Strategy analysis focuses on defining the changes needed to address the business needs. It covers the strategic thinking in business analysis , as well as the discovery of possible solutions that will enable the enterprise to create greater value for stakeholders, and capture more value for itself. A strategy may be captured in a strategic plan, product vision, business case, product roadmap, or other artifacts. The Strategy Analysis knowledge area includes the following tasks: • Analyze Current State : understands the business need and how it relates to the way the enterprise functions today. Sets a baseline and context for change. • Define Future State : defines goals and ...

The requirements Life Cycle Management area describes the tasks that BAs perform to manage requirements from inception to retirement. The purpose of requirements life cycle management is to ensure that business, stakeholder, and solution requirements and designs are aligned to one another and that the solution implements them.  The requirements life cycle begins with the representation of a business need as a requirement. The requirements life cycle continues through the development of a solution. The requirements life cycle ends when a solution and the requirements that represent it are retired.  The Requirements Life Cycle Management knowledge area includes the following tasks: Trace Requirements : analyzes and maintains the relationships between requirements, components, and other work products for impact analysis. Maintain Requirements : ensures that requirements and designs are accurate and current througho...