UML diagram

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 1 of 12

Assignment 1 Aim The objectives of this assignment include:

 Interpretation, Analysis and Creation of Conceptual Schema  Translation of Conceptual Schema into Relational Schemas

Task 1 - Description Background

For many decades, the city of Gothaman has grown exponentially in size and complexity, attracting all sorts of people to live and work there. The most recent decade saw a sharp increase variety and instances of crime, ranging from simple petty thefts, burglaries all the way to serious crimes like kidnapping and murder. Recognizing a need for the city's Justice Department to search for a new way to manage all kinds of related data, the mayor has awarded a contract to your company, to build an I.T. system that can keep track of the huge volumes of crime details, court cases and court personnel (e.g. lawyers, judges, etc). Your role is to interpret the requirements accurately, so as to design and produce a conceptual model of "Gothaman Courts of Justice Database System". After many rounds of interview and discussions with stakeholders from the Gothaman Justice Department, you have drafted the following specifications pertaining to your database. Business Requirements

The Justice Courts in Gothaman has been kept busy handling huge amount of court cases every day. For each court case, a lawyer is typically hired by his client to represent his interests. In the event a citizen is too poor to afford a lawyer, a public lawyer will be assigned to him. Sometimes, a single lawyer could be employed to represent a group of people (in cases of "collective action"), other times, it could be a single wealthy citizen hiring a group of lawyers for complicated cases. For each court case, a client is referred to, either as a "plaintiff" or "defendant". A system generated identification number is assigned to each client to uniquely identify him. A client is described by his identification number, passport number, first name, last name, gender, date of birth, residential address, tel. no. and email address. In a similar fashion, an identification number is generated for each lawyer (and judge) as well, so as to uniquely identify each individual. A lawyer is described by his identification number, passport number, first name, last name, gender, date of birth, specialty, company address, company tel. no. and email address.

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 2 of 12

Based on a lawyer's experiences and exposure, a lawyer could have more than one specialty (e.g. family law, criminal law, business law, real estate law, etc). Each specialty has an identification number, description. A court case is assigned to one and only one court, and each court may handle many cases. A lawyer can handle more than one case, and a client may be involved in more than one case as well. Each case is described by a case number, case type, general description, (supporting) evidence description, and list of hearing dates (typically, the last date on the list is also the judgment date!) Each court has a unique court name to it, and is described by a list of email addresses (for different types of cases) and a court (building) address. Each court has between 1 to 5 judges assigned to it, and each judge is assigned to one court. Judges are described by their identification number, passport number, first name, last name, gender, date of birth, specialty (same as the one for lawyer), years in practice, and a (work related) email address. Each judge should have at least 1 specialty.

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 3 of 12

Task 1 - Requirements A) The business requirements described in the earlier "Task 1 - Description" section

represents the latest (in on-going efforts) to document the user's needs. Whether you think it is complete or not, you are not allowed to add or change requirements / attributes to the specification given above!

B) The 'journey' in analyzing business requirements can sometimes be a subjective effort,

depending on factors like language proficiency, various statement interpretations and different perspectives / points of view. Therefore, apart from the final diagram model, it is very important that you are able to document the process of coming up with your final diagram!

C) For conceptual modeling, the process should be similar to the "6 steps methodology"

described in the slides from lecture file : (4) Conceptual Modeling.

D) You are to submit a softcopy report that explains the process in analyzing the requirements and deriving the model. EACH STEP should have the following sub- sections :

i) explanation and evidence (of requirements). You may quote, copy-paste 'partial' sentences / paragraphs from the business requirements, to support your explanation for areas like :

- why certain classes / objects are included, OR

- why a certain class should have certain identifiers / attributes / qualifications OR

- why you should have link attributes between classes 'A' and 'B'

- etc.

ii) diagrammatic fragments of the conceptual schema, (i.e. screen-captures from UMLet) E) In your report, you may include a new section "Assumptions and Justifications" - for

special situations where:

i) you are unable to find actual wordings / (direct) sentences in business requirements BUT ...

