Introduction to Business Analysis (Group 4)

Fit -   Here the term Fit means a solution that completely satisfies or matches the requirements. It is the solution that does exactly what the requirements says it must do or has the property the requirement says it must have no more and no less. The measurement of the requirement is its fit criterion. Why does Fit need a Criterion? There is a testing activity that demonstrates what the product does, how that product performs a function or posses the desired property. To carry out this activity, the requirements must have a benchmark so that testers can compare the delivered product with the original requirement. The benchmark is the fit criterion, which is a quantification of the requirement that demonstrates the standard to which the product must reach.

Usability Requirements Ease of Use Requirements: This requirement deals with the aspect to make the product usable for the user. The product should have the following properties for the ease of use Efficiency of Use  Ease of remembering    Overall satisfaction Feedback Personalization and Internationizational Requirements: These requirements deal with the way the product can be changed or advanced related to the user's choices or preferences. The product could have the following personalized requirements: Language or spelling preferences Currency choices Personal Configuration options Learning Requirements: These consider how easy it is to learn to use the product or the service. These requirements may differ on the level of technology or any advancement involved in the product. Some services also require for the engineers or the user to train in a specific program to be able to efficiently use the service or the product. Understandability and Politeness Requiremen

Non- functional requirements Non- functional requirements are properties that the functionality must have. The functionality can be represented either by a product use case or its constituent functional requirements. The eight major non-functional requirements for this product use case in chapter 11 are: 1   Look and Feel requirements 2   Performance requirements 3   Maintainability requirements 4    Operational requirements 5     Legal requirements 6    Security requirements     Political requirements 8     Usability requirements Cultural Requirements Cultural requirements specify special factors that would make the product unacceptable because of customs, religion, languages, prejudices, or almost any other aspect of human behavior. These requirements are necessary when we try to sell a product into a different country or in another culture.

In a business context, Ambiguity means doubtfulness of meaning, or uncertainty of intention, that makes a document capable of being understood in two or more senses. It is very necessary for any business to avoid any sort of misunderstandings that may occur due to such ambiguity. Ambiguity while writing requirements is can arise usually and it is very important to be avoided. But before sorting ambiguity, it is essential to understand why or how ambiguity occurs in any business case. The first reason can be the English language. English is a very vast language and can have several meanings for the same word. Such homonyms can lead to many confusing situations if the meaning is misinterpreted by the stakeholder. It is normally suggested to read the requirement or the sentence situation out loud before presenting it to the stakeholders. And after this, communicating with the stakeholder if they are on the same page and understand the meaning we wish them to know, can be helpful to es

Exceptions and Alternatives Exceptions are the unwanted variations but inevitable deviations from the normal case caused by errors of processing and incorrect actions. For example -   The things we don’t want to happen in the project. Alternatives are the allowable variations from the normal case. Alternatives might be considered as the second-best solution for the any kind of work.   For example -   Things we want as our backup in the project. Technological Requirements Technical requirements pertain to the technical aspects that our system must fulfill. Technological requirements are functionality that is needed purely because of the technology chosen by the company to carry out projects. Technological requirements are not there for business reasons, but rather to make the chosen implementation work. Stakeholders must understand clearly why a requirement appears in the specification, so it is important that the technological requirements are not introduced before the

The BA can begin the process of defining, articulating, and communicating project success criteria as soon as he/she has a strong involvement in the requirements process and familiarity with the product and the project context.  The attempt to define what kind of compensation between competing demands the stakeholders are willing to accept are much more important project success criteria than if the project should be delivered on time, and within budget and with complete specifications. Some people argue that the definition of success criteria is the project manager role; however, BAs can carry out this task - because some have the experience and knowledge to develop this activity.  Ideally, all stakeholder analysis should be carried out jointly between BA and PM. In fact, this is a more efficient and effective use for the success of the knowledge project that BA has already achieved. The BA can play an important role by acting as an "deputy PM". Ha