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 subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine






2. An analysis model that illustrates the architecture of the system's user interface.






3. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.






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






5. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.






6. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.






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






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






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






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






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






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






13. A type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






15. Software developed and sold for a particular market.






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






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






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






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






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






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






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






23. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






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






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






27. A shared boundary between any two persons and/or systems through which information is communicated.






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






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






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






31. A system trigger that is initiated by humans.






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






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






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






35. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






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






38. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






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






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






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






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






43. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.






44. A partial or preliminary version of the system.






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






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






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






48. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.






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






50. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.