Business Analysis & Software Engineering

SHAIK 1. What is the problem solved by business analysis? The main problem solved by business analysis is gather requirements in a proper manner, a business analysis take care till requirements become bug less features and till client satisfy (if requirements are not stable) . Business analysis will help to everyone those who involved in the project such as. 1. 2. 3. 4. 5. 6. Business analysis will communicate between technical and non-technical people Analyzing the business needs, future requirements and solutions to the problems Business analysis gives the designed documents (High- level and low - level Design )To understand the requirements to everyone stakeholder/ developers Business analysis will provide the solutions, if requirements come middle of the project Business analysis will help to choose appropriate model for the given project Verification and validation of requirements

Like this a business analysis will help both technical and non technical people in the project. 2. Who uses the output produced by business analyst? Business analyst will produce the list of requirements as a document and design these documents will help developers and non technical people to understand about the requirements, to capture the work flows (to understand the milestones) to one phase to another phase and it will also helps as a proof document. 3. How do you manage if requirements are changing rapidly? If requirements are changing rapidly middle of the project then I will analyze the requirements because it should not effect to the present prepared requirements, the cost and schedule, risk etc To not get this situation before choose model for the project, I will choose the model that suitable to the project requirement. If requirements are not upfront then I will choose agile model for the project. 4. What can a business analyst to differently than project or program manager (Design Architect) with respect to successfully getting the project implementation done? Project manager 1.Taking agreements with client 2.Finding the scope of the project 3.Finding the risk Business analyst 1.Eliciting requirements from the stake holders 2. Verification and Validation 3.Creating documents and design to understand requirements to developers and stake holders 4.Satisfying the client 5.Deployement (UAT)

4.Resoureces allocating 5.Daily meetings with developers

5. What would you do if client says that you and the other analyst cannot directly talk to the users? The role of business analyst and other analyst is very different. Some time users can be stake holders in project to gather good and future requirements a business analyst he/ she should speak with the users. 6. What is the main quality of a good requirement? A requirement would be a present or future need Qualities of a good requirement:    Simple:- The requirement should be simple not lengthy and it should be prepare within the time Clear:The requirement should clearly understandable for the developers and users Testable:- The requirement should be testable should not be complex and bug less Usable: - The requirement should be usable again and again, easily usable to knowledgeable and Unknowledgeable users

7. Roles of Business analyst? Business Analyst: - Who can transfer the business needs into software requirements The roles of business analyst is           Communicator Between stake holders and developers Selecting the model for the project Analyzing requirements Elicit requirements Prepare BRS and SRS Verification and validate the requirements Change the requirements into designing phase ( High level and Low level design) Giving the suggestions in middle of the project if require Prepare for UAT Deployment

