Give condition for tracking down the most likely arrangement of grammatical feature (POS) labels that could be used by a stochastic POS tagger. You ought to accept a bigram model. [5 marks] (b) Given the accompanying preparation information, show the evaluations that sounds acquired, all things considered for the probabilities in the situation you gave: the_DT0 green_AJ0 bottle_NN1 leaked_VVD ._PUN the_DT0 suppliers_NN2 bottle_VVB water_NN1 ._PUN green_AJ0 water_NN1 suppliers_NN2 bottle_VVB ._PUN [4 marks] (c) Explain what is implied by the terms smoothing and backoff with regards to stochastic POS labeling. [4 marks] (d) One normal wellspring of blunders in stochastic POS taggers is that things happening preceding different things (for example sailboat trailer ) are frequently labeled as descriptive words and, then again, prenominal modifiers are frequently labeled as things (for example preliminary deal ). Recommend potential purposes behind this impact.

(a) Define what is implied by a variable being inhabit a program point, cautiously recognizing adaptations in light of program construction and I/O conduct. Talk about these other options and their reasonableness for gathering utilizing words like "decidable" and "security". [4 marks] (b) Explain the distinction between dead code and inaccessible code, referencing any investigation important to eliminate such code. [3 marks] (c) Let q be an articulation (whose main free factor is a) which generally assesses to valid in spite of the fact that concluding this is past the force of a given compiler optimiser. Think about the capacity int p(int a, int b, int c, int d, int e) { int x = a+b, y = a+c, z=0, r; in the event that (a<5) { r = a+x; while (1) proceed; z = a+d; } else if (q) { r = y; } else { r = a+e; } return r+z; } (I) Give the flowgraph for p (accepting it to have been deciphered as navely as could be expected). [3 marks] (ii) Using your meaning of liveness appropriate for a compiler from section (a), give the arrangement of factors live on section to p, contrasting this and liveness expected by I/O conduct.

(a) Write C capacity revbits() which takes a solitary 8-bit roast boundary and returns a burn result by switching the request for the pieces in the singe. [4 marks] (b) Write C capacity revbytes() taking two boundaries and returning no outcome. The main boundary is a pointer to memory containing n adjacent bytes (each of type roast), and the second is the quantity of bytes. The capacity ought to have the symptom of switching the request for the pieces in the n adjacent bytes, seen as a bitstring of length 8n. For instance, the primary piece of the principal singe ought to be traded with last piece of the last burn. [6 marks] (c) You have been doled out the accompanying apparently working C code, which processes documents controlling the way of behaving of a framework. That's what you see, subsequent to getting a few ERR_MALFORMED blunders, ensuing calls to fopen bomb due to such a large number of records being open: int process_file(char *name) { Document *p = fopen(name, "r"); if (p == NULL) return ERR_NOTFOUND; while (...) { ... if (...) return ERR_MALFORMED; process_one_option(); ... } fclose(p); bring SUCCESS back; } (I) Explain how to fix the program involving offices in C. [2 marks] (ii) Now guess the capacity above was important for a framework written in C++ (however as yet utilizing the C document handling orders, for example, fopen and fclose), and that process_one_option() could raise at least one exemptions. Utilizing a class with a destructor, tell the best way to fix the "an excessive number of records open" bug above.

When Sever receives ciphertext, each letter in the ciphertext is decrypted as follows: a. x = dk'(y) (y - k') mod 52. b. After decrypting the ciphertext, the Server must display (ciphertext, plaintext) pair on the screen. c. For each message, server also sends acknowledgement message to client. 11)Client displays plaintext and ciphertext before it transmits ciphertext out through the socket. 12) Server displays ciphertext and plaintext after it receives ciphertext through the socket and decrypts it. 2. You can use any programming language of your choice. However, make sure to include the procedure how to compile and run your program as comments in the source code. (It is also a good idea what kinds of IDE you use to complete the project.

A program (server-client model) using sockets for communication; for more information about socket programming, please refer to the tutorial links posted in the Canvas under the "Supplements" menu link. The program simulates the communication between Client and Server using stream cipher and works as follows: 1) Client connects to the Server using socket; Server takes only one Client.

2) Upon a successful connection, client generates a random number k where 1 <= k <=1,000,000. 3) After generating the random number, Client calculates a secret key k' as k' = (a k + b) mod 52 where a = 250 and b = 479. (a and b are explained in step 6))

4) Client repeats steps 2) and 3) until k' becomes non-zero number.

5) Once Client obtains non-zero k', it sends k to the Server as a plaintext without encryption (and as a result they have the same k); we assume that there is no attacker who modifies k value.

6) Server transforms k to k' using the same equation that the Client used; k' = (a k + b) mod 52, where a = 250 and b = 479. We assume that a and b are shared between Client and Server even before the connection is established. Of course a and b can be any number. However, to make the program testing easy, we fix their values for this project.

7) Now, Client and Server have the same secret key k'. 8) To use Shift Cipher, we are numbering each letter as follows (total of 52 letters including upper and lower cases):

9) When Client sends data to Server, each letter in the plaintext is encrypted as follows: a. y = ek'(x) (x + k') mod 52 (where x is a letter in the plaintext and y is a letter in ciphertext transmitted to the Server) b. After encrypting the plaintext, the Client must display (plaintext, ciphertext) pair on the screen.

The purpose of this assignment is to provide you with experience in analyzing and designing a database for a given problem. It will help you to understand the nature and purpose of database analysis and design.

This assignment is an individual assignment. There are no restrictions on the use of word processors or similar tools to produce submissions for this assignment.

Be sure to maintain regular back-ups for any models or material prepared with the aid of software. Loss of files will not be accepted as an excuse for the non-completion of this assignment.

Submit your assignment to the canvas site of this subject. Marked assignments will be available from the canvas website of this subject.

2. Problem Description - Affordable Rental Services (ARS) Affordable Rental Services (ARS) was established recently. ARS requires you to design a database system to enable a smoother operation of its rental accommodation services. The requirement collection and analysis phase of the database design process has provided the following data requirements specifications for the ARS database and query transactions that should be supported by the database. ARS has four branches in Canberra. The details of ARS branches are given below:

Branch name Address ARS Dickson 150 Camilla way, Dickson2662, ACT ARS Bruce 12 Page St, Bruce 2617, ACT ARS Franklin 12 Trent St, Franklin 2912, ACT ARS Woden 221 Wonder St, Woden 2606, ACT

ARS database will record and store all data about each of their clients including the client's first and last name, postal address, and home address (street number, street name, suburb, post-code, city, state), gender, date of birth, telephone number and email address. The name (first and last name), contact telephone number, and email address of the client's next-of-kin are also stored in the ARS database. For each client, the system records and stores all activities of each client including the client's accommodation booking, invoices, and payments that each client has made as well as any unpaid invoices. Each client information stored relates to those that made a booking or currently renting a room from by ARS. Clients may rent a room from any of the three ARS hotels or any of the ARS service apartments. ARS has ten service apartments.

ARS has several staff members. For each staff member, the following data is stored in the ARS database: staff first and last name, staff number, position, gender, date of birth, details of the branch (i.e., Branch number and address), and section details (i.e., Section number and name) that the staff member works in, internal telephone number, email address. Each ARS branch consists of four sections. These are the agent accommodation booking and reservation section, administration section, accounts and payment section, and maintenance section.

The information about each section is stored in the ARS database. The information about each section includes section number, section name, location, branch number, telephone number, and email address. Each section has one telephone and one email address.

ARS works with several travel agents. Travel agents make accommodation bookings for clients for ARS accommodations. Travel agent details are recorded in the ARS database and each travel agent is given a travel agent number.

The travel agent accommodation booking and reservation section of ARS are responsible for the monitoring of the accommodation booking and reservation. The data stored about each travel agent includes the full name of the travel agency, location, travel agent first and last name, travel agent number, position, gender, date of birth, internal telephone numbers, the e-mail address of the travel agent, and the website of the travel agency. Each travel agent can have up to three telephone numbers and three emails.

ARS provides three hundred single and double bedrooms in their three hotels as well as their ten two bedrooms fully furnished service apartments. Each hotel has a hotel manager, and each service apartment has a service apartment manager. ARS stores full details of its accommodations. For hotel accommodation, the ARS database stores the hotel number, room number, room type, daily rental price, and hotel address. For service apartments ARS database stores apartment number, daily rental price, and its address.

A client may rent a room in a hotel or rent a service apartment. Rental agreements are issued at the start of each rental period with a minimum rental period of one day. Each agreement between ARS and its clients is uniquely identified using a rental number. The data stored for each rental includes rental number, duration (start and end date), client's name, and accommodation details.

