Section B – High level requirements analysis and MoSCoW prioritisation (40% of the marks) What is high level requirements? High level requirements are required system requirements and must be present in every system These requirements will determine the flexibility and stability of systems within an organization or company, which are important requirements in systems of corporate organizations and corporations For example: Buy and sell products in the program -> important functions of the program -> high level requirements Log in, log out -> functionality should be in the program -> low level requirements Identify any of the requirements that you feel are not appropriate high level requirements, giving your reasons for this In the list of requirements of each person, I removed some of the requirements are not high lever requirement These requirements are just the constraint or it is the functionality that should be in the system so that the system can increase performance and stability Those requirements include: Ben Brode (CFO) With this requirement, I find “The look and feel of the website should resemble the healthy lifestyle we are selling” that is not a high level requirement because the system only main functions include: logging, purchasing products and searching for products in the system System interface design can be done last and it is just a small development process in that system development Laine Conway (Marketing) “A way for people to return items they are unhappy with” is not a high lever requirement because this is a function should be in the system to help users can link with the store and the manufacturer so they can refund their products Paige McMan (Franchise owner) The association with charity is not a high-level requirement because they say that this function may or may not in the system Sue Thompson (Franchise owner) Managing the charity is not a high level requirement because the system is used for internal purposes But charity is beyond the reach of the company, so this function is not a high level requirement 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 Based on the information above, in order to build a high-performance and stable system, I have a list of the high-level requirements that the systems require including: Customers must be able to log in: Log on as the first criterion when developing the system It helps the system distinguish users and distinguish the functions of each system user A way to select items: The selection is also quite important, the user can create events of the system activity on the object information A way to pay for an item: The user can purchase products on the system, and the administrator can know what products are sold on the system Database design: This is where data can be stored and it is easy to query data, so it is used in all computer systems Data dissemination: It is very important that the company has many small stores Data distribution enables stores to connect to the company through a computer network Object management: The program can manage objects in the system with the management functions developed in the system System management will bring high accuracy and safety The system can store feedback from users: This function allows the administrator to know the wishes of users with this system Multi-platform operating system: Cross platform will help many users to use this system The system is stable: Damaged data or faulty systems not only affect the operation of the company, but also damage the system causing the system to fail The system needs to be upgraded and maintained regularly Accept third party connections: If third parties need information from your system You can share that information by allowing them to connect to the system to get your information, some systems now use this feature to reduce costs and convenience in the computer system The above requirements will help the system operate smoothly and efficiently These are mandatory standards that every system of every company in the world should follow and implement Use the MoSCoW rules to prioritise the requirements in your updated ‘high level requirements list’ Produce an updated ‘high level requirements list’ clearly showing the prioritization you have given to each of your requirements No 10 High level requirement Customers must be able to log in A way to select items A way to pay for an item Database design Data dissemination Object management The system can store feedback from users Multi-platform operating system The system is stable Accept third party connections Priority Must have Must have Must have Should have Must have Must have Could have Should have Must have Won’t have Time boxing 1: No High level requirement Customers must be able to log in A way to select items A way to pay for an item Data dissemination Object management Database design Priority Must have Must have Must have Must have Must have Should have These high level requirements will be developed first because these requirements are very important, so the development of the important and special functions of the program will be designed first Time boxing 2: No High level requirement Multi-platform operating system The system is stable Priority Should have Must have For systems that are generally used and stable, the following requirements will be initiated, but previous requirements must be finished Time boxing 3: No High level requirement The system can store feedback from users Accept third party connections Priority Could have Won’t have These requirements are not important if your system is a small system But if you want more system tasks or more useful, you should develop them Explain how you set about prioritizing the requirements and justify your reasons for the decisions that you made Customers must be able to log in: Log on as the first criterion when developing the system It helps the system distinguish users and distinguish the functions of each system user A way to select items: The selection is also quite important, the user can create events of the system activity on the object information A way to pay for an item: The user can purchase products on the system, and the administrator can know what products are sold on the system Database design: This is important and must have in system, It helps the system to not lose data and easily query the data Data dissemination: It is very important that the company has many small stores Data distribution enables stores to connect to the company through a computer network Object management: Along with the database, this is a function that should be in the system as it can manage all information of the object on the system The system can store feedback from users: This function allows the administrator to know the wishes of users with this system Multi-platform operating system: Cross platform will help many users to use this system The system is stable: It is important that the number of users always come with the number of devices that can run the system Accept third party connections: It only important if you want to share data for third parties ... have Won’t have Time boxing 1: No High level requirement Customers must be able to log in A way to select items A way to pay for an item Data dissemination Object management Database design Priority... A way to pay for an item Database design Data dissemination Object management The system can store feedback from users Multi-platform operating system The system is stable Accept third party connections... data can be stored and it is easy to query data, so it is used in all computer systems Data dissemination: It is very important that the company has many small stores Data distribution enables stores