ii) you feel there is strong, indirect evidence to include certain elements / aspects / characteristics of your conceptual schema.

Note :

It is up to your tutor's discretion to assess the accuracy of your assumptions/explanations. You cannot assume your tutor must fully agree with all your statements simply because you added them in!

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 4 of 12

F) You are required to use UMLet diagramming tool to design/draw all your conceptual

models. For your final conceptual model, you are required to save it as a *.bmp file (via File | Export As ... function in UMLet)

G) Please refer to Appendix A, for details on deliverables & file naming conventions for this

task. H) Please refer to Appendix B, for details on submission procedures and when to submit,

for this assignment. I) Please refer to Appendix C, which describes the assessment / grading guidelines for this

assignment

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 5 of 12

Task 2 - Description Background

You have just been re-deployed by your IT company to assist with the analysis, design and implementation of a database system. Your fellow colleagues have conducted multiple rounds of meetings and interviews (i.e. the requirements gathering phase of the project) with users to document the requirements specification. In addition, the project team has undergone 2 iterations of refinements to arrive at the conceptual model as shown below. You are to undergo the process of logical design, by transforming the conceptual schema (below), into a set of relational schemas. Conceptual Schema

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 6 of 12

Task 2 - Requirements A) Please make use of the conceptual schema (shown in the earlier "Task 2 - Description"

section) only. You are not allowed to add or modify classes / attributes in the model given above!

B) There are many considerations to be addressed, in order to produce a set of coherent

relational schemas. Therefore, it is very important that you are able to document the process of undergoing various transformations to arrive at your final output!

C) For logical design, the process should be similar to the descriptions & examples found in

the lecture slides : (6) Logical Design.

D) You are to submit a softcopy report that explains the process in analyzing / transforming the conceptual. EACH TRANSFORMATION should have the following sub-sections :

i) Type and explanation of transformation applied. You may include the following points, to support your explanation. For example :

- Type of transformation (e.g. multi-valued attribute)

- Affected Class(es) / Attribute(s) / Associations (e.g. 'Book', 'author-name', etc)

- Description of how you applied the transformation to the affected elements in the conceptual model

ii) "Before" and "After" diagrammatic fragments of the conceptual model, (i.e. screen- captures from UMLet), to contrast pictorially, the differences prior to, and just after you applied the transformation

E) For all diagrammatic fragments in this task, you are required to use UMLet diagramming

tool. F) For your final set of relational schemas, save it into a text file. The schemas must be

presented in a format described in the last few slides of the lecture file : (6) Logical Design

G) Please refer to Appendix A, for details on deliverables & file naming conventions for this

task.

H) Please refer to Appendix B, for details on the submission procedures and when to submit, for this assignment.

I) Please refer to Appendix C, which describes the assessment / grading guidelines for this

assignment

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 7 of 12

APPENDIX A

File Naming Conventions

For all files in general, please use following naming format as a PRE-FIX:

<FT/PT>_<Your Grp>_ A1-T1_<Stud. No.> _<Name>.<file extension>

- <FT/PT> Use “FT” for Full-Time student, “PT” if you are Part-Time student - <Your Grp> refers to your SIM tutorial group (e.g. TutGrp1 / TutGrp2 / etc.) - A1 if you are submitting assignment 1, A2 if submitting assignment 2, etc. - T1 if file contains answers for Task 1, T2 if file contains answers for Task 2, etc. - <Stud. No.> refers to your UOW assigned student number (e.g. 12345678) - <Name> refers to your UOW registered name (e.g. JohnDoeAnderson)

- <file extension> refers to the type of file (e.g. .bmp, .doc, .xls, .uxf, .txt)

Deliverables The deliverables include the following: a) A softcopy report (*.xls) describing your Conceptual Modeling process, where EACH

STEP in the process is supported by:

- explanation and evidence (of requirements)

- diagrammatic fragments of the conceptual model

