Build a shopping market simulator in eclipse -- 2

Requirements Specification A large supermarket chain wishes to develop an in-house supermarket simulation to help optimise the flow of customers through the store. The aim is to make it easy for key staff within the organisation to represent the components of a supermarket scenario and run a simulation based on various configurations in order to maximise the efficiency of the store. Ideally, results of each simulation should be stored persistently and available for analysis by Head Office. The product will be called 'The iShop'. Typically, the software artefact will support the behaviour of a typical shopping experience: shoppers will enter the store; pick-up a basket; select products from the store; place products in the basket; join a queue at the tills; wait to be served; be served; bag products and leave the store. The cashier will clock on and off as a till in opened or closed; serve the next customer in the queue; log each product in the basket and wait for the next customer. Create a working prototype for distribution across the supermarket chain using a standalone application with six functional requirements to: 1. Provide a usable interface that fulfils all other requirements; 2. Support a small database of 20 products; 3. Representation the following elements of the supermarket: shop floor, tills, shoppers, cashiers, shopping baskets, products and a single bag; 4. Initialise the simulation with suitable parameters to represent various scenarios such as the number of open tills; maximum queue size or number of shoppers; 5. Support a simulation of supermarket queue in processor time; 6. Quantify the flow of customers through the supermarket given the number and size of queues at the tills. Only after completing the minimal set of functional requirements can your additional but appropriate functional requirements be considered for extra marks up to a potential maximum of 10 further marks on this section. Non Functional Requirements In order to meet the requirements specification it will be necessary to create and deploy the iShop software using the Java Eclipse platform and the range of identified programming techniques. 1. The overall non-functional requirements must be based on the MVC design pattern as follows: a. Model – this must contain the state and behaviour of the model which includes the objects suggested in the specification using the best RDD techniques. b. View – must support any changes to the model by accepting updates. This could mean informing the user of changes or notifying a thread of changes. c. Controller- this must provide access to the model and be capable of manipulating the model. This might result in changing the state of the model as a result of user interactions or changes instigated by a threaded process. 2. It is essential that the system employs a multi-threaded environment to support the simulation. 3. To improve efficiency and functionality some form of object persistence is required. • The code and a runtime the implementation; README with standard installation instructions.