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. Creating working software in multiple releases so the entire product is delivered in portions over time.






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






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






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






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






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






7. Software developed and sold for a particular market.






8. An analysis model that illustrates the architecture of the system's user interface.






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






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






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






12. The set of capabilities a solution must deliver in order to meet the business need.






13. The problem area undergoing analysis.






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






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






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






17. A stakeholder who uses products or services delivered by an organization.






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






19. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various






20. A document or collection of notes or diagrams used by the business analyst during the requirements development process.






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






22. Interfaces with other systems (hardware software and human) that a proposed system will interact with.






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






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






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






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






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






28. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.






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






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






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






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






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






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






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






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






37. The set of processes templates and activities that will be used to perform business analysis in a specific context.






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






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






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






41. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet






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






43. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.






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






45. A solution or component of a solution that is the result of a project.






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






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






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






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






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







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