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






2. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).






3. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.






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






5. A target or metric that a person or organization seeks to meet in order to progress towards a goal.






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






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






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






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






10. A system of programming statements symbols and rules used to represent instructions to a computer.






11. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.






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






13. The set of capabilities a solution must deliver in order to meet the business need.






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






15. A system trigger that is initiated by humans.






16. A function of an organization that enables it to achieve a business goal or objective.






17. A temporary endeavor undertaken to create a unique product service or result.






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






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






20. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).






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






22. A structured examination of an identified problem to understand the underlying causes.






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






24. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.






25. An actor who participates in but does not initiate a use case.






26. A use case composed of a common set of steps used by multiple use cases.






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






28. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






30. An informal solicitation of proposals from vendors.






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. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.






33. The number of employees a manger is directly (or indirectly) responsible for.






34. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






35. A description of the requirements management process.






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






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






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






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






40. Software developed and sold for a particular market.






41. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






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






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






45. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.






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. The area covered by a particular activity or topic of interest.






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






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






50. Ability of systems to communicate by exchanging data or services.







Sorry!:) No result found.

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