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 actor who participates in but does not initiate a use case.






2. An analysis model that shows user interface dialogs arranged as hierarchies.






3. A data element with a specified data type that describes information associated with a concept or entity.






4. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.






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






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






7. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.






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






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






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






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






12. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.






13. A use case composed of a common set of steps used by multiple use cases.






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






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






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






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






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






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






20. The human and nonhuman roles that interact with the system.






21. Any recognized association of people in the context of an organization or enterprise.






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






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






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






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






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






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






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






30. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.






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






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






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






34. An assessment of the costs and benefits associated with a proposed initiative.






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






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






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






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






39. A description of the requirements management process.






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






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






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






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






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






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






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






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






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






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






50. A system trigger that is initiated by time.