Explore topic-wise InterviewSolutions in .

A business analysis presentation of the steps involved in DEFINING the interactions between a USER (actor) and a system (computer system) is termed as USE case model. It gives details on the interactions and sets the expectations of how the user will work within the system. (e Learning Portal)

The use case model consist of 2 main ELEMENTS:

1. Use case diagram – It is a graphical representation that details which actors can operate which use cases
2. Use case description – It is a detailed TEXTUAL step by step presentation of interactions and dialogue between the actor and the system.

A business analysis presentation of the steps involved in defining the interactions between a user (actor) and a system (computer system) is termed as use case model. It gives details on the interactions and sets the expectations of how the user will work within the system. (e Learning Portal)

The use case model consist of 2 main elements:

Flowchart SHOWS complete flow of SYSTEM through symbols and diagrams. It is important, because it MAKES the system easy to UNDERSTAND for developers and all concerned PEOPLE.

Flowchart shows complete flow of system through symbols and diagrams. It is important, because it makes the system easy to understand for developers and all concerned people.

No, that is not the advisable case. EVERY BA has to take the DECISION regarding business/technical aspects of a PROJECT only after discussions and meetings with the APPROPRIATE members of the team. In this way meetings and team discussion come off as the most important aspects of BA’s decision making capabilities.

No, that is not the advisable case. Every BA has to take the decision regarding business/technical aspects of a project only after discussions and meetings with the appropriate members of the team. In this way meetings and team discussion come off as the most important aspects of BA’s decision making capabilities.

The BA has a good share of both business knowledge and technical knowledge pertaining to a specific domain. So when it comes to marketing a PRODUCT or PROCURING a project, he can give his VIEWS and prospect ORIENTED perspective in a more acceptable manner to the customers. This MAKES him a good advantageous role in marketing department of an organization.

The BA has a good share of both business knowledge and technical knowledge pertaining to a specific domain. So when it comes to marketing a product or procuring a project, he can give his views and prospect oriented perspective in a more acceptable manner to the customers. This makes him a good advantageous role in marketing department of an organization.

Never should we bring out the small GLITCHES on the TOP. We have to see through the EYES of the BUSINESS persons and should always try to instill confidence in them, as much as we have on ourselves. As what they expect is the outer level of details, we should bring out the expectation, assumptions and other such criteria into picture CLEARLY.

Never should we bring out the small glitches on the top. We have to see through the eyes of the business persons and should always try to instill confidence in them, as much as we have on ourselves. As what they expect is the outer level of details, we should bring out the expectation, assumptions and other such criteria into picture clearly.

The documents that are responsible to be completed as a Business Analyst may INCLUDE:

• Study of Feasibility.
• Scope & Prospect of Project.
• Business Requirements Document.
• FUNCTIONAL Requirements document including UML, Activity and dataflow diagrams.
• Fact sheet for constraints from TECHNICAL side (as prescribed from client).
• Testing phase documents including QA Test requirements, PLAN and types of tests that have to be considered before DELIVERY.

The documents that are responsible to be completed as a Business Analyst may include:

To do it right the first time, has always been the motto for projects that are running under a tight SCHEDULE. To find out the right requirement thus is important. Translating the requirements from client to the DEVELOPERS is essential for the project to kick off on the right note. If this stage goes off-track, then you can be jeopardising the FUTURE of the entire project.

To do it right the first time, has always been the motto for projects that are running under a tight schedule. To find out the right requirement thus is important. Translating the requirements from client to the developers is essential for the project to kick off on the right note. If this stage goes off-track, then you can be jeopardising the future of the entire project.

The most important tools are meant for diagrammatically representing the PROJECT through its various phases. In this sense, the most important software tools are:

• MS-Word : Requirement gathering and discussions will customers will mostly be through Word documents, be it the marketing or business document.
• MS-Visio: This will be one of the most important TOOL that every BA has to have knowledge about. This will HELP you coordinate the project at every level of development.
• IBM-Rational Suite: This is a good tool to get good representations of requirements gathering and other functional diagrams.
• Other Testing Tools: Most of the time it is better to get involved in the QA tests as a Business ANALYST. So a good knowledge about the QTP, Load Runner etc will be of use. Other than these, MS SharePoint, SQL DATABASES will also find good use in the career of the Business Analyst.

The most important tools are meant for diagrammatically representing the project through its various phases. In this sense, the most important software tools are:

The following STEPS will detail out the procedural way of professionally dealing with this:

• Identify the scope of the project.
• Take out the key features expected by the client. Reason out the most critical aspects of the system that has to be built.
• Depict the business use oriented UML diagram and derive it further to the specificity of what is needed from the technology side of development.
• Detail out the use cases that will make the input from client clear to the developers. Refinement should always be done with peer discussions.
• ACTIVITY, work-flow and data-flow diagrams are of immense importance in DETAILING out the requirement. Identifying the best modeling technique and representation of the deciphered Client input will finally go through to the Development team across series of meetings.

The following steps will detail out the procedural way of professionally dealing with this:

The FIRST and foremost character that a Business Analyst has to show is confidence. Without that aspect, the INTERACTIONS with CUSTOMERS and clients can never be positive. Especially during the rough times of project when there are development related issues that are being handled, the customer has to be given the RIGHT positive picture from the business/development PERSPECTIVE. This has to be done and handled by the Business Analyst. Not just self-confidence but the confidence that he places on the other teammates come into prominence.

The first and foremost character that a Business Analyst has to show is confidence. Without that aspect, the interactions with customers and clients can never be positive. Especially during the rough times of project when there are development related issues that are being handled, the customer has to be given the right positive picture from the business/development perspective. This has to be done and handled by the Business Analyst. Not just self-confidence but the confidence that he places on the other teammates come into prominence.

I have always liked the career of Business Analyst not just because of the management perspective but also because of the responsibilities that would be held in order to make the entire project successful one.. Growing with the organizations success as a more prominent and EFFECTIVE analyst has always been in my mind right through. I would also LIKE to take up the BA certifications like the PRINCE 2 in the NEAR future. This would help me grow in a field that I like most, in a more professional way.

I have always liked the career of Business Analyst not just because of the management perspective but also because of the responsibilities that would be held in order to make the entire project successful one.. Growing with the organizations success as a more prominent and effective analyst has always been in my mind right through. I would also like to take up the BA certifications like the PRINCE 2 in the near future. This would help me grow in a field that I like most, in a more professional way.

As a Business Analyst, one always have the top notch communication skills. A PERFECT mix of TECHNICAL knowledge and business market knowledge is highly essential. I consider myself a very quick learner and with a GOOD ability to communicate with the development teams and the customers, I think I can CERTAINLY make a good difference to the organization on the whole. Ability to deal with conformance tests and identify the PROMINENT parts of the use cases and track them through time will make me more than efficient in the overall work that is involved.

As a Business Analyst, one always have the top notch communication skills. A perfect mix of technical knowledge and business market knowledge is highly essential. I consider myself a very quick learner and with a good ability to communicate with the development teams and the customers, I think I can certainly make a good difference to the organization on the whole. Ability to deal with conformance tests and identify the prominent parts of the use cases and track them through time will make me more than efficient in the overall work that is involved.

Give definite examples of your skills and ACCOMPLISHMENTS. Be positive, and emphasize how your background MATCHES the JOB description. Mention any SOFTWARE packages and spreadsheet software you are familiar with. Also LET them know if you have advanced knowledge of any of the software.

Give definite examples of your skills and accomplishments. Be positive, and emphasize how your background matches the job description. Mention any software packages and spreadsheet software you are familiar with. Also let them know if you have advanced knowledge of any of the software.

