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






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






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






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






5. A group of related tasks that support a key function of business analysis.






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






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






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






9. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.






10. A non-actionable directive that supports a business goal.






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






12. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.






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






14. A type of data model that depicts information groups as classes.






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






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






17. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.






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






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






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






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






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






23. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe






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






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






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






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






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






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. A data element with a specified data type that describes information associated with a concept or entity.






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






32. An informal solicitation of proposals from vendors.






33. A description of the requirements management process.






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






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






36. A group or person who has interests that may be affected by an initiative or influence over it.






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






38. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.






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






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






41. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.






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






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






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






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






46. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.






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






48. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.






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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).







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