Reference no: EM13840008

Systems Analysis and Design

Assignment

All assignment submissions must be completed individually. Collusion and cheating is considered to be a very serious issue and all assignments will be closely monitored to ensure that all students are submitting their own work. This ensures that all students are treated fairly and graded on their own knowledge and work. It is acceptable to discuss course content with others to improve your understanding and clarify requirements however you must not discuss the actual assignment solution and the solutions to assignment questions must be done on your own. You must not copy from anyone, including tutors and fellow students, nor provide copies of your work to others. Assignments that do not adhere to this requirement will be deemed as being the result of collusion or cheating. This may lead to severe academic penalties as outlined in the Student Academic Regulation Misconduct policy found at: - https://policy.usq.edu.au/portal/custom/detail/student- academicmisconduct/index.html.

It is your own responsibility to ensure the integrity of your work. It is recommended that you use passwords to protect your files and ensure that others are unable to access your work.

All assignments must be submitted in electronic form via the link on the Study Desk by the due date.

Ensure that you read the extension guidelines for this course as posted onto the course Study Desk. Only requests that fall within the specified guidelines will be considered. Do not assume that all extension requests will be approved.

Read each assignment question carefully and refer as required to your course textbook and StudyDesk materials. I encourage students to post any queries that they have regarding this assignment onto the course Study Desk. An appropriate response will be provided and this enables all course participants to view the relevant discussion.

For all assessment items digital file naming convention: When you have an assessment item you need to upload digitally, please use the following naming convention when saving your digital document:

Student last name_assignment #_CIS2000_Student USQ ID

For example, the fourth assignment for CIS2000 submitted by Poul Moller, student # 0061234567. If I (Poul Moller) was uploading this assessment item, my file would be named as follows: Moller_A4_CIS2000_0061234567.doc

CASE STUDY FOR ASSIGNMENT

Please read this Case Study and answer the following questions.

You are required to answer the following questions for the Dazzling Costumes information system.

Mark's 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. Please post queries on the Discussion Forum for Assignment on the StudyDesk.

Business requirements:

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 customer's 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.

Task 1

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.

Task 2

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.

Task 3

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 crow's feet notation to indicate cardinality. The format should be similar to the figure 9-21 of your textbook.

Task 4

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

Task 5

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.

Task 6

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.

Task 7

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.