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 high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.






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






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






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






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






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






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






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






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






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 description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.






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






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






14. A system trigger that is initiated by time.






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






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






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






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






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






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






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






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






23. A stakeholder responsible for assessing the quality of and identifying defects in a software application.






24. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.






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






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






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






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






29. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.






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






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






32. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.






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






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






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






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






37. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.






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






39. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.






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






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






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






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






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






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






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






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






48. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.






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






50. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests