JYOTI GHALE

BA CLASS NOTES

INTRODUCTION CLASS- MARCH 13TH, 2017

HARDWARE

SOFTWARE- Computer instructions or data. Anything that can be stored electronically is software. There are two
types: Operating system and Application software. Operating systems are Window 7, 8, 10, Linux. Application
software is Gmail, apps, MS office.

OS – helps you communicate between software and hardware. Example: windows xp, Linux

Application software: Facebook, Skype, Google map,

There are 3 layers (Tiers) in the software (all are related to coding)

 Front end
 Back end- information, data is store(database)
 Middle end- There are multi layers in the middle end

Project Types

 Greenfield approach—building a project from scratch, very new

 Legacy up-gradation---old to new – upgrading
GAP

TO-BE
AS-IS

ANALYSIS

Mainframe TEMPORARY NEW SYSTEM

SYSTEM
 Integration-----Making a change-upgrading- integrating
 Data Porting----transferring the data. We do ETL (Extract- Transform- load) nowadays.

Types of environment

 Desktop
 Client Server(Mainframe)-In the vicinity, no need of have Internet access, safer
 Intranet. You have information in your facilities/ location. You don’t actually need internet as it is in
your computer. It is more secured. An application architecture in which the client requests an action or
service from the provider of service, the server. Consider a web browser and a web server. When you
adder\ss a URL in the browser window, it (client) requests a page from a web server. The server returns
an html page to the client, which parses the page (data) and displays it on your computer.

 Web based Application- Can be used on both client server and cloud based. Example: www
 Google (http) url
 JYOTI GHALE
BA CLASS NOTES

 Cloud based- services, resources or data that is provided on demand via internet. Can be accessed through
internet.

SDLC (Software Development Life cycle)

Initiate—come up with an idea

Plan—product owner (has different projects)

Discover--- Gathering requirements lie creating BRDs

Design---architect design

Develop—software developers

Debug—Testers phase

Deploy—Give it to your end client

Maintain—

Waterfall methodology is given below: (1)

Initiate: Coming up with an idea to start software. Product Owner (PO), VP, President, Business Analyst,
Project Manager comes with an idea. This document is known as Project Charter. It talks about the scope of
the project.

Plan: plan your ideas to see if it is a profit and can be successful. Project Manager, Product Owner, BA. It is a
kick off meeting.

Discover: Gather all the requirements needed. BA, PM, PO, Lead Developer, Lead QA. The document writer
are either (BRD- business requirements document/ FSD- Functional specification documents/ TSD- technical
specification documents/ TRD- technical requirements documents/ USD- users specification documents) is
made ready and then requires approval meeting which is signed by CCB (Change Control Board).

Design: An architect will design an outlet of your initiate plan. It is designed by Architect, BA, PM, PO. There
is then Design Sign off signed by Design lead or PM lead.

Develop: Developer, BA, PM, PO. The document then gets sign off by the lead

Debug: A tester will test the application that is developed. There are QA, BA, PM, PO, Developer. There is
then go/no go meeting.

Deploy: Developers, PO, PM, BA

Maintain: Maintain that is deployed. There are two phases of maintenance. It consists of BA, QA. The
requirements have to meet as per your end users. If not it should be given for free or else there are fees.
 JYOTI GHALE
BA CLASS NOTES

Who are the people responsible for SDLC?

Product Owner, Project Manager, Business Analyst, Business System Analyst, Project coordinate, Quality
Analyst, Developer, client, Scrum Master, SME (Subject Matter Expert), Sponsors.

Stakeholder: Interest in business. Shareholders: Puts share/ money in the business

UI designers: User Interface

PMO (Project Management Office)

 Mentor for portfolio Management

 Project Health Check
 Project Management Support
 Single Data Repository- Structured and defined Manner---Shared point-(folder) A website where the
information is shared

Project Charter: The most important result of the project initiation phase is the project charter, which formally
authorizes the work of the project to begin and gives the project manager authority to do his job.

Project scope:

It’s the definition of what the project is supposed to accomplish and the budget of both time and money that has been
created to achieve those objectives.

We assign them Roles and Responsibilities!

So, we build them a RACI Chart

Process/Phase R(Responsible) A(Accountable) C(Consulted) I(Informed)

Plan Project Project Manager Sponsor Subject Matter Team stakeholders
experts
Plan Requirements Business Analyst Project Manager SMEs Sponsor, Quality
Assurance
Analyze Business Analyst Business Analyst SMEs, End User Project Manager
Requirements Developers
Test Product Quality Assurance Project Manager Business Analyst Sponsor, Team
Developers

There are certain ways to implement these methodologies:

 Waterfall Methodology (Big Bang Approach): IP5DM going from I to M.

 Prototyping (Non-working prototype and Working prototype)
 JYOTI GHALE
BA CLASS NOTES

 Spiral model Prototype: Each concepts or idea is going through or generated all the phases i.e.
IP5DM unlike waterfall.
 Phased Prototype
 Agile
 RUP

Day #2

The Agile manifesto- we are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value

Individuals and interactions over processes and tools (Agile is giving more value to individual and interactions than
processes and tools.)

Working software over comprehensive documentation (Similarly, avoids the extensive documentation and works on
the working (going on making) software/ developing software.)

Customer Collaboration over contract negotiation (Focus more on customers working together than contracts and
paper works (contract negotiation).

Responding to change over following the plan (Will be more flexible to change than strictly following the plans)

That is while there value in the item on the right side, we value the items in the left more.

Agile Buzzwords

 Sprint - It is a time box, where functionalities are developed. 2-4 weeks

Beginning with 15 minutes daily stand up meeting / where we finished 3 questions and they are what I did
yesterday? What obstacles I faced? What I am doing today?
/ And moved to work on user stories
 Backlog- Two types: product and sprint backlog. List of functions that needs to be developed where they
take user stories to do that. It is created by Product Owner and BA. Product backlog is all the things that
need to be done.
 Business and technical priorities Business priority by product owner. Technical priority by developer.
 Sprint planning And Sprint Poker: A meeting with BA, QA Lead, PO, software developer to decide what
needs to come in your sprint. Sprint Poker helps to know the story points (days) you will take to get the
job done. Sprint poker gathers information from user’s stories and continues.
 JYOTI GHALE
BA CLASS NOTES

 Sprint Retrospective- It is the meeting that is held in every end of the sprint.
It talks about the 3 Questions: What we did good? What we can do better? What obstacles we faced?

Sprint poker helps to create sprint (It is a time box, where functionalities are developed)

User Stories

 Alternate to use cases mostly used in agile to plan and estimate

 Uses real world scenarios to document the user needs
 User stories are easy for users to read.
 Usually documented using index cards.
 Common template
 ff by Mike Cohn

Example: As a <user type>, I want <some goal> so that <some reason>.

RUP (other methodologies) Rational Unified Process

 Inception- (Initiate and plan) In your interview say, I will come up with idea, plan…
 Elaboration – (Discover & Design)
 Construction—(Develop & Debug)
 Transition—(Deploy & Maintain)

Hybrid Methodology: Combination of two methodologies. Start with Waterfall methodology (initiate, Plan,
discover) and then continues with Agile (agile starts from design, develop and so on)

Most common hybrid methodologies (Waterfall & Agile)

In Agile environment user stories are written for (design phase)* Discover, Develop, Debug
*

Requirements: is a condition or capability needed by stakeholders to solve a problem or achieve an objective. A

condition or a capability that must be met or possessed by the solution or solution component to satisfy a contract ,
standard, specifications, or other formally imposed documents.

As a BA you need to be probing problems and giving clients a solution within time and budget.
 JYOTI GHALE
BA CLASS NOTES

As a Business Analyst, you should give your client better or best solution. What you can do. It can be high level
or mathematical based on who you are dealing either VP or developer. Requirements should meet the user
wants. Changes in requirement are expensive. Changing the requirements costs: 3 X much during the design
phase. 5-10 X as much during implementation. 10-100 X as much after release. 2/3 of finished system errors
are requirements and design errors.

Two types of Requirements

1) User Requirements
 Usually the first attempt for description of the requirements
 Services and constraints of the system
 In natural language and diagram
 Readable by everybody
 Serve business objectives

2) System Requirements
 Services and constraints of the system in detail
 Useful for the design and development
 Precise and cover all cases
 Structured presentation

Classification of requirements

 Business Requirements
Define the goals and objectives of the business at the enterprise level.
 Stakeholders Requirements – describes the goals and objectives of a particular group within an organization.
 Solution Requirements: describes the various characteristics of a solution that must be met.

Functional: describes the behavior and information that the solution will manage or the thing that has a input
and output

1. Non functional: describes the qualities of the process or system. Example: Quality of the processes, space,
memory, user interface

Elicitation (gathering) of Non- Functional Requirements

 Stakeholders goals, values and concerns
 Legacy system and existing platform constraints
 Competitive analysis of the system qualities
 Industry and market trends
 Standard non functional requirement template and categories
 JYOTI GHALE
BA CLASS NOTES

 Pre established trigger questions

Property Measure
Speed Processed Transactions/ Second User/ Event Response Time/ Screen
Refresh Time
Size Giga byte
Ram Chips
Ease of Use Training Time
Number of Incidents
Reliability Mean Time To Failure
Probability Of Unavailability
 JYOTI GHALE
BA CLASS NOTES

Rate Of Failure Occurrence

Availability
Robustness Time To Restart after Failure
Percentage of events causing Failures
Probability of data corruption in case of failure
Portability Percentage of target dependent statements
Number of Target systems

 Transitional requirement

Describe any capabilities of a solution that aren’t permanent but instead exist only to facilitate the transition from the
current state to the future state. A classification of requirements that facilitate transition from the current state to the
desired future state, but that will not be needed once that transition is complete.’

Homework 2
1) Give 5 advantages and 5 disadvantages of agile.
2) Which methodologies do you think is better and why?
3) Give 10 examples of functional and non functional
4) Give an example showing the difference between user requirements and system requirements
5) What are the agile buzzwords and explain.

1. Give five advantages and five disadvantages of agile methodology.

Advantage
 As, the agile methodology use less documentation, the very first advantage is that it saves time and
money.
 There is a sense of great customer satisfaction due to them being more involved and listened to and
also with continuous and rapid delivery of useful software.
 We can determine the issues in advance as there is daily meetings and discussions and therefore will be
able to work accordingly.
 Late changes in the requirements are welcomed.
 Quick development and testing helps to recognize the gaps existing in their requirements or technology
used and can help to find the solution.
Disadvantage
 This methodology focuses on working software rather than documentation; hence it may result in lack
of documentation.
 The project can easily get taken off track if the client is not clear what final outcome that they want.
 The terminologies can be confusing to the clients like, story points, velocity, and so on. So, the lack of
clients understanding will affect the project, in terms of educating them about every depth and methods.
 Agile will not work well for a team where communication is an issue. It needs open communication for
every day stand ups and retrospective.
 JYOTI GHALE
BA CLASS NOTES

 For the bigger and complex project, it is difficult to determine the efforts estimation at the beginning of
the software development.

2. Which methodologies do you think is better and why?

