Aussie Car Insurance provides automotive insurance to car owners. Initially, customers are required to fill out an Insurance Application Request Form. The details of this form are kept in
Aussie Car Insurance's application pending file until a policy is issued. A Driver's Record
Request Form is then produced and sent to the Motor Registration Branch (MRB), which sends back the Driver's Record Report to Aussie. The details of these are stored. (These details are updated whenever a policy holder notifies the company of any convictions for driving offences. In such cases, the original policy is endorsed and future premiums may be increased).
Vehicle Registration Request Forms are sent to MRB. MRB then supplies the Vehicle
Registration details. If the vehicle and driver information is found to be acceptable, a policy contract is drawn up and the customer is sent a copy of this document along with a policy payment slip.
Policy renewal notices are sent to policyholders annually. If payment is not received within one month a reminder notice is sent out. If payment has not been received within three months the policy is cancelled.
Assumptions
Notice that the word policyholder has been changed to Car Owner (which better covers all cases described). Also, notice that the words 'form' and 'report' have been replaced to reinforce the fact that data (moving) should be modelled not format (or implementation dependent) details.
Gifts Online provides online purchasing facilities so guests who have been invited to an occasion can select gifts from lists that have been prepared by the host(s) of

the occasions.
This will include ordering, provision of purchasing facilities, provision of secure ecommerce transactional facilities through to waiving and delivery.
After guest has entered their username and password, the user can select the name of the person(s) for Mom the occasion is being held from a keyword search facility. The system provides the user with the gifts that the host would like guests to look at. The user can view and select one or more gifts by looking at the Price, category, and details.
After the user has placed the gift(s) in the shopping trolley the user confirms the order. At this point a Secure Payment Gateway connection is established and the user is required to enter credit card details. After finally submitting the order, the company inventory and payments databases are updated and the user is sent an email with order confirmation and delivery details.
For the educator
This system can form the basis of discussion about similar systems that the students have interacted with or have heard of.
Typically, a business system analyst gets fragmented views of any system and user further analysis to complete the picture as it were. Students should become aware that the system supports a number of functions that are not available to general users and the processing for which is not described here (eg. Management of: users, inventory, suppliers, pricing and so on. For example, students need to be aware that Guests and the event to which they are invited must have already been created prior to their visiting the web site.
This example can be leveled to a 3th level because the Level 1 process Confirm
Payment has 5 love and is too complex to show all the processing that will be required by the system.
Data Stores do not provide a normalized view of data at rest. For example, for simplification, the Gifts data store contains master-record details of all gifts and gift types as well as gift inventory details (eg Quantity on hand, quantity ordered).

When an Australian meat exporter wishes to send product overseas, they must utilise the
AQIS (Australian Quarantine Inspection Service) meat export certification system.
The exporter applies for a Health Certificate from AQIS, providing the product details, including the slaughter date, abattoir, destination country and product description. This
"Request for Permit" (RFP) is stored.
The Health Inspector is notified of the lodgement of the RFP and inspects the meat and the documentation, providing an endorsement or a rejection. If the RFP is endorsed, a Health
Certificate is issued with the details provided in the RFP and the expiry date for the Health
Certificate. The HC is then printed (for attachment to the container for shipping) and forwarded electronically (as an EDI message) to the quarantine authority in the destination country.
Health Certificates once issued are stored. If the RFP is rejected, the applicant is advised of the reasons for the rejection. Often this is the result of administrative errors, and the applicant corrects these and reapplies. RFPs expire after 7 days, and are then deleted from the RFP file.
When the goods arrive on the dock or at the airport at the destination country, they are inspected by the local quarantine authority using the electronic HC. Once this inspection is completed AQIS is notified of the status of the goods and if they are rejected, the reasons for the rejection are passed back to AQIS. The Health Certificate for this shipment is then cancelled in the Health Certificates file.