CP 280 - RAPM Lec#2.pptx

CP 280 - Req Analysis and Process Modelling Lec 2 Lec 2  Stakeholders  Customers  Users  Requirements from the customer’s perspective  Role of Business Analyst  Establishing Business Requirements  Scope and Vision Statements  Conflicting Requirement...

CP 280 - Req Analysis and Process Modelling Lec 2 Lec 2  Stakeholders  Customers  Users  Requirements from the customer’s perspective  Role of Business Analyst  Establishing Business Requirements  Scope and Vision Statements  Conflicting Requirements Who is a stakeholder?  Any one actively involved in a project  Can affect or affected by its process or result  Can be internal or external Potential Stakeholders Potential stakeholders Who are the customers/users?  Customers a subset of stakeholders  an individual or organization that derives benefit (directly or indirectly) from a product  Users a subset of customers  who will actually use the product (either directly or indirectly) Requirements from the customer’s perspective Frequent customer engagement reduces the expectation gap The business analyst  An individual responsible to elicit, analyze, document, and validate the requirements  interprets requirements between the customer/user and the software development team  The business analyst The Business Analyst The business analyst’s tasks  Define business requirements  Identify project stakeholders and user classes  Elicit requirements  Analyze requirements  Document requirements  Communicate requirements  Lead requirements validation  Facilitate requirements prioritization  Manage requirements Establishing Business Requirements  Background  the rationale and context for the new product  Business opportunity  business problem to be solved plus the environment  Business objectives  business benefits in a quantitative and measurable way  Success metrics  indicators that stakeholders to define and measure success on this project Establishing Business Requirements – Contd…  Business risks  To summarize the major business risks related to the product  Business assumptions and dependencies Product Vision and Project Scope  Product Vision  states the form of the final product to attain the business goals  describes what the product is meant to be and what it ultimately would become  The product could present the whole or partial solution for the business requirements Moore’s Vision Statement Template  To summarize the long-term objective of the product.  For [target customer]  Who [statement of the need or opportunity]  The [product name]  Is [product category]  That [major capabilities, key benefit, compelling reason to buy or use]  Unlike [primary competitive alternative, current system, current business process]  Our product [statement of primary differentiation and advantages of new product] Sample Vision Statement “For scientists who need to request containers of chemicals, the Chemical Tracking System is an information system that will provide a single point of access to the chemical stockroom and to vendors. The system will store the location of every chemical container within the company, the quantity of material remaining in it, and the complete history of each container’s locations and usage. This system will save the company 25 percent on chemical costs in the first year of use by allowing the company to fully exploit chemicals that are already available within the company, dispose of fewer partially used or expired containers, and use a standard chemical purchasing process. Unlike the current manual ordering processes, our product will generate all reports required to comply with federal and state government regulations that require the reporting of chemical usage, storage, and disposal.” Product Vision and Project Scope  Product Scope  Clearly identifies what portion of the product vision the current project will deal with  The scope statement draws the boundary to indicate what’s to be included and what’s to be excluded Scope and limitations  About what the solution being developed is and what it is not  Major features  Scope of initial release  Scope of subsequent releases  Limitations and exclusions Relationship between Vision and Scope Vision Scope The vision applies to the The scope applies to a section product as a whole of the product The vision is static and long Scope is more dynamic subject lasting to the contents of each release The vision should be clear and The scope for the current achievable release should be clear, but the scope of future releases could be fuzzier The vision defines the scope(s) Each scope description must align with the vision The product vision Each scope is a subset of the encompasses the scope for strategic vision for the product each planned release Conflicting Business Requirements  Stakeholders’ objectives are not always in alignment, some business objectives might conflict  For example, the customer wants to spend less time, but the retailer would prefer to have customers spend more time in the store  The conflict of objectives may lead to conflicting business requirements  Business Analyst can help in notifying these conflicting business objectives, and facilitate conflict resolution  Since resolving such issues can be a political and power struggle, conflicting requirements must be resolved by the project’s decision makers References 1. Wiegers, K. E., & Beatty, J. (2013). Software requirements (3rd ed.). Redmond, WA: Microsoft Press. ISBN: 978- 0735679665. 2. Sommerville, Ian, and Pete Sawyer. 1997. Requirements Engineering: A Good Practice Guide. Chichester, England: John Wiley & Sons Ltd.