You are right place, If you are looking for Business analyst interview questions and answers, get more confidence to crack interview by reading this questions and answers we will update more and more latest questions for you…
A requirement is the capability possessed by a solution to solve a problem or achieve an objective.
A business analyst is a liaison between different stakeholders in an organization. He acts as a bridge, a connector and helps the complete project team work as a tightly integrated unit. Since stakeholders belong to different domains (e.g. finance, business, marketing) it’s very important for a business analyst to be able to sort and balance the needs of these stakeholders while fulfilling the business objectives at the same time.
The elicitation strategy depends upon the type of the project. One can take advantage of direct collaboration with client and have facilitated workshops, interviews and observe the end users. In conjunction, we can use techniques that provide us with more precise information like prototype and scenario building.
The following are the best practices that are followed to write a clear and well documented use
case: 1. Capture both functional and non-functional requirements in a use case. 2. Include use case diagrams along with the use case. 3. Include the UI details/notes in the use case.
Scope creep, also known as requirement creep is a term that denotes uncontrolled changes/deviation in the project’s scope without an increase in the other resources (schedule, budget) of the project. Scope creep is a risk to the project and is usually caused by poor project management, improper documentation of project’s requirements and poor communication between the project’s stakeholders.
Scope creep is a hindrance to the project’s success and could be avoided by:
A business analyst must possess fundamental skills such as elicitation skills, problem solving skills, communication and management skills. Alongside, he must have knowledge of IT skills,
Stakeholders sometimes could be difficult to deal with but we could overcome this situation by:
We consider the requirements are complete when:
All the requirements which pass the above four criteria, they are considered to be as formal and final. These requirements re then documented and become a part of the project scope.
Simply, flow chart explains the flow of a process through symbols and text. It is important because it:
MS Visio, Enterprise Architect, Rational Requisite Pro, MS PowerPoint, MS Word, MS Excel, DOORS.
Get more questions and answers from onlineitguru trainers after completion of Business analyst course
12. How do you manage rapidly changing requirements?
Too many changes can be detrimental to the success of the project and hence requirements should be managed carefully. We could do so by following a strict ‘Change control’ plan, according to which:
Nonfunctional requirements or ‘qualities’ of a system are the requirements that are used to judge the operation of a system. These requirements define how a system is supposed to ‘be’. E.g.: Throughput, usability, reliability, scalability and security
Each project has got different and unique needs and thus the SDLC phases should be chosen based on the specific needs of the project. Waterfall model follows a structured approach with each phase having
specific deliverable. But, it has little flexibility and adjusting scope later is very difficult. In spiral model, estimates of project constraints become more realistic as the work progresses and it involves the developers early in the project. But, it takes more time and high cost to reach the final product.
A misuse case is inverse of a use case and documents the scenarios that should not happen within the system. The actions depicted in a misuse case can be performed by any person or entity in order to harm the system. Thus, misuse case are usually used in the field of IT security and data protection.
Configuration management is everything that you need to manage in terms of a project. This includes software, hardware, tests, documentation, release management, and more. Configuration management includes, but is not limited to, version control. Version control is saving files and keeping different versions of them, so you can see the change over time.
The high level use case usually refers to the entire business process whereas when it is divided into smaller units, the outcome or the sub units are what are then referred to as the low level use case.
This is the abbreviation of the term System Design Document; it acts as the mediator between business users and the system developers so as the system developers may understand the business requirements of the system they are developing in order to know where to put emphasis and end up with a quality and objective based system.
Pareto analysis is a technique which is used to identify the issue that are causing the most number of defects. The issues and their respective defects are plotted in a bar graph and the issue which is causing the highest amount of defect is addressed first. Pareto analysis is considered as a creative way of looking at causes of problems as it organize data into logical segments for better analysis, comprehension and communication.
BPMN stands for Business Process Model and Notation. It’s a global standard for graphically representing business process in the form of a diagram. BPMN contains a set of graphic elements which
are used by business users and developers to create activity flows and processes. BPMN’s four basic element categories are:
Activity is a generic term that is used to denote a process/sub process and is a collection of a task or group of tasks whereas a task is a self-contained piece of work.
Joint Application Development (JAD) consists of a structured workshops session between end user/client, project manager, business analyst, technical team and subject matter experts (SME) to facilitate the design and development of the product. Applications developed through JAD development approach has higher customer satisfaction and less number of errors as the end user is directly involved in the development process.
Force-field analysis aids in making decisions by identifying the factors for and against a proposed change to the system. The ‘for’ and ‘against’ factors are tabulated and are then analyzed, discussed and evaluated for their impact on the change.
A test case is a document which contains listing of all the possible scenarios that could happen based on a respective use case. Thus, every test case is developed with a use case as a base. A test case contains main flow, positive scenarios, negative scenarios and scenarios covering non-functional requirements also. A single use case could contain many test cases and these cases are clubbed to make a test script. Test Cases are written in a testing tool like Test Director, but they can be also be written in MS Word. The audience for a test case are the QA testers.
The aim of testing is to verify and validate the quality of a developed functionality according to the project requirements. A BA does various types of testing, which are:
Black box testing: This is a functional testing where a BA validates that the output generated by the system is as per the requirements/use case
Unit Testing: A BA does unit testing on a developer’s machine to make sure the requested functionality is being achieved.
Integration Testing: This type of testing is done when more than one piece of code are integrated to realize a functionality. A BA does integration testing to make sure than the system is performing as expected after different modules are integrated.
Functional Testing: A BA is expected to conduct functional testing to validate that the system is achieving the functionality specified in the use case/functional requirement specification document (FRS).
Acceptance Testing: A BA along with the client, does the acceptance testing to validate that the system is performing as per the business requirements and the product’s acceptance criteria.
Regression Testing: Regression testing is done after a modification has been made to the existing system. Its aim is to make sure that all the system functionalities are working as expected.
Beta Testing: A BA along with the testing team, does the beta testing and it is done on a preproduction version of the product. This testing is done to make sure that the functional and nonfunctional requirements of the system are met.
SaaS is Short for Software as a Service and it is a software delivery model under which a software and its associated services are remotely accessed by an end user as a web based service. E.g. Facebook, which is deployed over internet and the users access its services by an internet enabled device.
Some of the problems faced by a BA during requirements gathering are:
The golden rule to measure the quality of a good requirement is the ‘SMART’ rule. According to this rule a requirement should be:
Specific: The requirement should be specific so that it could be properly documented
Measurable: We should be able to measure the success criteria of the requirement by different parameters
Attainable: The requirement should be possible to attain with the given resources
Relevant: The requirement should be in line with the project’s business case
Timely: The requirement should be posed in time i.e. early in the project life cycle.
There are a couple of different diagrams about which a BA should have concrete knowledge. They are:
A business analyst is expected to visualize the ‘big picture’ and his responsibilities extends towards both the business side as well as the technology side of the project. The major responsibilities that he is expected to fulfill are:
The major business analysis techniques used by a BA are: interview, SWOT analysis, facilitated workshop, brainstorming, observation, prototyping and root cause analysis.
The 100-point method is a prioritization method that can be used to prioritize items in a group environment. Each person within the group is given 100 points which they can distribute as votes across the available items.
8 Omega is a business change framework to improve the existing business processes. Based on its name, this framework consists of 8 lifecycle phases namely;
Also, it address 4 key perspectives of business i.e. Strategy, People, Process and Technology.
FMEA stands for ‘Failure Mode and Effects Analysis’ and it is used for failure analysis, risk analysis and quality engineering. It involves reviewing components, systems and subsystems on parameters like functional, design and process to identify failure models. The resulting data is then used for risk management and mitigation.
A use case is a methodology used in requirement analysis to identify, organize and document the requirements. Following are the main characteristics of a use case:
Alternate flow are the alternative actions that can be performed apart for the basic flow and might be considered as an optional flow whereas Exception flow is the path traversed in case of the error or an exception being thrown. For e.g. on a logic page the ‘Forgot password’ is the alternate flow and system showing ‘404 error’ when correct username and password are entered is exception flow.
Trigger is an action which will invoke a specific flow which would otherwise have been inactive.
Use Case Points are normalized unit of measurement used to size and estimate the cost of work that is to be done on a system.
In the context of use case modeling, sometimes two or more use cases share a common structure and behaviors. When this happens, we create a new use case that describes the shared parts of its parent use cases. Similarly, actor generalization is the relationship between two actors in a use case where the child actor inherits the properties of a parent actor.
Unit testing is the type of testing which is done at the developer’s desk and if a BA conducts unit testing he is able to find a defect before it gets integrated with other codes. This way, a bug gets identified early and is usually fixed in less duration.
Assumptions are scenarios that are considered to be as facts while a product is being designed/developed and constraints are restrictions that are imposed and have to be mandatorily followed.
Kano analysis is a quality measurement process aimed at categorizing and prioritizing the customer requirements in an effort to increase the customer’s satisfaction.
RACI matrix is a type of responsibility assignment matrix used to assign roles and responsibilities within the project team. The acronyms stands for Responsible, Accountable, Consulted and Informed.
44.What is rtm ? Y
ou can always tell that you are aware of it but it not used in your current organization. explain the other ways you use to keep track of the product development.
45.What is a data flow diagram?
you can tell that in your organization you only use use case and activity diagrams and they are also effective modeling tools.
46.What is the difference between user manual and training manual?
you can say you only prepare user manual.
Payroll system scenario is given.
48) What is your role in UAT?
A) Preparing Test Cases, End-User Manuals, KYC and FAQ’s. In UAT, we have to give a clear clarity on the Application to customer.
49) You are reporting to whom (Sr.BA/PM)?
A) Reporting to Sr. BA (Otherwise, we can face more difficult questions)
50) How to Interact with Clients (Directly, skype, IM, Mails)?
A) Depending on the project. Sometimes Directly, mails or telephone. Most of the time used IM (communicator) for getting clarification on Requirements.
51) How to do Stakeholder Analysis?
A) While doing Stakeholder Analysis, we need to consider two factors mainly.
(i) Stakeholders interest on the Project (II) Power/Influence of the Stakeholder. *Every interested stakeholder will not play a role in the project. Ex: Peon.
52) Before Getting SOW from Client, As a BA prepared some documents what are they?
A) Company to company document names changed. i said, Detailed Document of the Project. it contains, main theme of the project and functionality details like (Blue print) of Project.
53) BA can prepare test cases in sometimes only, Rest of test cases will be prepared by Test engineers, how did you check out those cases?
A) Test Review Document.
54) Say one Test case from your project?
A) Depends on what you kept project in your profile.
55) Client gives a No.of change requirements, Every two days Client change requirements, In this Scenario which SDLC model you can choose & Why? other than RAD?
A) I answered Agile Methodology is best SDLC for change of requirements. because of Agile methodology always welcoming the Change of requests even code delay. very good responding on CR’s.
56) Draw some System Flow Diagram Symbols?
A) we should practice the symbols. I drawn three symbols. He asked Draw symbol for Output as a Document?
57) What is Challenges you faced as a BA?
A) It is Common Question to all, as well as answer is also same Change of Requirement. i explained, when change of requirement happen what i was done in last project.
58) As a BA, you Skip One requirement, it is not any influence on Project. project is succeed. But your manager found that skip step. How did you conveyance your manager?
A) This was not happen till now in my career, because of documented every requirement clearly with clarity. as well as everyday i follow up my tasks and developers tasks., there is no chance to miss out or skip any requirement. but, he has not satisfied. (Why he asked this Question, when i was tell my strengths, i have self- motivated and Self-confidence person), so how did you motivated in this scenario.
59) At what year KYC starts?
A) A)2004, RBI rules.
60) Once explain my project in interview, he asked i want to implement the same application in my mobile, can you explain what is the proposed solution?
A) Depends on Your projects.
61) In Waterfall model, first time we gather all requirements from the client. Are you accepting, Client ask any change of requirement in the middle of the project?
A) Yes, we have to accept the request, because we are work for client. or else, PM and Sr.BA’ s will convert that requirements will New project.
62)Client gives a No. of change requirements, Every two days Client change requirements, In this Scenario which SDLC model you can choose & Why? other than RAD?
A) I answered Agile Methodology is best SDLC for change of requirements. because of Agile methodology always welcoming the Change of requests even code delay. very good responding on CR’s.
63)What is business analysis? One should not restrict the BA role to only being a link between Non-It and IT or only for development projects. BA is someone who is able to bring in improvements, changes(technology, process, people etc.) in an efficient manner. So a BA could be part of the marketing team who helps the marketing team in providing estimates/high level solutions for a said project which is under the process of procurement. Or he could be someone involved during the Requirement gathering/analysis once the project is initiated. Or he could be someone who brings profit to the company by performing process improvement activities ROIs at process level. Last but not the least BAs could be domain specific as well.
64)What is the career path for a Business Analyst? A Business Analyst in the IT field has many varied directions among which to choose a career path. The most direct would lead to a Lead Business Analyst position and then Project Manager whereby the incumbent manages projects through the entire lifecycle from inception to post-implementation
including the management of business analysts system analysts quality assurance analysts and most likely development project managers or team leads. That path would then lead to Program Management perhaps PMO management or Product Manager and on to Directorship. In addition a good Business Analyst may find they are heading toward a Customer Relationship Manager position whereby they become the primary IT interface to a given Business Unit (BU). This role most often leads to a position within the BU as a Manager of Applications or a Process Management role. Process Management opens many jobs including process re-engineering quality program development and large scale or enterprise process management programs such as ITIL or Six Sigma initiatives. These roles will continue to proliferate as companies realize the benefits of having a SME in process and quality. And still many Business Analysts find their understanding of business process entirely portable into purely system related positions in the business side that are only peripherally related to IT. These of course may lead to quantitative roles manager roles or operational roles such as supply chain logistics etc. Of central importance to a successful Business Analyst is the interest in speaking to people. Face to face verbal communication is paramount to support other tools such as surveys and diagrams. Incumbents must be interested in understanding not only the pieces that comprise a system but the people that comprise it and the realities that embrace the system. Briefly the Business Analyst must understand and not judge the what should be and the what is
65)How do you resolve issues?
I would rather focus on issues and the facts related. Origin of issue, severity of the issue, implications and possibles 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. What are the problems solved by business analysis? As a BA the most critical part is in gathering requirements (we should understand them very well from a Business User /stake holder point of view!!!) Reason: There might be a chance for the whole project to go in the wrong path due to wrong understanding of the Business users/ Stake holders’ needs and the gathered requirements created for the work following that step… i.e. going from A to C instead of going from A to B. Notes: (Business Users: are the individuals who work in organizations in different departments like Logistics accounting finance Inventory) in the company who wanted the software in Place for them to work on to help the Customers. Stake Holders: Someone who is related to the Project? 2 types of People are involved: Direct Stake holders: business end users customers developers tech team. Indirect stake holders: management etc. The Project Manager responsibility (usually) identifies the stakeholders determine their needs and expectations and more important must manage and take their help for the project success. (You should Understand them well to provide them with right service for the right success of the project)… SME’s: are the Subject Matter Experts who know about that project and have in-depth knowledge about that software application used and that particular business domain knowledge like Finance (terms and permutations etc.) Accounting (Business Planning Ledger maintaining Forecasting) Mortgage (Local banking rules Knowledge about compliancy of applications forms/ applications that needs the authorizations of the local Government bodies or counties Underwriting conditions (How flexible the Loan lending organizations at the individuals credit check or History) So The SME’s help the Project Manager or BA to help them understand about the necessities or needs of the Business Users or Stake holders like/interests- (How the Project help save time for the transactions or? how much secure/security is needed the application wise or profitable over long run) and SME’s explain How the Stakeholders or Business Users want the application to be or appear to be for the Customers or Business Users).
66) What is the difference between data model and an entity relationship diagram?
A data model is a model which shows how data is stored and used for e.g. a normal database It has 3 main parts1)Structural part:- how data is structured2)Integrity part:- Rules governing structure3)Manipulation part:- operators used to select,update,querry that data,eg select,update,delete commands in sqlTo further add Data Modeling is when we add this theory to Live instance. ENTERPRISE DATA MODEL(ENTERPRISE RELATIONSHIP MODELING) :- This can be called as an conceptual model or semantic model The sub parts of an ERM are1)Entity:- It is an objected employees,computer2) Relationship:- It captures how two or more entities are related to each other3)Attributes:- Every entity has its own sets of attributes (e.g. PAN no in India for each employee or SSN in US)To clarify the point look at eg A employee is an entity belonging to entity sets(All employees) which has a relationship with department, and attributes is emp code
67)Who uses the output produced by business analyst?
The output will be used by the Both IT and Non-It People, as IT people use this document as key for the building of the application and Non – It people use those document where they can see prototype of their application.
68)What is the educational qualification required for a business analyst?
There is no specific qualification for a business analyst. Well, if you are a management graduate it is an added advantage since you have they have better communication skills. One important thing a BA needs to have is domain knowledge or business knowledge. Unless he/she understands the client’s business process thoroughly they cannot draft the requirements properly.
69)Mention some of the important points a business analyst must take care while preparing business plan?
While Creating Business Document, Make sure you start from small problems. Don’t jump to big problems right way. Keep the Business sponsors and IT folks in the loop. Make sure your document clearly state Exceptions, Assumptions and Limitations. Sometime you need to keep in mind the legal issues. Business document should be well written for usability and for future projects.
70)Why is business analyst position vital in an organization?
The position is important because a BA is a people’s person when it comes to the users and an IT person when it comes to the developers. He can communicate with the users in jargon that they are comfortable with and is able to understand them in order to collect solid business requirements. Simultaneously he can effectively communicate these requirements and support them with documentation for a developers benefit.
71)Why excellent communication skill is essential for a business analyst?
A BA is one who sits with the client understands it and then tells the IT people what needs to be done hence BA needs to have excellent communication skills What are the industry and professional standards followed by business analyst? Industry standards that have been set for the BAs to follow are OOAD principles and Unified Modeling Language (UML). This is a common language used by business analysts all around the world to draft the functional requirements.
72)What are the quality procedures followed normally by a business analyst?
For quality there is no specific mark of course Six sigma and ITIL (Information technology infrastructural library United kingdom) are certain quality standard establishing organizations and methods. But As a normal the following should be followed: The quality of communication while gathering requirement should be excellent and outstanding. Sometimes users are just looking for functionality in system and they are not even able to say that what exactly will be their dream functionality which will be most convenient to them. In that case BA should explore them and figure out the exactly demanded requirements.
73)How is requirement analysis done by business analyst?
Requirement session is usually done through JAD session. Business Folks and Major sponsors are always there along with some technical folks. Business analyst then goes through each requirement and asks for the feedback. If Business Sponsors and Technical Folks think that all the requirements are according to the business and won’t be a barrier to existing system. They get the official signoff on Business Requirement document. IT manager and Business manager both do the sign off on that business requirement document.
74)Does the business analyst interact with clients directly? If so state the reason for the same?
It depends on the project to project it is not always the same that we do interact with the clients directly, some time there will be a team whom might be interacting with the client and gives you the requirement and if have questions either we do talk with that team or our manager.
75)Mention the difference between business process improvement and business process reengineering?
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)
76)How is business plan evaluated?
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.
77)What are the problems Business Analyst could face during gathering Business requirements
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.
78)What can a Business Analyst do differently than project or program manager (Design Architect) with respect to successfully getting the project implementation done?
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 deliverable like
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 environment.
79)Where would you document Functional and Non Functional Requirements (i.e. deliverable)?
Functional Requirements are documented in the SRS document / Use Case Document. Non Functional requirements are listed in the SRS document.
80)How do you identify the basic flow? What would you do if someone was struggling to determine the basic flow for a use case?
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.
81)What is the relationship between use case and test case?
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 Test Case is written using the use cases for a source. It takes a use case to a deeper level so that software testers can exercise every possible scenario that could occur, negative and positive scenarios. One Use Case can turn into 10 test cases. 10 test cases make up a test script. Typically Test Cases will be written in a testing tool like Test Director, but also can be written in MS Word. The audience is QA testers.
82) What would you do if the client says that you and the other analysts cannot directly talk to the users?
If this happens then explain the purpose of your talk (e.g. capture requirements) and why its 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.
83)We are going to a client on Monday to help them with their requirements. We have just received a business case from the client, and they have no tools in place. What would we do the first week?
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.
84)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. Version control and configuration management are terms used widely in the business industry, write short notes about the terms. 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.
85)Good documentation management systems are highly recommended in system development; briefly describe the factors that contribute to a good documentation management system.
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.
86)State the different software methodologies.
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. There are so many software methodologies and the choice as to which one to adopt is usually dependant on so many other factors such as the purpose of the given software, the prevailing conditions regarding the software development environment and the will of the company or the client procuring or intending to use the final software as some clients even look into the software or system engineers’ methodology to as one of the factors determining whether to contract him or not. Regarding the purpose of the software, let’s look at the following, example is a situation of a safety critical system such as an aircraft navigation system and a business system, one would find that in a business system, one can have its prototype done and users start using it as they identify its weaknesses and tell the engineers to rectify whereas in an aircraft navigation system, no weakness would be allowed at all for it can cause huge loss of property and life thus all the possible identifiable weaknesses are eliminated first before that system comes into operation.
Much stories and arguments apart, the following are the available software methodologies: i) SLDC- Software Development Life Cycle, also understood as System Development Life Cycle which encompasses activities such as Analysis, Design, Implementation, Testing, Inauguration and Maintenance in that order and then back to Analysis, note that it is a cycle hence once we get to the last stage, i.e. the maintenance we still go back to the analysis stage and move along to the maintenance once more iteratively ii) RUP – The Rational Unified Process, which when looked into intuitively is an iterative software development process framework that was created by the Rational Software Corporation in the US which is a division of the IBM (International Business Machine). However, this process is usually not considered as a single prescriptive framework yet as an adaptable process which can be tailored by the development team or organization selectively in order to end up with their respective results depending on the needs prevailing either on the client’s side, the industry standards or even the development constraints which involve time, scope as well as the budget, Intuitively, this process has characteristics
overlapping with other development processes and methodology as will be seen when considering the other methodologies below. iii) The iterative process iv) The waterfall model v) The agile software development methodology vi) The XP (Extreme programming) vii) The ISO 9000 methodology – provided by the International Standards Organization viii) The ISO 15504 model – also provided by the International Standards organization ix) The Capability Maturing Model Integration (CMMI) which replaced the former Capability Maturing Model (CMM) x) The Six Sigma methodology xi) The Test Driven Development (TDD)
87)Describe the abbreviation OOAD as used in Object Oriented Programming.
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. Just the way experienced civil engineers design building blocks for particular situations in a particular house so that the inexperienced mason just lays them appropriately in order to end up with a nice house is the way experienced software engineers make these objects. This helps even novice programmers to use the objects to build nice computer software or a program. It is the analysis and design of these objects with intention to make good software that is referred to as Object Oriented Analysis and Design, the OOAD. Programming languages that use the Object Technology include C++, JAVA, and the PHP among others.
88) Describe the meaning of the term data mapping.
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: i) Data mediation or transformation between the source and the destination of data ii) Assisting in data lineage analysis by identifying the data relationships iii) Assists in data masking by discovering sensitive data iv) Assists in data de-identification process v) Assists in consolidating multiple databases into one thus identification of redundant columns and advising the developers for consideration or even elimination.
89) Briefly explain the use case model.
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.
90) Describe your understanding regarding the exception flow in use case.
This is generally unpredictable situation that may lead to undesired result under normal circumstance in a system; several methodologies called exception handlers are available to help control such situation Describe the meaning of the following words as used in the use case scenario:
91) What are the documents related to the use case?
There are two documents related, namely the FRD (Functional Requirement Document) and the SSD (System Design Document) or the TRS (Technical Requirement Specifications).
92) Describe your understanding regarding logical data model.
It is the data model, which is not actually physical and describes how data is physically stored in the given database.
93) Describe your understanding regarding high level and low level use cases.
The high level use case usually refers to the entire business process whereas when it is divided into smaller units, the outcome or the sub units are what are then referred to as the low level use case
94) Describe your understanding regarding the SDD.
This is the abbreviation of the term System Design Document; it acts as the mediator between business users and the system developers so as the system developers may understand the business requirements of the system they are developing in order to know where to put emphasis and end up with a quality and objective based system.
95)Describe your understanding regarding the following terms
i) URS ii) FS The URS is the User Requirement Specification whilst the FS is the Functional Specification; traceability matrix is usually used to keep track of these requirements. TEST DIRECTOR can be used to do the traceability of the given requirements during the testing phase.
96)How is use case prepared?
It is prepared using drawing application software such as the Microsoft Visio and the also the Rational rose.
97)Describe how you would participate in testing as a BA (Business Analyst).
As a Business Analyst, I would participate by reviewing the test cases to ensure that all the stipulated requirements have been met by the system in question.
98) describe the main qualities of a good requirement.
There are several qualities regarding a good requirement but the most outstanding ones include the: Clarity – the requirement should be clear enough to be understood by its users. Understandable – the requirements should be put in a manner easy to understand by users of all levels. Consistent – the requirement should be such that it doesn’t contradict itself, it is important noting that during system development, all users need to be consulted, including the managers as well as the junior staff, one would find that the managers would like a wider control of the system so as to monitor the junior staff to the date whereas the junior staff are objecting these view, hence a contradiction. When this issue is not considered carefully, usually through consultation or negotiation either the managers or
junior staff may resent the system thus by this, once the users resent the system, obviously it will not be exploited to the maximum thus lowering the benefits the organization derives from it thus consistency must always be considered in the system development requirements. Verifiable – The requirements of a given system should always be verifiable as in they should be put in a manner that can be checked across in future so as one can clearly identify whether the particular requirement has been met or not, it is usually advised that the requirements are put in a manner that during verification, the answer is either true or false and nothing vague as it is during this stage that legal action can be taken by the either the contractor or client if at all the answer is no and always with the law, matters of doubt are generally not recommended.
99)Explain where you would use the rational rose and the requisite pro.
In a situation whereby different modules of a given requirements have been created for varied functions, then collected together and made into a single document, the requisite pro is the one which comes in handy. The other one, the rational rose, is used to create the business model as a visual representation. It is helpful in creating high level and low level use cases, activity diagrams, state diagrams, collaboration diagrams, sequence diagrams etc.
100)What is mean by logical data model?
Data model tells clear details about the data and how the data is stored physically in a database.
101)What do u mean by high level & low level use case?
A broad view of a business process is called a high level use case. And if we divide the big view into different small sub use cases, then it is called low level use case.
102)What do you know about SDD ?
It is also called system design document. My role as a BA is just a mediator or a middle layer between business users and developers and we make developers to understand the business requirements.
103)What do understand by URS & FS?
User requirement specifications and Functional specifications. To keep track of these requirements, we generally use Traceability matrix. By using Test director we can do traceability of requirements n testing phase.
104)How do you prepare use cases?
BY using MS Visio and Rational rose.
105)How do you participate in testing as a BA?
I participate mainly in reviewing the test cases to see if all the requirements have been met. What is the main quality of a good requirement? The requirement should be good, clear, understandable, and consistent and should be easily verifiable.
106)What are different diagrams to be known by a BA?
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 others arranged in time sequence. Very useful for developers and testers to understand the system better. Where did u use rational rose & requisite pro ? 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.
107) What do understand by version control & configuration management?
Basically version control is a part of configuration management. Mainly it handles when the previous document changes. Whereas configuration management handles the individual component.
108)What is meant by good documentation management system ?
Should allow to make any changes if required. Good security features. Should be able to change versions. Authorizations to only required people. (renditioning capability) Hide imp information from others. (redaction capable)
109)What are different software methodologies.?
SDLC, RUP, SEI-CMM, Six sigma, SWOT, Cost benefit analysis, Risk analysis, Gap analysis.
110)What is OOAD ?
Object oriented analysis and designing. Used in coding od object oriented languages like c++, Java, and SAP Badis etc.
111)What is UAT ?
User acceptance testing. If the UAT fails, BA did not understand the requirements properly.
112)What is bug?
Mainly used to see the performance issues and system hangs.
113)How do u measure the quality of a product?
We do it by seeing min bugs in the product according to standards maintained by company.
114)What is RAD ?
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.
115)What is ETL ?
Extraction Transformation and loading. Used mainly in data warehousing.
116)Types of testing?
Unit testing : by developer Black box testing : Functional and module level. Ad hoc testing : Random testing..no particular process. White box testing : Very detailed..into the code. Exploratory : ad hoc testing with some purpose/ goal. Front end : for web based applications. Back end : database level Regression : Testing again and again the same application. UAT : User acceptance testing Integration : testing the interaction of 2 or more than 2 modules at a time. System testing : Testing all the modules together.
117) Who is a Business Analyst and whats his role in an organization? These are the questions which we will be trying to answer here.
Business Analyst can be termed as an analyst who can delve deep into the business, understand the processes and make use of the knowledge in the betterment and success of the organization. But the term Business Analyst is used very generically in today’s professional environment. It can mean analyzing the system, business processes, requirement analysis, supporting the business or system functions, handling the sales or financial KPIs’ (Key Performance Indicators). But we will discuss the main responsibilities of a Business Analyst in a generic environment and it may happen that in some cases, its an amalgamation of roles or may be a subset of another role.
A Business Analyst is responsible for a host of processes and activities which are elaborated as follows:
a) At the Project Initiation process, its the responsibility of the Business Analyst to cover the high level scope and objectives of the project and establish communication channels
b) Understanding the business processes of a section or whole of the organization in a very clear cut manner so as to implement that knowledge in any required manner.
c) Clear Understanding and communication of Requirements is a very important aspect of a Business Analyst as it ensures that there is minimum gap between the expectations of the end users and the final deliverable from the technical team.
d) Analysis and Documentation should be very precise and clearly understandable so that starting from the end users or stakeholders to the developers can understand the underlying stated expectations in the requirement documents.
e) Solution assessment and validation is one of the main roles of a business analyst as it should be ensured that there are no gaps in the requirement process to the development stages.
f) Regular interactions by the business analyst with the developers and the module leads is essential as the knowledge transfer of the user expectations should be made clearly
g) The business analyst has a major role to play in the testing phase where he can actually take part in the systems testing phase and also provide support during the acceptance testing phase.
h) After the implementation of the software system, the business analyst also may need to handle the change management process if there are any new requirements or changes proposed.
The business analyst profile actually encompasses different roles like that of a process analyst, system analyst, project manager, application support, data analyst and tester. Gaining all round knowledge in all
these different role types will definitely give the Business Analyst an edge and will enable him to overview the project from all angles. Implementation of such responsibilities will help the Business Analyst become the interface between the users and the technical team. The organization should also be responsible for guiding the Business Analyst through his correct responsibilities for the better advancement of the individual as well as the company as a whole.
118)What is Business Analysis?
Business analysis can be described as the sequence of activities which are implemented in order to assess the business requirement needs and to fit the required solution so as to bring around the success of the organization and business. So, this sequence of task is normally performed by a “Business Analyst” or BA. Business Analysis can cater to different industries and so there are specialists created among business analysts. For e.g the business analysts who solely work on developing IT systems are the Technical Business Analysts, and the ones which cater to the functional parts of the business processes and their improvement or re- engineering are known as Process Analysts. Business Analysis is as such a vast subject and hence we will categorize it into subsets for better understanding of the various stages in any business process or software management. Business or Enterprise Level Analysis is the study and analysis of the business needs and the identification of initiatives to steer the organization on the path towards its strategic goals. This can include the finalization of the project scope, purpose and objective. This is the stage where the actual feasibility analysis occurs wherein the actual cost benefit analysis(CBA) of the project occurs and its evaluated whether the project should go ahead or not. Requirements elicitation and communication is vital to the basis of business analysis as it involves the actual collection of data from the stakeholders and ensuring that their requirements are clearly illustrated and conveyed to each and every member involved in the project. This is the level at which the actual requirement needs are captured using using various requirement methodologies like Zachman framework etc. Requirements analysis or engineering has been synonymous with Business Analysis always and represents the requirements planning, development and management processes.
At this stage the actual analysis of the requirements is done wherein the raw requirements are processed into functional objectives. The documentation of the requirements is done at this stage and may include the functional as well as the non-functional documents together with supplements like prototypes or UML diagrams. Finally,we come to Solution assessment and validation which ensures that the proposed solution design is in line with the requirements and there are no gaps in understanding which will trickle down the software development life cycle. At this stage, the requirements have taken form and have been converted to a solution design which can be developed and implemented as an application or software system. So its essential that analysis of the solution is done properly to ensure that the requirements are in synchronization with the solution. Business Analysis is not limited to this stage and can extend to the other parts of the project life cycle with significant contributions at the design, development, testing as well as implementation stage. Business Analysis, in summary, is the art of managing the requirements and the business needs and synchronizing them in line with the strategic objectives of the organization. In order to implement this management methodology, one needs to understand that Business Analysis forms the base of the successful implementation of any business process or software management event in an organization.
119)What is a Sequence Diagram?
Sequence diagrams are part of UML(Unified Modeling Language) diagrams and come under the interaction view as they depict the interactions between the entities and the transactions that are taking place with the trigger point and the end point clearly distinguished. The diagram shows the different
processes as vertical columns or lines and the messages or interactions between them is represented by arrows with the arrowhead pointing towards the receiver away from the sender. The name of the message is written above the messenger arrow line. It also includes the sequential order of events which will occur from the start to the end of the process(es). An important part of the sequence diagrams is that time passes from the top to the bottom. A message sent between two entities can be synchronous or asynchronous type. A synchronous type of message indicates that the sender will wait till the receiver has finished processing the message and then only proceed while in asynchronous message type, the sender will not wait for a response that the receiver has received and finished processing the message. A synchronous message is represented by a filled up arrowhead while an asynchronous message type is represented by an open arrowhead.
The sequence diagrams are helpful in detailing the flow of transactions between the entities such as actor, database, controller etc. Hence, for a sequence diagram to be prepared, its essential that the “use case diagram” would have been finalized, else it could mean rework might be required if the use case diagram is revised. Sequence diagrams can be used by business analysts in their functional documentation process or by solution architects or designers in their design models. But whether the sequence diagrams are created by the analyst or technical designer, whats important is that the diagram conveys the right message across to both the user groups and the development team.
Sequence Diagrams are a clear and simple way of depicting to the users, stakeholders and the technical team how the processing of messages will happen and an assessment of this will go a long way in clearing up any gaps or misunderstandings at the requirement level.
120)What is a Class Diagram?
For understanding class diagrams, we would need to understand UML first. So what is UML? UML is short for Unified Modeling Language and is a second generation notation for diagram-based object- oriented modeling. It was first developed by the company Rational Corp.(Booch). After that UML was advanced as an industry standard by the Object Management Group (OMG).
Class Diagrams are a part of the structural view of UML as they represent the static structure of a system. Class diagrams are basically used by Business Analysts or Solution Architects to design the static view of the classes involved. The diagrams depicts the grouping of classes which have the same attributes and behavior(operation or functions) and also it includes the interrelationships between two class. A class is an entity which is represented by a simple rectangle and is divided into three parts. At the top we have the Class Name, in the middle the list of the attributes specific to the class is included and lastly comes the class operation or function. If a simplified version of the class diagram is depicted then the last two compartments are not included or are left blank. The interrelationships are shown in the form of interconnecting lines between the classes and the dependencies are represented by symbols such as 1, 0, *(many), This part is similar to the data modeling diagram – entity relationship diagram. As class diagrams are essential to all object oriented analysis, its used in 90% of the software projects with UML diagrams. But you should keep in mind that even though there are a number of UML notations, the lass diagram should be as simple and clear as possible without complicating it with unnecessary notations. Classification of classes should be done keeping in mind the object orient principles and after listing the relevant classes you can depict them with the help of the class diagram. An example of a class diagram is given in Figure A to give you an idea of the structure of class diagrams: Figure A : Example of Class Diagram In Fig A, lets take the “Dishware” class, it has three compartments. At present the attributes and operations compartment have been left blank, Each operation is prefixed a “+” sign to depict that its a function and suffixed by “(). The variables which will be input or passed through the function can be included within the symbol”()”.
Also included in the example are six other classes “Plate”, “Bowl”, “Wooden-plate”, “GlassPlate”, “WoodenBowl”, “GlasBowl”. The two classes “Plate” and “Bowl” are generalization of the main class “Dishware”. This can be depicted by the hollow triangle symbol as shown in Fig A. The two classes “WoodenPlate” and “GlassPlate” are generalization of the class “Plate” and similarly for the class “Bowl”, the two classes “WoodenBowl” and “GlassBowl” are generalizations. Generalization means that the sub classes will inherit the behavior of the main class but will have attributes their own as well. Lets take the example of “GlassPlate”, it will have the attributes of the class “Plate” like shape etc nut will also have its own attributes.
121)What is RUP (rational unified process)?
RUP stands for Rational Unified Process. Its a software development process framework which has been taken forward by Rational(part of IBM corporation) Its a proper guidelines to be followed so to achieve standardization and improvement of the existing processes. RUP has phases and iterations which have to be followed with the help of templates and guidelines implemented at each stage. The intention of usage of RUP is to provide standards for all stages of the software development life cycle. RUP is supported by different tools and methodologies among which is Rational’s UML(Unified Modeling Language). In the figure, the Rational Unified Process Model can be diagrammatically viewed. As depicted, RUP has four distinct project life cycle phases: a) Inception – is the part where the actual exploration of the concept happens with the stakeholders management, definition of the project scope, cost benefit and feasibility analyses. This is the starting phase of the project and actually provides the foundation for each of the ensuing processes. b) Elaboration – This is the phase where the project starts to take shape. The requirements are more or less frozen and the design of the system gets into its first draft. c) Construction – This phase is the actual building phase of the project where the software takes shape and it involves the major coding part out of the four phases. Testing is also part of this phase.
The first cut release of the software is the objective of the phase d) Transition – This phase is the wrapping up of the system with the release to the client and the final support phase of the software system starts. RUP also has six engineering disciplines and three supporting disciplines. These nine RUP disciplines are part of each iterations required in the project life cycle. The six engineering disciplines are somewhat similar to the waterfall model phases whereas the three supporting disciplines are unique to the RUP framework.
I. RUP Engineering Disciplines
a) Business Modeling – Initial modeling of business with the analysis and scope formation
b) Requirements – gathering and communication of requirements
c) Analysis and design – analysis and formation of the solutions designs
d) Implementation – Implementing the solution
e) Test – testing the system as a whole and in units
f) Deployment – finally deploying the system at client site and going into production
Level II RUP Supporting Disciplines
a) Configuration and Change Management – configuration of the versions of documents and code. Management of changes to requirements, solution and codes as required
b) Project Management – Planning, estimation, resourcing and overall managing the team and customers as part of the project
c) Environment – Ensuring that the project team is aware of all aspects and of the RUP implementation.
the RUP framework is depicted as a “hump chart” with the matrix showing the RUP phases and the RUP disciplines. Lets say for example, the requirement discipline is peaked at the initiation and elaboration stage after which it flattens bout does not completely disappear. Similarly project management discipline is required to be at a constant peak throughout the project and cannot flatten or lag behind in any phase. RUP is one of the most complex software development project life cycles and involves proper project planning for the successful implementation of the system
122)What is GAP analysis
123)UAT (User Acceptance Testing):
124)Probably you must be wondering what exactly a business analyst is. After all those stereotypical definitions of a business analyst, you still must have some questions as to what exactly does a business analyst do and how does he fit in a firm. Well, this article will let you know how a typical day looks like in the life of a business analyst.
A business analyst needs to have knowledge of both the business and the IT of the firm. Business would include policies, processes, business models and infrastructure while the IT part involves the implementation of these. When firm is facing a strategic or organizational obstacle- that is where the business analyst jumps into action. A business analyst needs to have the right blend of both in order to carry out his tasks effectively. Hence a BA is required to have both the IT skills to understand the current implementation and also knowledge of business to remodel it.
When a BA is presented with a case, the following would be the typical steps that he would take to solve it:
Impact Defining the problem will include doing the initial analysis of the case to give it more clarity and to eliminate possible miscommunications between the BA and the client. This would require setup of meetings with stakeholders either for clarification or follow-up, getting hold of relevant documentation pertaining to the problem and documenting your analysis and findings. Making a business decision requires hard data along with wisdom and leadership.While defining the problem, the BA will require to couple quantitative analysis with strategic thinking in order to arrive at the way of approach to solution.
While staffing the team, one must remember that it is not necessary for the entire team to be present at one location. Teams could be divided by geographic location and time zones. In such cases, proper communication with all sub-teams forms an important part for everyone to stay in the same page. Another task of the BA would involve getting an heads-up from different teams in different time zones. Also while leaving for the day; they would have to inform the next set of duties for the team in a different geographic location. This show why being able to work in a team and proper communication is some of the required key skills in a BA. A BA distills his discoveries into solutions creating an impact in the way the client organization will function from now on. A simple example of the role of the business analyst could be in the task of cost cutting. In the current economy, many organizations and firms would have implemented cost cutting in their business models in order to survive the bad times. A BA is the one who identifies the issues (in this case, the extravagant expenditures), forms various hypotheses and analyses, distill their conclusions into recommendations and present it to the client management who will incorporate that into their business. A BA could either work closely at the client side or at the parent organization, but in any case his job would be to get as much information about existing systems from the client, have brainstorming sessions with team to input ideas and help build effective solutions.
125)What is a Communication Diagram?
A UML 2.0 Communication Diagram models the objects or parts of a system, the interactions (or messages) between them, and the sequence in which these interactions occur. There are a lot of similarities between communication diagrams and sequence diagrams in terms of the information they show, but because of how each diagram presents the information, one diagram may be better at conveying or emphasizing specific information over the other. Communication diagrams use a free-form arrangement of objects or parts of a system. This can be compared to how classes and objects are laid out in UML class and object diagrams. Then the interactions between the objects or parts of the system are show and labeled to indicate the chronological sequence in which they occur. The free-form arrangement of objects lends itself week to showing the sequenced interactions in a more compact space, allowing the analyst to place objects that have the highest number of interactions with each other near one another. This is the advantage of the communication diagram over the sequence diagram. While showing nearly all of the same information as a sequence diagram, the communication diagram can, at a glance, place a strong emphasize on which objects are interacting with one another While communication diagrams are formally intended to show system objects and the interactions between them, many analysts choose to create them at a higher level of abstraction. Instead of showing the interactions between objects of a system, larger parts of a system may be represented such as the interaction between web methods, web services, or entire systems. By using the communication diagram in this way, it shows some similarities to a system context diagram. The primary differences between the two are that a system context diagram places a focus on a single system in context along with which actors and systems outside of the scope of the system interact with it. Additionally, a system context diagram does not show the sequence of interactions.
126)What are the advantages and disadvantages of using screen mockups in the requirements gathering process of a system solution?
Screen mockups can support the requirements gathering process when introduced at the right time, but if introduced too early they can become problematic. Here are a few key points that an analyst should remember.
1) Mockups are nice because they help the business representatives or clients visualize the functionality of the system. This can be a big advantage to help analysts and stakeholders identify problems early on. However, if introduced too soon in the process the natural tendency is for the business reps/clients to try and be screen designers. Instead of stating that the system shall support “x”, they beginning saying that they need a dropdown to capture “y” and a button to do “z”. The client is not a UI designer, in fact few business analysts truly are, so this can lead to a screen design which does not have an appropriate emphasis on usability. Similarly, specifying the controls needed on a screen detracts from the true requirements of the system and often results in an inadequate level of discussion around why a system must support certain functionality.
2) When requirements are captured in screen mockups with no supporting requirements list, it becomes impossible to know whether an early screen design decision was made because it supports a necessary requirement or if it was made for some other reason. How can the analyst and developers know whether they can eliminate or alter the screen feature without losing an important requirement. Questions like, “Do we really need to have the control on this screen, or can we capture the data at a later point in the process?” becomes unanswerable without going back to the original stakeholders. And, on complex projects no one stakeholder may be able to answer the question.
3) Screen mockups alone cannot capture the flow through the system. Often analysts will accompany screen mockups with a written description of what happens when certain buttons are clicked or when certain values are entered within a field or dropdown. These descriptions are helpful, but they fall short of describing the end to end processes that the system must support. Further document such as process flows or use cases are required, but often overlooked when too much emphasis is place on screen mockups during the requirements gathering process. While analysts and stakeholders who are involved in the screen mockup process may have a basic understanding of the processes supported, developers and testers will not. Ultimately, the introduction of UI mockups can be very helpful, but this should only occur after an exhaustive list of features and usage scenarios (what business process flows need to be supported by the system) have been documented. Only then can the UI mockups be generated without introducing major pitfalls.
127)What is a Context Diagram and what are the benefits of creating one?
The Context Diagram shows the system under consideration as a single high-level process and then shows the relationship that the system has with other external entities (systems, organizational groups, external data stores, etc.). Another name for a Context Diagram is a Context-Level Data-Flow Diagram or a Level-0 Data Flow Diagram. Since a Context Diagram is a specialized version of Data-Flow Diagram, understanding a bit about Data-Flow Diagrams can be helpful. A Data-Flow Diagram (DFD) is a graphical visualization of the movement of data through an information system. DFDs are one of the three essential components of the structured-systems analysis and design method (SSADM). A DFD is process centric and depicts 4 main components.
A sample Context Diagram is shown here. A Context Diagram (and a DFD for that matter) provides no information about the timing, sequencing, or synchronization of processes such as which processes occur in sequence or in parallel. Therefore it should not be confused with a flowchart or process flow which can show these things. Some of the benefits of a Context Diagram are: Shows the scope and boundaries of a system at a glance including the other systems that interface with it No technical knowledge is assumed or required to understand the diagram Easy to draw and amend due to its limited notation Easy to expand by adding different levels of DFDs Can benefit a wide audience including stakeholders, business analyst, data analysts, developers.
128)When performing Cost-Benefit Analysis using discounted cash flows, how do you select and appropriate discount rate?
Cost-Benefit Analysis (CBA) is a critical activity in the work of a business analyst. While many business analysts may be brought onto a project well after this activity has occurred, nearly all projects which require a large amount of resources (time, people, or money) are assessed based on the CBA of the project. The activity is typically performed by a business analyst, often one specializing in the area of financial analysis, though any business analyst can learn this straightforward activity. The most prominent and well known aspect of CBA is Discounted Cash Flow (DCF) analysis which discounts future cash flows (both negative and positive) using a Discount Rate to arrive at a Net Present Value (NPV). This is represented by the following equation. NPV = (FVpos – FVneg) / [(1 + i)^t] where, NPV = Net Present Value FVpos = Future Value of a Positive Cash Flow at “t” years FVneg = Future Value of a Negative Cash Flow at “t” years i = Discount Rate t = time (years from present) Future cash flows are discounted using a Discount Rate (i) that is chosen to accurately reflect several factors: Time Preference – The theory that a person or institution would rather have money in hand now to spend on immediate wants or needs rather than waiting for future cash flows. Interest – Accounts for the fact that a person or institution that doesn’t receive money for several years also loses the opportunity to gain interest on the money for that period of time. Risk Premium – Reflects the additional return that a person or institution requires on later cash flows to account for the risk of future payments not materializing.
While the Discount Rate used for DCF calculations will vary, it becomes clear that the discount rate should be larger than any single factor above. If the interest that can be attained on the money that is being tied up is %5 per year, the discount rate should certainly be higher than 5% to account for Time Preference and the Risk Premium.
129) What are the contents that go into the object model and domain model during GAP analysis. how are the AS-IS and To-BE system documentation prepared?
When performing analysis between an existing system (AS-IS) and its desired future state (TO-BE) you could take into account all aspects/dimensions. Having said that, I realize that this approach may not always be practical nor necessary. So you should probably determine the focus of your gap analysis by answering the following questions: – What are they key characteristics of the system? – What do you know about the existing system? For example, if your system is workflow centric then it would probably be very beneficial to focus on the differences in workflow and document them by creating a workflow diagram which focuses on the differences. On the other hand – if the only documentation you have of the existing system is a list of requirements then you should start by identifying he requirement gaps. So getting back to the domain model…. If you are doing a Domain Model gap analysis focus on and document the following: – Differences in business entities (new entities, entities no longer needed, etc.) – Differences in entity relationships (diffs in types of relationships, diffs in multiplicities, etc.) – Differences in attributes for a given entity (new attributes, attributes no longer needed, etc.) – Differences in methods/behavior
130) How do you follow business rules in a project while working on a project?
Business rules are the key in defining any business process. example credit card company wants to prepare the process and the key business rule is – check applicant’s credit score and income. the process will need to include these two sub-process to complete the main process and without with it will through an exception. you can use the use case diagram or process diagram to include this information in your Use case document or Functional Requirement Document.
131)What is the difference between high-level and low-level use case? How business analysts can performs that job?
High-level Use Case Diagram gives you snap shot for your system and contains many process within it. Low-level Use Case Diagram will describe one process in details with alternative flow, exception and include/exclude descriptions.
132)What roles business analysts play during change management?
The Business Analyst will check the requested change against the original requirement. If its part of the requirement and need to fix it as a defect, it will be done through defect management. If its part of the new requirement (which is not mentioned in Business Requirement Document), he/she need to analyze the impact of change in terms of feasibility, schedule, resource planning and project scope. The detailed discussion and sign off required if the change will have major impact on the project.
133)How would you assess your value as a BA?
How does a business analyst save an organization money? You might mention a few examples such as: Make a process more efficient saving the company time and resources (which translates as money) Drive out the real requirements of a system, instead of a half-baked solution, ultimately reducing the amount of rework and re-development required to develop a system that delivers the intended value (rework means lost money) Identify opportunities for increased customer satisfaction leading to greater customer retention and greater new customer conversions (more money) If you have quantifiable examples of work that you have produced in the past and know precisely how much your work saved a company (not the work of the entire team, but YOUR actual contributions) this information can be very powerful. This is your true value as an analyst within a similar organization and role. But few people have the information required to make this kind of assessment. In addition, the value you bring to an organization is very different from your “potential value”. If an organization has you writing specs for a system, your opportunity to bring value may be much lower than if you are re- engineering a multi-million dollar business process to eliminate hundreds of thousands or even millions of dollars of waste.
134)This line of reasoning leads us to the question “Do you have the skillset required to be a marketable business analyst”?
You may have expert knowledge of traditional SDLCs and be able to create complex analysis diagrams, but if the organizations that are hiring all require you to work in an Agile environment then what value can you bring them? Even though your potential value for some organizations may be quite high, your value to others that use a different range of skills may be quite low. This example shows how your value is dependent upon the industry environment and the tools, competencies, and methodologies that are popular at that time. It also shows the need to keep your skillset current and then stress those skills that are most relevant to the interviewing organization.
If you can talk through these concepts with an interviewer, then you will have demonstrated that you don’t take you value as a business analyst for granted and that you are the type of person that will maximize your value within the organization that hires you.
135)How would you influence people when you do not have decision making authority?
Few business analysts have the final authority to make critical decisions on projects. That’s why it’s so important for business analysts to polish their influencing skills. The process used to influence people can be a formal, well thought out presentation, or it can be an informal conversation. Either way, it never hurts to think through a standard framework by which to structure your thoughts before attempting to influence someone. The following is a concise 5-step
framework that can be used for both formal and informal communications that involve influencing another person or audience. Define the What, Why, and Who Prepare your case Deliver your message Obtain a commitment Agree to a specific action plan These 5 steps provide a framework to structure and plan your communication to maximize your influence over a person or audience, but it’s the details of each step that will determine how influential you will be.
136)Develop milestones for reaching the final objective.
Identify resources and assign roles and responsibilities Develop a method for tracking progress To re-iterate, if you are planning a formal communication or presentation you will have a lot more time to spend thinking through the details of this 5-step process. However, even for brief communications within a short conference call, mentally thinking through these steps for just a few second can help guide your conversation and increase your degree of influence with your audience.
137)What is the purpose of a flow chat?
a flow chart shows the process which is shown using a graphical representation. This makes it easier for people to understand.
138) Explain what a case model is?
a case diagram is used to give vivid details about the business environment. a case diagram is a number of events that are part of a process that is performed by an actor.
139) what is meant by alternate flow in use care?
it is a flow or series of events that will fall into place when a failure in the system occurs and the expected results are not met.
140) the different between extends and includes when using in a use care.
As a business analyst you should also know by now that extend means that a specific event has to take place. Include means that the event might or might not happen.
141)What are Typical process steps to Conduct Feasibility Study?
Based on the size and/or complexity of the situation, the study effort may be broken down into smaller, more manageable pieces and prioritized accordingly. The typical process steps to conducting a feasibility study include those outlined below. It must be noted that these steps are often be conducted concurrently, iteratively and, in fact, some steps may be omitted entirely, depending on the complexity and criticality of the effort.
Process steps include:
* Determine requirements for the study
* Determine objectives, scope and approach, and plan the effort
* Conduct a current state assessment
* Identify potential solutions
* Determine the feasibility of each option
* Document and communicate the results of the study, and obtain approval to develop the Business Case for the recommended solution.
142)Knowledge and Skills needed for a Business Analyst to conduct Feasibility Analysis? Ideally individual(s) will have broad experience in business and IT, understand the concept of project value and what it may mean to their organization. In addition, the Business Analyst needs to understand * Financial analysis to evaluate the viability of a potential solution * The industry and the organizational vision, mission, and strategic goals, as well as organizational policies and procedures that may affect the study or be affected by the change initiative under study * A broad, not deep, understanding of the IT infrastructure that supports the business
Skills Due to the wide range of techniques that are used when conducting a major feasibility study, the Business Analyst may not possess all of the skills required to plan and execute the study. Therefore, the Business Analyst must enlist a team of experts to provide the skills required, including: * Research and information analysis skills * Ability to plan and conduct the study, and document the results * Technical writing skills
* Leadership and organizational skills * Change management skills * Communication skills (oral and written) in order to better facilitate, interview and communicate in a collaborative manner * Ability to work independently or in a team environment.
143)What is the career path for a Business Analyst?
A Business Analyst in the IT field has many varied directions among which to choose a career path. The most direct would lead to a Lead Business Analyst position and then Project Manager whereby the incumbent manages projects through the entire life cycle from inception to post-implementation including the management of
business analysts’ system analysts quality assurance analysts and most likely development project managers or team leads. That path would then lead to Program Management perhaps PMO management or Product Manager and on to Directorship. In addition a good Business Analyst may find they are heading toward a Customer Relationship Manager position whereby they become the primary IT interface to a given Business Unit (BU).
This role most often leads to a position within the BU as a Manager of Applications or a Process Management role. Process Management opens many jobs including process re-engineering quality program development and large scale or enterprise process management programs such as ITIL or Six Sigma initiatives. These roles will continue to proliferate as companies realize the benefits of having a SME in process and quality. And still many Business Analysts find their understanding of business process entirely portable into purely system related positions in the business side that are only peripherally related to IT. These of course may lead to quantitative roles manager roles or operational roles such as supply chain logistics et cetera. Of central importance to a successful Business Analyst is the interest in speaking to people. Face to face verbal communication is paramount to support other tools such as surveys and diagrams. Incumbents must be interested in understanding not only the pieces that comprise a system but the people that comprise it and the realities that embrace the system.
Briefly the Business Analyst must understand and not judge the what should be and the what is.
144)What analysis and modeling techniques do you use to translate business objectives into system requirements?
Create project-initiation diagrams including business use cases, activity diagrams, workflow diagrams, flowcharts Determine project scope and derive context diagrams and project use cases from the business diagrams Detail the use cases by using activity diagrams or other techniques Create high level analysis data flow diagrams, domain class diagrams, and entity-relationship diagrams from the use cases or other high level diagrams Recognize and understand the various design models, including the other relevant types of UML diagrams, detailed design entity-relationship diagrams, and decomposed data flow diagrams Determine when to use which modeling technique, following them through a project life cycle, and understand which diagrams are derived from others
Understand the basic concepts of normalization and decomposition so can converse intelligently on the topic and review diagrams that have been normalized or decomposed mention some of the tools commonly used by business analyst? There might be various tools that you as a business analyst would be using depending upon the work environment.
AGILE BUSINESS ANALYST INTERVIEW QUESTION AND ANSWERS
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), scrum and kanban.
Scrum is the most widely used process framework for agile development.
Concepts of scrum include:
The spring planning meeting is held at the start of every sprint and comprises of the project team, product owner and the scrum master. The aim of this meeting is to:
Agile development, due to its innate nature, is both iterative and incremental. Owing to this characteristic, all the development aspects (design, quality, requirements) are constantly reviewed and improved progressively with each sprint. Thus, the product could be adapted at any time based on the client’s need and the level of customer satisfaction is very high.
Sprint backlog is a collection of requirements that the development team must achieve in the next sprint. A sprint backlog is created based on the development team’s capacity and the priority of the requirements. Conversely, a product backlog is a prioritized list of high-level requirements of the product.
A sprint burndown chart is graphic visualization of the rate of progress of the current sprint. This chart is updated daily over the course of a sprint.
Scrum Team comprises of Product Owner, Scrum Master and the Development Team
The responsibilities of a Product Owner:
The responsibilities of a Scrum Master:
A spike is a time bound activity to conduct analysis or answer question rather than producing shippable product. Spikes are usually planned to take place in between sprints.
Velocity of a sprint is the total amount of work the development team is capable of doing over the duration of the sprint. Velocity for a sprint is agreed upon based on the historical data available about the previous sprint of the project.
The progress of an agile project is represented by a story board. To do so, a white board is divided in four columns ‘To do’, ‘In Progress’, ‘Test’ and ‘Done’ and post It notes are placed in each column indicating the progress of individual development item (user story/task). This way, everybody is aware of the current status of the project and of the user stories as well.
The tracer bullet is a spike with the current architecture, current technology set, and current set of best practices which results in production of quality code.
Impediment denotes the ‘cause’ that is hindering the team member to work to its fullest capability and ScrumBag refers to the person, group, or any other blockers that could be a factor for Impediment.
A User story is document which defines the requirement of a system/project/product in the agile environment. They dictate the ‘who’, ‘what’ and ‘why’ of a requirement. To explain a requirement, a number of user stories might get created with each one of them defining a specific aspect of the requirement. These user stories are the prioritized based on their importance, broken down into tasks followed by the developers estimating the duration of completion of each of these tasks.
INVEST is a mnemonic describing the characteristics of a good user story:
While managing a large project, there are a lot of requirements spread across multiple domains of the project and it becomes difficult to manage such large number of requirements. Thus, these requirements are documented in form of user stories and the user stories belonging to the same section
of the project are clubbed to form an ‘Epic’. An epic is considered as complete only when all the user stories (and their respective tasks) belonging to it are complete.
Planning Poker is an agile planning technique aimed at gaining consensus on the estimated time to complete an activity. Team members are given Planning Poker cards with values like 1,2,3,4 and these values represent the estimation unit (hours, days) Then, a user story is discussed and the team members are called to disclose the duration that an activity is expected to take by displaying a Planning Poker card. If all estimators selected the same value, that becomes the estimate. If not, the estimators discuss their estimates and the same process is repeated until the complete team reaches a consensus.
to our newsletter
Today application testing is the deciding factor to launch the application into the market. And people do not launch the application unless it goes true.
Today many people were enthusiastic, to know the exact details of things happening around him. This can get the proper knowledge on Blockchain.
Zeal to learn ethical hacking is common among college students and IT professionals. Because everybody wants to secure their system from cyber attacks.
Python is a dynamic interrupted language which is used in wide varieties of applications. It is very interactive object oriented and high-level programming language.
Tableau is a Software company that caters interactive data visualization products that provide Business Intelligence services. The company’s Head Quarters is in Seattle, USA.
Pega Systems Inc. is a Cambridge, Massachusetts based Software Company. It is known for developing software for Customer Relationship Management (CRM) and Business process Management (BPM).