Identify the key tasks involved in planning the solution.

The first step is to collect all data relevant to the current information system including the people, procedures, equipment, data, hardware and software. Then, use this information to analyse the flow of data within the system and identify any key problems, to help determine the requirements, constraints and scope of the solution. The next step is to design a solution that - following the requirements, constraints and scope specified earlier, such as access to the cloud. The code is then written for the solution and then tested, before being implemented in the current (or revised) network. Management of the system should be easy and allocated to one person, preferably the Owner/Manager (Dallas). Evaluation of the solution should be done after a sufficient amount of time, using user feedback and suggestions, and should be used to find the success of the solution.

Suggest and justify a variety of methods that could be used to collect data on the current information system and needs so that a new software solution can be designed.
Create documents/diagrams that would describe the current system setup, which would allow easier identification of any problems that exists with the flow of data in the system. Ask the organizations staff a series of question in order to better understand the current information system, to help identify other key problems: Dallas Janson: Owner/Manager o What is the store website being used for? o Do you have any roles/interactions with the system? Lambert Campari: Accountant o How are invoices being handled? o Are invoices being validated by being checked against the stock orders? o How is the invoice data being transferred to Ash (to be used for distribution of stocks)? Ash Kumato: Stock Manager o How difficult/efficient is the current process of updating the spreadsheet? o What is done with the printed spreadsheet after completion? o How are stocks determined to be low or high ? Parker Roma: Employee Manager o Where/How are employees being notified of staffing requirements or changes? o How does the list of specials help determine the staffing requirements?

Purchaser o How are recommendations made by Ash or the community stored? o How are stocks determined to be obtained from rural or international suppliers? Ellen (Set-up I.T network) o How efficient is the current network? o What is the wireless aspect of the network like? Retrieve feedback from the staff members (via survey) about the efficiency of the current system, to help generate ideas of improvement for the system.

Brett Santorini & Kane Granadero: Import Manager & Produce

Describe the networked environment in which the solution will operate.