I would RATHER focus on issues and the facts RELATED. Origin of ISSUE, severity of the issue, implications and possible solutions to solve the issue. Try not to focus on the PERSON who brought up the issue. Another important part is how to avoid similar issues in FUTURE.

I would rather focus on issues and the facts related. Origin of issue, severity of the issue, implications and possible solutions to solve the issue. Try not to focus on the person who brought up the issue. Another important part is how to avoid similar issues in future.

EXTRACTION Transformation and LOADING. Used mainly in data WAREHOUSING.

Extraction Transformation and loading. Used mainly in data warehousing.

• It is called as rapid application development.
• It is a development process that is used to build APPLICATIONS in SMALLER periods like 50-70 DAYS i.e with some compromises.

We do it by seeing min bugs in the PRODUCT according to STANDARDS MAINTAINED by COMPANY.

We do it by seeing min bugs in the product according to standards maintained by company.

MAINLY used to SEE the performance ISSUES and SYSTEM hangs.

Mainly used to see the performance issues and system hangs.

It REQUIRES slight PROGRAMMING knowledge to EXAMINE the outputs.

It requires slight programming knowledge to examine the outputs.

It is completely a functional TESTING. i.e the TESTER need not know how it WORKS TECHNICALLY. He only BOTHERS what input he is giving and what output he is getting.

It is completely a functional testing. i.e the tester need not know how it works technically. He only bothers what input he is giving and what output he is getting.

It is the MAPPING of DATA from SOURCE SYSTEM to a DESTINATION system.

It is the mapping of data from source system to a destination system.

• USER ACCEPTANCE testing.
• If the UAT fails, BA did not understand the REQUIREMENTS PROPERLY.

Object oriented ANALYSIS and DESIGNING. USED in coding od object oriented languages LIKE c++, Java, and SAP Basis ETC.

Object oriented analysis and designing. Used in coding od object oriented languages like c++, Java, and SAP Basis etc.

SDLC, RUP, SEI-CMM, Six SIGMA, SWOT, Cost benefit ANALYSIS, Risk analysis, Gap analysis.

SDLC, RUP, SEI-CMM, Six sigma, SWOT, Cost benefit analysis, Risk analysis, Gap analysis.

Basically version control is a PART of configuration management. MAINLY it handles when the previous document changes. Where as configuration management handles the INDIVIDUAL COMPONENT.

Basically version control is a part of configuration management. Mainly it handles when the previous document changes. Where as configuration management handles the individual component.

When we CREATED DIFFERENT modules of REQUIREMENTS for different functions, and finally collected all together and made a SINGLE requirement document, we used requisite PRO to do this. And we used rational rose to create the business model as a visual representation.

When we created different modules of requirements for different functions, and finally collected all together and made a single requirement document, we used requisite pro to do this. And we used rational rose to create the business model as a visual representation.

Entity relationship diagram, data FLOW diagram, use case diagram, class diagram, activity diagram, state chart diagram, SEQUENCE diagram, collaboration diagram, component diagrams, deployment diagrams etc..
Use case diagram: basically explains the BUSINESS environment. Series of all related actions PERFORMED by actor.
Activity diagram: Used in the early stage of analysis and designing level. It describes each individual component.
Sequence diagram: It tells the objects INTERACTIONS with each other’s arranged in time sequence.

Entity relationship diagram, data flow diagram, use case diagram, class diagram, activity diagram, state chart diagram, sequence diagram, collaboration diagram, component diagrams, deployment diagrams etc..
Use case diagram: basically explains the business environment. Series of all related actions performed by actor.
Activity diagram: Used in the early stage of analysis and designing level. It describes each individual component.
Sequence diagram: It tells the objects interactions with each other’s arranged in time sequence.

UML is BASICALLY Unified Modeling Language. This is the standard language used in the system to understand, DOCUMENT, CONSTRUCT different COMPONENTS in the system.

UML is basically Unified Modeling Language. This is the standard language used in the system to understand, document, construct different components in the system.

