SECTION B – REQUIREMENT ANALYSIS Taking a gander at the outline rundown of the ‘high level requirements’ from the facilitated workshop session held at TOG for the development of A Touch of Glass system with the key staffs of the organization in attendance, it can deduce that some requirements considered to be high level requirements are inappropriate to be called high level requirements B1 High Level Requirements and Inappropriate High-Level Requirements Having a brief understanding on what high level requirements, functional and non -functional requirement will give an insight to answer this question High-level requirements: High-level requirements are well defined statement portraying the future system to be built which simply provide guidance to the principle key issues and not point by point There are in accord with business processes taken at feasibility phase High-level requirements are further divided into functional and non-functional requirements Functional Requirements: Functional Requirements depict what a system should and also describe the performance of the system in accordance with its functionality, this has to with what part of the system can be deliver to user in a fix timebox(es) Non- Functional Requirements: Non- Functional Requirements are related to the usability of the system by describing how the system should behave or work It places a constraint on the behavior of the system it can equally be as define the quality attributes for a system examples are: Reliability, Usability, Capacity, Scalability, Maintainability, Manageability, security and so on A Touch of Glass System Requirements Requirements Register and login Customer search and browse different product Existing customer should have an account to login Well design Look and feel of the website Rotating 3D views of the Products Sign up for tours and glass blowing classes Persons’ Suggestions References Sarah Bromley (Company Owner and manager) Willow Grant (Customer care and social media) Sarah Bromley (Company owner and manager) Page of case study Sarah Bromley (Company owner and manager) Sarah Bromley (Company owner and manager) Sarah Bromley (Company owner and manager) Sarah Bromley (Company owner and manager) Page of case study Page of case study Page of case study Page of case study Page of case study The site must load quickly Select a product Sarah Bromley (Company owner and manager) Thomas Enslin (Packing and Shipping) Pay for an item Thomas Enslin (Packing and Shipping) Specify Shipping method and what to be manufactured People create their own designs Thomas Enslin (Packing and Shipping) Return items their unhappy about Thomas Enslin (Packing and Shipping) Ask questions about the process and items or about the tours and classes Checkout Gather statistics on item popularity Willow Grant (Customer care and social media) Willow Grant (Customer care and social media) Willow Grant (Customer care and social media) Willow Grant (Customer care and social media), Sarah Bromley (Company owner and manager) Willow Grant (Customer care and social media) Willow Grant (Customer care and social media) Frederic Smith (Operations) The site must be safe and secure Frederic Smith (Operations) Track item lifecycle Frederic Smith (Operations) Book keeping service for the new system Mary Crowley (Accounts) Easy to use Mary Crowley (Accounts) Reporting system for graphs and figures on sale and marketing Mary Crowley (Accounts) Feedback Quick and easy communication including messages and sending pictures Hosting Register URL Thomas Enslin (Packing and Shipping), Frederic Smith (Operations) Page of case study Page of case study Page of case study Page of case study Page of case study, Page 10 of case study Page of case study Page of case study Page of case study Page of case study Page of case study Page of case study Page 10 of case study Page 10 of case study Page 10 of case study Page 10 of case study Page 10 of case study Page 10 of case study Page 10 of case study B1.1 High level requirements (inappropriate) Requirements Site Framework Well design Look and feel of the website Persons’ Suggestions References Sarah Bromley (Company owner and manager) Page of case study Mary Crowley (Accounts) Page 10 of case study Sarah Bromley (Company owner and manager) Sarah Bromley (Company owner and manager) Page of case study Willow Grant (Customer care and social media), Sarah Bromley (Company owner and manager) Page of case study Frederic Smith (Operations) Page 10 of case study Bookkeeping service for the new system Mary Crowley (Accounts) Page 10 of case study Gather statistics on item popularity Frederic Smith (Operations) Page 10 of case study Reporting system for graphs and figures on sale and marketing Mary Crowley (Accounts) Page 10 of case study Return items their unhappy about Thomas Enslin (Packing and Shipping) Page of case study Specify Shipping method and what to be manufactured Thomas Enslin (Packing and Shipping) Page of case study Usability Easy to use Performance Rotating 3D views of the Products The site must load quickly Quick and easy communication including messages and sending pictures Page of case study Security The site must be safe and secure Order Maintenance Feedback Track item lifecycle Willow Grant (Customer care and social media) Frederic Smith (Operations) Page of case study Willow Grant (Customer care and social media) Page of case study Page 10 of case study Help Ask questions about the process and items or about the tours and classes Reasons why these requirements are not appropriate for high-level requirements Well design Look and feel of the website: This feature is not a critical requirement for A Touch of Glass system to run This can be improved and integrated later into the website when the most essential are achieved The site must load quickly: This functionality is not about what the system should but rather it describes the behavior and performance of A Touch of Glass system That is, how the system should behave Therefore, it is a non-functional requirement Rotating 3D views of the Products: This is not an urgent requirement for A Touch of Glass system to run since It’s about the behavior of the system, how the display of product should look like This can be improved and included later Safe and secure: This requirement shows how the system should behave not what the system can deliver to the user applying incremental approach by means of timeboxing Therefore, it is not an urgent feature required to create the system as it is considered to be a non-functional requirement Gather statistics on item popularity: This requirement is not an urgent feature to make the Touch of Glass system to run since it involves the collection of data regarding the popularities of items This can cause the system to be complex due to increase in data Ask questions about the process and items or about the tours and classes: This functionality is not very urgent for the startup of A Touch of a Glass system, it be integrated later Report system service for graph and figure on sale and marketing: This requirement is not good to be consider as high-level requirement to get the Touch of Glass system running within months of the start of the project as proposed because it has to with collection of information regarding graphs and sales which will make the complete system slow As a result of the system been slow, customer will feel reluctant to visit the website Quick and easy communication including messages and sending pictures: Functional requirements are requirements needed to start up the system, but this feature is not needed to start up the system Therefore, it is functional requirement Specify Shipping method and what to be manufactured: This feature is not a feature main to start up the system It can be added later on thus, it is not a functional requirement Return items their unhappy about: This requirement is a rare feature as it is being used once in a while by the customers, so it is not an urgent requirement to start up the system Track item lifecycle: It is not every customer that will have the time to track the order processes, after the payment order is successfully done This means the system can still function well without this feature As such it is not a function requirement Bookkeeping service for the new system: Bookkeeping of the system is only done appropriately which the system is already running, as it is not needed immediately as a startup feature, but it is an important feature needed after other features are already functioning, so it is regarded as a functional requirement Feedback: This is not a high-level requirement because customer might decide to give feedback or not to give feedback So, with or without this feature the system will run B1.2 Re-Writing High-Level Requirements Below is the list of high level requirement appropriate for the development of A Touch of Glass system Functional Requirements Person(s) who Suggested Reference(s) Product Catalog Customer search and browse different product Sarah Bromley (Company owner and manager) Page of case study Select a product Thomas Enslin (Packing and Shipping) Page of case study People create their own designs Thomas Enslin (Packing and Shipping), Frederic Smith (Operations) Page of case study, Page 10 of case study Sarah Bromley (Company owner and manager) Willow Grant (Customer care and social media) Page of case study Thomas Enslin (Packing and Shipping) Page of case study Willow Grant (Customer care and social media) Page of case study Account Existing customer have an account to login Register and login Page of case study Payment Pay for an item Shopping Cart Checkout Hosting Hosting Register URL Willow Grant (Customer care and social media) Willow Grant (Customer care and social media) Page of case study Frederic Smith (Operations) Page 10 of case study Page 10 of case study Order Maintenance Track item lifecycle Reasons why they are considered to be high-level requirements Register and login: The system requires this functionality so as to grant access to users to login This very important functionality for a system to have as it imposes system security Customer search and browse different product: This is a very vital feature for an ecommerce website as it will be great help to customers or user to view products for what they will like by means of using the search bar This saves time as they don't have to go through the whole website to search for what they want to buy and it makes them pick more interest in the website Pay for an item: This is a very important functionality for TOG system because a customer needs to pay for the item they want to make order for since it is an online store Select a product: This is a very important requirement for TOG system because customer(s) need to choose the product they will want to buy before placing an order Existing customer have an account to login: This feature is very important because they are already existing customers of Touch of Glass so should be allowed to gain access to the new website by providing them with an account to login to the new website of TOG People create their own designs: This is a very important functionality of the system Some customers will desire to have their own kind of design rather than what is been display on the website Hosting: Hosting is a very vital functionality for A Touch of Glass system to start up as it requires sever in the internet to run for customer to have access anywhere they are connected Checkout: This is a functional requirement is very important as customer needs to checkout after making payment for items ordered Register URL: This is a very important functional feature for the website because customers will need a domain name that describes the website in order to search for the website online B MoSCoW Prioritization of System Requirements B 2.1: Updated list of High-Level Requirements for A Touch of Glass System based on Moscow prioritization rule Functional Requirement Person suggested Reference Hours Prioritization Customer search and browse different product Sarah Bromley (Company owner and manager) Page of case study 200 Select a product Thomas Enslin (Packing and Shipping) Page of case study 150 Thomas Enslin (Packing and Shipping), Frederic Smith (Operations) Page of case study, Page 10 of case study Existing customer have an account to login Sarah Bromley (Company owner and manager) Page of case study 100 MUST HAVE Register and login Willow Grant (Customer care and social media) Page of case study 150 MUST HAVE Thomas Enslin (Packing and Shipping) Page of case study 200 MUST HAVE Willow Grant (Customer care and social media) Page of case study 150 MUST HAVE Willow Grant (Customer care and social media) Page 10 of case study 100 MUST HAVE Willow Grant (Customer care and social media) Page of case study 150 MUST HAVE Frederic Smith (Operations) Page 10 of case study 100 SHOULD HAVE Product Catalog People create their own designs MUST HAVE MUST HAVE SHOULD HAVE 100 Account Payment Pay for an item Hosting Hosting Register URL Shopping Cart Checkout Order Maintenance Track item lifecycle Estimated Total Project Hours 1,400 MUST HAVE - 1,150 - 82% SHOULD HAVE – 250 - 18% The table above outlined the prioritization of the high-level requirements of Touch of Glass system using a technique in DSDM called MoSCoW rule This rule was used to prioritize the requirements to guide teams understand what customers want and their requirement which are needed for the system to start and which od those requirements will be delivered in the first phase of development then the remaining can be deliver in the future development Time, Cost and quality are fixed, gathering the most urgent and important features is the best solution to making progress and equally meeting up to deadline given because features can change and can be deliver according to priority MoSCoW rule of prioritization general format is written as follows: M = Must Have (are features that must be included before the system can be launched There is the minimum scope for the product to be useful.) S = Should Have (are features that are not needed for the system to be launch, but are regarded to be important and of a high value to the user.) C = Could Have (are features that are needed but cannot be excluded due to insufficient time duration, so may be included in a future phase of development.) B 2.2: Justifying the reason for Requirements Prioritization Pay for an item: This is a MUST HAVE requirement for Touch of Glass system because customers must make online payment for product they order for seeing that Touch of Glass is an online store This functionality must be included in the first increment develop to lunch the system Register and login: This is a MUST HAVE for the system because it is a very important functionality as it enforces security on the system by identifying and authenticating all customers who place order for products Customer search and browse different product: This feature is very important and it is a MUST HAVE to be included in the first phase of increment of TOG system to be lunched for the reason that customers should be able to view all varieties of products on the website store to able to select what product is best for them whether they are login or not Checkout: This is a very important functionality and a MUST HAVE for Touch of Glass system a customer should be able to check out after making payment for all the product ordered Track item lifecycle: This is SHOULD HAVE because it is very important but not critical feature to include in the first release because the system will still work with or without the feature at first release People create their own designs: This is prioritized as SHOULD HAVE though it is very important feature but it most not necessarily be in the first increment development because the system can be lunch without this feature This can be included in the next release Hosting: It is very important for every Touch of Glass website to be hosting in server in the internet for customers to able to access it, view product sand make transaction online wherever they are Existing customer have an account to login: This feature is very important because they are already existing customers of Touch of Glass so should be allowed to gain access to the new website by providing them with an account to login to the new website of TOG ... feature for the website because customers will need a domain name that describes the website in order to search for the website online B MoSCoW Prioritization of System Requirements B 2.1: Updated... must be included before the system can be launched There is the minimum scope for the product to be useful.) S = Should Have (are features that are not needed for the system to be launch, but... increment of TOG system to be lunched for the reason that customers should be able to view all varieties of products on the website store to able to select what product is best for them whether they