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. The set of capabilities a solution must deliver in order to meet the business need.






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






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






4. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).






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






6. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.






7. The features and functions that characterize a product service or result.






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






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






10. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.






11. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.






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






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






14. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.






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






16. Software developed and sold for a particular market.






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






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






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






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






21. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.






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






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






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






25. Ability of systems to communicate by exchanging data or services.






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






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






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






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






30. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.






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






32. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a






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






34. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.






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






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






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






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






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






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






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






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






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






44. A stakeholder with legal or governance authority over the solution or the process used to develop it.






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






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






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






48. A measure of the profitability of a project or investment.






49. Limitations on the design of a solution that derive from the technology used in its implementation.






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







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