The REQUIREMENT should be GOOD, clear, understandable, and consistent and should be EASILY VERIFIABLE.

The requirement should be good, clear, understandable, and consistent and should be easily verifiable.

Am aware of TWO types of diagrams namely the use case diagram and the collaboration diagram, the use case diagram has been discussed above and as a result I will only talk about the collaboration diagram here, these are diagrams put into being by modeling the objects of a given systems and then representing the prevalent associations between the objects in questions with the use of LINKS.

Am aware of two types of diagrams namely the use case diagram and the collaboration diagram, the use case diagram has been discussed above and as a result I will only talk about the collaboration diagram here, these are diagrams put into being by modeling the objects of a given systems and then representing the prevalent associations between the objects in questions with the use of links.

This is the diagram used in a BUSINESS system to show the workflow involved, activities happening as well as the completed actions. In a company comprising of several departments e.g. the medical department, accounting department, and EVEN the human resource department, usually each department has its own peculiar privileges to the system, for INSTANCE the medical department can only be allowed to access the screens related to their activities such as medical records while the human resource department will be allowed to view only the screens which are relevant to them too, THUS these activity diagrams assist in showing the relationship between particular activities with their relevant and related departments so that during coding, the coders may refer to them to implement the discrepancies accordingly. Designers too can be guided by these activity diagrams.

This is the diagram used in a business system to show the workflow involved, activities happening as well as the completed actions. In a company comprising of several departments e.g. the medical department, accounting department, and even the human resource department, usually each department has its own peculiar privileges to the system, for instance the medical department can only be allowed to access the screens related to their activities such as medical records while the human resource department will be allowed to view only the screens which are relevant to them too, thus these activity diagrams assist in showing the relationship between particular activities with their relevant and related departments so that during coding, the coders may refer to them to implement the discrepancies accordingly. Designers too can be guided by these activity diagrams.

The term UML is an abbreviation of the term Unified Modeling Language which is the standard language used in construction of as well as visualization and documentation of varied SYSTEM components. It has a COLLECTION of GRAPHICAL notation TECHNIQUES used in the development of ABSTRACT models for certain specific systems.

The term UML is an abbreviation of the term Unified Modeling Language which is the standard language used in construction of as well as visualization and documentation of varied system components. It has a collection of graphical notation techniques used in the development of abstract models for certain specific systems.

This is a MODEL used by SOFTWARE ENGINEERS to describe the business environment of a GIVEN project. It encompasses of a series of workflow that are pertained to a PARTICULAR actor.

This is a model used by software engineers to describe the business environment of a given project. It encompasses of a series of workflow that are pertained to a particular actor.

It is EASIER to interpret as it is graphical in nature and THUS all persons involved in the project development can UNDERSTAND it with EASE.

It is easier to interpret as it is graphical in nature and thus all persons involved in the project development can understand it with ease.

Black box testing is the type of testing WHEREBY the ENTIRE unit is tested as a whole without considering the contents or even how the inner components of the unit under test work, the tester’s only consideration is to enter a KNOWN input signal and check whether the output behavior is the one expected out of that unit GIVEN his input signal.

Black box testing is the type of testing whereby the entire unit is tested as a whole without considering the contents or even how the inner components of the unit under test work, the tester’s only consideration is to enter a known input signal and check whether the output behavior is the one expected out of that unit given his input signal.

By definition, the term data mapping is the process by which a system developer creates data element mappings that relates two models of data (databases) in order to assist in data INTEGRATION. This usually assists in the following MANNER:

• Data mediation or transformation between the source and the destination of data.
• Assisting in data lineage analysis by identifying the data relationships.
• Assists in data masking by DISCOVERING sensitive data.
• Assists in data de-identification process.
• Assists in consolidating multiple databases into one thus identification of REDUNDANT columns and advising the developers for consideration or even elimination.

By definition, the term data mapping is the process by which a system developer creates data element mappings that relates two models of data (databases) in order to assist in data integration. This usually assists in the following manner:

