BA Practice Final Aug 19

8/4/2019 BA Practice Final Aug 19

1/26

Table of Contents

BA with UML

Domain Focus:

Session 08/10/20119.00PMEST6.00 PMPST

BA roles s and responsibilities

Goal of the training program:Goal of the training program is to get a job as a BA

Other Names for BA :SMEDomain ExpertFunctional Consultant / Presale ConsultantData Analyst, Process Consultant

Where To Apply :IT Product Company - IBM , HP , Honeywell , Oracle

IT Application Company - Customization of products is done to specificbusiness process

IT User Company - Banking, Insurance, JP Morgan..

IT product companies(IBM, Oracle etc), IT application and IT usercompanies

Why should they hire u?

They will be looking for certain skill sets in a candidate who can becometheir employee

Skills Required for a BA:1.Domain KnowledgeA quick way of gaining domain knowledge can be done by

Reading the literature related to domain Case studies


2/26

Downloading the software products related to specific domain andwork on that product by referring the end user manual.

Tips to gain the domain knowledge:

Like Flexcube banking product from oracle crop. And competitor isFinnacle by Infosys. This will be used by the stake holders (Cashiers,managers, cust. , end users. etc)Ex: Try to locate some soft products related to Insurance claimmanagement, health care domain (clinical trails) , download it and startworking on it with an end user manual.

Download EZ claim product and find out similar products like EZ Claimand preferably search in open source category. Ram will help u in givinglist of more products.Pick your domain: Try to find out software products related to thatdomain and download the same, work on the end user manual, do areverse engineering (create documentation like BRD,SRS looking at theproduct )

2.Methodology Understanding Methodology is the processes involved in developing a software productor application.Other terms for methodology

SDLC (Software Development Life Cycle)PDLC (Product Development Life Cycle)ADLC (Application Development Life Cycle)

This methodology can be broadly classified into two categories:

a. Traditional Methodology: By traditional methodologies we meanearlier methodologies. Ex: (Waterfall Model, spiral model, Prototypemodel etc.)

b. Modern Methodology/ Agile Methodology: Modernmethodologies are the most recently used methodologies. The examplesof them being:- RUP (Rational Unified Process)- SCRUM- XP(Extreme Programming)- Lean Software Development


3/26

- TDD(Test Driven Development)- Crystal Clear

3. Entire understanding of SDLCSDLC comprises of the following steps:

Business modelingRequirements AnalysisDesignDevelopmentTestingChange ManagementProject ManagementDelivery/ Deployment/ Maintenance

Post Maintenance

Each of the above is the process by itself. Now, you need to have aoverall understanding of all the steps involved in SDLC/PDLC etc

4. Modeling techniques used in SDLCIn all the steps mentioned above, for as is and to be modeling we usevarious modeling techniques and these techniques are:

- UML (Unified Modeling Language)For a BA there will be three diagrams which are important and one of thediagram is use case diagram and the other ones are activity diagram,object state diagram and if you have idea of two more diagram thats alsohelpful and th ats class and sequence diagram

- Data Modeling (Domain Modeling or Conceptual Modeling)Data modeling is further segregated into logical modeling (EntityRelationships diagrams) and physical modeling (Converting ERdiagrams into tables/physical diagrams).

- Process Modeling (Data Flow Diagrams )

- Organizational Modeling Organizational Charts (Identifying key stake holders positively ornegatively impacted by the outcome of the project).


4/26

- Workflow Diagrams

- Process Flow Diagrams

- Flow charts

- Business Rule Catalog

- Decision Tree

5. Requirement Process in-depth understanding

We should know who (BA) should do what, when, how, why and whatshould be the deliverables. Deliverables can be also be called as artifact,

work product, output (The guiding methodology will be RUP).

6. Requirement Process Elicitation Techniques Understandings

- Benchmarking- Joint Application Development- Interviews- Questionnaires- Requirement Workshops

7. Business Problem Analysis Techniques

- GAAP analysis- SWOT (Strength, Weakness. Opportunity, Threat) analysis- PERETO (80-20 rule)- Fishbone (Root cause Analysis)

8. Requirement Process Deliverables Understanding

- Vision Documents- Requirement Management/ Work plans- BRD (Business Requirement Document)- SRS ( Software Requirement Specification)- FRS ( Functional Requirement Specification)- DRS ( Detail Requirement Specification)- PRD ( Product Requirement Document)


5/26

- RFI ( Request For Information)- RFP ( Request For Proposal)- RFQ (Request For Quotation)- SOW (Statement Of Work)- Job Order- SLA ( Service Level Agreement)- Release Notes- Business Use case models- System Use case models

9. Testing (Black box or functionality) Processes

Who should do what, when to do, why to do, how to do and whatshould be the deliverables

10. Testing Deliverables

- Test Plan- Test Case- Test Script- Test Data- Test Reports

11. Change Management Process Understanding in- depth

Who should do what, when to do, why to do and what should be thedeliverable

12. Change Management Deliverables

- Change plan- Change Request- Requirement traceability matrix

- Impact analysis report

To do all this the software use isRUPMicrosoft VisioEnterprise Arch.Rational Requisite Pro


6/26

13. Project Management overall macro understanding and projectdeliverablesProject Data

14. Software UnderstandingMS Office, MS Visio, Enterprise Architect

Learning Take Away: To have an understanding of all the skill sets required for aBusiness Analyst

Reading Material : Course PPT ( BA Session 0 )

Assignments : Locate the domain products ( refer to recap Document of Session

1 and 2 )Prepare PPT on Waterfall, Spiral, Prototype, Iterative, Incremental Models

Add Ons

Session 18/11/20119.00PMEST6.00PM

PST

Software Engineering Process Models

Methodology DefinitionFramework of steps (Requirement analysis, design, etc) when appliedshould result in development of a quality product or application withinright time, right budget and meet the expectations of all the stakeholders( is anyone who is positively or negatively impacted by theoutcome of the project)

If you r able to achieve the above then which ever methodology u rfollowing is a good methodology

There r many methodologies and have a common goal develop aquality product in right time, right budget and meet the expectations of

all the stake holders

Depending on the need of the project we should know, whichmethodology or a combination of methodology that can be applied.

Methodology proven best practices which have yielded good resultsFramework collection of best practices which are repeatable


7/26

Learning Take Away : there r 3 scenarios how a methodology is applied

1)

Client tells u what methodology u have to follow to develop their softwareproduct or application2) Software development company will have internal processes defined (Quality

assurance team will design) to develop a product for an application3) Every project is unique itself. A methodology can be defined for that unique

project

Reading Material : Roger Preesmen Software Engineering

AssignmentsAssignment 1: Costs of Product and market share of all? How many core moduleswill be there? Everything in Excel and find out end user manuals.

1) Temenos 1000 institutions in 125 countries2) Microbanker and Finware - Flexcube 395 instalations , 125 countries.

Windows, unix platform. Head quarter in india.HDFC, HSBC, Kotak Mahindra,etc

3) Finnacle by Infosys4) Fedility 14000 institutions in 100 countries. Head quarters in Jacksonville,

FL. Cust are MAC,

Assignment 2: Find out products realted to healthcare domain. Narrowing itdown to Clinical trails. Open ClinicaFind out competetors to open clinica, their market share, clients, costing and needin the market

Assignment 3: Create a data base of all the brouchers for tomorrows sessions Assignment 4: Refer White Paper, Blogs on sdlc and prepare a PPT similar towhite papers, and even add RAD and Concurrent Developement

Find Process Model details as much as possible

Add Ons


8/26

Session 28/14/20117PM IST9.30AMEST

6.30 AMPST

AGILE Methodologies

Many agile methodologies that follow aCommon manifesto giving more imp to communication rather thanprocess (taking decisions fastly and based on communications)

- Compliance process (following a set of rules) is kept at bare min.- Less imp to documentation- Working deliverables in an incremental way- Involving the customer in every phase

1. RUP*2. Scrum*3. Xp*4. Test driven development5. Crystal clear6. Lean software development7. Open unified process8. Essential unified process

RUP: Rational Unified process by IBM

- Use case driven, architecture centric* , iterative and incremental

Every project will have triple constraints

-time , cost and scope (inter-related)- a change in 1 puts pressure on theother 2 constraints

- Extremely documentation centric

*Used on product oriented projects

Phases in RUP : inception, elaboration, construction and transition

Inception : scope is determined here , deliverables called manydeliverables (BA , customers ) -involvedElaboration : architecture of the product (designer and architect )-involvedConstruction : Code (product id developed)


9/26

Transition : transferring the product to the customer(BRD* other names- opportunity definition doc, business processassessment reports)

Disciplines:-business modeling , req Analysis and design , development, testing,change mangt , project magt , environmental

The process models are granular who, what, when, how to do thedeliverables

RUP follows the concept of iterative approach (one complete disciplineiteration) 1 iteration= 1 complete sdlcSmall projects- do 3 iterations

6 for medium projects9 for large projects

Milestone : progress of the projectDeliverable:Build : something that is not handed over to the customer(internal)Release :something that is been tested (given to external stakeholder)

SCRUM :

The entire concept of scrum is based on time boxing (start andend point)

Deliverables : there are 4- Product backlog- Sprint backlog- Impedepement list

-

Burned down chartPeople involved in scrum are

1. Scrum master2. Scrum team3. Product owner


10/26

Meetings (cermonies) :

sprint backlog meetingdaily scrum meetingssprint backlog review assesment meeting

Everything in scrum starts with product backlog (template) (whichcontains the reqs documented as user stories )

User stories will be prioritized , how to give a demo to thecustomer for the req completion

Attributes of the user story- Priority- Effort

Assume product backlog has 500 reqs

In scrum a delivery has to be made in either 2 weeks or 30 days.

1 sprint = 2 weeks or 30 days =1 sdlc

A meeting will be called which is sprint backlog meeting(suggested guideline 4 hrs meeting)

Product owner sponsorScrum master PM levelScrum team- not to exceed more than 9 ppl (no hard rule)(BA. Architect, developer, QA, stake holders etc., )

Output of the meeting :sprint backlog (contains the shortlisted reqsfrom product backlog to be finished in 30 days)

Assuming to do 200 reqs in sprint backlog in 30 days

7 reqs a dayEvery day: scrum meeting 15 minsWhat did you do today , yesterday and any problems ?

All problems will be documented in impediment list .


11/26

Responsibility of scrum master to manage the impediment list

Burned down chart monitors the progress containsaccomplished tasks

180 only could have been developed and demo has to be presentedto the customer

Conduct a review assessment meeting why only 180 instead of 200 as planned ?

Remain 20 +300 for next sprint

Cycle repeats and sprints are repeated to conclusion.

Extreme programming- XP

Developer is the boss and talks to the customer ,Customer gives reqs to developer

Good for small projects

Learning Take Away

To have an understanding of agle methods and manifesto , RUP, XP & SCRUMTheir APPLICABILITY IN SOFTWARE DEVELOPMENT OR PRODUCTDEVELOPMENT ,

Reading Material

Assignments

- Do the comparative analysis of RUP , XP and Scrum (check in whitepapers/articles/blogs )

Add Ons

- Small ppt on Lean software development

Session 3 Analysis & Enterprise


12/26

Analyzing a business process

1. Study the business process2. To identify the business problem of the business users and

stakeholders(diagnostic approach to be followed)3. Gain Stake holder agreement on the problem*4. Propose solutions5. Gain agreement of the solution from the stake holders6. Document the business process problem(documentation, plain text

or as is modeling) solution (text, to be modeling) and take a signoff BRD (main focus of BRD business process and businesssolution only*)

O/P of analyzing business : Business case , BRD

Learning Take Away

- To analyse a business process and to deliver a business process andsolution in documented manner

Reading Material

Assignments

Add Ons

Session 4 UML & Basic OOPS Concepts

Unified modeling language (UML) in 1997 :Anything can be called a language if it has a syntax n semantics

Syntax: notations/symbols/ elements(same things) that we use

Sementics of UML: are basically the rules that we follow to combine all theseelements and make a particular diagram .

OMG- Object mangt group- diff it companies put together


13/26

UML2.1 VERSION CURRENT

Uml2.0 is being used. Applying UML results in prominetly 9 diagrams(5 static and 4dynamic diagrams)

5 static diagrams :

1. Important diagram : -Use case diagram* (BA Resp)2. Object diagram3. Class diagram4. Component diagram5. Deployment diagram

4 dynamic diagrams

1. Sequence diagram

2.

Collaboration diagram3. Object state machine or transition diagram4. Activity diagram

4 new diagrams added to UML adding upto 13 diagrams1. Timing diagram2. Package dependency diagram3. ? Communication diagram 4. - ? Composite structure diagram

BA perspective diagrams :

- Use case diagrams- Activity diagram- Object state event diagram

Other technical diagrams : class and sequence diagrams

UML constitutes 4 things

- Structural things (symbols that are used in the static diagrams are structural )- Behavioral things ( symbols used in behavioral diagrams)- Grouping things (packages and subsystems)- Annotations (notes attached to the diagrams)

UML syntax and semantics can be extended by using stereo types & constraints resp.

Learning Take Away

To have an understanding of UML and applications


14/26

Reading Material

Read UML ppt sent by ram

Assignments

Small ppt on UML

Add Ons

EA ENTERPRISE ARCHITECTURE

Session 5 Managing Requirements- rup

Req Definition : Need of the stakeholder.Formal def: condition or capability to which a system must conform to.IIBA : Condition or a capability to solve a problem or reach an objective.

Managing rqs is about- Eliciting reqs , ( Discovering reqs (existing reqs); Ex: elicitation

techniques like JAD sessions, interview etc., )- Document reqs ( Pictorial/documented, Ex: Business case, VD,

RWP, RMP, BRD, SRS, RFI, RFP, RFQ, SOW, SLA etc., )- Organize reqs ( catogerize based on their attributes like high-

mediu-low priority reqs ; assigned to who ; critical/noncritical ,must have, good tohave, )

- Managing the changing reqs . ( change management procedures ,RTM - req tracebility mx***(reqs related in all ways, topdown/bottom up))

Base lining**: mutually agreed reference point. (Can be applied to everyproject deliverable)

Business rules (independent of technology) documented using decision

tables or business rule catalogs. Ex: emp cant work more than 8 hrs a dayetc.,

Reqs need to be managed to eliminate confusions.

All the deliverables mentioned in 5.3 depicts reqs in a documented way


15/26

which can be textual or diagrammatical. These deliverables mentioned in5.3 are interrelated. The inter relationship is called tracebility . It is doneby requirement tracebility matrix. Changes in 1 doc reflects changesin all docs.

Need to install : enterprise architect, Ms Visio, rational rose (optional)

Learning Take Away :

Is to have an understanding of all req mngt deliverables. And how to manage usingtracebility matrix.

Reading Material :Read RUP**- Introduction & concepts

Assignments :Make a ppt of the reading material.

Add Ons :

Session 5.1 Types & Levels of Requirements

Business architecture (by business analyst): Identifying the business problemand solution.Deliverables: BRD, business case etc.,

Technical architecture (by system analyst/architect )Deliverables: SRS, Design document (high level, low level , technical specificationdocument)

Database architect : responsibility of database designDeliverables: Conceptual model, logical model(Entity relationship diagram) andphysical model (tables)

Infrastructure architect : Is to work on network design, connectivity,hardware and software related stuff Deliverables: n/w diagrams , deployment diagrams etc.,


16/26

Enterprise Architect** (keyword) :

Requirement definition: Need of the stake holder. Documented solution

proposed to a stakeholder

Formal DEF: A condition or a capability to which the system must conform to.(Defined by IBM RUP)IIBA(International institute of business analyst)

Types of requirements :

1. Functional requirements (can be depicted as use case diagrams)These addbusiness value(tangible reqs )

2. Non functional requirements Quality of service reqs (performance,

Reliability , how many years data can be retained )

**Functional and non functional reqs are part of BRD(called business use case diagrams &SRS(called system/application use case diagrams)

3. Find out any additional requirement types??

Solution : Other types of requirements are

a. Transition or Implementation Requirements:

b. Customer/User/Stake Holder requirements: Expectations of the systemin terms of mission objectives, environment, constraints, and measures of effectiveness and suitability

Other requirements include

- Domain Requirements :

- Architectural requirements: Architectural requirements explain whathas to be done by identifying the necessary sys architecture of the system.

- Structural requirements: Structural requirements explain what has to bedone by identifying the necessary structure of the system.

- Behavioral requirements: Behavioral requirements explain what has tobe done by identifying the necessary behavior of the system.

- Derived requirements: Requirements that are transformed from higher-level requirement.

- Allocated requirements: A requirement that is established by dividing or


17/26

otherwise allocating a high-level requirement into multiple lower-levelrequirements.

- Design requirements: The build to, code to, and buy torequirements for products and how to execute requirements for

processes expressed in technical data packages and technical manuals.

Levels of requirements : Part of BRD

1. Regulatory reqs : enforced by govt , HIPPA rules2. Strategic level of reqs :CEO level3. Business reqs : sr.level managers 4. Operation level reqs :5. Solution or user level reqs :

Risk :Unforeseen conditions which may impact the project in a positive or negativeway.- Risk mitigation (reducing the severity)- Risk transfer (ex: insurance)- Risk acceptance- Exploit(if its a positive risk)

Learning Take Away:

Reading Material :

Zachman architecture , Togaf architecture, cloud computing , service orientedarchitecture

Assignments

Add Ons :

Session 5.2 Requirement Elicitation Techniques

Learning Take Away

Reading Material


18/26

Assignments

Add Ons

Session 5.3 Requirement Deliverables Purpose Comparison

Business modeling (in RUP) OR Requirement analysis step :

Organizational goals:Every org will be keen to achieve their goals.

The project starts with the following documents

Everything starts with one particular document called

1. Vision document (Template- define/customize by QA team) :High level business problem and business solution are to be presented tokey stake holders who are sponsors.

2. Requirement work plan : Budget and time will be sanctioned bythe sponsors after assessing the vision doc.

(ESI guide line, 10- 15% of the time is allocated for reqs process ; 15 -25% costing)

3. Requirement management plan: Contains the whole plan ,planning.

4. BRD : Business problem(as is modeling Business use casediagram, business use case spec) and solution(to be modelingbusiness use case diagram, business use case spec)

5. SRS : Business solutions will be converted into detailedspecifications. Those detailed specifications are documented inSRS( Software Requirement Specifications or Technical Design

Document) From architect (sys analyst) or designer

Note: Develop the project internally or company can outsource theproject.

6. RFI(Request for Information) : Potential Vendor information isgathered.


19/26

RFI Template is designed by QA.

7. RFP(Req for Proposal) : Shortlisted vendors have to submit theproposal. Non disclosure agreements and confidentialityagreement would need to be signed by vendors. Presentations,discussions will follow. Base line RFP will be signed( mutualagreement)

8. RFQ( Req for Quotations) : submitted by the vendor. Afterdeliberations, a single vendor is finalized.

9. SOW(Statement of work or job order) :

10. SLA(Service level agreement ) :warranties etc.,

Develop the project internally case:

Development planTest planChange mangt planProject charter


20/26

Learning Take Away

Reading Material

Assignments :

Download empty and filled templates and prepare a small ppt.Ram will provide ppts after assignments Add Ons

Session 5.4 Requirement Deliverables Of RUP

2 Areas : Business modeling & Requirements

Business modeling: when we are conducting business modeling, mainfocus is on identifying business problem and proposing a businesssolutionDeliverables/artifacts/output/workproducts of business modeling are

1. Business stake holder request2. Business Vision3. Business use case model4. Business use case specification5. Business glossary6. Business rules

All these become input to reqs.

Requirement deliverables :

1. Stake holder request2. Vision document3. Use case model4. Use case specification5. Glossary6. Rules


21/26

Use case model :

Purpose of Use case* diagrams: To depict the behavior of the systemas expected by users (stake holders) of the system. Use case digram talksabout .What the system does ? only and not how.

Use case diagram Ingredients :

1. Actor An external entity (human being/users , device/Automated /triggered by itself) , external system/ anything outside the scopeor secondary actors ) who should invoke or receive an observableresult ( positive or negative) of a value.

Tips for finding actors: Nouns have a potential to become actors

but not all nouns are not actors.

2. Use case - A distinct business functionality which invoked by anactor should produce an observable result. Ex: withdra/depositcash, generate reports.

3. Relationships - Actor to usecase ->binary association , which isactor can talk to use case and vice versa .

There can be relation to an

- actor to actor. ( Is a kind) generalization and specialization- usecase and usecase. (Include and extend)- actor and a use case. (Binary association)

4. Boundary This determines the scope of the project and isrepresented by a rectangle

5. *Scenarios (or flow of events) No symbols, All scenarios are tobe documented in use case specification document/ use casenarrative document or use case destination.

Normal flow : When use case is successful

All permutations and combinations are to be captured in use casespecification document. Ultimate business logic is in the use case


22/26

specification document.

Use case Specification talks about the complete detailed functionalityfor a particular use case Many companies have different templates for Use case specificationThe most common thing in any of the templates r the following:

1. Use case name name of the use case Maintained TC2. Use case brief description this use case allows all employee to

maintain time card info3. Flow of events: normal( successful) and alternate ( non successful)

Techniques to keep in mind to identify the flow of events are: Keep CRUD( create, read, update, delete) in mind Always think from actors/user (Emp) perspective this use case