In my understanding it really depends on the nature of the project and the requirements of the clients to
choose a methodology to develop software. However, saying this in today's fast-paced business environment
and changing market conditions. Companies are producing software in agile development practices to help
them stay competitive.
The most important lessons you will get about your software will come from customers. Agile processes are
highly collaborative, iterative and all focused on the rapid and repeatable delivery of software. Agile teams are
able to get software into their hands quickly by only building just enough software to get valuable features
delivered. Since agile teams are also experienced at delivering software on a frequent basis, your business can
respond and deliver better software based on customer feedback.

3. Give 10 examples of functional and non-functional

Functional
Checking your status online for the product you buy online
Logins of websites with username and passwords
Help clicks in webpage
Tracking packages through shipment providers like FedEx, ups
Submission of application which generates prompt submission confirmation
Booking movie tickets online
Ordering books online
Maps
Checking balance online
Paying bills online

Non-functional
It must be compatible with Internet Explorer and Safari browsers.
It must be mobile device capable for input and reporting.
It must be backed up nightly.
It must be able to delete all names older than 4 years from the list.
It should be available to all users 5 days a week, M-F, 24 hours a day.
It should be able to authenticate the email address
It should be able to not save the username
It should authenticate and only take five numbers in zip code
It should not take special characters in the Name field
It should take the date format as m/d/y

 
4. Give an example showing the difference between user requirements and system requirements
User requirements are what the software is required to do, what task the user wants to perform. For example:
A user needs a package that will handle invoices and produce monthly summaries and connect to their bank's
website to handle payments. That's a user requirement.
And the system requirement is the measurable and very specific terms that the system must meet to fulfill the
user requirement. Perhaps, accepting the invoice numbers from 1000-5000, should generate financial
statements automatically with monthly summaries, monthly summaries should include income statement,
 JYOTI GHALE
BA CLASS NOTES

balance sheets and cash flows, and amount should be in Dollar currency, payments should only link to the
company’s bank.

5. What are the agile buzzwords and explain.

 Sprint - It is a time box, where functionalities are developed. It is an agreed timeframe within which specific
work has to be completed and made ready for review. There is usually four parts in sprint and the duration is 2-4
weeks but also it depends on the complexity of the application and the product release. There will be a standup
meeting every day for 15 minutes where they will ask questions like what you did yesterday? What obstacles were
faced? What you are doing today? And moves forward to work on user stories.
 Backlog- This is where PO&BA comes in, where they take user stories. It is a to-do list or the list of everything
that PO wishes to see in the final product.
 Business and technical priorities
It is the categorizing the task according to the highest priority that is given which also depends on business
requirements.
 Sprint planning And Sprint Poker
Each Sprint begins with the planning meeting. During the meeting the PO and the Developers agree upon how
much work can be accomplished during the sprint. The PO has the final say on what criteria need to be met for
the work to be approved, all these comes under Sprint Planning.
Whereas, Sprint Poker is a gamified technique for estimating efforts or time in the software development in
which members of the group make estimate by playing number card face down to the table and reveal the card
and discuss the estimate on how much time needed to complete the task.
 Sprint Retrospective- It is the meeting that is held in every end of the sprint. It is the last thing done in the sprint
where there cover questions like, what we did good? What we can do better? What obstacles we faced?

Day#3

User Requirements Problems

 First attempt to describe functional and non functional requirements.
 Problem faced – ambiguous language
o Lack of Clarity
o Requirements confusion- functional- Non-functional requirements, design information are not distinguished
o Requirements amalgamation- several requirements are defined as a single one
o Incompleteness- requirements must be missing
o Inconsistency- requirements may contradict themselves

Guidelines to minimize the issues

 Separate requirements- functional or non-functional requirements must be clearly identified.
 Include a rationale for each requirement – helps clarify reasoning behind the requirements and may be useful for evaluating potential changes in the requirements.
 Invent or use a standard form/ template
 Distinguish requirements priorities
 Avoid Technical Jargons
 Testable(write test cases)
 Deliverables

System requirements:

 Elaborate the user requirements to get a precise, detailed and complete version of them
 Used by designers and developers
 JYOTI GHALE
BA CLASS NOTES

Writing Good System Requirements

 Natural language (informal requirements)
o Reviled by academics
o But widely practiced: everybody can read them, finding a better notation is hard
 Structured natural language
o Forms/ Templates are used to bring some rigor to natural language presentations
 Graphical notations
o Using boxes, Arrows…but they mean different things to different people.
 Formal Specifications
o Based on logic, state machines…
o Hard to understand for many people

Requirements Engineering

 5 important activities
1. Feasibility study
2. Requirements elicitations and analysis
3. Requirements Documentation
4. Requirements Validation
5. Requirements Management

1. Feasibility study

 It is done at first to decide whether or not the project is worthwhile

 Look at different perspectives:
o Market analysis, financial, schedule, technical, resource, legal…..
 Should make you aware of the risks
 Doing the study
o Consult information sources; managers, software engineers, end users….
o Based on information collection (interviews, surveys and questionnaires…)
 Should be short 2-3 weeks

Feasibility Study

 What if the system wasn’t implemented?

 What are current process problems?
 Do technical resources exist?
 What is the risk associated with the technology?
 Is new technology needed? What skills?
 How will the proposed project help?
 How does the proposed project contribute to the overall objectives of the organization?
 Have the benefits identified with the system being identified clearly?
 What will be the integration problems?
 What facilities must be supported by the system?
 What is the risk associated with cost and schedule?
 What are the potential advantages and disadvantages?
 Are there legal issues?
 Are there issues linked with the fact that this is an offshore project?
