HW14 Composer: Smart parking

Create a Business Network Archive (BNA) with the appropriate models, transactions, and access constraints that fulfill the requirements below. The BNA must have an initial transaction (setupHomework) that sets up a ledger state, where the fulfillment of each requirement can be demonstrated (assuming that the ledger is empty before the call of the initial transaction). Transactions that would dynamically add participants or assets are not needed, unless noted explicitly under the requirements, except the initializer transaction.

Please test your solution on Composer Playground before submission.

For every Participant and Asset type, the unique identifier must be a non-optional String field with the name id. The value of the field must conform to the following format: <TYPENAME>_<COUNTER>. For example, if we have a Participant type named User, then the id of the first created user must be USER_0, the id of the second user must be USER_1, etc.

Problem statement

Implement a BNA for smart parking.

• There are two participant types: User and Company.
• Users have names and a list of number plates representing their cars.
• Companies have a name and assets representing parking spaces, which are identified by numbers (company-unique).
• Parking spaces aren't assigned for time periods.
• Users can reserve a parking space by specifying a plate number and a parking space number.
• Users cannot cancel their reservations.
• Reserved spaces cannot be reserved again until the reservation is canceled.
• Companies can add new parking spaces using a transaction if they specify the unique parking space number.

Additional requirements:

• The initializer transaction should set up at least a company with 2 parking spaces, and 2 users.
• Parking space additions needn't be checked for name conflicts (it can be assumed that companies will not try to add parking spaces whose numbers are already in the system).
• Parking space numbers are given by the company and are not necessarily sequential.
• Transactions that create users or companies are not required.

Example scenario

Alice and Bob want to reserve parking spaces at the company Claire's Parking, which has two parking spaces (1 and 2). Alice reserves the parking space 1 for her car (ABC-123), and the reservation is successful. Bob wants to reserve the same spot for his car (ABC-124), but the reservation fails. He doesn't want to reserve space 2 as he doesn't like even numbers, so he contacts the company which adds a new parking space (3), which he then reserves.

Transactions

• reserve
• addParkingSpace