Coursework part b by nguyen bang vu

Nguyen Bang Vu Supervisor: Pham Thuy Duong September 2018 High level requirements analysis and MoSCoW prioritisation Abstract This report will implement the knowledge about high level requirements and timeboxing into part B of the coursework by analyse, modify the requirements mentioned in the case study Furthermore, prioritising requirements will be included in Chapter to clearly show the understanding of Moscow rules that student have been learnt at school Every statement made in this report will be explained and back up with evidences and knowledge learnt from this course Table of contents Abstract Chapter 1: Review the ‘high level requirements’ list given in the scenario 1.1 Identify any of the requirements that are not appropriate high level requirements with reasons 1.2 Rewrite high level requirements and justify the need of each statement from the case study Chapter 2: Use the MoSCoW rules to prioritise the requirements in updated ‘high level requirements list’ 2.1 Produce an updated ‘high level requirements list’ clearly showing the prioritisation for each requirement 2.2 Explain how you set about prioritising the requirements and justify your reasons for the decisions Appendix Chapter 1: Review the ‘high level requirements’ list given in the scenario 1.1 Identify any of the requirements that are not appropriate high level requirements with reasons In this case study, there are many requirements that did not meet the criteria for high level requirements which will be outlined and explained in this section ​“​The site should be easy to use and quick to load​” stated by Ben Brode is not a high level requirement because it is not realistic In order to address his statement, he have to outline what is required to make the website easier to use, what technology should be implemented to increase the speed of the website Also, ​“​The look and feel of the website should resemble the healthy lifestyle we are selling” i​ s too ambiguous to be high level requirement, abstract words such as “The look and feel” is too vague for developer to understand what kind of design Ben would like to be High level requirements must have clear, on-point statement to avoid confusion in further stages After an observation on all requirements, there are alot of requirements that start with “We probably need to arrange for this site to actually “be” on the internet” ​is not a high level requirement since the statement itself is not realistic because using ambiguous word such as “be” in this case show that the person who write the statement doesn’t have adequate understanding about an online system which can lead to misconception in the future “People should be able to ask us questions about products and services so we can link them to the correct merchandise or franchise.” is not a high level requirement since the statement was too detailed and many words should be reduced or grouped into more simple phrases and requirements should not contain self-opinion words such as “we”, “us” ​“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” ​also has the above problems The whole statement could simply reduced such as “ Establish connection to database” instead Also, high requirement only include functions on user side only so connecting to database is not a valid requirement in this scenario 1.2 Rewrite high level requirements and justify the need of each statement from the case study This section will include a new list of high-level requirements that is based on the case-study The list may contains new requirements or rewrite existing requirement from Appendix A and each of the changes will be explained with gathered information from the scenario Also, a business case is produced at the Appendix of this report to identify the goals of the project which can aid the process of producing a high level document High level requirement list: Customer should be able to register and log in to the system Customer can search for products Customer can buy products on the page Admin can view sale report on the system Admin can manage everything on the system An ordering system for market material and products for local stores A community for communication process with charity organization Online payment system for staff Communication system for members and staffs 10 A rating system for customer reviews 11 A bookkeeping service to aid the process of management 12 An online system for customers to make bookings, pay fees and join clubs The first purpose of the system is to establish an e-commerce system so users should be able to buy products as well as register to save their information online Also, if the product list is large, they need to be able to search for specific one Requirements 1, 2, are adequate to implement the most basic e-commerce system The second main goal of the project is implementing central management system and interact with charity organizations Admin will need features such as add,delete,update,search to manage many things on the system and the sale should be able to summarized into reports to help admin to keep track of data and statistics According to the case study, a community that allow communication such as chatting should be implemented to maintain relationship with charities The above requirements are accomplished by requirements 4, 5, 6, on the list Any requirements after are less important than the first half because of Moscow rules which will be explained later and they acts as support functions that can improve the performance of main requirements or provide better experience for user in the whole system Requirements 8, 9, 11 can make use of management system to apply more online functions for staffs and support existing management features while numer 10 and 12 aid e-commerce system by providing more function and extend the feature from buying products to online booking and join classes Chapter 2: Use the MoSCoW rules to prioritise the requirements in updated ‘high level requirements list’ 2.1 Produce an updated ‘high level requirements list’ clearly showing the prioritisation for each requirement Requirements Priority Customer should be able to register and log in to the system Must have Customer can search for products Must have Customer can buy products on the page Must have Admin can view sale report on the system Must have Admin can manage everything on the system Must have An ordering system for market material and products for local stores Must have A community for communication process with charity organization Must have Online payment for staff Could have Communication system for members and staffs Could have A rating system for customer reviews Should have A bookkeeping service to aid the process of management Should have An online system for customers to make bookings, pay fees and join clubs Should have 2.2 Explain how you set about prioritising the requirements and justify your reasons for the decisions The prioritising process was taken according to Moscow rules that include identifying Must have, Should have, Could have and Won’t have requirements The updated requirement list is based on the list from task which include an e-commerce and a central management system according to the case study In general, the e-commerce system has more priority since the manager require the marketing system to be completed in the first months and the central management system only need to be done as beta version in months afterward and “Must have” requirements should only occupy 60% of the list In the e-commerce system, the first step is to identify priorities of requirements Requirements which belong to “won’t have” priority will not be included in this list because the list is limited to only 10 to 12 requirements so only important and interesting requirements are visible in the list “Must have” functions include buying products, register and searching functions since they are the most basic functions of the system that allow online trading to take place Rating system and online booking are classified as “Should have” requirements since they are not mentioned in the case study but it can provide better experience for customer along with e-commerce system About time distribution, “Must have” requirements should occupy about 60% at maximum of project time according to Moscow prioritize rules However, since the case study is limited at identifying requirements, 40% of the remaining time is focused on “ Should have” requirement The central management system is much easier to identify crucial requirements since “Must have” requirements only need basic management task such as Create, Update, Delete, View, Search which are grouped into one requirement Local ordering system and sale report are also essential because they are mentioned in the case study As a managing system, it is also important to communicate so a community allow interaction for staffs is needed but it belong to “Should have” requirement since the workshop did not mention about this Bookkeeping acts as support function for management task so it is also classified as “Should have” requirement Other requirements that can improve the system such as online staff payment, communication between admin and staffs are classified as “Could have” requirements because they are not relevant to the general goal of the project but they could help in some scenario By using Moscow rule, “Must have” requirements occupy 60% of the project time, “Should have” occupy 25% and “Could have” take the rest 15% of the time Appendix Business Case Introduction: W2L is a franchise company which started as a walking organization and now it became a fitness centre that include spinning, yoga and pilates classes along with walking and running club It also has its own health food and supplement that aid training process that members can buy at the center The company is aiming to corporate with charities organizations to host walkathons and developing healthy products marketing campaign to distribute to other center Ben, the CFO of the company wants to develop a system that can allow a franchise to keep track of their own members, classes and programmes, and an E-commerce system for marketing materials, health food and supplement range In addition, the system would help franchises that have links to charities to manage those relationships as well Business objectives: The project is expected to implement an effective and easy way to manage facilities and members for all franchise, maintain relationship with charities organization and lastly, it plays an important role in marketing campaign which is a vital role in selling healthy products of W2L in the future Current Situations and problems/opportunities statement: Many franchise owner doesn’t like the idea of selling products online and they fear that it could affects their own sale However, Ben still implement this requirements into the plan which means this part of the system may not work effectively since it doesn’t receive many support from participants Critical assumptions and constraints: In order to make this project become successful, a large number of manpower at shipping department need to be implemented to distribute products to other centre and this can cost a lot of money Analysis of options and recommendations: The only available option for this project is building an e-commerce website that allow all tasks to be done and executed quickly Management tasks and online buying need to be real-time accurate which means building an Internet based project is the best option available Preliminary Project Requirement: The main requirements of this project include basic features of an e-commerce sites which are Log-in, buy products, search products and product sale reports for admin For centralised system, franchises must be able to keep track and modify classes, members schedules, And members must be able to register and join classes Since integrating with charity is also in the plan, franchise should be able to communicate with them through the website Schedule Estimation: The project manager confirmed that e-commerce system will be developed and ready to run at months period and another months to release the beta version of the centralised system 10 ...Abstract This report will implement the knowledge about high level requirements and timeboxing into part B of the coursework by analyse, modify the requirements... must be able to keep track and modify classes, members schedules, And members must be able to register and join classes Since integrating with charity is also in the plan, franchise should be able... project is building an e-commerce website that allow all tasks to be done and executed quickly Management tasks and online buying need to be real-time accurate which means building an Internet based