( Note : refer to the earlier section "Task 1 - Requirements" ) Please rename your file according to the required file naming convention! E.g. => FT_TutGrp2_A1-T1_1234567_JohnDoeAnderson_Rpt.xls b) A *.bmp image of your final Conceptual Schema diagram (exported from UMLet) Please rename your file according to the required file naming convention! E.g. => FT_TutGrp3_A1-T1_1234567_JohnDoeAnderson_Diag.bmp

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 8 of 12

c) A softcopy report (*.xls) explaining your Logical Design transformations process, where

EACH TRANSFORMATION should have the following sub-sections

- Type and explanation of transformation applied

- "Before" and "After" diagrammatic fragments of the conceptual model

( Note : refer to the earlier section "Task 2 - Requirements" ) Please rename your file according to the required file naming convention!

E.g. => PT_TutGrp1_A1-T2_1234567_JohnDoeAnderson_Rpt.xls d) A *.txt file of your final set of relational schemas Please rename your file according to the required file naming convention! E.g. => PT_TutGrp1_A1-T2_1234567_JohnDoeAnderson_Schema.txt e) Compress all your assignment files into a single zip file. Please use the following

naming format :

<FT/PT>_ <Your Grp>_ A1_<Stud. No.> _<Name>.ZIP

Example : FT_TutGrp3_A1_1234567_JohnDoeAnderson.ZIP

- <FT/PT> Use “FT” for Full-Time student, “PT” if you are Part-Time student - <Your Grp> refers to your SIM tutorial group (e.g. TutGrp1 / TutGrp2 / etc.) - A1 if you are submitting assignment 1, A2 if submitting assignment 2, etc. - <Stud. No.> refers to your UOW assigned student number (e.g. 12345678) - <Name> refers to your UOW registered name (e.g. JohnDoeAnderson)

f) A Q&A / demo / testing will be held during lab session. You must be prepared to present / perform certain tasks / answer questions posed by the tutor, regarding your application of the process and the final answer in your submission.

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 9 of 12

APPENDIX B

How to Submit – Normal Workflow A) Please double-check that all your filenames are in the correct naming convention B) Please submit via Moodle using the following steps:

(i) Login to your Moodle account

(ii) Select the site for this Subject : CSIT115 Data Management and Security

(iii) Scroll down and look for the section on Submissions

(iv) Click at the link “in this place you can submit the outcomes of Assignment . . .”

(v) Click at a button “Add Submission” (vi) Use the link “Add . . .”, OR drag your ZIP file into the area “You can drag

and drop files here to add them . . .” (vii) Click at a button “Save changes” (viii) Click at a button “Submit assignment” (ix) Click at the checkbox with a text attached : By checking this box, I

confirm that this submission is my own work, … in order to confirm the authorship of your submission

(x) Click at a button Continue

(xi) … and that’s it! C) Please take note of the following submission policies

(i) Only one submission of this assignment is allowed and only one submission per student is accepted

(ii) A submission marked by Moodle as "late" is always treated as a late submission no matter how many seconds it is late.

(iii) A submission that contains an incorrect file attached is treated as a correct submission with all consequences coming from the evaluation of the file attached. (i.e. no marks can be given if file does not contain the required content!)

How to Submit – “Emergency” Workflow

In the event of UNFORSEEN SITUATIONS : ( E.g. New student+skip orientation, joining the current quarter as the 1st semester, Student's moodle account not ready, cannot login to moodle, forget password, eLearning site down on submission day, repeated interrupted internet connection, unable to upload assignment, etc ) Please submit your Assignment using the following steps :

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 10 of 12

A) Please double-check that all your filenames are in the correct naming convention

B) Compress all your assignment files into a single zip file. Please use the following

naming format :

<FT/PT>_ <Your Grp>_ A1_<Stud. No.> _<Name>.ZIP

Example : FT_TutGrp1_A1_1234567_JohnDoeAnderson.ZIP

- <FT/PT> Use “FT” for Full-Time student, “PT” if you are Part-Time student - <Your Grp> refers to your SIM tutorial group (e.g. TutGrp1 / TutGrp2 / etc.) - A1 if you are submitting assignment 1, A2 if submitting assignment 2, etc. - <Stud. No.> refers to your UOW assigned student number (e.g. 12345678) - <Name> refers to your UOW registered name (e.g. JohnDoeAnderson)

