Database Applications
web | 代做report | security代做 | 代做Algorithm | javascript代做 | java代写 | project作业 | 作业unity | assignment | IT代做 | 作业lab | sql代写 | 代写database | oracle – 这个题目属于一个javascript的代写任务, 是比较典型的web/report/security/Algorithm/javascript/java/unity/IT/sql/database/oracle等代写方向, 这是值得参考的lab代写的题目
ISYS1101/1102 | Semester 2 202 2
assignment 1: database Design and Optimisation
Assessment Type Database Design, Database Optimisation, Implementation, and
Demonstration
Individual Assessment
Due Date (M 1 ) Week 5 , during the lab sessions. Further details will be provided on
Canvas.
Due Date (M 2 ) 23:59 Sunday 28 August 2022
Demonstrations (M 3 ) Week 7 , during the lab sessions. Further details will be provided on
Canvas.
Silence Period (M 1 ) None
Silence Period (M 2 & M 3 ) Starts at 5:00PM Friday 26 August 2022
Weight Milestone 1 : 5 marks
Milestone 2 : 15 marks
Milestone 3 : 5 marks
Submission Online, via Canvas. Submission instructions are provided on Canvas.
1 Overview
1.1 Assessment Criteria
This assessment will determine your ability to:
- analyse the requirements outlined in the problem description;
- develop a conceptual model to assist you with the design of the database backend required for the system;
- use an industry-standard ER modeling tool to draw the ER model and generate sql DDL statements for generating table schemas;
- identify and implementing efficient storage strategies for extremely large tables
- identify and implementing efficient partition strategies for extremely large tables
- write efficient queries on extremely large tables and describe the query plans that query optimiser would likely be using and explain how a cost-based query optimiser would execute such query plans;
- write stored procedures and triggers to automate common tasks in a oracle database.
1.2 Learning Outcomes
This assessment will assess how you attained the following course learning outcomes: CLO 1: apply advanced data analysis and modeling concepts, physical design, integrity, security and transaction management. CLO 2: create triggers, stored procedures and functions to enhance the usability of a database; CLO 3: apply techniques for efficient storing, accessing, securing, and recovering of data; CLO 4: build an efficient database application with an emphasis on storage management, indexing, and query optimization.
2 Assessment Details
2.1 Preparation Work
You are required to implement the database backend for the below mentioned application on Schools
Oracle server. In order to successfully complete these tasks you must have completed Week 1 4 lab
sheets and ensure that your Oracle account is correctly initiated and SQL Developer on your laptop is
configured correctly.
Another learning outcome of this assignment is to learn to use an industry-standard ER modeling tool to
draw the ER model and generate SQL DDL statements for generating table schemas. We use Oracle SQL
Developer tool for this purpose. Complete Part 2 of the Week 3 Tute/ Lab session prior to attempting
the data modeling part of this assignment.
2.2 Assignment Task Description
Introduction
The Australian Electoral Commission (AEC https://aec.gov.au) is responsible for providing the
Australian people with an independent electoral service which meets their needs and encourages them
to understand and participate in the electoral process. Australias manual system of federal elections
has one of the most complex and time-consuming counting operations in the world. While IT can at
times require patience, the federal election counting process delivers (1) integrity to the results,
concentrating on (2) accuracy in a (3) highly transparent manner.
While manual process ensures these three key priorities, there are two areas of concern to may stake
holders, namely:
- The time it takes to count votes and the human resources required to complete the process within an acceptable time frame
- The volume of papers it requires and the environmental impact of running a manual election.
Lets suppose you are employed by a software development company that just received a contract from
AEC to build a computerised voting system for federal elections. As in the case with manual elections,
the most important aspect of this system is to ensure the integrity of the voting system, accuracy, and
transparency.
System requirements
The system is developed in several phases. The first phase, which you are responsible for, is limited to federal general elections for House of Representatives. The following voting processes are not in the scope of this phase:
- Federal general elections for senate
- Federal by-elections
- State and territory elections
- City council and shire council elections
- Referendums
- Any other election services provided by AEC
In this assignment, you are required to analyse the database requirements, design the database backend for the voting system, identify various database optimisations, and implement the system.
Elections
In Australia, federal elections are held every three years. In these elections, the voters get an opport unity to vote for both lower house (the house of representatives) and upper house (the senate). There are currently 151 seats in the lower house, and 76 seats in the senate.
As the scope of this assignment is limited to federal general elections for House of Representatives no further details are provided on the upper house (the senate) and how the elections are conducted for senate seats.
Members of the House of Representatives are elected by the voters registered in each electorate using full preferential voting. Each electorate elects one member.
Electorates
For the House of Representatives, each state and territory is divided into electoral divisions (or commonly known as electorates or seats). Population determines the number of electorates. To ensure continued equal representation, the boundaries of these electorates have to be redrawn (redistributed) periodically. As of last re-distribution based on 2017 population data, there are 151 electorates in Australia.
State
Population (in
2017) Electorates
NSW 7,797,791 47
VIC 6,244,227 38
QLD 4,883,739 30
WA 2,567,788 16
SA 1,716,966 10
TAS 519,050 5
ACT 419,256 3
NT 247,512 2
Total 24,396,329 151
Election Process
When the sitting government is nearing its term (3 years) or under circumstances it is dissolved, the Australian Electoral Commission (AEC) calls for nominations of candidates. Registered political parties will then nominate their candidates for one or more electorates. Most political parties nominate candidates for many electorates. Independent candidates can nominate themselves for the election.
Once the nomination process is over, AEC will determine the election date and will print ballot papers for each electorate. A sample ballot paper is shown below. A screenshot of a real ballot paper (Higgins electorate in 2016 election) also shown.
On the election date, registered voters are required to attend a polling station and cast their vote on a ballot paper similar to above. The actual voting process is much more flexible with pre-poll voting, postal voting, absentee voting, and declaration votes. However, for the scope of this assignment, we only consider regular voting process on election day.
The preferential voting system
Candidates for the house of representatives are elected using the preferential voting system. In this system, the voters are required to cast their order of preference to ALL candidates contesting in their electorate. As shown in the above ballot paper, the voter has given first preference to the fifth candidate on the ballot paper. The voter has given their second preference to the first candidate on the ballot paper.
At the end of the election day, after all the polling stations are closed, the counting begins. The counting of preferential votes is a complex process.
Step 1: Count of first preferences (primary vote)
In this step, all of the number 1 votes are counted for each candidate. If a candidate gets more than half the total first preference votes, that candidate will be elected.
Step 2: Distribution of preferences
If no candidate has more than half of the votes, the candidate with the fewest votes is excluded. This candidates votes are transferred to the candidates according to the second preferences of the voters on the ballot papers for the excluded candidate. If still no candidate has more than half the votes, the second-last candidate who now has the fewest votes are excluded and the votes are transferred according to the next preference on the ballot papers. This process is continued until one candidate has more than half the total number of valid votes.
This process is illustrated with a real example (distribution of preferences in Aston electorate in 2019 election) on the page 32 of the following document.
https://www.aec.gov.au/about_aec/Publications/electoral_pocketbook/2019/2019-electoral- pocketbook.pdf
A screen shot of the above-mentioned page:
At the end of this two-stage counting process, the winning candidate is declared as the new Member of Parliament for the corresponding electorate.
Components of the proposed system.
The proposed computerised election system must be able to conduct the entire election process for federal house of representatives elections. The major tasks in the election process are listed below:
- Maintenance of electoral role
- Maintenance of information required for conduct of an election (such as basic election information, electorate information, political party information, candidate information, etc. Refer to details below.
- Election Day This process should mimic the manual process where a voter visits a polling information, once identification is established a ballot paper issued, marks their preferences and lodges the ballot paper.
- Counting of ballot papers (counting is a complex process, refer to details below).
This system will maintain the following information.
1. Computerised Electoral Role
The system will maintain a computerised electoral role, i.e. a database of registered voters for each electorate. For each registered voter, following information is stored:
- Title
- First name*
- Middle names (if any)
- Last name*
- Gender
- Date of Birth*
- Residential Address* (Unit number, street number, street name, suburb, postcode, state)
- (no letter box addresses accepted)
- Postal Address (as above, or can be different)
- Contact Details (daytime phone number, mobile phone number, email address)
- Electorate (determined by the system based on residential address)
There are around 17,259,000 Australians are currently enrolled to vote (https://www.aec.gov.au/Enrolling_to_vote/Enrolment_stats/index.htm). The increase of the size of the electoral role is approximately proportional to the population growth in Australia. The current population growth in Australia is approximately 1.2%. (https://population.gov.au/sites/population.gov.au/files/2022-04/2022-23_budget_overview.pdf)
2. Details of Elections
The following details about elections are required to be stored in the database.
- Election Serial Number (a unique code generated and stored by the system)
- Date of the election
- Type of election (house of representative, senate, by-election, etc)
- Total number of electorates
- Total number of registered voters (the number of registered voters at the closing of the electoral role registrations for the corresponding election) 3. Details of Electorates
The following details about electorates are required to be stored in the database.
- Electorate Name (refer to page 156 158 of https://www.aec.gov.au/about_aec/Publications/electoral_pocketbook/2019/2019-electoral- pocketbook.pdf) for full list
- Name of the electorate
- Total number of currently registered voters
- Historical record of registered voters (the historical data are captured at closing date of the electoral role registrations for the past elections. Both the date and no. of voters are stored)
- Name and party of the current member of parliament
4. Details of Political Parties
The following details about political parties are required to be stored in the database.
- Party Code (refer to page 160 of https://www.aec.gov.au/about_aec/Publications/electoral_pocketbook/2019/2019-electoral- pocketbook.pdf)
- Name of the party
- Party Logo
- Postal address of the party headquarters
- Secretary of the party
- Contact Person (name and other contact details such as daytime phone number, mobile, and email) 5. Details of Candidates
The following details about political parties are required to be stored in the database.
- Name
- Political Party Code (or IND, if they are independent)
- Contact Details name and other contact details such as daytime phone number, mobile, and email)
- Election Code
- Electorate Contesting 6. Computerised Ballot papers cast
The computerised ballot paper captures and stores voters preferences (similar to whats written on a paper-based ballot paper.
[Very important] To ensure integrity and confidentiality of the voting process, once a voter is issued a computerised ballot paper, there should not have any identification records to positively identify who cast that vote. As such, only the following data are stored with each computerised ballot paper.
- Election Code
- Electorate
- Preferences cast (i.e which candidate got the first preference, who got the second preference, etc)
However, there must be a mechanism in place to record the issuance of a ballot paper to a voter. The issuance record must capture the following information:
- Election code
- Electorate
- Polling Station Name
- Identifying details of the voter these data should be sufficient to uniquely refer to a voter in the electoral role
- Timestamp 7. Election results
At the end of counting process, for each electorate, the following result data are stored.
- Election Code
- Electorate
- Primary vote for each candidate (i.e. first preferences)
- Preferential vote count for each candidate, at the each iteration of elimination process (refer to page 32 of https://www.aec.gov.au/about_aec/Publications/electoral_pocketbook/2019/2019- electoral-pocketbook.pdf)
Assignment Tasks
Milestone 1:
You are required to build the data model for this application using an Entity-Relationship diagram. This diagram should be developed on Oracle SQL Developer. This diagram should be of professional quality with sufficient details that any other database personnel should be able to comprehend.
Then, convert your data model into the physical database design and finally generate the DDL script to build the back-end database schema for the application. Ensure that primary keys and foreign keys are correctly identified.
In order to complete this milestone, you are required to demonstrate your workings and the final DDL script to your tutor during Week 5 lab sessions. It is very important to get it marked off by the tutor before you proceed to Milestone 2. If your design does not meet the business requirements, your tutor will allow you to make any amendments (only once) and present again for evaluation.
Milestone 2:
- Identify the tables, in your final schema, that are expected to be extremely large and are expected to grow over time.
For each of these tables:
- Describe the expected record size (in bytes or kilobytes), the estimated initial table size, and estimated table size after 10 years of use.
- Describe a suitable storage strategy for such tables. Your answer must include the modified SQL DDL statements to define your chosen strategy.
- Identify 3 common queries that would need to be run frequently against the database (at least 2 must include a join, and one must include a transaction with multiple steps).
For each of the queries:
- Produce the SQL to correctly produce the expected result.
- Identify what indexes would help. Identify the type of index and columns that are used to build these indexes (justify your design).
- Show the SQL commands for building these indexes in Oracle.
- Show the query execution plans both before the index is added and after adding the index.
- Explain how the index was utilised (or not) and why. What join algorithms were used? What changes would you need to make for the index to be properly utilised, or for a different join Algorithm to be used instead? (Provide concrete details of the changes).
- Describe a suitable partition strategy for extremely large tables you identified in step 1. Include details of the partitioning type and which columns/key should be used. You must include the SQL DDL statements used to implement your partition strategy.
You must justify your design decisions. Include details about which of the above queries it will improve the performance of and how it helps with concrete examples. (You must explain in clear terms such as partition pruning, partition joins, and parallel SQL, applicable to each of these queries.)
(Note: While you will be able to test that there are no syntax errors, you may not be able to actually implement them on RMITs Oracle servers due to permission restrictions).
- Before a voter is allowed to vote, to ensure the integrity of the election system, the system should check if he/she had voted earlier on this election. Write a trigger previouslyVoted() , to check if the voter had voted before.
This trigger reads the election code, electorate, voter identification as inputs and returns a Boolean value (true, if voted before and false, if not voted before).
6) Write a stored procedure primaryVoteCount(), to complete the step 1 of the counting
process. This stored procedure requires election code and electorate name as inputs. It will read
Computerised Ballot Papers and does required processing, and update Election Results table with
primary votes (first preferences) received by each candidate in chosen electorate in the chosen election.
7) Write a stored procedure distributePreferences(), to complete the step 2 of the
counting process. This stored procedure requires election code and electorate name as inputs. It will
read Computerised Ballot Papers and does required processing, and update Election Results table with
preference votes received by each candidate at each preference distribution in chosen electorate in the
chosen election.
Milestone 3:
You are required to do a demo of your complete application hosted on the school's Oracle server. These
demos will be conducted during the week of 5 th September (Week 7). You should have some voter data
and stored in the application and the tutor will test out the functionality by using a test bed of data.
Tutors will use a standard testing plan for all submissions and you will only receive your second
milestone marks if you can demonstrate the functionality of your application in this milestone.
3 Submission
Follow the instructions on Canvas to complete your submission for the project for each Milestone.
3 .1 Milestone 1 Submission
You will need to submit:
- The conceptual model for the database backend, in the form of an entity relationship diagram using Barkers notation
- The physical database design, in the form of a database schema
- A SQL script to create tables and other related database objects in Oracle
- A small report outlining any assumptions you made in order to complete your design, steps taken to optimize your database design, and any design and implementation considerations that must be useful in the next milestone.
3. 2 Milestone 2 Submission
Submit your report, sql code, and any other associated files in a zip file using the Canvas Assignment
page. It is your responsibility to make sure the submission is (1) complete; (2) correctly zipped; (3)
clearly labelled files. Please verify that your submission is correctly submitted by downloading what you
have submitted to see if the files include the correct contents.
3 .3 Milestone 3 Submission
No additional submissions required for this milestone.
3 .4 Assessment Declaration
When you submit work electronically, you agree to the RMIT assessment declaration.
3 .5 Silence Period
For Milestone 1 , there is no silence period.
For Milestones 2 & 3 , a silence period will take effect from 5.00pm, Friday 26 August 2022.
This means questions about this assignment will be not answered, whether they are asked on Canvas
Discussion Forum, by email, or in person. The silence period is in place because staff members are
generally unavailable over the weekend. Additionally, to be fair to all students giving presentations, we
will not respond to questions about the Milestone 3 presentations during Week 7.
Make sure you ask your questions with plenty of time for them to be answered.
3 .6 Late Submissions & Extensions
A penalty of 10% per day is applied to late submissions up to 5 business days, after which you will
receive zero marks.
Short extensions may be granted by the course coordinator up to 1 business day before the due date in
accordance with RMIT Assessment Adjustment process. However, extensions are not guaranteed and
require suitable documentation. The course coordinator may refer requests to Special Considerations.
Special Consideration may result in an equivalent assessment , which may take the form of a timed
assessment assessing the same knowledge and skills of the assignment and are generally granted on an
individual basis. For more information refer to the RMIT Special Consideration process.
3 .7 Supported software for assessment and grading
Only the software and resources listed on the Canvas and used in the tute/lab sessions and preparation
work outlined in Section 2.1 are used for the purpose of assessing this project. Its your (the student's)
responsibility to ensure:
- Your HTML/ PHP/ javascript program for your project can be fully compiled and executed using GitHub Codespaces. In the event of disputes, GitHub Codespaces will be used to assess your work.
- Your source code for your project can be fully compiled and executed using only the VSCode setup (including extensions and java libraries) as described on Canvas.
- If you make use of (as extension activities) any additional JavaScript or web libraries, that you: o Inform course staff before using these libraries. o o Ensure the use of these libraries comply with the project requirements. o o Ensure you use the libraries in accordance with their License conditions. o Receive confirmation from course staff that the use these libraries is permitted.
- All SQL databases can be opened. read and written to through ORACLE and the JDBC library as described on Canvas. Work that does not run using the supported course software may result in grade penalties. If you have any concerns about software you are using, you must consult with course staff in a timely manner.
4 Marking Guidelines
4 .1 Milestone 1
- Conceptual model using entity-relationship model 3/
- The database design, in the form of a database schema 2/
4 .2 Milestone 3
The marks are divided into the following categories:
- Storage Optimisation 8/
- Partition Optimisation 4/
- Teamwork & peer assessment 3 / 15 The detailed breakdown is provided on the marking Rubric available on Canvas.
4 .3 Milestone 3
The marks are divided into the following categories:
- Presentation Skills 2 / 5
- Coverage & Questions 3/ The detailed breakdown is provided on the marking Rubric available on Canvas.
5 Academic Integrity and Plagiarism (Standard Warning)
Academic integrity is about the honest presentation of your academic work. It means acknowledging the
work of others while developing your own insights, knowledge and ideas. You should take extreme care
that you have:
- Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have quoted (i.e., directly copied), summarised, paraphrased, discussed or mentioned in your assessment through the appropriate referencing methods
- Provided a reference list of the publication details so your reader can locate the source if necessary. This includes material taken from Internet sites. If you do not acknowledge the sources of your material, you may be accused of plagiarism because you have passed off the work and ideas of another person without appropriate referencing, as if they were your own.
RMIT University treats plagiarism as a very serious offence constituting misconduct. Plagiarism covers a
variety of inappropriate behaviours, including:
- Failure to properly document a source
- Copyright material from the internet or databases
- Collusion between students
For further information on our policies and procedures, please refer to the RMIT Academic Integrity Website. The penalty for plagiarised assignments includes zero marks for that assignment, or failure for this course. Please keep in mind that RMIT University uses plagiarism detection software.