8. What is business analysis? ANALYSIS: - The meaning of Analysis Is analyzing something The Business analysis is analyze (understanding needs, problem solving, finding causes, choose options and develop business 9. How would you influence people if you don t have decision making authority?

10. Benefits of following SDLC? SDLC: - SDLC (Software Development Life Cycle) is a phase that define how activities are performing at each stage of software project     Provide structure to every project (Depend on constraints) Easy to reach milestones The major benefit of SDLC is we can find how much the work has been done It controls the project from Analysis phase To Implementation

11. How RAD implementation is differing from Structured Evolutionary Prototyping Model? RAD (Rapid Application model):          Conduct a work shop with stake holders and gathered requirements Contact with users through Automated tools to get feedback about requirements Requirements are well known Client people will involved throughout the life cycle Project will be Time boxed Hard to use with legacy system Product will release in increments Low risk Low cost Performance is not a constraint

Structured Evolutionary Prototyping             Developers create a prototype during the requirements gathering phase Requirements will not be stable in this model Users will give Feed back Requirements are evaluated with users Loop continues until user satisfy Basic and critical functions developed first More accurate quality It suitable For new project and new technology Short lived demonstrations(not for the lengthy projects) Accurate quality Quick and dirty Cost will very high

12. Describe the importance of testing in software development? Types of testing process? Testing is of the major role in Software life cycle to get quality (Bug less) in project Types of testing: Unit testing:In this phase we test only the developed component  Integration testing:We use this test while integrating functionalities (is the functionality is integrated properly or not)  System testing:In this phase we test hole the developed features/product after integration  UAT(user acceptance test):This test is done by the users, to define the developed project is satisfied the user requirements or not  Alpha testing:This test is done before deploy the project and this test will done in the company location  Beta testing:This test is done in client location before release the project and this test will done by end users 13. What is the difference between iterative model and waterfall model? Water fall is the basic model of SDLC, this model name only contains the meaning of this model it flows like water and it cannot come back from one phase to another phase The major difference between water fall and iterative models is we cannot add the requirements at middle of the project in waterfall but in iterative we can add the requirements in the middle of the project and we can go back from one phase to another phase. 14. What is the difference between iterative and prototype model? In iterative model we release only one final product but in prototype model we release prototypes first after prototypes are ok then we release the final product. 15. What is spiral model? Describe the usage of different activities of spiral? Spiral is just like water fall model only but this model contains some other aspects those are prototyping and risk analysis Uses of Spiral We can find the risk in early stages We can see the project in prototypes High risk functionalities developed first

16. What is software life cycle? Software life cycle is a process that contains 6 phases in it those are
Requirement Design Development Testing Deployment Maintenance

17. What is the meaning of SDLC.net? If we use SDLC to .net projects we call it as a .net SDLC 18. What are the objective, iteration, UAT, and system testing ? Same answer of 12th question 19. Benefits of writing use cases and test cases? Use cases:-Business analysts will write use cases to understand the requirements to developers and it is a communicator between requirements and coding (when developer got a doubt while writing code he will check the use cases to understand the problem) Test cases: - Test engineers will prepare the test cases to test the project (accurate/quality product and to make bug less product) 20. Reason to project failure? How can the BA play the role to make it successful? A project is a collective requirement (features) Reason to project failure:     Not proper analysis Unachievable requirements Improper verification and validation of requirements Improper Documentation and designing ( Developer can t understand what customer want) Bad testing process

Business Analyst (BA) plays a major to succeed the project from Eliciting Requirements (verification and validation about the requirements) to till UAT and deployment 21. Describe the programming part towards developing a software system and How BA role goes under this phase? Programming made project into product (Develop the features are requirements through coding) Role of Business analyst in programming Phase:    Convert the requirements into document and design phases (High- level and Low level), These will help programs to understand how to build a feature or requirement through coding. This document will also help as solutions to project (if developer gets doubt in middle of the project) To Track the progress as well

22. Role of system analyst? A business analyst would be a system analyst he take care about all requirements (Eliciting requirements from stake holders) 23. The best reason to select Waterfall model? Reason to select Waterfall model:     Easy to use Low cast Accurate Quality Easy to track the progress Easy to control

24. How V&V model can serve best then that of waterfall? V&V model is just like water fall model only but it consists of V&V (Verification and validation) at each Phase of life cycle. 25. When to use V&V model?     Requirement should be Up-Front Requiring high reliability Technology is well known Cost and schedule should not be constraint

26. Give me summarized information about structured evolutionary prototyping?            Developers create a prototype during the requirements gathering phase Requirements will not be stable in this model Users will give Feed back Requirements are evaluated with users Loop continues until user satisfy Basic and critical functions developed first More accurate quality It suitable For new project and new technology Short lived demonstrations(not for the lengthy projects) Quick and dirty Cost will very high

27. Which models are using prototypes? Models using prototypes        Structured evolutionary prototypes RAD (Rapid Application Development) Incremental model Scrum Spiral FDD( Feature Driven Design) DSDM ( Dynamic system Development Method)

28. How can finish the project development very fast in RAD model? There are few reasons to complete project very fast in RAD model those are mentioned below     Low risk project Time Box approach Customer involved throughout the project High performance not required

29. Benefits of Incremental model?       Major functionalities developed first Work break down tasks Each increment release consist new features Low cost Increment Deliveries are fast Reduce the risk

30. What would be the best reason to use spiral? Uses of Spiral      We can find the risk in early stages We can see the project in prototypes High risk functionalities developed first Design not have to be perfect It has the RAD model and Waterfall model in it

31. What are the spiral quadrants? There are 4 Quadrants in spiral those are     Determine objectives alternative and constraints Evaluate alternative, identify risk and resolve Develop next level product Plan for the next phase

32. Strengths of spiral?     Find the risk before development the project( save the money) Customer can see the prototypes High risk functions developed first Feedback from users

33. Brife me about Extreme programming?

34. How can you develop overall model in FDD (FEATURE DRIVEN DESIGN)  Develop an overall model:- In this phase we develop an over design model with the help of chief architect  Build feature list:- In this phase we build features list  Plan by feature: - In this phase we plan about the feature (How to build, resources etc...)  Design by feature:- We develop a design by feature  Build by feature :- in this phase we prioritize the feature and develop accordingly 35. Which are the models using RAD?  Spiral  DSDM 36. When can you use the DSDM (Dynamic System Development Method)?     To release the product very fast User should participate in the project If client want incremental delivery If client want Good Quality

37. Explain project life cycle in DSDM?      Feasibility:- Finding the scope of the project Business study:- Prioritize the requirements Functional model:- Finding the risk Design and Build:- Design and build the iterations Implementation:- Implementing the project

38.How cam you call XP as a extreme ? 39. Which is the model can allow the client for changing requirements?     Structured evolutionary prototyping model RAD Increment AGILE

40. How would you identify yourself as a BA? I have a set of skills, these skills are required to every Business Analyst I think, those are mentioned below        communication skills Analyzing skills Problem finding and solving skills Quick learning skills Delegating skills Leadership skills Motivating skills as well as having the business related Academic background (having Business skills)

Check it these or the correct answers or not