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 partial or preliminary version of the system.






2. A prototype that dives into the details of the interface functionality or both.






3. A practitioner of business analysis.






4. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.






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






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. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






8. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






10. A system trigger that is initiated by time.






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






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






13. A link between two elements or objects in a diagram.






14. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.






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






16. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






17. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






18. A data element with a specified data type that describes information associated with a concept or entity.






19. The degree to which a set of inherent characteristics fulfills requirements.






20. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.






21. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.






22. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m






23. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme






24. A unit of work performed as part of an initiative or process.






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






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






27. The work that must be performed to deliver a product service or result with the specified features and functions.






28. A state or condition the business must satisfy to reach its vision.






29. The problem area undergoing analysis.






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






31. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






32. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






33. A system trigger that is initiated by humans.






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






35. Software developed and sold for a particular market.






36. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






37. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.






38. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).






39. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options






40. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






41. 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






42. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.






43. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.






44. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.






45. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.






46. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






47. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig






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






49. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






50. A measure of the profitability of a project or investment.






Can you answer 50 questions in 15 minutes?



Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests