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






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






3. Software requirements that limit the options available to the system designer.






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






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






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






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






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






9. A stakeholder who uses products or services delivered by an organization.






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






11. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.






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






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






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






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






16. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons






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






18. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti






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






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






21. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.






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






23. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.






24. A system trigger that is initiated by humans.






25. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin






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






27. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.






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






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






30. A prototype that dives into the details of the interface functionality or both.






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






32. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






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






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






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






37. The area covered by a particular activity or topic of interest.






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






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






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






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






42. Something that occurs to which an organizational unit system or process must respond.






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






44. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.






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






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






47. An analysis model showing the life cycle of a data entity or class.






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






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






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