Contents B1 HIGH-LEVEL REQUIREMENT B1.1 Non-High Level Requirements B1.2 HIGH LEVEL REQUIREMENT B2 MOSCOW RULES B2 USING MOSCOW RULE TO PRIORITIZE HIGH-LEVEL REQUIREMENT EXPLAINATION OF MOSCOW B2.2 Prioritization requirement and justification B1 HIGH-LEVEL REQUIREMENT B1.1 Non-High Level Requirements “The look and feel of the website should be well designed and showcase the products well I also want there to be rotating 3D views of the products” The reason why I state this as a non-high level requirement is because the look and feel of the website isn't an issue or worry to TOG This website will indeed fulfill the need of it users with or without this requirement However, it’s a system requirement that will make the website better and attractive “Customers must be able to register and log in However, it would be great if we could already create accounts for customers we know about and e-mail them their usernames and passwords” The signup and login requirements are fundamentally base on the security part of any system, however, TOG customers don’t need to login because their main purpose of using the website is to place an order, so therefore this means that it can’t be considered as part of the TOG functional requirement but non-functional thus it doesn't have impact on the business procedure of company According to the justification given by me, signup and login shouldn't be high level requirement “The site must load quickly” The reason why I state this as a non-high level requirement is because performance of the system is non-high level requirement and TOD didn't prioritize the requirement for speed as one of their big concern “It is imperative that the website be easy to use, but it should also be visible if people search for glassblowers in the area so they could find us online” Usability of the website wasn’t mentioned as priority because it’s not part of their main goal So obviously, this is non-high level requirement since it’s not even a functional requirement B1.2 HIGH LEVEL REQUIREMENT The system should contain add to cart function: The customer may want to order more than one product at once, this means that they can save each product they want to order and checkout So therefore, this function need to be considered as high level requirement 2 The system should search and browse different products: It is high level requirement because TOG want their customers to find what they want to order easily without any frustration Furthermore, it’s a fundamental requirement that every e-commerce must have otherwise the system may not be considered as successful system, for that reason this requirement it’s a high-level requirement The system should have a way to select a product: This requirement is vital and need in TOG system because any customer that need to order must select that particular item in order to view the item details so therefor, a way to select product is a fictional requirement that will need to deliver for TOG on time and this makes it a high-level requirement The system should provide a way to pay for an item This requirement is a high level in TOG because every customer need to pay the item ordered, for that reason the new systems have to provide a way to pay for the item The system should be able to track the life cycle of an item: This requirement is a highlevel requirement because tracking of order like customer knowing the order status as well as the organization, tracking of order also serve as a security to the order and customers will feel like their items are safe because all the movement are monitored by the organization A way for people to return items if they are unhappy: This is high requirement because TOG end-users might wrong order or broken items which will surely want to return those items to the host organization A way for us to know what we should manufacture, and to make ship: This is high-level because TOG might need to get statistics data on which items sell the most or the most popular item, thus they could know the items to produce more and items to discontinue The system should be secured: It is high-level because it is very important for an ecommerce websites to be secured Nowadays, 90% of e-commerce sites are highly secured and without security in our TOG website, user credentials are highly venerable and this might incur great lost to the organization With the above justification, the requirement should be met at the very early of the development Hosting: This is high-level requirement because end-users need to access the TOG organization website before ordering any of it items B2 MOSCOW RULES B2 USING MOSCOW RULE TO PRIORITIZE HIGH-LEVEL REQUIREMENT NO REQUIREMENT PRIORITY The system should contain add to cart function Must have The system should search and browse different products Must have The system should have a way to select a product: Must have The system should provide a way to pay for an item Should have The system should be able to track the life cycle of an item Must have A way for people to return items if they are unhappy Could have A way for us to know what we should manufacture, and to Could have make ship The system should be secured Should have Customers should be able to contact us for bespoke items and Should have the system should facilitate communication with them, including messages and sending pictures 10 Hosting Must have EXPLAINATION OF MOSCOW When building a software, all propose requirement are vital to the system yet MOSCOW is needed MoSCoW is a method used to organize system requirement and see the significance of every prerequisite to know how to plan its conveyance The MSCW signifies 'Must Have', should Have', 'Could Have' and 'Won't Have' Must Have This are set of the most important requirements in the system In the event that even one of the requirements in the 'Must Have' isn't conveyed, then the entire programming perhaps will be considered as non-successful Those requirements are vital and ought to be conveyed first to the client Should Have This set of requirement are additionally as essential as the 'Must Have' however the ‘should Have' requirement can be postponed a bit till after the 'Must Have' are conveyed first and even without them the system may be considered as successful Could Have This are set of requirement that will be implemented and if and only if must have and should have features are conveyed successfully however, they could be easily left out This requirement is utilized to improve the system and increment fulfillment however not that vital Won’t Have This set of requirements are the least essential to the software and are just actualized later if the clients choose to incorporate them if there is enough time and the system is considered as successful even with or without them B2.2 Prioritization requirement and justification The system should have a way to select a product “Must have” Omission of this at the very first iteration tends to influence the software to invalid This requirement is considered as ‘Must have’ because it is very important for customers to be able to select for an item in order to view item detail before they purchase it So, for that reason, this should be conveyed at the beginning of the iteration The system should contain add to cart function “” Omission of this at the very first iteration tends to influence the software to invalid This requirement is considered as ‘Must have’ because the customers might want to buy more than one item at the same time, so with the add to card feature they will be able to save more than one item at a time and then decide to checkout anytime they want 3 The system should be secured “Could have” Even without this requirement, how to secure the system doesn't stop the software for being legitimate Because it is not one of TOG major business aim however it could be deliver at the second iteration A way for us to know what we should manufacture, and to make ship “Could have” It is not necessary for TOG to know what to manufacture because they already know what to manufacture without the reporting system but they could have this requirement because they will be able to know which product have the highest sell and that will help them in deciding which product to manufacture and deliver more The system should be able to track the life cycle of an item “Must have” It is must feature because it is very important for a customer to be able to track item status of an orders they make and again the admin of the system will be able to know the status of an order for example, order is on process, packaging shipping, location etc For this reason, the requirement its must and should be deliver at the first iteration of the development A way for people to return items if they are unhappy “Could have” This procedure doesn't frequently happen on the grounds that it doesn't influence the business target of TOG association and has almost no effect if not met at the early iteration of the development However, it is vital to give customers a room to return the item they don’t want The system should provide a way to pay for an item “Should have”: It is very important for TOG organization to provide a way for customer to choose their way of payment however, not meeting this feature at very early stage (iteration) will still make the system valid The system should search and browse different products “Must have” Avoiding this requirement at the first iteration may tend to influence the software to invalid because the site may contain much items and which the customers might want to order for an item that they can see immediately So, with the help of the browse, items can be found easily Customers should be able to contact us for bespoke items and the system should facilitate communication with them, including messages and sending pictures “Could have”: This can be met at second iteration if there is enough time however, the system could have it because customers might want to make an enquiry about an item or staffs of the system might also want to contact the customers for confirmation purposes etc 10 Hosting “Must have” It is must for TOG organization website to hosted because without hosting the website, their end-users won’t have the ability to use their website remotely and this requirement have to be met at the first iteration of the system development because without it, the system might be considered as invalid ... their big concern “It is imperative that the website be easy to use, but it should also be visible if people search for glassblowers in the area so they could find us online” Usability of the website... will make the website better and attractive “Customers must be able to register and log in However, it would be great if we could already create accounts for customers we know about and e-mail... have’ because it is very important for customers to be able to select for an item in order to view item detail before they purchase it So, for that reason, this should be conveyed at the beginning