At the start of each rental, a client is given an invoice for the rental period. Each invoice has a unique invoice number. The data stored about each invoice includes the invoice number, rental number, duration (start date and end date), payment due date, amount to be paid, client's full name and accommodation details, and name of staff who issued the invoice.

Each client is required to make a payment for each of their accommodation bookings. The method of payment can be cash, check, or credit card. The payment can be performed via ARS branches, the ARS website, or travel agencies that booked the client's accommodation.

The data stored about each payment includes the payment number, invoice number, rental number, duration (start date and end date), date of payment, the amount paid, client's full name, and accommodation details.

ARS has a gym at each of its hotels. ARS gyms are used by ARS clients that have rented a room at any of ARS hotels for free.

ARS database record and store the data about each of its gym instructors including first and last name, email address, postal address, and home address (street number, street name, suburb, post-code, city, state), sex, and type of gym classes that an instructor can conduct. The name (first and last name), contact telephone number, and address (street number, street name, suburb, post-code, city, state) of the instructor's next-of-kin is also stored in the ARS database.

ARS offers several types of gym classes. These are namely Body Balance, Body Pump, and Yoga classes. An instructor can teach up to two different class types. The details of all classes that each instructor can teach are also stored in the ARS database. These details are instructor number, class number. The details of each gym class are also stored in the ARS database. These details are the class number, the class name.

ARS has several staff members in each gym. For each staff member, the following data is stored in the database system of ARS: staff first and last name, staff number, position, sex, date of birth, section number and branch number where he/she works, internal telephone number, email address and hotel number.

ARS has a loyalty program. Clients of ARS can join the ARS loyalty program and receive one point for every dollar that they spend on ARS accommodations. Each client of ARS that joins the ARS loyalty program receives a loyalty program number and their ARS loyalty points are stored with the ARS loyalty customer number in the ARS database. These details are client number, the total amount spent by a client at ARS accommodations, date, client loyalty program number, total loyalty points received, the rental number for the accommodation booked.

Additional instructions from the student: Requirement: For the scenario in the problem above: (a) Identify entity types and their attributes, including the primary keys (in third normal form). (25 Marks)

(b) Compile an E-R diagram for the above scenario based on your solution part (a) above. (State all assumptions that you have made)

(a) The ACID properties are frequently used to characterize value-based semantics. (I) Define "atomicity" as utilized in the ACID setting. [1 mark] (ii) Define "toughness" as utilized in the ACID setting. [1 mark] (b) Write-ahead logging is a usually utilized plan to achieve value-based semantics while putting away an information base on a square stockpiling gadget, for example, a hard plate. (I) Under what conditions, during compose ahead log recuperation, can a exchange in the UNDO list be moved to the REDO list? [2 marks] (ii) Synchronously flushing submit records to circle is costly. How might we securely lessen coordinated I/O procedure on a high-throughput framework without forfeiting ACID properties? [2 marks] (iii) Describe two execution changes that could emerge from utilizing your answer to part (b)(ii). [2 marks] (c) (I) Transaction records in a compose ahead logging plan contain five fields: hTransactionID, ObjID, Operation, OldValue, NewValuei, however putting away the complete old and new qualities can consume huge measures of room. One methodology that may be utilized, for reversible activities being applied to certain information like XOR by a steady, is to store just the consistent contentions, instead of the full when information. What issues could happen because of this plan decision? (ii) Write-ahead logging frameworks should know the real on-plate area size for the compose ahead log to accurately act. A deviant plate merchant chooses to rebrand its 512-byte area circles as 2K-area plates, and changes the worth announced back to the information base framework. How should this influence data set uprightness? [4 marks] (iii) Explain how an information base seller who knows about the issue portrayed in part (c)(ii) moderate this issue in programming, and what impediments may there be to this methodology. [4 marks] 9 (TURN OVER) CST.2013.5.10 9 Concurrent and Distributed Systems Sun's Network File System (NFS) is the standard conveyed document framework utilized with UNIX, and has gone through a movement of variants (2, 3, 4) that have slowly further developed execution and semantics. (a) Remote technique call (RPC) (I) Explain how Sun RPC handle byte request (endianness). [2 marks] (ii) This approach might bring about pointless work. State when this happens and how should this be stayed away from. [2 marks] (b) Network File System variant 2 (NFSv2) and rendition 3 (NFSv3) (I) A key plan premise for NFS was that the server be "stateless" with deference to the client. State how this affects dispersed document securing in NFSv2 also, NFSv3. [2 marks] (ii) Another key plan premise for NFSv2 was the "idempotence" of RPCs; what's the significance here? [2 marks] (iii) One vital improvement in NFSv3 was the expansion of the READDIRPLUS RPC. Make sense of for what reason did this helps execution. [4 marks] (iv) NFSv3 carries out what is named "near open consistency" for document information reserving: assuming that client C1 keeps in touch with a record, shuts the document, and client C2 now opens the record for read, then, at that point, it should see the consequences of all composes gave by C1 preceding close. Notwithstanding, assuming C2 opens the document before C1 has shut it, then C2 might see some, all, or none of the composes gave by C1 (and in inconsistent request). Near open consistency is accomplished through cautious use of coordinated RPC semantics, joined with document timestamp data piggybacked onto server answers on all RPCs that work on records. Make sense of how near open consistency permits execution to be gotten to the next level. [4 marks] (v) NFSv3 adds another RPC, ACCESS, permitting the client to assign access control checks at document open opportunity to the server, as opposed to performing them on the client. This permits client and server security models to vary. Make sense of how this expansion additionally assists execute with shutting to-open consistency within the sight of perused storing.

(a) The ACID properties are frequently used to characterize value-based semantics. (I) Define "atomicity" as utilized in the ACID setting. [1 mark] (ii) Define "toughness" as utilized in the ACID setting. [1 mark] (b) Write-ahead logging is a usually utilized plan to achieve value-based semantics while putting away an information base on a square stockpiling gadget, for example, a hard plate. (I) Under what conditions, during compose ahead log recuperation, can a exchange in the UNDO list be moved to the REDO list? [2 marks] (ii) Synchronously flushing submit records to circle is costly. How might we securely lessen coordinated I/O procedure on a high-throughput framework without forfeiting ACID properties? [2 marks] (iii) Describe two execution changes that could emerge from utilizing your answer to part (b)(ii). [2 marks] (c) (I) Transaction records in a compose ahead logging plan contain five fields: hTransactionID, ObjID, Operation, OldValue, NewValuei, however putting away the complete old and new qualities can consume huge measures of room. One methodology that may be utilized, for reversible activities being applied to certain information like XOR by a steady, is to store just the consistent contentions, instead of the full when information. What issues could happen because of this plan decision? (ii) Write-ahead logging frameworks should know the real on-plate area size for the compose ahead log to accurately act. A deviant plate merchant chooses to rebrand its 512-byte area circles as 2K-area plates, and changes the worth announced back to the information base framework. How should this influence data set uprightness? [4 marks] (iii) Explain how an information base seller who knows about the issue portrayed in part (c)(ii) moderate this issue in programming, and what impediments may there be to this methodology. [4 marks] 9 (TURN OVER) CST.2013.5.10 9 Concurrent and Distributed Systems Sun's Network File System (NFS) is the standard conveyed document framework utilized with UNIX, and has gone through a movement of variants (2, 3, 4) that have slowly further developed execution and semantics. (a) Remote technique call (RPC) (I) Explain how Sun RPC handle byte request (endianness). [2 marks] (ii) This approach might bring about pointless work. State when this happens and how should this be stayed away from. [2 marks] (b) Network File System variant 2 (NFSv2) and rendition 3 (NFSv3) (I) A key plan premise for NFS was that the server be "stateless" with deference to the client. State how this affects dispersed document securing in NFSv2 also, NFSv3. [2 marks] (ii) Another key plan premise for NFSv2 was the "idempotence" of RPCs; what's the significance here? [2 marks] (iii) One vital improvement in NFSv3 was the expansion of the READDIRPLUS RPC. Make sense of for what reason did this helps execution. [4 marks] (iv) NFSv3 carries out what is named "near open consistency" for document information reserving: assuming that client C1 keeps in touch with a record, shuts the document, and client C2 now opens the record for read, then, at that point, it should see the consequences of all composes gave by C1 preceding close. Notwithstanding, assuming C2 opens the document before C1 has shut it, then C2 might see some, all, or none of the composes gave by C1 (and in inconsistent request). Near open consistency is accomplished through cautious use of coordinated RPC semantics, joined with document timestamp data piggybacked onto server answers on all RPCs that work on records. Make sense of how near open consistency permits execution to be gotten to the next level. [4 marks] (v) NFSv3 adds another RPC, ACCESS, permitting the client to assign access control checks at document open opportunity to the server, as opposed to performing them on the client. This permits client and server security models to vary. Make sense of how this expansion additionally assists execute with shutting to-open consistency within the sight of perused storing.