The term OOAD is an abbreviation of the phrase Object Oriented Analysis and Design. Contrary to the traditional programming, also called PROCEDURAL programming whereby the entire code of a given program is WRITTEN LINE by line, from scratch. There is a new more powerful approach to software development or simply programming referred to as the Object Technology where predefined objects pertaining to particular situations are pre-designed by experienced software ENGINEERS and then the programmers just call them into their code in ORDER to implement a given function in their code.

The term OOAD is an abbreviation of the phrase Object Oriented Analysis and Design. Contrary to the traditional programming, also called procedural programming whereby the entire code of a given program is written line by line, from scratch. There is a new more powerful approach to software development or simply programming referred to as the Object Technology where predefined objects pertaining to particular situations are pre-designed by experienced software engineers and then the programmers just call them into their code in order to implement a given function in their code.

The term SOFTWARE methodology, software development methodology and software process mean ALMOST the same thing in computer software or system development, i.e. the activities carried out by computer system engineers or computer software engineers in an attempt to procure PARTICULAR computer software that servers a certain function or purpose. This INCLUDES the framework adopted, structure, plan as well as the control of the resources engaged in the software or system development process.

The term software methodology, software development methodology and software process mean almost the same thing in computer software or system development, i.e. the activities carried out by computer system engineers or computer software engineers in an attempt to procure particular computer software that servers a certain function or purpose. This includes the framework adopted, structure, plan as well as the control of the resources engaged in the software or system development process.

For a documentation system to be considered good, the following factors should be prevalent in it: It should be made in such a way that it can accommodate future changes, including version changes, bearing system security features such as providing access only to the ALLOWED users, i.e. have good authentication features. In general, one should TAKE in DATA as well as information security measures in place, putting in mind that the documentation should ALSO be able to bend to the CHANGING needs of its users as well as the market conditions.

For a documentation system to be considered good, the following factors should be prevalent in it: It should be made in such a way that it can accommodate future changes, including version changes, bearing system security features such as providing access only to the allowed users, i.e. have good authentication features. In general, one should take in data as well as information security measures in place, putting in mind that the documentation should also be able to bend to the changing needs of its users as well as the market conditions.

By definition, version control is essentially a subset of CONFIGURATION management. It is usually concerned with the HANDLING changes ARISING in previous DOCUMENTS as opposed to configuration management which essentially handles the INDIVIDUAL components.

By definition, version control is essentially a subset of configuration management. It is usually concerned with the handling changes arising in previous documents as opposed to configuration management which essentially handles the individual components.

First week in this CASE is always advisable to do a due diligence of the AMOUNT of work, expectations, existing process, time lines with the constraints surrounding. One of major constraints in this case would include lack of tools.
Depending on the project timelines, complexity and VOLUME of the project present your recommendations for tools to be USED and the estimated budget allocation required. Document the comparison of PRODUCTIVITY and flexibility with and without tools used. This should help the project sponsors to take a call on going for tools.

First week in this case is always advisable to do a due diligence of the amount of work, expectations, existing process, time lines with the constraints surrounding. One of major constraints in this case would include lack of tools.
Depending on the project timelines, complexity and volume of the project present your recommendations for tools to be used and the estimated budget allocation required. Document the comparison of productivity and flexibility with and without tools used. This should help the project sponsors to take a call on going for tools.

If this happens then explain the purpose of your talk (e.g. capture requirements) and why it’s important to talk to users directly (e.g. the quality of requirements will be better if they comes directly from the users mouth). Explain them that it will be a high risk to the project if analyst can't talk to the users directly. Client can give access to indirect (surrogate) users but explain that the quality of requirements will be not good. Hopefully your client will AGREE by now otherwise FLAG it as a HIGHER risk in Business Requirement Document and HIGHLIGHT during your meeting with your PM and Project Sponsors. Now, it’s your PM or project sponsors duty to PROVIDE you access to those direct users. If they can't than you are safe anyways.

