(Some Fundamental Truths)
Created by: Ramandeep Kaur
1.) What is the focus of business requirements gathering?
Ans: Requirement gathering is the process of generating the list of requirements like functional, technical, system, etc. from the various stakeholders that are used for the formal requirements definition. In various cases, stakeholders are not aware of the possibilities that exist because the process is not as straightforward as the stakeholders want the system to do and in the current state, it may be limited by their immersion. It focuses on the understanding of business problems and providing a solution to it.
2.) What are the functional and non-functional requirements?
Ans. Functional requirements:- It specifies a function in which the system component must be able to perform. It can be documented in various ways. The most common ones are written descriptions in documents and use cases. A typical functional requirement will contain a unique name and number, a brief summary and a rationale. A functional requirement is what a system is supposed to accomplish. It may be calculations, technical details, data processing, and other specific functionality.
Non-functional requirements:- It specifies the criteria that can be used to judge the operation of a system rather than specific behaviors. Non-functional requirements can be divided into two main categories: execution qualities, such as security and usability, which are observable at run time and evolution qualities, such as testability, maintainability, and scalability, which are embodied in the static structure of the software system.
3.) What are the constraints? Give an example.
Ans. Constraints are global issues that shape the requirements. They can be limitations on the project itself or restrictions on the eventual design of the product. The so-called 'Triple Constraint'-the triangle of time, cost and scope-are the big hitters and every project as project drivers has one or two if not all three project constraints. An example of a constraint is the fact that there are only so many hours in a day to accomplish things.
4.) What is the process of Volere requirements?
Ans. The process is to start testing the requirements as soon as we writing them. There is a need to make a requirement testable by adding its fit criterion. This fit criterion measures the requirement, making it possible to determine whether a given solution fits the requirement.
5.) How to understand the business problem and find a solution?
Ans. There are three main steps in the problem-solving process in business:
- Identify the problem:- It's important to understand the causes of the problem, rather than simply looking at its effects. State the problem and develop a detailed problem description.
- Consider the options:- Consider the specific factors that must be addressed in the solution. Identify potential solutions that address most or all of the factors.
- Choose the best solution:- Weigh the risks of tentative solutions. This is the opportunity to prepare for and take steps to avoid any potential negative effects of final decision at no cost. Choose the most appropriate solution to implement.
In Microsoft every software and hardware project go through a phase called Requirements Gathering. A successful project begins with a difficult set of discussions on what should be done. It’s the major responsibility of IT business Analyst to gather the requirements from the clients. Getting the correct requirements from the client can often be one of the biggest hurdles in any project. For Business Analyst, it is necessary to pick methods which work best for gathering requirements. Also, Business Analyst has to decide who participates in this phase. If Business Analyst invests time in developing a clear, concise, correct and measurable set of Requirements, it usually gives the surety of developing Quality software and hardware as per client needs.
ReplyDeleteMicrosoft deals with major constraints all the time that are separate from the common three. A continuous problem Microsoft has to deal with is on the legal front. For years Microsoft has been accused of abusing a monopoly or in other cases they have been shown to break smaller companies patents. These sorts of issues force Microsoft to be strict on the requirements so that the project is unique and legally acceptable. Another major constraint for Microsoft is that there are so many upper management members that it can take much longer to get permission on a project or about the smaller details.
ReplyDeleteThe so-called 'Triple Constraint'-the triangle of time, cost and scope-are the big hitters and every project as project drivers has one or two if not all three project constraints. An example of a constraint is the fact that there are only so many hours in a day to accomplish things.partners don't know about the conceivable outcomes that exist in light of the fact that the procedure isn't as direct as the partners need the framework to do and in the present state, it might be restricted by their inundation. It centers around the comprehension of business issues and giving an answer for it.
ReplyDelete