its a part of system design, just need the object collaboration and non functional requirements of a cas study.

 this is the case study
Inshore Insurance Ltd (IIL) is a profitable Australian regulated financial institution with
assets in excess of $1 billion. Head office is in Sydney and there are branches in every
state capital city. IIL provides General and Accident Insurance services directly and via
brokers to the Australian marketplace. IT services are managed in-house and the main
data centre is in the head office. IIL uses cloud services to do business with brokers and
has web enabled applications to service customers (policy holders) via the corporate web
site. Disaster recovery and document archiving uses an Australian 3rd party data centre.
Business Case
Research has concluded that the timing and location of the crimes and accidents which
result in personal, vehicular and household insurance claims have a direct relationship to
the frequency and cost. The IIL Board has directed IT to provide IT solutions sufficient to
prepare for the next budget cycle due Q4 2016. A Statement of Work has been completed
and preliminary estimates for the work has been included in the 2016/17 budget of $1.35
million.
Scope
The IIL Board seeks a high level analysis and recommendations for the IT solution. It is
assumed at the outset that the current IIL Risk Analysis Product (RAP) application will
provide the necessary functional processing services. The applications impact analysis will
be a separate project. RAP is hosted on the current virtualised in-house platform in the IIL
data centre. The solution must define a single platform to support a large volume of
primary and generated data sourced from existing in-house and cloud platforms.
Storage Requirements
Key factors: (note changes to factors)
 Highly sensitive competitive and personal private data
 Very large volumes of data, low transaction volumes
 Restricted number of users (six users only in HQ)
 Restricted report distribution (six users and CIO)
 Episodic localised workday access only
 Limited performance expectation
 RAP may comprise online and some batch (overnight) processing based on
priorities of jobs.
Capacity Data: (note changes to estimates)
 Estimated database size 10TB growing at between 50% to 70% pa
 Service extension for end of 2017 for new Location Intelligence initiatives will
initially add a further 10TB of highly sensitive data
 Data retention is 5yrs for personal data, 10yrs for vehicle data, and 20yrs for
home data.
Platform Security:
 The highest level of storage security is provided in-house for policy data and
customer information. This data has a higher level of security requirement.
Archived data is at the same security level as other archived customer and
business data.
Access Security:
 Less than 10 nominated users on desktop devices within HQ.
 RAP application is the only API required.
 Access and report distribution security is of equally sensitivity to stored data.
 All access and report distribution will be securely logg

i need you to help me with

1.0   Object Collaboration

1.1   Collaboration Diagrams describe the relevant system level Collaboration processes

1.2   Access Model describe the relevant access control system, rules and process

2.0   Non Functional Requirements

2.1   Performance Considerations list if relevant, including challenges like volume, security, cost

2.2   Design Constraints list relevant design constraints

2.3   Test Criteria include test criteria for the new platform

2.4   Proof of Compliance describe the evidence that the new solution is compliant