Detailed study

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 detailed study is more in-depth than the option described in the study. The detailed study shows how the system meets the requirements. Detailed studies can be created on several topics. Solution options can be developed and evaluated in the detailed study. In IT projects, the outcomes of the detailed studies are summarized in the system architecture. They form an appendix to the system architecture.

Background

Reason for preparing the detailed study.

Example: a detailed study will be created for user administration and the role and access concept.

Requirements

The requirements that affect the entire future system are described in the system requirements document. If the detailed study concerns only one subject area, the corresponding applicable requirements from the study are to be listed.

ID	Requirement	Type 1	Acceptance criterion	Importance 2	Urgency 3
A1	Enter course registration	F	Successful tests according to test case specification	5	5
A4	Transmit data with encryption	S	Successful tests according to test case specification	5	4
A5	Ensure methodological coherence	C	Validate method components with HERMES CD	5	3
1) Type = Requirement type: B = Business organization, F = Functional, Q = Quality, S = Security, M= Migration, A = Architecture, O = Operation, C = Compliance (legislation, directives, standards and guidelines) 2) Importance: 5 = mandatory implementation; 4 = very important; 3 = important; 2 = normal; 1 = not important 3) Urgency: 5 = must be implemented immediately, 4 = very urgent, 3 = urgent, 2 = normal, 1 = not urgent

Table 2:	Relevant rough requirements from the study

Solution concept with options and evaluation

Option 1

Description

Possible description grid

Description
Brief description	Optimized business organization with centralized operation
Development and process structure	Proposed solution with reference to the business organization concept
Functions & data (IT application)	Proposed solution; assignment to subsystem/component
Interfaces	Proposed solution
Hardware (screens, printers, scanners, servers, etc.)	Proposed solution
Operating systems, database, telecommunications	Description of proposed solution

Table 3:	Description grid

Requirement coverage

ID	Requirement	Assignment to subsystem/component	Evaluation of requirement coverage
nn	Enter course registration	100%
nn	Display confirmation	100%

Table 4:	List of requirements with assignment and coverage

Option nn

Description

Requirement assignment

Feasibility evaluation – comparison of options

Evaluation criteria	N1*	N2*	N3*
Costs
Project costs	8	7	4
Recurring costs	7	7	9
Benefits
Quantifiable benefit
Non-quantifiable benefit
Risks
Sustainability
Legal basis
Other
* On: 9-1; 9 = very good; 1 = very bad

Table 5:	Feasibility evaluation for each option

Recommendation

Brief description of the preferred option On.

Abbreviations and glossary

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

Table 6:	Abbreviations and glossary

Contents

List of changes	1

Description	1

1	Background	2

2	Requirements	2

3	Solution concept with options and evaluation	2

3.1	Option 1	2

3.1.1	Description	2

3.1.2	Requirement coverage	3

3.2	Option nn	3

3.2.1	Description	3

3.2.2	Requirement assignment	3

4	Feasibility evaluation – comparison of options	3

5	Recommendation	3

Abbreviations and glossary	4

Contents	5

Tables	5

Tables

Table 1:	Change control	1

Table 2:	Relevant rough requirements from the study	2

Table 3:	Description grid	2

Table 4:	List of requirements with assignment and coverage	3

Table 5:	Feasibility evaluation for each option	3

Table 6:	Abbreviations and glossary	4