Business Process Modelling for Inshore Insurance Ltd

Running head: BUSINESS PROCESS MODELLING 1
Business Process Modelling
Student Name
Institutional Affiliation

BUSINESS PROCESS MODELLING 2
Table of Contents
1.0 Introduction........................................................................................................................................3
1.1 Introduction....................................................................................................................................3
1.2 Solution Scope...............................................................................................................................3
1.3 Solution Overview.........................................................................................................................3
1.4 Constraints.....................................................................................................................................4
1.5 Exclusions......................................................................................................................................5
2.0 Use Cases...........................................................................................................................................5
2.1 Actors.............................................................................................................................................5
2.2 Use Case Diagrams........................................................................................................................6
3.0 Design Overview...............................................................................................................................6
3.1 Solution Architecture.....................................................................................................................6
3.1.1 Project Governance Process...................................................................................................7
3.1.2 IT Infrastructure Solution......................................................................................................8
3.1.3 Infrastructure Security...........................................................................................................8
3.1.4 Application Solution..............................................................................................................9
3.1.5 Data Solution.......................................................................................................................10
3.2 Capacity Requirements................................................................................................................10
3.3 System Interfaces.........................................................................................................................10
3.4 Constraints and Assumptions.......................................................................................................11
4.0 System Object Model.......................................................................................................................11
4.1 Sub Systems.................................................................................................................................11
4.2 Subsystem Interfaces...................................................................................................................11
5.0 Object Collaboration........................................................................................................................12
5.1 Collaboration Diagrams...............................................................................................................12
5.2 Access Model...............................................................................................................................12
6.0 Non-Functional Requirements.........................................................................................................12
6.1 Performance Considerations........................................................................................................12
6.2 Design Constraints.......................................................................................................................13
6.3 Test Criteria.................................................................................................................................13
6.4 Proof of Compliance....................................................................................................................14
7.0 Conclusion.......................................................................................................................................14
8.0 References........................................................................................................................................15

BUSINESS PROCESS MODELLING 3
1.0 Introduction
1.1 Introduction
Conducting system analysis and developing requirements specification is the first step in meeting
the business requirements. After a critical analysis, Inshore Insurance Ltd (IIL) realize that their
current Risk Analysis Product (RAP) application has some setbacks and cannot address some of
the business requirements like timing and locating crime incidences and accidents. Therefore, IIL
needs an IT solution that will solve the identified problems. Data storage is one of the essential
requirements that the solution should address because of the increasing amount of data that the
business is handling. The institution expects that the volume of data will increase drastically and
the solution should be able to operate on them using a single platform.
1.2 Solution Scope
The IIL board expects relevant recommendations and high-level assessment of the IT solution.
The scope of the project is that the Risk Analysis Product that is already in place will be used to
process all the required functionalities and user requests. The institution has utilized a virtualized
in-house platform to host the RAP application which will remain as an independent project. The
solution should also propose a single platform that will be able to process and handle huge
volume of primary and generated data.
1.3 Solution Overview
The IT solution should be able to address the storage and incident reporting challenges currently
faced by the institution. The volume of data is increasing and a high rate and the proposed IT
solution should have the ability to generate, store, examine, manage, and archive the data.
additionally, one of the key requirements that the solution should meet is the ability to record the

BUSINESS PROCESS MODELLING 4
location and time when a crime or accident occurs. It should also have access control mechanism
so as to restrict the number of users accessing the system to the specified number.
1.4 Constraints
There are several constraints that is associated with the project including human resources,
financial constraints, data sensitivity, and risks. Data sensitivity is an important factor that should
be addressed in software development. It is the responsibility of the institution that the data
collected is kept safe from any unauthorized access or external attacks to maintain privacy and
confidentiality. Benefits realization plan aids in identifying, executing, and sustaining the
benefits associated with the IT solution. it is essential to have such a plan so as to give guidelines
on how to achieve the project objectives and benefits. The realization plan reflects on the
strategic goals that the business anticipates for instance, productivity, process improvements,
quality, customer satisfaction, efficiency, revenue generation, and rate of customer growth. In
project management, a threat model is a crucial tool for managing risks. Having a threat model
will help the project team to identify security threats that may face the system, prioritizing them,
and providing mitigation strategies.
Figure 1: Threat Risk Modelling