starts when emp wishes to either create/update/read TC If emp wishes to create TC the following should be performedEmp clicks on the button Create TCSystem will display the following info fro emp confirmation (ID(non editable autofetch field)Name (non editable)Type(non editable)

Emp confirms the above and wishes to proceedThen system will present the following info for empTC ID (auto generate integer)Emp Name,Emp ID ( Auto generate)Project ID and name ( Autofilled )Start Time ( date and time format)End TimeOver Time ( derived attribute)Error messages ( all messages are alternate flow of events)

If the use cases are done well then itself can become an input for a testcase.

Then actor clicks OK, TC is saved.Use case ends.

Use starts when emp clicks on update TC button


23/26

Write down the steps by tomorrowMaintain TC srujanaMaintain PO KeerthiSelect Payment method suneetha and hiteshGenerate emp query reports deepa, murdulaMaintain emp info prashamsaGenerate Pay check allRun admin reports Raj Kiran

Req deliverables comparision PPT

Pre condition LoginPost condition Timecard savedExtension points noneSpecial reqs statutory req

Learning Take Away

Reading Material

Assignments :

1. Asset mngt, payroll and course specification case studies ( On both Visioand enterprise architect)

Add Ons

Session 6.0 Analysis & Design

Learning Take Away


24/26

Reading Material

Assignments

Add Ons

Session 7.0 Testing Process

Learning Take Away

Reading Material

Assignments

Add Ons

Session 8.0 Change Configuration Process

Learning Take Away

Reading Material

Assignments

Add Ons

Session 9.0 BABOK (Orientation) Business analyst body of knowledge(Version 2)Learning Take Away

Reading MaterialRam will send a ebookAssignments

Add Ons

Session 10 Project Management (Orientation)

Case Studies


25/26

Payroll Case StudyCourse registrationInsurance Claims Management SystemPersonal loan Approval System

BPM Tools (Optional).

Discussion on Aug 15 th :

1) Requirement management : (eliciting , managing, documenting and organizing etc., )(session 5)

2) Requirement deliverables: (vision doc, req mangt plan, req work plan, brd, srs rfi, rfp,rfq, sow , NDA etc., for all methodologies except for RUP methodology)(session 5.3)Assignment: download empty and filled templates.

3) Requirement definition : Types of reqs and Levels of reqs

Assignments:

Refer RUP for session 5Session 5.1 : Small ppt on types and levels of reqs session 5.1 Session 5.2: Req elicitation techniques( discussed tomorrow)Session 5.3 **** : Requirement deliverables ppt (empty/filled templates)Read all case studies***

Agenda for tomorrow:

USE CASE MODEL, Session 5.2 & 5.4 and Case studies

August 16 th Session :

Session 3 : Ram to send pptSession 4 : Ram to send pptSession 5 : read RUP (Introduction and concepts) Keerthy to send PPT to everybodySession 5.2 : Req Elicition Tech Srujan ans ramSession 5.3 : Req deliverables comparision *** Whole class PptSession 5.4 : RUP Deliverables (Business modeling and requirements) Only practicals- Noppts (In class discussions of 3 case studies )

Session 6 : Analysis and design (In class) -- Ram to send pptSession 7 : testing process - Ram to send pptSession 8: change mangtSession9 :BABOK (In Parallel to session 5) Ram to send a book Session 10 : PM (Ram)

The tip for Comparing the deliverables of requirements is


26/26

For every doc download the table of contents and compare the table of contentsCompare table of contents for different BRD and SRS, RPI,RFP,etc

Suppose there is a BRD Inside the BRD there is a use case diagram, glossary,

RUP

Business use case diagramBusiness use case specificationBusiness GlossaryBusiness supplementary specification

All the above can be clubed and become a single doc called BRD

Suppose there is SRS.. Inside SRS they will be

RUP

System use case diagramSystem use case specificationSystem GlossarySystem supplementary specification

Suppose if it is not RUP and it is SCRUM, then what is BRD?It isproduct backlog - inside this the reqs are documented as user stories

Suppose if it is not RUP, not SCRUM then we may have onlyBRDThe Quality Assurance team will decide the template contents of the BRDFor a project most of the BRDs will be filled templates.If you r a BA , then you should understand the contents of a BRD, then we will bein a position to modify the BRD.

Agenda for aug 19 th 6 Analysis and designTesting process, change management process

BA Practice Final Aug 19

Documents

Transcript of BA Practice Final Aug 19