There are 6 computers - three desktop computers (i5, 4GB, 120GB SSD, 19 LCD) and three Notebook computers (i5, 4GB, 250GB HDD a NAS (Netgear ReadyNas Ultra 4 with 4 500GB HDD in a Raid 2 configuration) as well as a printer that are all connected in the network by an 8-port hub. The computers specifications provided allows us to assume that the rest of its hardware is also up-to-date and an upgrade should not be required. There are no indications of the cabling used, so there could be complications that arise that cannot be identified because of this. The usage of the 8 port hub in this network is also inefficient, as all the ports are in-used so any additional non-wireless device that wished to be added would require modifications made to the network. The use of the hub would also allow collisions to occur, which could slow the rate of data transfer in the network. It would be wise to consider replacing the 8 port hub with a 16 (or higher) port switch. There is also information regarding the wireless aspect of the network. The stores are assumed to be distanced from each other, which a wireless router may not be able to reach. They would have to set the cloud on the internet, and individual routers for each individual store to access the internet.

Create a Use Case diagram to accurately represent the current processes within Jansons Supermarkets. Take note to use all symbols correctly (actors, use case, system boundary, associations and any relevant includes or extends) Represent the current process of ordering stock by creating a DFD. Take note to use all symbols correctly (entities, processes, data stores and data flows). Discuss the inefficiencies with data processing that need to be addressed

in regards to the design of the new software solution. Refer to evidence gathered via the DFD in your response.
Based off the DFD, there is no indication that anything is done with the printed stock spreadsheet (Is it being discarded? Uploaded over the previous weeks spreadsheet?). It also shows that other processes dont require a printed spreadsheet, so its unnecessary to print it out instead of editing it on the network. Everything is done using information from a printed (physical) spreadsheet, which cannot be accessed easily and makes it hard to obtain required data from, as the all the stores are spread across different locations. The physical aspect also makes it hard to validate and keep a log of updates made to the spreadsheet. The printed spreadsheet is updated manually, so there is a possibility of an error in data transfer from things like reading the data incorrectly due to bad handwriting. All the data being used in other processes also come from the printed spreadsheet, so an error in the printed spreadsheet data storage would impact the whole system and could be the reason behind the lack of stock in shelves. Paid invoices are not being checked against the stocks being ordered, so theres a possibility of inconsistency between the two. This can cause problems as specials are devised based on the original stock spreadsheet and not the paid invoice, while the distribution of products uses the paid invoice, so there would be more/less products than they expect. According to the DFD, the store website is not being used for anything, making the process of updating the specials on the website pointless.

Construct a Software Requirements Specification (SRS) from the materials above and the following: Describe the requirements of the software solution including functional and non-functional requirements.
Functional: - Links all of the stores via cloud network - Accessible by multiples users (stores) at once - Create new week spreadsheet for each week - Easily and instantly updates the spreadsheet with inputted data (of store stock data) - Retrieves stock information/spreadsheet from cloud - Validates input data (stocks, invoice etc.) by restricting values (e.g over 0 and under a reasonable amount) - *OPTIONAL* Compares invoices and stocks ordered so they relay the same information.

*OPTIONAL* Instantly updates stock list through purchases made by cash registers

Non-functional: User Interface is easy-to-use and understand/straightforward - Designed for a mobile device - Potential of touch-pad usage - Easy to maintain and modify the spreadsheet - Fast-response rate when retrieving/updating stock information - Quick connection i.e lack of unnecessary images etc. that could result in a slower loading time on mobile devices - Robust - Easy navigation - Secure from unauthorized access/vandalism

Describe all relevant constraints that affect the solution.

User-friendliness: The solution must be easy-to-use and easily understood, as employees might not have the necessary I.T knowledge (and could be the reason why a printed spreadsheet is used). Cost: The solution most not be expensive (especially any network remodeling) as Jansons Supermarkets is not rich, but could use the majority of their funds as it is essentially a revamp of their entire operations. Security: The solution must be well secured, as most of the data will be located on the cloud network, and the threat of it being compromised would result in a loss of all the data. Because of this, the solution must successfully interact with all connections with a secured line while rejecting those with unsecured or unauthorised access. Mobile devices: The solution must be compatible with operating systems on mobile devices, with its user interface being simple and easyto-navigate as mobile display screens are often smaller, so icons must be visible and obvious to avoid confusion.

Describe any security vulnerabilities that will affect the design of the software solution.
There is no information giving regarding the security of the network, but if the cloud was to be located on the internet, then wireless routers would have to be implemented. The wireless signal would have to be encrypted to disallow unauthorized to gain access to the network, otherwise it would result in a security breach which would compromise the whole system as they could wipe the database or copy information flowing through the system (e.g stealing credentials from paid invoices).

There are no backups of the spreadsheet as the new spreadsheet is not being copied or updated onto the spreadsheet located on the current network. This means that if the data is compromised, the entire operation would have to come to a halt, as the processes would be using invalid data. This can be fixed by creating copies in an alternate network, storing it in the NAS or creating a physical copy of the information.

Describe the personnel and their role in the system.

Dallas Janson: Owner/Manager Manager of the entire system, and overlooks the processes being undertaken by the rest of the staff. He personally is not involved in the system at all, but still maintains it to ensure it is working correctly. Lambert Campari: Accountant Lambert handles all the finances involved in the system, paying off the invoices provided by international and rural suppliers, and provides Ash the invoice information to be used in the distribution of products. Lambert is also in charge of paying the employees. Kane Granadero: Produce Purchaser Kane handles the purchase of produce that can be obtained locally. He orders produce which are often regular orders from his rural supplier. Ash Kumato: Stock Manager Ash creates the week spreadsheets by printing out the previous weeks, and updates this with information on the stocks from the stores. Using the information from the stock spreadsheet, he alerts Brett and Kane of the low stock items for them to fill their stock orders with, while also providing recommendations for products. He uses the data obtained from the stock spreadsheet to ascertain the excess stock products in order to devise specials, and publishes these specials on the stores website and sends memos to stores with a list of specials. Ash also manages the distribution of the stocks, and is also in charge of the timesheet (worker schedule). Parker Roma: Employee Manager Parker is in charge of the management of employees in the stores. He uses the list of specials and produce delivery for the week, and is responsible for hiring extra hands, should they be necessary. Brett Santorini: Import Manager Brett is responsible for the import of produce that is found internationally. He does this by contacting and placing orders with his internationally supplier, based on low stocks data and

recommendations received by Ash and the community, as well as his own judgment on new product lines from the supplier. Software Requirements Specification Template 1. An introduction. The introduction outlines the purpose of the software solution and its scope. 2. A description of the proposed software solution. This includes what functions it will perform, what characteristics the user interface will have, the constraints on the solution and any dependencies. 3. The specific requirements of the software solution. This section can be the most detailed, often with separate subsections detailing the user interface as well as the functional and non-functional requirements. 4. A description of the environment within which the solution will operate.