Chapter 2 - Requirements Classification Schemes and Designs






11)    What are Stakeholders?

Stakeholders, these are one of the important parts of a business. These are the participants, or we may say a group or any individual with whom a business analyst interacts either directly or indirectly.  The few roles of a stake holders are:

Project manager, Tester, Operational support, Customer, Business Analyst, Regulator and supplier.





22)    Today I am going to talk about the Project manager. So, what a project manager is? What he does?

Well according to the chapter in our book, a Project manager has the responsibility of planning and executing the project and he is professional in it. He has to do this all by considering the budget, quality, resources and the scope of what is he going to do. If we talk about the roles of a project manager, then it may include the team leader, project leader, technical leader, developing schedules, organizing and a lot more.



33)    Requirements and Designs:

Requirements are focused on the need whereas designs are focused on the solution. The difference between these both is not very clear as the same methods are used to analyze and modeling them. Whether it is the business analyst or some other role that completes the designs, the business analyst often reviews the final designs to ensure that they complete all requirements. Set of requirements can be used to define a design. Later, that design can be used to extract some requirements  to define more detailed designs. Then the business analyst can give requirements and designs to other stakeholders who further works on the designs.



44)    Requirements Classification Schema:


Business requirements, Stakeholders requirements, Solution Requirements, Functional requirements, Non functional requirements, Transition requirements. 
• Business requirements: statements of goals, objectives, and outcomes that describe why a change has been initiated.

 • Stakeholder requirements: describe the needs of stakeholders that must be met in order to achieve the business requirements.

• Solution requirements: describe the capabilities and qualities of a solution that meets the stakeholder requirements.

• functional requirements: describe the capabilities that a solution must have in terms of the behaviour and information that the solution will manage, and

 • non-functional requirements or quality of service requirements: describe conditions under which a solution must remain effective or qualities that a solution must have.

 • Transition requirements: describe the capabilities that the solution must have and the conditions the solution must meet to facilitate transition from the current state to the future state, but which are not needed once the change is complete.

Comments

  1. Parminder Singh11 September 2019 at 19:14

    Detailed Requirements Schema



    • Business requirements: statements of goals, objectives, and outcomes
    that describe why a change has been initiated. They can apply to the whole
    of an enterprise, a business area, or a specific initiative.


    • Stakeholder requirements: describe the needs of stakeholders that must
    be met in order to achieve the business requirements. They may serve as a
    bridge between business and solution requirements.

    • Solution requirements: describe the capabilities and qualities of a
    solution that meets the stakeholder requirements. They provide the
    appropriate level of detail to allow for the development and
    implementation of the solution. Solution requirements can be divided into
    two sub-categories:
    • functional requirements: describe the capabilities that a solution
    must have in terms of the behaviour and information that the solution
    will manage.
    • non-functional requirements or quality of service requirements:
    do not relate directly to the behaviour of functionality of the solution,
    but rather describe conditions under which a solution must remain
    effective.


    • Transition requirements: describe the capabilities that the solution must
    have and the conditions the solution must meet to facilitate transition from
    the current state to the future state, but which are not needed once the
    change is complete. They are differentiated from other requirements types
    because they are of a temporary nature. Transition requirements address
    topics such as data conversion, training, and business continuity.


    Reference: - All information gathered in "A Guide to the Business Analysis Body of Knowledge® , Version 3, International Institute of Business Analysis, pages. 24-27, Accessed on 09/09/2019.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 1 - What is Business Analysis?

Hello! Welcome to our Business Analysis blog.  We are Mariane, Harleen, Kent and Parminder, and we are Business Technology Management students at Red River College.  Throughout our Fall term we will be using this blog to share some important concepts regarding Business Analysis.  For our first post, we will start with the basics, and define exactly what is Business Analysis, and other important concepts related to it. According to BABOK, " Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Business analysis enables an enterprise to articulate needs and the rationale for change, and to design and describe solutions that can deliver value. "  Business analysis cannot work without having a representative to intermediate these practices within an enterprise. This professional is called a Business Analyst who is responsible for putting in practice the tasks desc...
Read more

Chapter-12 Fit Criteria and Rationale

Image
FORMALITY GUIDE Horse ventures need to have an exact and effectively shareable comprehension of the significance of necessities. It has been our experience that when the task has numerous partners—which is the standard for horse ventures—various partners relegate various implications to prerequisites. Including a reason and a fit basis to every necessity implies it is for all intents and purposes inconceivable for errors to happen. We prescribe that pony ventures incorporate both of these in their necessities. Elephant ventures must utilize methods of reasoning and fit criteria. These tasks are compelled to deliver a composed determination to be given on to some other gathering, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable necessities is pivotal to elephant ventures on the off chance that the other party is to comprehend and, at that point convey the right item Scale of Measurement Any prerequisite can be ...
Read more

Chapter 5 - Investigating the Work

The starting point for any product that will be built is the owner's work.  The book mentions that business analysts go "trawling" after business requirements.  The first task in the business requirements gathering process is to understand and investigate the work that is being done. Once that's understood, then the "essence needs to be understood, that is the clean picture of the business, without technology.  In this chapter the "Brown Cow Model" is also introduced. Which is divided into 4 parts:  How-Now: shows the implementation of the work as it currently exists, including physical artifacts, people and processors to do the work.   What-Now: shows the real business policy (essence). No machines, people, or organizational departments. Future-What: shows the business as your owner wants to have it, but still with no technology applies to it. Future-How: shows the idealized future business policy, augmented with the technology and people ...
Read more