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






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






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






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






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






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






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






8. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.






9. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.






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






11. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.






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






13. A prototype that is continuously modified and updated in response to feedback from users.






14. A temporary endeavor undertaken to create a unique product service or result.






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






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






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






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






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






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






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






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






23. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.






24. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.






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






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






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






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






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






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






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






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






34. The problem area undergoing analysis.






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






36. A system trigger that is initiated by time.






37. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.






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






39. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.






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






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






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






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






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






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






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






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






48. A model that defines the boundaries of a business domain or solution.






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






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







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