Professional Documents
Culture Documents
DIRECTORATE-GENERAL
INFORMATICS
Information systems Directorate
European Commission
Date: 38491.92
Version: 0.0
Authors: admin
Revised by:
Approved by:
Public:
Reference Number: MAP-2005-008 rev2
Commission européenne, B-1049 Bruxelles / Europese Commissie, B-1049 Brussel - Belgium. Telephone: (32-2) 299 11 11.
1. INTRODUCTION......................................................................................................................................5
1.1. Purpose......................................................................................................................................................5
1.2. Scope.........................................................................................................................................................5
1.3. Definitions, Acronyms, and Abbreviations..............................................................................................5
1.4. References.................................................................................................................................................6
1.5. Overview...................................................................................................................................................6
2. POSITIONING...........................................................................................................................................6
3. PROPOSED APPROACH........................................................................................................................8
6. FEATURES...............................................................................................................................................14
7. PLANNED RESSOURCES.....................................................................................................................16
8. CONSTRAINTS.......................................................................................................................................16
[The introduction of the Vision document provides an overview of the entire document. It
should include the purpose, scope, definitions, acronyms, abbreviations, references, and
overview of this Vision document.]
[The introduction could per example be :]
The purpose of this document is to collect, analyse, and define high-level needs and features of
the <<System Name>>. It focuses on the capabilities needed by the stakeholders, and the target
users, and why these needs exist. The details of how the <<System Name>> fulfils these needs
are detailed in the use-case and supplementary specifications.
1.1. Purpose
[This paragraph is optional] - [Maximum length : 5 lines]
[Specify the purpose of this Vision document.]
1.2. Scope
[Maximum length : 1 page]
[A brief description of the scope of this Vision document; what Project(s) it is associated with
and anything else that is affected or influenced by this document.]
Description (EN)
Description (FR)
Domain1
1
Domains momentarily apply to one of the following corporate domains : Document
management, Other External (policy related), Financial, Human Resources, Other Internal
(administration), Methodology (RUP), Portal (internal), Resource planning / reporting, Security,
Data Warehouse.
<Project Name> Vision Document - Page 4 / 15
Document Version 0.0 dated 38491.92
1.4. References
[Maximum length : ½ page]
[This subsection provides a complete list of all documents referenced elsewhere in the Vision
document. Identify each document by title, report number (if applicable), date, and publishing
organisation. Specify the sources from which the references can be obtained. This information
may be provided by reference to an appendix or to another document.]
1.5. Overview
[This paragraph is optional] [Maximum length : 10 lines]
[This subsection describes what the rest of the Vision document contains and explains how the
document is organised.]
2. POSITIONING
[An Information System position statement communicates the intent of the application and the
importance of the project to all concerned personnel.]
2
This refers to the Information systems typology in the Commission defined in the annex 2 (§ 1)
of the IT governance communication SEC(2004)1267
3
This refers to the Information System classification (Normal, High, Exceptional) defined in the
Information System Security Policy – Part I (§ 2.3 and 2.4)
<Project Name> Vision Document - Page 6 / 15
Document Version 0.0 dated 38491.92
2.4. New or updated Business Processes proposed for automation
[Maximum length : 1 to 10 lines per process]
[IT GOV] [Identify the business processes affected by the new information system. This list is a
subset of the CEAF Process Glossary. For example:]
Description (FR)
Description (EN)
Domain4
Name
ID
3. PROPOSED APPROACH
[To effectively provide Information Systems and services that meet your stakeholders’ and users'
real needs, it is necessary to identify and involve all of the stakeholders as part of the
Requirements modelling process. You must also identify the users of the system and ensure that
the stakeholder community adequately represents them. This section provides a profile of the
stakeholders and users involved in the project, and the key problems that they perceive to be
addressed by the proposed solution. It does not describe their specific requests or requirements
as these can be captured in a separate stakeholder requests artefact. Instead, it provides the
background and justification for why the requirements are needed.]
4
Domains momentarily apply to one of the following corporate domains : Document
management, Other External (policy related), Financial, Human Resources, Other Internal
(administration), Methodology (RUP), Portal (internal), Resource planning / reporting, Security,
Data Warehouse.
<Project Name> Vision Document - Page 7 / 15
Document Version 0.0 dated 38491.92
• How does this Information System or service support your goals?]
4.2. Stakeholders
[Maximum length : ½ page per stakeholder]
[There are a number of stakeholders with an interest in the development. They are the future
users but also non-user stakeholders. Present a list of all stakeholders.]
Name [Name the stakeholder type (e.g. DG representative, Project Owner,
Production Manager, Designer, Citizen, employee, accountant …)]
Description [Briefly describe the stakeholder.]
5
The user population may be DG (internal to the DG), COM (several DGs of the Commission),
INST (internal to the Institutions), EU&MS (INST and the Member states) or ROW (particular or
general public outside the Commission). It is assumed that these populations are nested, DG being
the innermost and ROW being the most peripheral level. Indicate the outmost level.
<Project Name> Vision Document - Page 8 / 15
Document Version 0.0 dated 38491.92
• What solutions does the stakeholder or user want?]
[It is important to understand the relative importance the stakeholder or user places on solving
each problem. Ranking and cumulative voting techniques indicate problems that must be solved
versus issues they would like addressed.
[This section provides a high level view of the Information System capabilities, interfaces to
other applications, and systems configurations. This section usually consists of five subsections,
as follows:
• Information System perspective
• Assumptions and dependencies
• Cost and Timing
• Quality Ranges and Information System requirements
• Licensing and Installation]
5.4.1. Availability
[Define the required level of availability. For example:]
The System shall be available during working hours (7.00 AM to 21.00 PM) including
weekends. However, scheduled maintenance in weekends is acceptable. All maintenance
activities shall be planned and announced well in advance.
5.4.2. Usability
[Define the required level of availability. For example:]
The System shall be easy-to-use and shall include search and on-line help facilities.
5.4.3. Maintainability
[Define the required level of maintainability. For example:]
The System shall be designed for ease of maintenance. All data should be table-driven and
modifiable without recompilation of the System.
6. FEATURES
8. CONSTRAINTS