C) Please email your single zip file to your tutor at :

[email protected] for FULL TIME students

[email protected] for PART TIME students In your email subject line, type in the following information :

<FT/PT> <Your Grp> <assignment info> <student number> and <name>.

Example: To : tutor's email (see above) Subject : FT TutGrp1 A1 1234567 JohnDoeAnderson Note 1 : The timestamp shown on tutor’s email Inbox will be used to determine if the assignment is late or not.

Note 2 : After email submission, your mailbox’s sent folder would have a copy (record) of your sent email, please do not delete that copy !! It could be used to prove your timely submission, in case the Tutor did not receive your email!

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 11 of 12

When to Submit A) After the submission of deliverables, students may be given a chance to explain / demo

their understanding of the process, and how they derive their answers. Depending on the time-table, a demo / Q&A / testing for your assignment may be scheduled during the

- 3rd - 5th lab session for the semester (i.e. lab 3 - 5), for Full Time (FT) students

- 2nd - 4th lab session for the semester (i.e. lab 2 - 4), for Part Time (PT) students Further instructions will be given by the Tutor during the subsequent respective labs. Please consult your tutor for further details. Some time would be allocated for each student to present / demo / explain his solution during the session. Please pay attention as failure to adhere to instructions may result in deduction of marks.

B) Please refer to the following table which contains general info on the different submission events and deadlines

Assignment Submission Deadline

(check Moodle for EXACT date-time ) Assignment Demo / Q&A / Testing (Tasks), during your

respective ... PT

(must be before ...) FT

(must be before ...)

1 Lab 2 Lab 3 Lab 2(PT), Lab 3(FT)

2 Lab 3 Lab 4 Lab 3(PT), Lab 4(FT)

3 Lab 4 Lab 5 Lab 4(PT), Lab 5(FT)

Note: (PT) = Part Time Students, (FT) = Full Time Students !

C) Non-submission of any of the above mentioned deliverables will result in ZERO marks! Please check with your Tutor personally if you are unsure!

University of Wollongong School of Computing and Information Technology

CSIT115 Data Management and Security

Page 12 of 12

APPENDIX C

! VERY IMPORTANT !

PLEASE FOLLOW ALL THE INSTRUCTIONS STATED IN ALL THE APPENDICES !!

IT IS CRUCIAL THAT YOU FOLLOW CLOSELY ALL POINTS STATED IN TASK REQUIREMENTS

IF YOU ARE NOT SURE,

PLEASE CHECK WITH YOUR TUTOR DURING LABS / LECTURES !

MARKS WILL BE DEDUCTED IF YOU FAIL TO FOLLOW INSTRUCTIONS !!

Assessment Guidelines In general, student’s deliverables will be assessed based on the following principles : (i) Whether the submission has adhered to the instructions (painstakingly elaborated) in the

assignment document. For example, marks may be deducted for situations like :

- missing / partial / incorrect file naming conventions

- incorrect file format ( e.g. submitting *.xlsx instead of *.xls )

- partial / non submission of required deliverables

- late submissions / plagiarism

- submitted files cannot be opened by the relevant software

- content in deliverables is partially or totally different from what is stated in task requirements (e.g. drawing use case diagram instead of class diagram)

- content in deliverables does not conform to the required format (e.g. adding 'strange' notations / symbols in diagrams which are not part of UML syntax)

- failure to fulfill the administrative instructions stated in the assignment in general

- inability to explain / demonstrate understanding of own answers, during Q & A

(ii) With regards to requirements stated under the Sections "Task Requirement" (for different tasks), the following guidelines apply :

- Coverage : How much of the information mentioned in the Task Description has been considered in your process and your final answer

- Clarity / Accuracy : Are there any portions of your process / final answer that is unclear or subject to multiple interpretations. Are there any attempts to use different examples to prove your understanding?

- Verification : Successful demonstration, clarity of communication and satisfactory answers given during Q & A