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






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






3. A system trigger that is initiated by time.






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






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






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






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






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






9. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.






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






11. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.






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






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






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






15. Formal approval of a set of requirements by a sponsor or other decision maker.






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






17. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.






18. A system trigger that is initiated by humans.






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






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






21. Any effort undertaken with a defined goal or objective.






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






23. An informal solicitation of proposals from vendors.






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






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






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






27. An error in requirements caused by incorrect incomplete missing or conflicting requirements.






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






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






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






31. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.






32. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.






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






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






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






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






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






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






39. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.






40. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






41. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.






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






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






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






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






46. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.






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






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






49. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.






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