2. Requirement elicitation and analysis
 Stakeholders: person or group of persons who will be affected by the system, directly or indirectly.
 All stakeholders should be involved in requirements elicitation and analysis.
o Stakeholders don’t know what they really want
o Stakeholders express requirements in their own terms
o Different stakeholders may have conflicting requirements
 JYOTI GHALE
BA CLASS NOTES

o Organizational and the political factors may influence the system requirements.
o The requirements change during the analysis process. New stakeholders may emerge and the business environment change.
Different techniques for requirements elicitation and analysis
o Brainstorming
o Questionnaires
o Prototyping
o Interviewing

Interviewing: synchronous elicitation technique

Questionnaires: asynchronous elicitation technique

Based on:

o Ask questions and listening the answers

o Be prepared to ask follow up questions
o Ask for the document you need
o Log the answers (to support, complete or contradict what was said/ written)
o Involve all the stakeholders

User stories

 Alternate to use case mostly used in agile to use plan and estimate
 Use real world scenarios to document the user needs
 User stories are easy for user to read
 Usually documented using index cards
 Common template by Mike Cohn

Scenarios

o If it often easier for people to relate on real-life example rather than abstract statements.
o Scenarios and descriptions – sequences of events- of how the system is used in practice.
o Scenarios are composed of:
 A description of the initial state of the system
 A description of the normal flow of events in the scenario
 A description of what can go wrong and how it is handled
 Information on the other activities that might be going on concurrency
 A description of the final state of the system

#3) Requirements Documentation

Use Case

Use Case Id: UC2

Use Case Name: View details for a blu-ray disc
Descriptions: As a customer I would like to view the details for a specific blu-ray disc
Pre conditions: UC1 must have been done
Standard Flow: 1. Customer clicks a blu-ray from the list
2. Web shop sends a request about details for the give blu-ray disc to the DB
3. DB retrieves the requested data and send it to the web shop
4. Web shop displays details
Post Conditions: Details shown
 JYOTI GHALE
BA CLASS NOTES

Use Case:

Use Case ID UC6

Use Case Name View details for checking balance
Description Customer is directed to his/her banking portal
Pre Conditions UC5 Must have been done
1. Customers types in username (50 alpha/ num) and password (50 alpha/num)
correctly
Standard Flow 2. Login information is send to DB for verification
3. DB retrieves the requested information and sends it back to the website
4. Customer is directed to his/her banking account.
Post Conditions Balance displayed
1.1 Customers enters wrong password
1.2. DB retrieves the requested info and displays inappropriate password
1.3 Customer enters wrong password
1.4 System displays forgot password
Alternate Flow
1.5 Systems ask to enter answer to secret question
1.6 Secret answer is send to DB and verified
1.7 Customer is asked to type in new password twice.
2. DB retrieves the new password and customer is directed to his/her bank account
Post Conditions Balance displayed

(In interview just choose one techniques because using more can be costly, prototyping only if you are using
prototyping methodology)

WEEK 2, Day#1
Textual description of a Use Cases includes:
 Use case id
 Use case name
 Actors
 Description
 Pre condition
 Post condition
 Normal course
 Alternative course
 Extends
 Includes
 JYOTI GHALE
BA CLASS NOTES

 Priority

Use cases relationships

Inclusions

 A use case contain the behavior from another use case(unconditional)

 Can be seen as a factorization
 Introduced by the <<include>> keyword

Extensions:

 A use case conditionally interrupts the execution of another use case to argument its functionality
 An extension point may specify a precondition for the extending behavior
 Introduced by the <<extends>> keyword
4) Requirements Validation
 Requirements must be checked for :
 Validity, comprehensibility, traceability(source, dependency between requirements),
consistency, completeness, realism and verifiability
 Validation techniques
o Requirements reviews
 Expert review, two independent reviews
 Formal (developers, lead QA’s, , SMEs)/informal (peer BA’s)
 Involvement of the stakeholders necessary

o Test case generation

 Test case are developed for the requirement
o Prototyping
o Mini definition of the requirements
 A team redefined the requirement and compares them with the list of the
produced requirements

5) Requirements management: (RTM- Google it for interview) RTM is where your

requirements (BRDs) (use cases) are tested
o It deals with the process of managing changes in the requirements during the
requirements engineering process and system development
 JYOTI GHALE
BA CLASS NOTES

o Requirement traceability is concerned with the relationships between

requirements (dependencies), their sources and the system design.
o Case tools are necessary for the requirement storage and management
 Diagramming Techniques
o Flowchart
o UML diagram (activity diagram)
o Data flow diagram (DFD): is a graphical representation of the “flow” of data through an
information system, modeling its process aspect. It is also known as data modeling.

DATA STORE

FLOW
EXTERNAL
ENTITY

FUNCTION

 BPM (Business Process Model) Notation

It’s a diagram used to diagrammatically define business process model
 JYOTI GHALE
BA CLASS NOTES

DATA

EVENT
GATE WAY

CONNECTOR

ACTIVITY GROUP

UML DIAGRAMS
 JYOTI GHALE
BA CLASS NOTES

Activity Diagram

o Describes workflows with simple diagrams.

 JYOTI GHALE
BA CLASS NOTES

PROCESS -connector

* *

SWIM LANES

o The swim lanes The swim lanes are flowcharts with an addition that process and decision are
group visually by placing them in lanes .Parallel lines divide the chart into lanes ,with one
lane for each person ,group or sub-process .Lanes are labeled to show how the chart is
organized
 JYOTI GHALE
BA CLASS NOTES

Week 2 class 2

Class diagram Commented [S1]: It is a structure uml diagram, where it

classifies a system according to its class name, attributes and the
behavior
Class name

Attributes

Operations

Object: anything has performance or action.

Object: Research on object

Creating a class

o Type-

Name: what is it?

Ex: name, employee, bank account

o Properties and data-

Attribute: what describes it?

Ex: width, height, color, files type

o Operations or behavior-

Behavior: what can it do?

Play, open, save, print, close

o Principles: A PIE

A – Abstraction (object)

P – Polymorphism (overriding)

I – Inheritance (all the attributes and behaviors from super class) taking all the functionalities from the parent and some
more functions) adding
 JYOTI GHALE
BA CLASS NOTES

E – Encapsulation (making info (+) public and (-) private)

Encapsulation

Bank Account

Account Number (-):

Date Opened (-):
account Type (-):

(+)Open()
(+)Close()
(+)Deposit()
(+)Withdrawal()

o Public (+)
o Private (-)

Person
-Name
-Email
-phone
+change Email()

Employee Customer
-(has everthing with Person) +(has everything with person)
+empoyeeGrade() -customerNumber()
+joint()
+retire()
 JYOTI GHALE
BA CLASS NOTES

Polymorphism

Overwriting functionality in a subclass.

Bankl Account
-accountName balance
-deposit()
-withdrawl()

Savings Account Investment Account

Checking Account
-(has everything from BankAccount) -(has everything from BankAccount)
-(has everthing from BankAccount)
+InterestRate() -accountRep ()
+lastCheckNum() -withdrawal()

Overriding

Identifying Objects

o Use Case Scenario

Customer confirms items in shopping cart. Customer provides payment and address to process sale. System
validates payment and responds by confirming order, and provides order number that a customer can use to
check on order status. System will send Customer a copy of Order details by email.
Noun List
o customer
o item
o shopping cart
o payment
o address
o sale
o order
o order number, order details, order status
o email
o system

Object (Nouns)
#1.Customer/ #2.Payment/ #3.Order/ #4.Shopping Cart/ #5.Address/ #6.Email
Verbs
Confirms items-4
Provide payment-2
Validate Payment-2
Provide address-5
 JYOTI GHALE
BA CLASS NOTES

Provide Order-3
Confirming Order-3
Check order Status -3
Customer receipt-6

ERD (Entity relationship Diagram)

Summary:
User wants to enroll in the healthcare plan. User opens health care portal and clicks on get coverage tab.
System provides dropdown menu options for State and user selects AL as state and clicks on Continue. System
provides the field to enter Zip code and choose among three options. User enters zip code and selects one of
the options and clicks Continue. System validates Zip code and option. System redirects user to the new page to
create an account.

Nouns: user, healthcare portal, coverage Tab, menu options, State AL, Zip code, New Page
Verb:

User Heathcare portal Coverage Tab Menu options

1 1 11 1 *
+opens heath care portal() +clicks on get coverage tab() +Provides Dropdwn Menu options()

1 1 Zip Code 1 1
New Page State

+Provides Zip Code()

+Redirects to new page () +Provides St as AL()
+Validates Zip Code()
ERD
(Entity relationship Diagram)
 JYOTI GHALE
BA CLASS NOTES

Home Assignment
Find real life use cases activity diagram, swim lane Diagram, Class diagram

Wednesday 22nd
Requirements Gathering
BABOK divides requirement gathering into 10 methods as follows

 Brain storming  Observation

 Document Analysis  Prototyping

 Focus group  Requirements workshop
 Interface analysis  Reverse engineering
 Interview  Survey

BRAIN STORMING
 Brainstorming is used in requirements elicitation to get as many ideas as possible from a
group of people. Generally used to identify possible solutions to problems, and clarify details
of opportunities. Brainstorming casts a wide net, identifying many different possibilities.
Prioritization of those possibilities is important to finding the needles in the haystack.

Document Analysis

 Reviewing the documentation of an existing system can help when creating

As-Is process documents, as well as driving gap analysis for scoping of migration projects. In
ideal world, we would even be reviewing the requirements that drove creation of the
existing system – starting point for documenting current requirements. Nuggets of
information are often buried in existing documents that help us ask questions as part of
validating requirement completeness.

Focus Group

 A focus group is a gathering of people who are representative of the users or customers of a
product to get feedback. The feedback can be gathered about the needs/ opportunities/
problems to identify requirements, or can be gathered to validate and refine already elicited
requirements. This form of Market research is distinct from brainstorming in that it is a
managed process with specific participants. There is a danger in “following the crowd”, and
some people believe focus groups are at best ineffective. One risk is that we end up with the
lowest common denominator features.
 JYOTI GHALE
BA CLASS NOTES

Interface Analysis

 Interface for a software product can be human or machine. Integration with external systems
and devices is just another interface. User Centric design approaches are very effective at
making sure that we create usable software.
Interface analysis- reviewing the touch points with other external systems-is important to
make sure we don’t overlook requirements that aren’t immediately visible to users.

(BA Certification)

Interview

 Interviews of Stakeholders and users are critical to creating the great software. Without
understanding the goals and expectations of the users and stakeholders, we are very unlikely
to satisfy them. We also have to recognize the perspective of the each interviewee, so that
we can properly weigh and address as inputs.

Observation

 The study of users in their natural habitats is what observation is about. By observing users,
an analyst can identify a process flow, awkward steps, pain points and opportunities for
improvement. Observation can be passive or active (asking questions while observing).
Passive observation is better for getting feedback on a prototype (to refine requirements),
where active observation is more effective at getting an understanding of an existing
business process. Either approach can be used to uncover implicit requirements that
otherwise might go overlooked.

