You are required to answer the following questions for the Dazzling Costumes information system
Marks business Dazzling Costumes has been handling the hiring of clothing items (for example, dresses, costumes, masks and accessories) manually. The business has seen a recent growth with many more customers hiring clothing for special events and parties. It is becoming increasingly more difficult to maintain information manually. They need an information system to help them to run the business.
The functionality stated here has been deliberately oversimplified and you should not attempt to analyze the stated processes for improvement. You must provide a solution based specifically on these simple requirements. You should ensure that you do not extend the scope beyond that specifically stated below. You will not gain extra marks for including extra functionally. Try to keep it simple; if needed you may make reasonable and appropriate assumptions, however these should be documented.
The first time that a customer borrows a clothing item, details such as first name, last name, date of birth, gender, address, and email address are collected about that customer and the new customer is added to the system.
When the customer hires another item at a future date, these details are displayed and confirmed by the customer service staff. When the customer indicates differences, the customer service staff updates the customers details.
The business identifies each individual clothing item with a unique code. This is displayed on the item and the code is entered whenever it is hired out or returned. For each clothing item, the system also needs to record details such as clothing item name, brand and general description.
There may be multiple pieces of the same clothing item within the store. For example, the business holds multiple Sparkly fairy wings, Superman and Peter Pan costumes.
For each individual item piece, the business needs to record the date of purchase, the cost of purchase, colour, size and a special general notes field so that the business can record relevant notes about this item piece. Each item piece also has a status indicator which can be set to specific values to indicate that the item piece is available for loan, out on loan, overdue, in repair or lost.
It is not necessary to group items together into a particular set of items. For example if a customer hires a superman outfit, they would hire the individual pieces such as suit, cape and pants, rather than the one superman set.
All hires are made for a one week period and are due back one week from the date of hire. For each hire, the system needs to record the customer who hired the item piece, the item piece that has been hired, the hireddate, due-date and the returned-date.
When an item piece is returned by a customer, the status indicator for that item piece is reset to available and the item piece is then returned to the floor for display.
Every Monday, the manager receives a report with the details of all customers who have items overdue as well as the details of the overdue items. The manager then uses this list to personally follow up with these customers.
Please note:
There is no requirement to cater for any financial aspects of this business such as the purchasing of stock. Other functionality may be added at a future date such as search facilities, reservations, purchasing and ordering of new items, and inventory control. However these are not to be considered for this phase and therefore should be ignored.
Draw a context diagram data flow diagram for the system described above. The format should be similar to the context diagram in figure 5-13 of your textbook.
Draw the Level 0 DFD (Data Flow Diagram). All processes on this diagram should be functional primitives. The format should be similar to the context diagram in figure 5-16 of your textbook.
Draw an ERD (Entity Relationship Diagram) which represents the entities described in the case study, fully normalised to reflect all entities, relationships, cardinality and optionality. Ensure to follow the crows feet notation to indicate cardinality. The format should be similar to the figure 9-21 of your textbook.
Create a 3NF design for the system described in the case study. Provide the entity attribute list in 3rd normal form to support the ERD in Task 3. Make sure that all primary and foreign keys are identified properly. It is not necessary to provide the earlier normalisation forms (1NF and 2NF) as these will not be marked
Draw a class diagram for the system described in the case study. The format should be similar to the class diagram in figure 6-30 of your textbook. Make sure to include all relevant attributes and methods for each class.
The Manager of Dazzling Costumes is most interested in your work. She has no knowledge of Systems Analysis and Design and has asked for a brief explanation of what you have done and what these mean to her. Write - 1 page report explaining your work in Tasks 1 5.
Briefly describe various system changeover methods. Suggest a changeover method for the system described in the case study and provide specific reasons to support your choice.