Posts

Showing posts from November, 2018

Non functional requirements

Non functional requirements mean how the product or system is supposed to be in terms of safety, security, usability and many more. They are very useful to make the product attractive or usable. They are used to enhance the quality of the product. These requirements should be properly overlooked or valued otherwise it may lead to failure. Look and feel requirements Look and feel requirements describe the intended spirit, the mood, the style of the product’s appearance. These requirements specify the intention of the appearance, and are not a detailed design of an interface. For example, Fibe TV should meet the designing standards. For this, it is not saying about any technical design nor there is something like its material or specifications. Overall, the statement just says whatever the designing requirements are the Fibe TV should develop some characteristics to meet them. The look and feel includes the following characteristics:       Simple to use...

Chapter 10

Functional requirements vs non-functional requirements: Functional are requirements of what a feature should do. Non-functional are how the feature should work. It is important to know the difference and make sure both are defined in the project or product. Also these requirements guide the work that needs to be done and helps developers know exactly what to do for certain features.

Chapter 10

Functional requirement is something that the product must do in order to operate the product. Level of Detail or Granularity The ease to understand the requirement also depends upon how is it written. If the requirement is written in single line with a single verb then it becomes easy to test it and it reduces the chance of misunderstanding it. Moreover, it increases consistency for stakeholders to define what the product is supposed to do. For example: Bell MTS Fibe TV is maintaining the signal stability. Description and Rationale Description is something that tells what the product is doing. But, it is strongly suggested to add a rationale to prove why the requirement exist or why the product is performing a certain action. For example: Description:   Bell MTS Fibe TV is maintaining the signal stability. Rationale: To increase the customer satisfaction.

Swim Lanes, Personas and Innovation WorkShops

Swim Lanes Swim Lanes provide end to end information of what is happening  in the each business department and what are the requirements to be made after each domain. Personas Persona is an imaginary invented personality which is used in the mass market research criteria. It is useful when there are multiple and similar users in the market and it is difficult to interview each of them. In this case, few people are interviewed and a persona is created based upon their choices and needs. Innovation Workshops These workshops are organized when there are large number of stakeholders. In this team members and stakeholders discuss and provide the innovative ideas to meet the business requirements. The BA facilitate the whole group and these workshops end with innovative ideas to improve the models. It is also useful to develop the existing model and replacing the existing models.

BRG Module 3 BUC and The Brown Cow Model

Business Use case involve some process to achieve a business goal or to make the changes to the existing techniques. For example, To ensure the delivered product work properly or not we follow some process to evaluate the procedure. In Bell MTS whenever a new service is introduced, it's performance is tracked. The online surveys are conducted, then customers are asked to provide the relevant feedback and then that feedback is used to implement the changes and assure the delivery of product or service accurately. In this way, the value of product is enhanced and improved. The Trawling for business also involves the Brown Cow Model . In this business analysts evaluate that what we have at present and what changes are required to be made in the future.They also consider the business focus for today as well as future. Their are basically four quadrants, what are the business cases(today and future each) and how the systems to be used( future and present each)