Test your basic knowledge |

  • 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 prototype that dives into the details of the interface functionality or both.

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

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

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

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

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

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

8. A description of the requirements management process.

9. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce

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

11. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.

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

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

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

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

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

17. An informal solicitation of proposals from vendors.

18. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m

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

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

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

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

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

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

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

27. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.

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

29. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.

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

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

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

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

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

35. The problem area undergoing analysis.

36. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).

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

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

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

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

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

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

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

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

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

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

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

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

49. A set of requirements grouped together in a document or presentation for communication to stakeholders.

50. A fixed period of time to accomplish a desired outcome.