Bison Transport

Chapter -12 Fit Criteria and Rationale Fit Criteria: Fit Criteria is used for functional requirements. A functional requirement is something that the product must be done action it must take. The fit criterion specifies how you will know that the product has successfully carried out that action. It quantifies the behavior, the performance or some other quality of the requirement. Formality Guide: Let’s take example of the stories, as when we are listening to the stories, we must pay particularly attention to the reason behind the story as it is same as with the rationale as it makes the important contribution in the ending of the product. 1.Rabbit Project: In the rabbit project they use the blog or the wiki to find the non-functional requirements. As it is suggest deriving the appropriate fit criterion, confirming with the stakeholders and note the test case using that fit criterion. 2.Horse Project: As we know horse projects have the different number of the stakehold...

CHAPTER-11 NON-FUNCTIONAL REQUIREMENTS NON-FUNCTIONAL REQUIREMENTS: The non-functional requirements define that specifies criteria that can be used to judge the operation of a system as compared to specific behaviours. They describe about how your does the things it does. Non-functional requirements are often called ‘quality attributes’ of a system. In other words, non-functional requirements are qualities, quality goals and quality of service requirements. FORMALITY GUIDE: Rabbit projects should use the requirements specifications template as a checklist of non-functional requirements types. Non-functional requirements of all stakeholders are capture in horse projects. Elephant projects have a need to capture all of their requirements in written form. FUNCTIONAL VS NON-FUNCTIONAL REQUIREMENT: Functional requirement is any requirement which specifies what the system should do. In other words, a functional requirement describes a particular behaviour...

Blog 9 (Pawandeep Kaur) CHAPTER – 10 Functional Requirements Functional Requirements:   Functional requirements describe what the product has to do to support and enable the owner’s work. They should be, as far as possible, independent of the technology used by the eventual product. The functional requirements specify the product to be developed, so they must contain sufficient detail for the developer to build the correct product with only the minimum of clarification and explanation from the requirements analyst and the stakeholders. Description and Rationale:   in simple words I can say that a statement, picture in words, or account that describes;  descriptive representation . the act or method of describing . Here is an example of description: Description: The product shall record roads that have been treated. now to describe the rational: The rationale indicates whether the requirement is worthy of some attention. Its different keywords to define i...

Chapter-8 Starting the solution Starting the solution means focus on the third and fourth quadrant rather than first and second of brown cow model which make links towards physical world, from policy to technology, from problem to solution; from purpose to design, where in the fourth quadrant, we begin the design of solution to the business problem. Iterative development This process depends on frequent releases of software to test the design suitability. In some cases, this process become time consuming due to lack of actual understanding of problem by the stakeholders. Basically, the actual need for this process depend on how you and your stakeholders identify the actual need of the solution instead of giving priority how you are developing software. Essential Business The word essential business relates to essence of the business which refer above the horizontal line that divides the ‘how’ and the ‘what’. These views show the what-now and the future-what quadrants...

CHAPTER-7 UNDERSTANDING THE REAL PROBLEM If the real problem was never stated, it is impossible to understood it correctly. When working with requirements it is important to focus on ideas rather than solutions. Abstraction can help us to get the real problem. ABSTRACTION: It is simply a business process. Is the idea, not the implementation.   A business process is set of activities no matter how you implement it. It does not matter whether the process (now or in the future) is done by a person, computer, robot, mechanical device or anything else.   THE ESSENCE: We refer to as the essence of the business above the horizontal line that divides the ‘how’ and the ‘what’. These views show the what-now and the future-what quadrants. The reason for spending time above the line is to discover the real problem and avoid what happens in many organizations where people waste their entire 60 minutes building solutions to the wrong problems. SOLVING T...

Chapter-5 Investigating the work   According to book information, investing the work means become known about the activities and actions while spending the portion of time which will increase the chances of making a positive impact on the business and it only become possible when you have deep understanding of process and then you able to do changes and generate new ideas when you need to do improvement in services on various stages of process. Trawling the business The word trawling means method of fishing with help of nets and similar actions are required in the business sector. In other words, individual able to stand at the stage where he or she know the way of catching every possible requirement and make the impossible things possible with the help of experience and trawling techniques. Trawling and business use cases The business use cases are the work's responses to the business events. These are studied until the analyst understands the desired functio...

Chapter-6   Scenarios Scenarios : According to the book, the proper meaning of the Scenarios is giving the outline of the project or the steps that should be followed in the sequential order to complete the requirements. It is the neutral medium and the simpler way to understand the requirements of the stakeholders. In this ‘plot’ means that the target or the aim should be divided into the different series or the steps for the success of the project. It also helps the user to explain the project in the better way and here each chunk or the step is called business use case which helps the user in the problems and success of the project. We can take the different examples such as: passing airline check-in, making of pasta etc. Diagramming the Scenario: This type of the scenarios is required by the analysts or the stakeholders for the explanation of the functions performed by the business use case.  It basically depends how your stakeholders wants your idea in text ...