Prototyping

 Prototypes can be very effective at gathering feedback. Low fidelity prototypes can be used
as an active listening tool. Often, when people cannot articulate a particular need in the
abstract, they can quickly assess if a design approach would address the need. Prototypes are
most efficiently done with quick sketches of interfaces and storyboards. Prototypes are even
being used as the “official requirements” in some situations.

Requirements

 More commonly known as a Joint Application Design (JAD) session, workshops can be very
effective for gathering requirements. More structured than a brainstorming session, involved
parties collaborate to document requirements. One way to capture the collaboration is with
 JYOTI GHALE
BA CLASS NOTES

creation of domain- model artifacts (like static diagrams, activity diagrams). A workshop will
be more effective with two analysts than with one, where a facilitator and a scribe work
together.

Agenda (talk to your PO, achievable functionalities)

Reverse Engineering

 Is this a starting point or a last resort? When a migration project does not have access to
sufficient documentation of the existing system, reverse engineering will identify what the
system does. It will not identify what the system should do, and will not identify when the
system does the wrong thing. Write about what it does not focus on what it doesn’t do.

Survey
 When collecting information from many people – too many to interviews with budget and
time constraints- a survey or a questionnaire can be used. The survey can force users to
select from choices; rate something (Agree Strongly, Agree.), or have an open ended
questions allowing free form responses. A well designed survey would provide qualitative
guidance for characterizing the market. It should not be used for prioritization of the features
or requirement.

Decision Tables

Decision tables are used to lay out in tabular form

Use Cases

Use case is a documentation technique to identify, clarify, and organize system requirements to achieve a
particular goal using a set of steps and one or many actors.

 Use cases are the part of the rational unified process since the late 1990’s.
 They were developed by Jacobson and perfected by Cockburn.
 Use cases define what the system will do not how.
 Use cases define the interaction between the system and the users.
 Use case defines a set of scenarios that describe externally visible behavior that delivers
value to one or more users of the system.

Use Case Terminology

 JYOTI GHALE
BA CLASS NOTES

 Actors
 Goals
 Use case title
 Use case body

Types of Use Cases

 Informal use case also called a casual use one.

 Fully dressed use case also known as formal use case

Informal Use Case

 Title
 Primary Actor
 Scope
 Level (whom you are writing it for or in which language)
 Steps: A set of steps to achieve the goal.

Fully Dressed Use Case

Id Success guarantees
Title Trigger
Primary Actor Main success Scenario (steps)
Secondary Actors Extends
Goal in context Includes
Scope Technology and data variation list
Level Related Information
Precondition
Minimal guarantees (risk that you face in that
use case)

BA Tools – Jira (well-used), visio

Business Case
 JYOTI GHALE
BA CLASS NOTES

A use case will need to tie in to a business case where the business case is actual reasoning to initiate the
project. The use case may extend the business case.

(Business case talks about the required doc where, they talk about the scope of the business.)

Wireframes

 A wireframe is a schematic or other low fidelity rendering of a computer interface, intended to

primarily demonstrate functionality, features, content, and user flow without explicitly specifying
the visual design of a product.
 Axure Rp
 Balsamic Mockups
 Denim
 Visio and GUUUI prototyping Tools, and Yahoo! Design Stencil Kit

BRD Template
 Title  Methodology
 Version  Functional Requirements
 Description Of Change(updates) o Context (relationship of the system to
outside world)
 Author o User Requirement( the expectation of
the user from the software, what the
user expects the software will be able
to do )
 Date o Data Flow Diagram( how your Commented [S2]: YouTube practice
data/information flows in the system)
 Contents o Logical Data Model/ Data dictionary

 Introduction  Other Requirements

o Purpose  Interface
o Scope
o Background (Previous Version)
o References
o Assumptions (assume what the
document would be ) and Constraints
(limitation)
o Document Overview
 Data Conversion
 Hardware/ software
 JYOTI GHALE
BA CLASS NOTES

 Operational
 Appendix A- Glossary

System Requirement Document (SRD)

System Requirement Document (SRD) presents the result of the definition of need, the operational concept,
and the system analysis tasks. As such, it is a description of what the system’s customers expect it to do for
them, the system’s expected environment, the system’s usage profile, its performance parameters, and its
expected quality and effectiveness. Thus it presents the conclusions of the Analysis Cycle.

System Requirement Document (SRD) Template

1. Introduction to the document 3.1 External Interface Requirements
1.1 Purpose of the product 3.1.1 User Interfaces
1.2 Scope 3.1.2 Hardware Interfaces
1.3 Acronyms, Abbreviations, Definitions 3.1.3 Software Interfaces
1.4 References 3.1.4 Communication Interfaces
1.5 Outline of the rest of the SRS 3.2 Functional Requirements
2. General Description of the 3.3 Performance Requirements
product
2.1 Context of Product 3.4 Design Constraints
2.2 Product Functions 3.5 Quality
2.3 User characteristics 3.6 Other
2.4 Constraints 4. Appendices
2.5 Assumptions and dependencies
3. Specific requirements

Job Responsibilities of a BA

o Be the liaison between the business units, technology teams and support teams
o Elicit requirements using interviews, document analysis, requirements workshops, surveys, business
process descriptions, use cases, scenarios, business analysis, and task and workflow analysis.
o Critically evaluate information gathered from multiple sources, reconcile conflicts, decompose, high-
level information
 JYOTI GHALE
BA CLASS NOTES

Domain
Healthcare Insurance
EDI (Electronic Data Interchange)

EDI 834 ----- Enrollment & Maintenance

EDI 837 ----- CLAIMS (From Provider to Payer)

EDI 270 ---- Eligibility inquiry (From Provider to Payer)

EDI 271 ---- Eligibility inquiry response (From Payer to Provider)

EDI 276 ---- Claim Status Inquiry (From Provider to Payer)

EDI 277 ----- Claim Response (From Payer to Provider)

EDI 835 EOB (explanation of Benefits)

PPO/HMO/EPO

OBAMA CARE (EDI 834) Front-end (EDI 834: Enrollment and Maintenance, these are called member level
detail, plan level details and demographic level details).

Member level details

DOB

Zip code
 JYOTI GHALE
BA CLASS NOTES

Gender

Whether you are a tobacco user or not?

Whether you are a full time student or not?

Is someone in your family pregnant or not?

Plan Detail

 Co-pay (upfront pay –whenever you go to doctor , you have to pay)

 Deductible (you have to pay the deductibles, greater than deductibles will pay by the Payer)

 Out of pocket – 10,000

 In-network

 Out Network

Demographic Information
Personal – Legal status (Resident & Marital)
Financial – SSN, household composition (how many people are in the house, how many dependents
are in the house), income calculation (annual income), Medicaid (is run by State) under poverty line
Medicare (federal) is for the people who is over 65 federal poverty line.
Part a- Medical insurance hospital, Part b- Medicare insurance professionals, Part c- Medicare by
private company, Part D-
After hitting submits ---- system validates and you will get a member id number in few days.
After submitting the application id/reference no will be generated.
From UI all information comes to internal administrative server
Staging area: processing two types:

Real Time Processing (when the information comes in, it immediately goes for validation it does not wait
for a batch)

Member center (validation of the 834 with the Business rules) is the guidelines that are laid down in your
compliance guide 5010 (HIPPA)
 JYOTI GHALE
BA CLASS NOTES

BIZ Talk (this tool converts your X12 (all EDI are x12 format – not readable) to xml format.

Then this information Membership system and then in that Membership system creates your member ID

EDW (enterprise Data Warehouse)

Real time processing- application information immediately goes for validation.

In batch processing (Cut-off time): certain number of application process together
Member center: validation of 834 with business rules *(the guide line that lay down in your compliance guide
5010) 5010 are a set of business rules passed by HIPPA.
From member center it goes to BIZTALK which convert from X12 to XML
Converted info goes to in house MEMBERSHIP SYSTEM and member ID generated and stored in EDW
(enterprise data warehouse). FACETS commonly use by private org.

 Medicare is a federal program that provides health coverage if you are 65 or older or
have a severe disability, no matter your income.

 Medicaid is a state and federal program that provides health coverage if you have a
very low income.

Medicare 4 parts
Part a- Medical insurance hospital

Part b- Medicare insurance professionals

Part c- Medicare by private company

Part D- Pharmacy

Affordable Care Act (Obama Care)

Marketplace—also known as -HIX Portal (Health Insurance exchange) e.g. Healthcare.gov federal facilitated

When you put a zip code if it accepts and takes you to Marketplace otherwise

(When you don’t go to HIX Portal) it takes you to State Exchange and to Mass Connect

Which State follows HIX portal and which state follows State Exchange
 JYOTI GHALE
BA CLASS NOTES

1095A-

Includes:

Recipient information

Coverage Household

Household Information
 JYOTI GHALE
BA CLASS NOTES

Cognizant Company owns QUICLINK, FACETS (You can make changes and add in
FACETS) and TRIZETTO

The three statuses that comes in EOB 835

 Paid - They print the check and sent it to the

 Pending
 Denied

QNXT
 JYOTI GHALE
BA CLASS NOTES

FACETS Backend uses SQL

837 P – Professional (Doctors)

837I – Institutional (Hospitals)

837 D- Dental
EDI 835: 3 status comes on EOB 835 are PAID, PENDING and DENIED
PAID – automated clearing house, printing check
PENDING – if the claim pending it goes back to mapping tool and a copy of 835 will be sent to provider.
DENIED – 835 shows denied.

837 format

HEADER

[MEMBER LEVEL DETAILS

[PLAN LEVEL DETAILS

[PROVIDER LEVEL DETAILS

[CLAIM LEBVEL DETAILS

[ICD CODES(INTERNATIONAL CLASSIFICATION OF DISEASES) Commented [S3]: ICD’S ARE TWO TYPES ICD9&ICD10
CONVERSION till before oct, 2015
[SERVICE LEVEL DETAILS

FOOTER
 JYOTI GHALE
BA CLASS NOTES

ICD (The International Classification of Disease) code has two structures: Diagnosis structure and
Procedural structure

 Diagnosis structure:
 ICD 9: 3-5 characters. First character- number/ alphanumeric, 2 to 5- Numeric
 ICD 10: 3- 7 characters. First character- alphabet, 2nd- numeric, 3-7: alphabet or numeric
 Procedural structure
 ICD 9: 3-4 characters. All characters are numeric; all codes have at least three characters.
 ICD 10: Has 7 characters, each code can be alphabet or numeric. Numbers 0-9: A-H, J-N, P-Z.

The whole mapping is GEM (General Equivalent Mapping)

CPT HealthCare

MORTGAGE Domain Tuesday (28th March, 2017)

There are three elements of Mortgage

1) Borrower
I. Personal information
 Name
 Address
 Phone number
 Dob
 Email address
 Residency Status
 Driver’s license no.
 Co-signer
 SSN
 House you are living is owned or Rental
II. Financial Information
 Employment status
 JYOTI GHALE
BA CLASS NOTES

 Proof of Income (W2s and Pay Stub’s Income )

 Credit History – Credit Score

3 Credit Bureaus( Governing body for Credit Score)

 TransUnion
 Equifax
 Experian
 Land, building – fixed assets
 Debt History( how much you spend in a month like, your
car payment, House rent, cc debts, utilities)

2) Lender
 Down Payment
 APR- Annual Percentage Rate- how much Interest rate you
pay
 Types of Loan
o Conventional Loan
 Minimum has to be 5 % Down payment
 Minimum Credit score is 650 ( depends upon yearly)
 Ideal credit score is 700

PMI (Premium Mortgage Insurance) you have to pay

PMI when you pay less than 20% of the down payment -
You can cancel when you reach 78% of the home value
or your bank will automatically cancel it once it reaches
to 80

o Federal Housing Administration(FHA Loan)

 JYOTI GHALE
BA CLASS NOTES

 First Time Home buyer

 Min. 3.5%
 Credit score criteria 620- 630 approx
 The APR is less than Conventional Loan
o VA( Veterans Affair) Loan
 3 % down payment
 Don’t have to pay PMI
 Sometimes, they even qualify for no interest
o Non conventional Loans
o Rural Loans
o Jumbo Loans ---- are the loans whose house value is
more than 417K
 Can be FHA and conventional also
 APR is higher (luxury House)
 Loan Terms
a) 15 year fixed
b) 30 year fixed
c) 5’1 ARM (Adjustable Rate Mortgage) you can
lock your interest rate for 5 years
d) 7’1 ARM (Adjustable Rate Mortgage) you can
lock your interest rate for 7 years
e) 10’1 ARM (Adjustable Rate Mortgage) you can
lock your interest rate for 10 years
 Refinancing (After certain Arm, if the market rate is
high then they refinance to get a lower rate)
 Cash- out Refinance
 Regular Refinance(paying towards the house-
lowering interest rate )
 JYOTI GHALE
