Posts

CHAPTER 12: FIT CRITERIA AND RATIONALE

-
CHAPTER 12: FIT CRITERIA AND RATIONALE What are fit criteria and the rationale of a requirement? There are some differences between the fit criteria of functional and non-functional requirements. The fit criteria of functional requirements determine how business analysts will realize that the product has effectively accomplished that activity. For functional requirements, it is hardly possible to decide the scales of measurement: The action is either finished or not finished. Completion relies upon satisfying an authority that the product has correctly performed the action. The authority mentioned can be the source of the information or the nearby system that commenced the action. Business analysts can write functional requirements for various types of action. The fit criteria of non-functional requirements is a measure of those qualities such as usability, look and feel, performance, operational, and so on. In the first place, some of the nonfunctional requirements may appear ...
3 comments
Read more

Chapter 10: Functional requirement

-
Chapter 10:  Functional requirement Question 1. What is the definition of the functional requirements? Answer The functional requirement mainly specifies what the product or service must to satisfy the work and business. In other words, we can say the action that product or service must do and anything that relates to the product or service functionality. Functional requirement is not dependent on the technology used by the product or service. Sometimes, it is collaborated with the technical requirements of the product. There is should be the full detail how the product will perform. For example, for TD project a functional requirement is “The system must allow the users to enter the case log into the SharePoint”. Question 2 .What is description and rationale in the requirement and why we need it? Answer In order to build a clearer solution for developer to build a requirement need a rationale and description. The description points out the what in the requirement and...
3 comments
Read more

Chapter 11

-
Chapter 11 - Non-functional Requirements Q-1 What are Non-functional requirements? Ans : Non-functional requirement specifies the quality attribute of a software system. They judge the software system based on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to the success of the software system. Example of non-functional requirement is, "How fast does the website load?". Failing to meet non-functional requirements can result in systems that fail to satisfy user needs. Q-2 What is the difference between Functional and Non-functional requirements? Ans: Functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be. Functional requirements along with requirement analysis help identify missing requirements while the advantage of non-functional requirement is that it helps you to ensure good user experience and ease of operating the software. A funct...
3 comments
Read more

Chapter 5

-
Image
Chapter 5 - Investigating the Work Q-1 What is trawling the Business? Ans: Trawling is the activity of investigating. It is central to the requirements process. Although, in general, trawling is a method of fishing but, in the context of business, it's used methodologically to catch every possible requirement. Once the blastoff is completed, the business analysts start trawling the work to learn and understand its functionality. It uses the outputs of blastoff activity as its starting point for investigating the work and accumulating knowledge about it. Business Analysts use many trawling techniques to discover the true nature of work. Q-2 What is Brown Cow Model? Ans: The Brown Cow Model is a way of reducing the complexity of systems modelling by dividing the model's viewpoints. The Brown Cow Model illustrates four points of view that help to uncover the real business problem and identify useful innovations. The four quadrants which are - What-Now, What-Future, How-No...
3 comments
Read more

Chapter 8: Starting the Solution

-
Chapter 8: Starting the Solution Question 1. What is a persona and when is it used? Answer: A persona is a virtual character that represents a large number of customers (or users) with similar characteristics or demographics. Personas are constructed from data collected through surveys of your target audience and so represent most of your eventual users. It is important that you construct your persona with enough characteristics for you and your team to feel that they understand it well enough to know what it wants.  Personas are used when you have a large number of in-house users, or a large number of customers who will be using the product. The business analysts and designers use a persona as their source of user specific requirements. Question 2. What do you mean by "Designing the User Experience" ? Answer: Designing the whole of the user experience is the best way to come up with a product that makes people want to buy it and/or use it. Experience de...
3 comments
Read more

Chapter 7 Understanding the right Problem

-
Image
Chapter 7 Understanding the right Problem Question 1. What the brown cow model does? Answer The brown cow model is all about the number of ways (viewpoints) in which we can look at the work area, when we are investigating work area. In brown cow model there are four quadrants namely- How Now, What Now, Future what, How Future.   How Now is the place to start in most of the times and it shows the implementation of the work as it currently exists. Which includes physical artifacts, people that are used to do the work.   What Now shows the real business policy or the essence of the work. Future What shows the business as your owner want to have it in the future but still with technical neutrality that being used to implement that business. Future How shows the future business policy with the use of technology that being used to implement it. Question 2.   What are persons and how it is useful? Answer ...
3 comments
Read more

CHAPTER 6: SCENARIOS

-
Image
CHAPTER 6: SCENARIOS What is the scenario? Why to have scenarios in a project? Scenarios are the future events which are foreseen by considering various feasible results or outcomes. One exact picture of the future is not clearly shown in the scenario. Instead, the scenario presents several alternative future developments. As a result, a scope of possible future outcomes is observable. The outcomes and the development paths leading to the outcomes are both observable. Scenario helps business analysts facilitate business decisions by taking into account a number of potential developments and possible future events in business environments. Business analysts can use scenarios in the business use case workshops and even in risk management of a project. Why should business analysts concern about the essence of business? The essence of business is in the above quadrants of the Brown Cow Model, the What-Now and Future-What views which is the reason why focusing on the essence o...
3 comments
Read more