Situation analysis

Project name

Classification	Select an element
Status	Select an element
Program name
Project number
Project manager	Project manager
Version	0.1
Date	Click here to enter a date
Project sponsor	Project sponsor
Author(s)
Distribution

List of changes

Version	Date	Change	Author
0.1

Table 1:	Change control

Description

The situation analysis describes and analyzes the current situation and future developments. It supplements the situation analysis in the study and goes into more depth. Together with the system objectives, the situation analysis forms the functional basis for the definition of the system requirements to be met by the project outcome. It is neutral in terms of objectives and solutions.

Introduction

General description of the current situation, possible need for action

Basic reflections on developments and trends, such as general market trend, increasing user requirements or changes in the situation since the study was prepared

Business organization

The current business organization is described here. Existing documents are mostly used as a basis. If nothing is available, it is necessary to check the extent to which documentation on the actual situation of the business organization is needed. It is a case of drawing up a rough description of the most important tasks/goods/services and the main processes, as well as the organizational structure.

Organization chart, function descriptions, process landscape, current process descriptions, quantity structure of business cases, employees, customers, etc.

Description of the current system

Objective and intended use, function

Explanations regarding the current system in prose

Documentation on system and operating organization

Document name	Description
V7 user manual	Description of the IT application, including user cases and practical examples

Table 2:	Documentation

Parameters and specifications

Document name	Description
Security instructions	Description of specifications with regard to data security and data protection

Table 3:	Parameters and specifications

System description

Description of system landscape and system architecture

General illustrations and descriptions

System: S01 System name

Technical information on system nnn

Topic	Detailed information
Architecture model	3-tier architecture, standard xyz
Software	Standard IT application xyz
Location	Bern
Operator	Internal operation
Supplier	xyz
Developer	aaa
Users	132
Size of database	6.5 GB
Operating costs per year	32,000	2019
Other operating costs	Paper: 25,000 p.a.
Total development costs	370,000
Support costs per year	55,000	2019
Investment costs from launch to date	490,000

Table 4:	Technical information

Information security and data protection

Description of the current situation

Quantities and frequencies

Material resources used

No.	Description	Explanation
01	PCs	25
02	Vehicles	13 station wagons

Table 5:	Product or IT system/material resources used

Transactions

Transaction	Average per time unit	Peak per time unit	Minimum per time unit
Payments	8,500/mth	20,000/mth	500/mth

Table 6:	Transactions

Data sets

Object type	Stock	Mutations per time unit	Inflows per time unit	Outflows per time unit
Requester	20,000	1,500/mth	750/mth	500/mth

Table 7:	Data sets and movements

Analysis of strengths, weaknesses and causes

Strengths

Prose description including considerations as to whether the strengths could be maintained or even enhanced in the future

No.	Description	Cause	Maintenance prospects*
01	Practically faultless outgoing payments	Highly qualified employees	+
* Maintenance prospects: + = enhancement possible / H = high / M= medium / N= low

Table 8:	Strengths and their causes

Weaknesses

Prose description including considerations as to whether the weaknesses could be eliminated

No.	Description	Cause	Elimination prospects*
01	Inefficient handling of the business process Pxxx	Lack of functionality in IT application	H
* Elimination prospects: H = high / M= medium / L= low

Table 9:	Weaknesses and their causes

Causes

Findings based on the analysis of (direct) causes

System context

Description of the system context

Description and diagram

The description of the system context shows which aspects are relevant for defining and understanding the requirements of the system in question

Context diagram

Description and illustration in the form of a data flow or use case diagram

The context diagram shows all players (stakeholders, peripheral systems) that interact with the product/system and that wish to:

produce flows of information and material

receive flows of information and material

Abbreviations and glossary

Abbreviation/specialist term	Explanation
HERMES	Methodology for projects and programs HERMES 5 is an eCH standard

Table 10:	Abbreviations and glossary

Contents

List of changes	1

Description	1

1	Introduction	2

2	Business organization	2

3	Description of the current system	2

3.1	Objective and intended use, function	2

3.2	Documentation on system and operating organization	2

3.3	Parameters and specifications	2

3.4	System description	2

3.4.1	Description of system landscape and system architecture	2

3.4.2	System: S01 System name	3

3.5	Information security and data protection	3

4	Quantities and frequencies	3

4.1	Material resources used	3

4.2	Transactions	4

4.3	Data sets	4

5	Analysis of strengths, weaknesses and causes	4

5.1	Strengths	4

5.2	Weaknesses	4

5.3	Causes	4

6	System context	5

6.1	Description of the system context	5

6.2	Context diagram	5

Abbreviations and glossary	6

Contents	7

Tables	8

Tables

Table 1:	Change control	1

Table 2:	Documentation	2

Table 3:	Parameters and specifications	2

Table 4:	Technical information	3

Table 5:	Product or IT system/material resources used	3

Table 6:	Transactions	4

Table 7:	Data sets and movements	4

Table 8:	Strengths and their causes	4

Table 9:	Weaknesses and their causes	4

Table 10:	Abbreviations and glossary	6