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 type of diagram that shows objects participating in interactions and the messages exchanged between them.






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






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






4. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.






5. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.






6. Any unique and verifiable work product or service that a party has agreed to deliver.






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






8. The quality attributes design and implementation constraints and external interfaces that the product must have.






9. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.






10. A system trigger that is initiated by time.






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






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






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






14. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.






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






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






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






18. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.






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






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






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






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






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






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






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






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






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






28. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.






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






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






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






32. A person with specific expertise in an area or domain under investigation.






33. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.






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






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






36. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.






37. Software developed and sold for a particular market.






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






39. Creating working software in multiple releases so the entire product is delivered in portions over time.






40. A link between two elements or objects in a diagram.






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






42. A partial or preliminary version of the system.






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






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






45. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.






46. The product capabilities or things the product must do for its users.






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






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






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






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