Mahindra Satyam Confidential1 BASE TM Methodology Guide Quality Management System BASE TM Methodology - 17 Slides Continue Back

Mahindra Satyam Confidential2 Analysts didn’t capture the requirements clearly! The scene…. Requirements are not clear! Functional specifications are vague! Frequent requirement changes during the course of the project! Designers haven’t done good job! Requirements documented are at very high level! User is not sure of the requirements!

Mahindra Satyam Confidential3 Business?...Requirements?..

4Introduction Methodology for Business Analysis Captures domain knowledge Business Essence – No Technology, Time, Place, etc. Work products

Mahindra Satyam Confidential5 Concept

6 Business Context Model Industry Context Business Roles in the Industry Value Exchange between Business Roles Activities performed by Business Roles Refer QUALIFY for BCWP Guidelines

Mahindra Satyam Confidential7 Business Process & Model Single Business Event pertinent to the business. Sequence of process steps No Technology, department, locations, people, functions or time of the day. Business Process Model is a pictorial model of the flow of processing steps of a Business Process. Refer QUALIFY for BPWP Guidelines

Mahindra Satyam Confidential8 Business Requirements/Rules Atomic step in a Business Process. Atomic Statement which expresses “What is done?”. Verifiable with ‘Y/N’ answer. Always in the context of Business Process. Acts on one “Unit of Work”. Always starts with a ‘Verb’. Independent of implementation. Clear target for implementation. Always associated with Business Requirement Logic associated with the Business Requirement Constraint/Control applied in relation to business Can be used to validate the capability of systems Functional Requirements and can be tested Business Requirements Business Rules Refer QUALIFY for BRWP & BRLWP Guidelines

Mahindra Satyam Confidential9 New Approach - Elements of a Business Requirement

Mahindra Satyam Confidential10 Business Process

Mahindra Satyam Confidential11 Business Process

Mahindra Satyam Confidential12 Business Process

Mahindra Satyam Confidential13 Business Process

Mahindra Satyam Confidential14 Where is BASE used? Getting Business Requirements right. Business Architecture Decisions Enhance Replace Right set of applications Business Problem Analysis Business Impact Analysis Product Evaluation & System Evaluation BASE TM is “Generic” – can be used in all verticals

Mahindra Satyam Confidential15 Help for Project Teams Methodology for capturing Domain Knowledge Domain Knowledge retention Requirements gathering Input for Architecture & Design Input for User Acceptance Test cases Impact Analysis for Enhancements/Change Reqs. Helps in reducing the Rework Helps in customer interactions (Business Language) Reusability Gap Analysis – Future releases/projects Easy to train new members

Mahindra Satyam Confidential16 ‘Z’ Model

Mahindra Satyam Confidential17 Thank You