A Statement of Work (SOW) is a document routinely employed in the field of project management. It defines project-specific activities, deliverable and timelines for a vendor providing services to the client.
The Use Case Model describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between a user (human or machine) and the system. A Use Case is a single unit of meaningful work; for example login to system, register with system and create order are all Use Cases. So, Each Use Case has a description which describes the functionality that will be built in the proposed system. A Use Case may ‘include’ another Use Case’s functionality or ‘extend’ another Use Case with its own behavior
An Actor is a user of the system. This includes both human users and other computer systems. An Actor uses a Use Case to perform some piece of work which is of value to the business. The set of Use Cases an actor has access to defines their overall role in the system and the scope of their action.
Alternate flow are the alternative actions that can be performed apart for the basic flow and might be considered as an optional flow whereas Exception flow is the path traversed in case of the error or an exception being thrown. For e.g. on a logic page the ‘Forgot password’ is the alternate flow and system showing ‘404 error’ when correct username and password are entered is exception flow.
A Business Requirement Document is created to describe the business requirements of a product/process and the intended end result that is expected from the product/process. It is one of the most widely accepted project requirement document and is referred throughout the development life-cycle for any project.
A BRD mainly focuses on answering ‘what is the business solution’ as opposed to ‘how to achieve the business solution’ and thus it’s mainly centered around the business requirements. So A BRD is created with the help of the project team (BA, client, subject matter exerts, business partners) and is also used as a communication tool for other stakeholders/external service providers.
The Business Requirement Document contains:
– Project Background
– Business goals and objectives
– Requirement scope
– Functional requirements
– Data requirements
– Non-functional requirements
– Interface requirements
– Business glossary/Definitions
– Dependencies of existing systems
It is Business Process Model and Notation. It is a graphical representation of business processes.
|Generate CR||A submitter completes a Change Request (CR) Form and sends the completed form to the Change Manager / Business Analyst|
|Log CR Status||The Change Manager / Business Analyst enters the CR into the CR Log. The CR’s status is updated throughout the CR process as needed.|
|Evaluate CR||Project personnel review the CR and provide an estimated level of effort to process, and develop a proposed solution for the suggested change|
|Authorize||Approval to move forward with incorporating the suggested change into the project/product|
|Implement||If approved, make the necessary adjustments to carry out the requested change and communicate CR status to the submitter and other stakeholders|
Scope creep, also known as requirement creep is a term that denotes uncontrolled changes/deviation in the project’s scope without an increase in the other resources (schedule, budget) of the project.
Scope creep is a risk to the project and is usually caused by poor project management, improper documentation of project’s requirements and poor communication between the project’s stakeholders.
A Requirement traceability matrix is used to record and track the relationship of the project requirements to the design, documentation, development, testing and release of the project/product. Finally this is done by maintaining an excel sheet which lists the complete user and system requirements for the system (in form of use cases) which are in-turn mapped to the respective documents like Functional Requirement, Design Document, Software Module, Test Case Number, etc. A RTM is maintained throughout the life-cycle of the various releases in a project and it’s a vital document to track project scope, requirements and changes in any project.
An interview is a systematic way to get information out of a person/group of people through a formal or informal conversation.
The interviewer asks direct or indirect questions from the participant to elicit information and mold the questions as open or close ended to get the information he wants. Then documents and catalogs the information in a structured format. So, this technique is widely used throughout the project life cycle and primarily in initiating, requirement gathering and monitoring and controlling phases.
A Facilitated workshop is a conversation among the carefully selected stakeholders and subject matter experts and is led by an experienced and neutral facilitator.
These workshops aids in requirement gathering, helps generate new ideas and reach an agreement about a discussion element/solution. So this technique is used in requirement gathering and planning phase.
Brainstorming is a group/individual technique aimed at finding a solution to a specific problem by gathering ideas from different people/sources.
Brainstorming is an informal and creative technique and the ideas generated through this technique are later reviewed and prioritized for implementation. So, this technique is used in planning and executing phase.
Observation involves closely monitoring and assessing a process or an individual.
This technique is useful when there is a modification of the existing process and the observer watches the way of work closely. The observation might be active or passive and the observer documents. As a result, the observer might himself perform some hands on activity to get a better understanding of the process.This technique is used in initiating and requirement gathering phase.
A prototype or mock-up is an initial version of a product and gives a visual depiction of the end product.
They also contribute in user interaction and getting feedback about the system. Therefore Prototypes are widely used to depict data/process navigation, requirements validation and scenario depictions.This technique is used in requirement gathering, executing and testing phase.
Get more questions and answers from onlineitguru trainers after completion of BA Certification
Although Business analysts are not explicitly asked to create test cases but they must understand what they constitute and how to create one, as they sometimes have to test functionalities by referring to the test cases.
A test case is a document, which has a set of test data, preconditions, variables and expected results created to verify and validate whether a particular piece of functionality is behaving as intended (or as documented in the requirement documentation). So, a test case becomes a standardized document which should be referred every time a requirement has to undergo testing.
The components of a test case are:
– Test Case ID
– Test Scenario
– Test Data
– Test Steps
– Expected Results
– Actual Result
– Test Environment
Root cause analysis involves finding out the underlying source of the problem. Root cause analysis is done to correct the main cause of a problem and prevent is re-occurrence, rather than simply treating the problem’s symptoms. So, these methods to find the root causes are fish-bone diagram (or cause and effect diagram).
to our newsletter
Today application testing is the deciding factor to launch the application into the market. And people do not launch the application unless it goes true.
Today many people were enthusiastic, to know the exact details of things happening around him. This can get the proper knowledge on Blockchain.
Zeal to learn ethical hacking is common among college students and IT professionals. Because everybody wants to secure their system from cyber attacks.
Python is a dynamic interrupted language which is used in wide varieties of applications. It is very interactive object oriented and high-level programming language.
Tableau is a Software company that caters interactive data visualization products that provide Business Intelligence services. The company’s Head Quarters is in Seattle, USA.
Pega Systems Inc. is a Cambridge, Massachusetts based Software Company. It is known for developing software for Customer Relationship Management (CRM) and Business process Management (BPM).