BA CLASS NOTES

 Closing Cost
o Locking Fee (get the house in that amount,
locking amount)
o Inspection Fee- Inspecting the house, if the
house is in working conditions
o Broker’s fees
o Attorney fees
o HUD1 fees before 2008- to itemize services and fees charged
to the borrower by the lender or broker when applying for a loan for the
purpose of purchasing or refinancing real estate. HUD refers to the
Department of Housing and Urban Development.
o Title service Cost
o Recording Fees- Recording in Home Loan
Department
o Documenting of Transaction Stamps or Taxes
(This is done by jurisdiction, respective county)
o Transaction Stamps or Taxes
o Mortgage application Fee (Buyer)- this is
processing your Loan application
o Appraisal Fees (Valuation of the property)
o Home Warranty
o Settlement Fees
o HOA (Home Owners Association)

3) Property
 Year your property was build
 Location --- flood zone, hurricane zone
Single Family Home – Free Standing house with Front yard and
Back Yard
 JYOTI GHALE
BA CLASS NOTES

Town House: The owner owns the house, land, Front yard and
Back Yard and certain permitted height above (sky)
Town Houses (two types) – 1) land belongs to you
2) Condominium- You own the walls, everything inside it
3) Apartments- It is rented (you don’t own anything)

Best Practice In Use Case ---- first separate Functional and non
functional, use diagrams for clarity and use notes in the case of
necessity.
BRD’S, FSD’S AND RTM are owned by BA
Non-functional requirements- quality of the User story -15 a
day and use case 2 in a week

Next Class: How the IT side of Mortgage is done (Wednesday--28th March, 2017)

Test Case

Test Plan:

IT Part Of Mortgage (Backend database)

How your process works is POS(Point of Sale)- gather information from

customers, has most of the borrower’s financial information and lender’s
information. All these come in a form of 1003, this form is regulated by Fannie
Mae.

The flow

From POS(gathers information) -----(Processing)the application, it goes to

processing and is reviewed and verified the documentation by QA’s that we get
from 3rd party(appraisal & inspection)-------Underwriting (underwriter- loan
 JYOTI GHALE
BA CLASS NOTES

officer) checks whether the loan is approved or not approved, we are reviewing,
its fraud or not and put it in the application, 1008 form Underwriter verifies.
Underwrite will accomplish with the form Approved, Decline, Hold

CLOSING AND FUNDING

WHATEVER THE DOCUMENT (loan packet) ARE SEND by the underwriter is

reviewed then confirm the closing date and fees, and prepare the closing packet
and send it to different departments or different modules and here again the
loan packet is reviewed. Follow up with the settlement agent with any missing
or problem document.

Final is Shipping and delivery, where packet is prepared and sent to the
appropriate party

Los (Loan origination system) Modules

 POS
 PROCESSING
 UNDERWRITING
 CLOSING AND FUNDING
 Shipping and delivery

How do you price your Mortgage: what is there in the closing and funding – your
credit score, loan types, taxes, down payments

JAD session preparation

 Process flow chart- Presentation (By BA)
 Key participants
 JYOTI GHALE
BA CLASS NOTES

 Agenda

(Meeting minutes- output of the JAD meeting)

BA interview

I’ve worked as a BA ---BA experience

Technical experience

Health care experience

And integrate everything

Burn-down

Requirement Gathering Technique

 Delphi Technique – when there is different confidential views and

you don’t want to disclose the person’s idea
 Nominal Technique

Good points of BA
Communication is one of the greatest techniques, I keep track to
data matrix
Strong in documentation
I make version control
Good in Presentation, business walk through Meetings
Weakness- Too much attention to details
No programming background so I could better know about my
developers coding
Challenges
Create one scenario story:
 JYOTI GHALE
BA CLASS NOTES

I was working with different small groups, manual forms to convert

into digital – many legal issues