Post on 11-Nov-2015
description
transcript
Business Analyst Training
Role of a Business Analyst
Responsible for analyzing the business needs of their clients and stakeholders to help identify business problems and propose solutions.System Analyst vs. Business AnalystGoalsReduce waste Complete projects on time Improve efficiency Document the right requirements
Software Engineering
20Software Engineering
Software Engineering is a collection of techniques, methodologies and tools that help with the production of a high quality software system with a given budget before a given deadlinewhile change occurs.
Software Development Life Cycle
Otherwise called software development processSDLC -Building the systemSteps Feasibility Study Analysis Design Development Testing Implementation Maintenance
Software Development Processes
Several processes, each describing approaches to a variety of tasks or activities that take place during the process.
Waterfall Model:After each step is finished, the process proceeds to the next step.
Continued.
Iterative development:Construction of initially small but ever larger portions of a software projectAgileExtreme ProgrammingScrumOthersRational Unified ProcessAgile methods differ from iterative methods in that their time period is measured in weeks rather than months and work is performed in a highly collaborative manner. Others
Waterfall method
Where SDLC fits
System Development
Process Improvement
Marketing, Training, etc
Transition
Construction
Elaboration
Inception
IT Project Life Cycle
Business Units Project
SDLC
Questions ?
Project Management
Types of ProjectsGreenfield Engineering Development starts from scratch, no prior system exists, the requirements are extracted from the end users, the client, applicable standards Triggered by user needs
Re-engineering Re-design and/or re-implementation of an existing system using newer technology Triggered by technology enabler
Interface Engineering Provide the services of an existing system in a new environment Triggered by technology enabler or new market needs
Project Life Cycle
Project InitiationTurn an idea or work request into a defined project by specifying scope and objectives, identifying resources, and determining project approach and milestones. Steps in Initiation Client Project Meeting: Initial meeting with the client to discuss what they would like to accomplish, timing, etc. Project Definition (also known as a 'Project Charter')/Project Proposal: A document that describes the purpose, objectives, scope and deliverables of the project Project Approach (also known as a 'Project Life Cycle'): A document that describes the phases, kinds of results, and major review points of the project
Planning
Set the foundation for the project work by defining the tasks to be accomplished, and the timeframe, resources, staffing, communication, and costs involved in completing these tasks.
Steps in Planning Project Team Kick-Off Meeting: Meet with the project team to discuss the reason for the project; review the Project Charter; discuss roles; etc. Project Task List: Define the work that it is it going to take to get the project done and how to the work task relate to each other. Resource Assessment: Determine the resources that are needed to get the project work done including roles, skills, hardware, software, networking, etc. Staffing Plan: Determine who is available to work on the project and the skill pool available from these staff.
Schedule: Put together the time allocation for the project work tasks and the related calendar for project work.
Communication Plan: Determine the communication that needs to go on during the project and who needs to be involved including methods, meetings, mail lists, minutes, etc.
Project Integration: Identify any system or service (a) on which a project depends, (b) which depends on the result of a project, or (c) is affected by the project, is a candidate for integration.
Implementation/ Manage the PlanTrack your team's progress in relation to resources, scope, and schedule factors. Take corrective steps wherever needed.
Steps in Implementation
Project Team Status Meetings: Meetings with the project team members to review work progress and status; technical issues relating to the project work; problems; etc. Project Status Reports: A report of progress on the project work.
ClosureAfter project deliverables are completed and accepted by the sponsor and clients, formally end the project.
Steps in Closure
Project Close Out Checklist: A checking off of the project's final deliverables Project Team Wrap Up Meeting: A meeting with the project team to discuss the project; identify areas of change or improvement for the next project; discuss the on-going work requirements or plans for future work on the project Project Closure Report: A final written handoff document
Project ScopeScope defines what is or is not included in the project and controls what gets added or removed as the project proceeds. Project changes that impact scope include: requirements, constraints, assumptions and risk
Nishidha Kumaresan - Three constraints of Project Management Time, Cost, Scope
Business Opportunity/ProblemIdentify and document business process to understand what is being builtThis is a critical activity in any project
Business Architecture WorkflowBusiness Process model helps understand the business environmentCaptures significant events that are of interest to the businessSets context for tasks to be supported by systemEasily documents as a series of steps or process diagram
Business ObjectivesBusiness Objectives willExplain why the project is neededIdentify business improvements/opportunities to be addressedProvide the basis for determining the success of the investmentClarify the boundaries of the initiativeDefine what the business is expected to deliverSupport Corporate objectivesExamples Reduce cost of operations, Increase customer satisfaction, expand customer base
Project ObjectivesCharacteristics of Project ObjectivesDefine the scope of the projectSummarize the purpose of the projectIdentify at a high-level the products of the projectWhat the project team is expected to deliverExample- Automate services, Develop the connectivity to send and receive information
Needs and FeaturesNeeds Originate from a business stakeholder and define the initiate problem or opportunity the project addressesFeaturesHigh-level description of system behaviorWhat the product will do
Exclusions, Assumptions, ConstraintsExclusionsDetails that the project will not addressAssumptionsTrue, real or certainInvolves a high degree of riskEx- system can be implemented all over the worldConstraintsApplicable Restrictions that will affect the performance of the projectShould not be tied to cost or schedule unless these have been agreed as fixed valuesEx. Automate by next June
Scope Creep
Seemingly small and incremental scope and requirement changes lead to substantial cost, budget and schedule overruns.
Points to RememberBefore exploring requirements for a new project you have to understand the following:The business problem or opportunityScope of the ProjectStakeholder interests in the projectConstraints on an acceptable solution
Questions ?
Requirements
What is a Requirement ?Features become RequirementsA requirement is a necessary attribute, capability, characteristic or a quality factor of a system or product.Requirements must be unambiguous, complete, correct, consistent, traceable, modifiable, understandable, verifiable, ranked for importance and stability.
Requirements DefinitionsBusiness Requirements: High level capability required to meet business needWhat needs to be done, not how it is done
Functional Requirements:An action that the product must be able to take functional characteristic of end solutionShould not include technical directions on how to achieve requirementShould only be derived from business requirements
Requirements DefinitionsTechnical Requirements:Specific attribute or characteristic of end product and behavior it must exhibit to meet functional needsLow level detail typically containing technical language
Non Functional Requirements:Describe quality, characteristic or property that a solution must haveTypically apply to entire solution and/or multiple business requirements Not necessarily project specific can be leveraged at the program level
Definitions ExamplesBusiness RequirementClaim Service Representatives (CSR) must be able to verify customer information while on a customer support callFunctional RequirementCSRs must search for a customer based on name, address, policy/account number or social security number Technical RequirementThe information the system needs will come from the Client, Insurance Policy, and Bank Account domainsNon Functional RequirementAvailability must be accessible 24/7Performance system must be able to process transaction within 90 seconds 90% of the time
Requirements Visual Breakdown
Business RequirementsTechnical RequirementsNon-Functional RequirementsLinked Business RulesLinked Data ElementsAvailability/ ReliabilityUsabilitySecurityFunctional RequirementsMaintainability & SupportabilityPerformanceScalability
Requirements Management1. Gathering Requirements- Identify sources of raw requirements data2. Analyzing Requirements- Develop and analyze raw requirements data and Develop basic models ( Process Maps, Use Cases)3. Specifying Requirements- Develop requirements. Develop BRDs4. Validating Requirements- Review the Requirements5. Tracking Requirements- Develop Traceability Matrix and track changes
1. Gathering RequirementsGather information about present methods, procedures, systems, work processes and data operations to understand needs.Choosing a technique: Is there a right/wrong You decide what works best.Techniques used:A. Hard Sources (documentation)B. Interviews, Surveys, QuestionnairesC. BrainstormingD. Joint Application Development (JAD)
D. JADStructured workshop sessionMore structured and more productiveMeeting agenda provides structure, a facilitator directs the process and visual aids clarify concepts being discussed.Facilitator, End users, developers, Tie breaker, Observers, Subject Matter Experts. JADs drive major requirements and interface look and feelAddresses Requirements, data and process models, screens, and report designs
Steps to develop RequirementsIdentify Users (Users become Actors)Identify Tasks (in the process diagram) performed by the users (Tasks become Use Cases)Detail the tasks in use case formatDocument Non-functional requirementsDocument business rules
2. Analyzing RequirementsTwo sections: Individual gathering requirements outline: by utilizing documentation, templates and Additional requirementsModeling techniques: process maps, data elements, business rules and use cases
3. Specifying Requirements
Create the Requirements documentPrioritize the requirementsPeer review- Done by your project teamAll requirements should be testableEach Requirement should have a unique identifier
What is a Testable Requirement?SMART - Specific, Measurable, Action Oriented, Realistic, Time Bound
Imperative Shall, Will, Must, Must Not, Required
Complete - must be able to stand on its own
Non Ambiguous only one interpretation
Non Compound no sub-requirements (and, or, nor, if/else/then)
Correct verified by business owners
4. Validating RequirementsFormal Requirements ReviewAuthorize the Requirements documents
5. Tracking Requirements Develop a Traceability Matrix Change Requests if changes are needed
Questions ?
Requirements- Exercise 1
Business Analyst Deliverables
Possible BA DeliverablesVisionGlossaryProcess Maps As is and To beBusiness Requirements DocumentSoftware Requirements SpecificationBusiness Rules Data ElementsUse CasesSupplementary SpecificationsTraceability MatrixTest Cases
VisionAlso called Product Requirements DocumentThe Vision captures very high-level requirements and design constraints to give the reader an understanding of the system to be developed. It provides input to the project-approval process
Glossary Business DefinitionsEx. SLA- Service Level Agreement: It is the length of time agreed upon by our Company to provide service to the customer
Process MapsA visual presentation of the flow of work required to produce the desired response to a business event.
Components of a process map:Swim lanes: Horizontal lanes showing( person, group or system) performing business processes.Process Shapes: Will depict the processes or activities utilized in a flow
Customer applies for Credit Card using the Internet
Customer
System
Bank
Fill out credit card Application
Submit app
Process Application
Create Customer profile
Create Customer Account
Activate Account
Initial Credit card activation
Apply for credit card
App completed
Application submitted
Declined notice sent
Approved notice sent
Request to activate Account
Customer account created
Profile created
Account Activated
Last updated xxxx
Project name
Business Requirements Document
Captures Business RequirementsTraditional methodOptional
Software Requirements SpecificationCaptures the complete software requirements for the system, or a portion of the system. Package containing use cases and applicable Supplementary Specifications and other supporting information.
Data ElementsPieces of information needed by the business
Type/ length- Data type and length of data elementNumeric(99) Length of 99 with numbersAlphanum(99)- length of 99 can contain Letter, number and special characteristicsAllowed values- (E.g. up to 4000)
Business Rules- Any other editing information that may apply to this field ( E.g. required, optional)
Exceptions- Any exceptions state where/where not a data element exists. ( E.g. IL only, Not Ohio)
Determine Eligibility:Military Data ElementsMilitary DataData ElementRequiredField ValidationSourceFormatProof of military serviceyesRadio button (yes/no)userProof related to datesyesRadio button (yes/no)userTotal Active serviceyestext box; auto tabusernumericReceiving Disability benefityesRadio button (yes/no)userFrom where the member is receiving disabilityyesRadio button (VA,Military, Don't know)userActive or InactiveyesRadio button (Active/InactiveuserDishonorably dischargedyesRadio button (yes/no)userPOWyesRadio button (yes/no)user
Business RulesCalculationsGuide or constraint on business behavior or activityEx. Gold card customers have a limit of 20000; Silver 10000Ex. APR calculationA credit card account can have only 1 primary cardholderPremium is calculated using X divided by YExplicit conditions/rules regarding Data Elements
Use CasesDefines a goal-oriented set of interactions between external actors and the system under consideration.Actors are parties outside the system that interact with the system. An actor may be a class of users, roles users can play, or other systems. A primary actor is one having a goal requiring the assistance of the system. A secondary actor is one from which the system needs assistance. Use cases capture who (actor) does what (interaction) with the system, for what purpose (goal), without dealing with system internals.
Use Case TemplateUse Case ID (UC - 1) Use Case Name ( Verb + Noun)Actors
Description
Pre-conditions
Basic Flow Ex. open credit card account- log in first timePost-conditions
Alternative Flows Ex. Open saved credit card applicationExceptions Ex. Incomplete/InformationSpecial requirementsAssumptions
Use Case Exercise 3
Supplementary SpecificationCapture Non-functional requirementsFURPSFunctionality Usability Reliability Performance Supportability
Design constraints Implementation requirements Interface requirements Physical requirements.
Traceability MatrixThe traceability matrix is used to ensure all requirements are met and to locate affected system components when there is a requirements change
Test CasesA Test case is a set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.Test cases reflect the requirements that are to be verified.The requirements you choose to verify will be a balance between the cost, risk, and necessity of having the requirement verified.
Questions ?
Assignment - Case Study 1
End of Session 1
Rational Unified Process
Iterative ApproachAn iteration:Phases and associated Iterations:
InceptionIterations focus on management, requirements, and design activitiesElaborationIterations focus on defining, validating, and base lining the architectureConstructionIterations focus on design, implementation, and testingex. Fixing Bugs iteration needed including implementation and testingTransitionIterations focus on testing and deploymentex. User feedback iteration needed
Inception: Project Objectives Milestone (project viable or non-viable)
1. Business Modeling 2. Requirements 3. Analysis & Design 4. Implementation 5. Test 6. Deploy
Elaboration: Product Architectural Milestone (architecture is proven)
1. Business Modeling 2. Requirements 3. Analysis & Design 4. Implementation 5. Test 6. Deploy
Construction: Operational Capability Milestone (all functionality developed)
1. Business Model 2. Requirements 3. Analysis & Design 4. Implementation 5. Test 6. Deploy
Transition: Product Release Milestone (product released into production)
1. Business Modeling 2. Requirements 3. Analysis & Design 4. Implementation 5. Test 6. Deploy
RUP phases and their milestones
WORKFLOW STEPS FOR AN ITERATION
Contd..
Test (Quality Assurance) For initial iteration, CREATE Class Diagrams, Logs, Lists, Components, Classes & Architecture; for all subsequent x iterations DETAIL Class Diagrams, Logs, Lists, Components, Classes & Architecture. Test Cases, Test Classes, Test Plan, Test Evaluation Summary, Test Scripts, Test Ideas List, Workload Analysis Model, Test Data, Test Results, Test Log, Test Guidelines, Test Classes, Test Components, Test Interface Specification, Test Automation Architecture, Test Environment Configuration
Unified Modeling Language