If this happens then explain the purpose of your talk (e.g. capture requirements) and why it’s important to talk to users directly (e.g. the quality of requirements will be better if they comes directly from the users mouth). Explain them that it will be a high risk to the project if analyst can't talk to the users directly. Client can give access to indirect (surrogate) users but explain that the quality of requirements will be not good. Hopefully your client will agree by now otherwise flag it as a higher risk in Business Requirement Document and highlight during your meeting with your PM and Project Sponsors. Now, it’s your PM or project sponsors duty to provide you access to those direct users. If they can't than you are safe anyways.

A use case is written from a "user" perspective describing the interaction of a piece of software between the user and the software. These are written in common language typically from the business or user point of view and in enough detail for the developer to CREATE a piece of software. Typically written in a MS Word TYPE tool. Use cases capture the functional REQUIREMENTS of the system. It describes the expected interaction the user will experience, in detail. The audience is the business, for signoff, and technology for development.

A use case is written from a "user" perspective describing the interaction of a piece of software between the user and the software. These are written in common language typically from the business or user point of view and in enough detail for the developer to create a piece of software. Typically written in a MS Word type tool. Use cases capture the functional requirements of the system. It describes the expected interaction the user will experience, in detail. The audience is the business, for signoff, and technology for development.

Basic flow for USE CASE can be identified from Business REQUIREMENT Documents or Functional Requirement Documents as these use cases are PREPARED on the BASIS of these requirement.

Basic flow for use case can be identified from Business Requirement Documents or Functional Requirement Documents as these use cases are prepared on the basis of these requirement.

Functional REQUIREMENTS are DOCUMENTED in the SRS document / USE CASE Document. NON Functional requirements are listed in the SRS document.

Functional Requirements are documented in the SRS document / Use Case Document. Non Functional requirements are listed in the SRS document.

• Business Analyst role is not entirely different than Project manager role but Project Manager is bigger role than business Analyst.
• Project manager is responsible for all the deliverables like

1. SCHEDULES/ timelines
2. resources management
3. risk management
4. Daily/weekly status report to project stack HOLDERS etc.

• where as business analyst sometimes report to project manager or may report to business manager.
• Business Analyst deals with business users to gather requirements prepare RD, FD and coordinate with development team for development and then do the testing involve with users in testing get the SIGN off and MOVE component to live.

The availability of the people (e.g. managers, supervisors and the end users) the BA WANTS to talk with for gathering business requirements. These people have regular daily WORKS to do and their time to SPEND in the gathering sometimes hard to SCHEDULE and for this reason gathering business requirements is delay.

The availability of the people (e.g. managers, supervisors and the end users) the BA wants to talk with for gathering business requirements. These people have regular daily works to do and their time to spend in the gathering sometimes hard to schedule and for this reason gathering business requirements is delay.

A BUSINESS plan is evaluated by CHECKING the contents of the plan such as if the plan have BASED on the RESOURCE planning and envisioning phase of the project.

A business plan is evaluated by checking the contents of the plan such as if the plan have based on the resource planning and envisioning phase of the project.

The Unified Modeling Language (UML) is a standard language for SPECIFYING, visualizing, constructing, and DOCUMENTING the artifacts of software systems, as well as for BUSINESS modeling and other non-software systems. The UML represents a collection of best ENGINEERING practices that have proven successful in the modeling of large and complex systems.

The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, as well as for business modeling and other non-software systems. The UML represents a collection of best engineering practices that have proven successful in the modeling of large and complex systems.

Business process improvement IMPLIES changing a step SUB step or any PART of the process i.e. process is not completely changed In BPR we actually study the business and find out what is the best way I can carry out the process and change the WHOLE way the process runs(business process redesign).

Business process improvement implies changing a step sub step or any part of the process i.e. process is not completely changed In BPR we actually study the business and find out what is the best way I can carry out the process and change the whole way the process runs(business process redesign).