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. Work carried out or on behalf of others.






2. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s






3. An analysis model describing the data structures and attributes needed by the system.






4. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.






5. A set of requirements grouped together in a document or presentation for communication to stakeholders.






6. The product capabilities or things the product must do for its users.






7. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






8. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






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






10. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






11. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.






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






13. A fixed period of time to accomplish a desired outcome.






14. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.






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






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






17. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






19. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






21. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






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






26. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






28. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.






29. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.






30. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.






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






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






33. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






34. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.






35. A prototype that is continuously modified and updated in response to feedback from users.






36. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






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






38. Metadata related to a requirement used to assist with requirements development and management.






39. A solution or component of a solution that is the result of a project.






40. The problem area undergoing analysis.






41. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






42. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.






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






44. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.






45. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






46. The business benefits that will result from meeting the business need and the end state desired by stakeholders.






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






48. Information that is used to understand the context and validity of information recorded in a system.






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






50. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.







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