Recent Posts

Pages: [1] 2 3 ... 10
Business Analyst Concepts Discussion / Re: Project fail?
« Last post by Satish kumar Gajula on April 25, 2018, 09:45:57 pm »
Reasons for Project Failure:
   Improper requirement gathering
   Continuous change in requirements
   Lack of user involvement
   Lack of Executive Support
   Unrealistic Expectations
   Improper planning
Agile-Scrum Interview Questions

1. What is Agile-Scrum?
2. Did you follow the agile-Scrum methodology in your project?
3. What are the several light weight methodologies in Agile?
4. Give the example of Agile - Scrum?
5. Give Example of Diagram?
6. What is the template?
7. Any documents do you follow in Agile- Scrum?
8. What is your role in Agile-Scrum?
Elicitation Techniques in Business Analysis are as follows:
   Brainstorming
   Document Analysis
   Reverse Engineering
   Focus Groups
   Observation
   Workshop
   JAD (Joint Application Development) – Requirements Workshop
   Interview
   Prototyping
   Questionnaire (Survey)
Business Analyst Concepts Discussion / Re: use case actors
« Last post by Satish kumar Gajula on April 24, 2018, 06:17:41 pm »
Actors include in Use Case:
1.   Primary Actor
2.   Secondary Actor

Difference between Primary and Secondary Actor:
Primary Actors are actor(s) using the system to achieve a goal. The Use Case documents the interactions between the system and the actors to achieve the goal of the primary actor. Secondary Actors are actors that the system needs assistance from to achieve the primary actor's goal
A flowchart depicts the flow of operation through a programme or process by dividing the system or process into events/activities and presenting the logical relationship between them. A flowchart is a tool for analysing processes, programs or systems
Followings are Business Analyst delivered documents:
1.   Business Requirement Document (BRD)
2.   Functional Requirement Document (FRD)
3.   Software Requirement Specification Document (SRS)
4.   Requirement Traceability Matrix (RTM)
5.   Minutes of Meeting (MOM) (Note: It Depends)
6.   User Manual
Following tools are used by a Business Analyst:
Documentation Tools:
1.   Ms-Office
2.   Think free
3.   Adobe Buzzword
4.   Zoho writer

UML Drawing Tools:
1.   Ms-Visio
2.   Rational Rose
3.   Smart Draw
4.   Magic Draw
5.   Concept Draw
6.   Visual Paradigm
7.   Enterprise Architect
8.   Argo UML
9.   Star UML
10.   Case Complete

Prototyping Tools:
1.   Justinmind Prototyper
2.   Wireframe sketcher
3.   Axure
4.   Iplotz
5.   Pidigo
6.   Pencil
7.   Microsoft expression Blend
8.   iRise

Business Modeling Tools:
1.   eBPMN
2.   AgilePro

Software Development Process Model:
1.   RUP (Rational Unified Process)

Brainstorming Tools
1.   Evernote – A note taking, brainstorming and web clipping tool
Free Mind – Free mind is free mind mapping software written in java

Meeting Minutes:
1.   Meeting Sense

Other Tools:
1.   Rational Requisite Pro
2.   Analyst Pro

Note:  Some Tools written for awareness.
Steps to follow to draw a Use Case diagram from a case study:
1.   Information which we Do Not model in Use Case diagrams are
a)   Name of the systems (Laptops, Desktops, Workstations),
b)   Architectures (2 Tier, 3 Tier, n Tier, Client Server),
c)   Databases Names (DB2, SQL Server, My SQL),
d)   Networks (LAN, WAN, Internet),
e)   Brand Names (HP, Lenovo, Wipro, Sony)
f)   Technology Names (Java, .Net, Mainframes)
2.   Differentiate information against actions
3.   Write all sequence of actions
4.   Try to find out which actor is performing the above action
5.   Try to identity Essential Use Cases and Supporting Use Cases
6.   Try to identity some modules with respect to functionality or usage
7.   Try to draw the relationships appropriately between the identified actors and use cases.
Business Analyst Concepts Discussion / Re: Business Analyst delivered documents.
« Last post by 1172831810 on April 07, 2018, 05:02:00 pm »
The type and specifications a business analyst is expected to create in an organization depends upon many parameters like organization’s processes and policies, need and expectations of the business, and the stakeholder requirements. Detailed below are the common documents a business analyst is expected to create and they are extensively used throughout the course of a project. Each of these documents has a specific template and it’s a part of the overall project documentation.

The documents are:

Project vision Document
Requirement Management Plan
User stories
Use cases
Business Requirement Document
Requirement traceability matrix (RTM)
Functional requirement specification (FRS)/ Functional Specification Document (FSD)
System requirement specification (SRS)/ System Requirement Document (SRD)
Test case
The following checklist shows the steps necessary for the construction of use case diagrams from the external view.

  • Collect information sources—How am I supposed to know that?
    Identify potential actors—Which partners and customers use the goods and services of the business system?
    Identify potential business use cases—Which goods and services can actors draw upon?
    Connect business use cases—Who can make use of what goods and services of the business system?
    Describe actors—Who or what do the actors represent?
    Search for more business use cases—What else needs to be done?
    Edit business use cases—What actually has to be included in a business use case?
    Document business use cases—What happens in a business use case?
    Model relationships between business use cases—What activities are conducted repeatedly?
    Verify the view—Is everything correct?

Pages: [1] 2 3 ... 10