Section B – High level requirements analysis and MoSCoW prioritisation (40%of the marks) Name: Hoang Tien Dat ID: GCH15336 B1 Review the ‘high level requirements’ list given at the end of Appendix A Definition of high level requirement Requirements are descriptions of the services that a software system must provide And high level requirement is the set of basic requirements, the core requirements to create the website It is the functional requirement provided to the user However, it is just a frame, not details about advanced requirements such as interface, structure, etc To better understand, we'll look at the following example: High level requirement: Login function Low level requirement: login interface must be beautiful, bright color suitable for website content, password must be hidden, B1.1 Identify any of the requirements that you feel are not appropriate high level requirements, giving your reasons for this Person Ben Brode (CFO) Not appropriate high level requirements - We also need the following: * The site should be easy to use and quick to load * We probably need to arrange for this site to actually “be” on the internet * We need to register the web URL Walk2Live.co.uk The system should replace the current systems at our franchise centres - The look and feel of the website should resemble the healthy lifestyle we are selling Laine Conway (Marketing) We must ensure that people who use the website can register with their email address and and log in so we can Reasons Here are some additional requirements for interfaces, performance, and not high levels this is not a system function, it is a request to change old system to new This is not a high level cause it is not a factor, the core requirement for website creation, this is a requirement for improving the look and feel of the store To say that people can create accounts and log in, it is a functional or high level have their details to send them marketing materials John Oldman (Consultant) Paige McMan (Franchise owner) For the most part we can use the system I have already written You just need to write the code to connect the database to the frontend – I’ve already created the database in MS Access - We need to ensure that a bookkeeping service is built into the new system, as this will make my job easier - Could I ship online orders in my area and get the money for those sales? Clients can use the system like Facebook, to communicate with each other and build an online community They should be able to find out who are in their classes and contact those people requirement But he says everyone can create their email account, it will not be a high level anymore A used to use old system, and only need to edit some number in the database It is not a required level cause it is not functional requirement for system This is a requirement that is quite important, but its purpose is to reduce the workload of accounting, they can still otherwise We can add it later This is a question, can they ship in the area and receive the ship money It's not a high level requirement, the requirement is just a suggestion to earn more for the members of the company This is a way for members to communicate with each other, we can use a lot of other ways In general, this is not a high level requirement B1.2 Rewrite, and add to, the list to end up with a total of 10-12 high level requirements that you feel are required for building the system Briefly justify the need for each of your high level requirements against information you have gathered from the case study Old high-level requirements Customers must be able to log in Customers must be able to buy things Customers must be able to search and browse products to buy, whether they are logged in or Rewritten and justify high-level requirements Function login for customers so they can easily and quickly order Online shopping functionality can be implemented directly on the website for customers, even if they log in or not This saves them time and does not have to go to the store Product search and browse can be used with everyone, even if they are not signed in This not A way to select items A way to pay for an item A way for us to know what we should pack and ship A way for people to return items they are unhappy with My centre has links with lots of charities and it would be great if the new system could communicate with theirs in a way If not, I need to be able to at least keep track of charity events we are involved in (when, where, who the charity is, how proceeds are managed, etc) I need to be able to order items from the central office to sell in my store helps new customers not have to spend too much time signing up for a login, Cart functions must be available to help customers purchase multiple products at a time Customers can choose the form of payment for their invoice, some payment methods such as, payment upon receipt, ATM card, visa, We have a lot of orders, we need to know what orders have been delivered and have not been assigned to be able to package and ship orders When customers are not satisfied with the product, they can return This is an indispensable function, so we need to have ways to pay orders like watch the goods right when viewed, directly at the store, The center is affiliated with many charities, we need at least some functionality to keep track of the events that the center is involved in Moreover, it is a great advantage to be able to communicate with everyone in order to promote participation in charitable organizations Out of stock is a great influence if not prepared in advance The center needs a cart management function in the juice bar When the goods are nearly ready, they can be prepared B2 Use the MoSCoW rules to prioritise the requirements in your updated ‘high level requirements list’ B2.1 Produce an updated ‘high level requirements list’ clearly showing the prioritization you have given to each of your requirements Updated High level requirement Function login for customers so they can easily and quickly order Priority Should have Reasons Login function is a function to help familiar customers purchase, they may be easier in the purchase process because they not Online shopping functionality can be implemented directly on the website for customers, even if they log in or not This saves them time and does not have to go to the store Product search and browse can be used with everyone, even if they are not signed in This helps new customers not have to spend too much time signing up for a login, Cart functions must be available to help customers purchase multiple products at a time Must have Customers can choose the form of payment for their invoice, some payment methods such as, payment upon receipt, ATM card, visa, We have a lot of orders, we need to know what orders have been delivered and have not been assigned to be able to package and ship orders When customers are not satisfied with the product, they can return This is an indispensable function, so we need to have ways to pay orders like watch the goods right when viewed, directly at the store, The center is affiliated with many charities, we need at least some functionality to keep track of the events that the center is involved in Moreover, it is a great advantage to be able to Should have have to re-enter personal information, However, they can still buy goods that no login required so i leave it as it “should haves” An online sales web can not be impossible to order online, right? So this is “must haves” Must have If you can not browse and search products, customers can choose the item they want to buy it right So it is “must have” Should have Cart function is extremely important, most people want to buy more than one product at a time However they can still buy without this function, so it is just “should haves” Optional payment functions may be available if the company can meet However, they may still be forced to pay in certain forms if the company has only one way of paying It is "Should haves" To ensure fairness for pre-ordered invoices, this power is also very important we should have Should have Must have Return unwanted orders, this is an indispensable function it is must have Must have The customer's request is almost certainly one of two, which seems very important so I give it a must have communicate with everyone in order to promote participation in charitable organizations Out of stock is a great influence Could have if not prepared in advance The center needs a cart management function in the juice bar When the goods are nearly ready, they can be prepared You can manage the stock manually even though it is quite hard, but this function may or may not, depending on the time of the project B2.2 Explain how you set about prioritising the requirements and justify your reasons for the decisions that you made I applied the MoSCoW method to project management more clearly Customer requirements are ordered in order of priority to minimize their cost or unrealistic It is easier to develop or support the project by ignoring the less important requirements By focusing on key requirements, you will complete the project with a product that can be sold and meet the minimum requirements Every participant knows what needs to be done first, when it must be completed and why it is important By prioritizing requests, a project becomes more manageable and ensures progress M - MUST HAVES - These are minimum requirements and should be determined before final results are achieved If this requirement is not met, the project will not be successful and the product will not be usable S - SHOULD HAVES - these are the most requested and desired additions Priority for these requirements is quite high, but not essential for final product availability C - COULD HAVES - these conditions can be considered if time permits Otherwise neither the problem nor the negative impact on the end result W - WILL NOT HAVES These are future expectations that are often difficult or will take a lot of time to implement If it's simply not feasible, it's best not to waste any resources on it My reasons for the decisions that you made Check out column of the table of section 2.2