Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.






2. Influencing factors that are believed to be true but have not been confirmed to be accurate.






3. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






4. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.






5. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.






6. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.






7. All materials used by groups within an organization to define tailor implement and maintain their processes.






8. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.






9. Any unique and verifiable work product or service that a party has agreed to deliver.






10. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.






11. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






12. Any recognized association of people in the context of an organization or enterprise.






13. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






14. Software developed and sold for a particular market.






15. A description of the requirements management process.






16. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.






17. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






18. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.






19. A stakeholder who provides products or services to an organization.






20. Limitations on the design of a solution that derive from the technology used in its implementation.






21. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






22. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.






23. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






24. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






25. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






26. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.






27. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






28. A stakeholder person device or system that directly or indirectly accesses a system.






29. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






30. The process of examining new business opportunities to improve organizational performance.






31. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.






32. A person with specific expertise in an area or domain under investigation.






33. A model that defines the boundaries of a business domain or solution.






34. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.






35. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.






36. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






37. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.






38. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






39. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.






40. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.






41. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.






42. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode






43. A system trigger that is initiated by humans.






44. A specific actionable testable directive that is under the control of the business and supports a business policy.






45. A prototype developed to explore or verify requirements.






46. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.






47. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.






48. The quality attributes design and implementation constraints and external interfaces that the product must have.






49. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.






50. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests