Resources
- Identity Use Cases & Scenarios.
- FIDIS Deliverables.
- Identity of Identity.
- Interoperability.
- D4.1: Structured account of approaches on interoperability.
- D4.2: Set of requirements for interoperability of Identity Management Systems.
- D4.4: Survey on Citizen's trust in ID systems and authorities.
- D4.5: A Survey on Citizen’s trust in ID systems and authorities.
- D4.6: Draft best practice guidelines.
- D4.7: Review and classification for a FIDIS identity management model.
- D4.8: Creating the method to incorporate FIDIS research for generic application.
- D4.9: An application of the management method to interoperability within e-Health.
- D4.10: Specification of a portal for interoperability of identity management systems.
- D4.11: eHealth identity management in several types of welfare states in Europe.
- Profiling.
- Forensic Implications.
- HighTechID.
- Privacy and legal-social content.
- Mobility and Identity.
- Other.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
Mapping the information
The information may be mapped onto the models as well as onto a matrix. Table 2 shows a typical matrix for developing an identity management system: one axis being the five principles of information management and the other axis being the stages of development of the identity information system. In the present document, development refers concretely to the development of the information system for supporting our research reflecting on the concept of Identity, and arguably to identity management systems developers in general. The approach, given its status as a method for systems development, addresses the tasks of developers rather than those of end users.
The information may be mapped onto the models as well as onto a matrix. Table 2 shows a typical matrix for developing an identity management system: one axis being the five principles of information management and the other axis being the stages of development of the identity information system. In the present document, development refers concretely to the development of the information system for supporting our research reflecting on the concept of Identity, and arguably to identity management systems developers in general. The approach, given its status as a method for systems development, addresses the tasks of developers rather than those of end users.
|
Information
|
Duty of Care |
Processes and Procedures |
Enabling Technologies |
Monitor And Control
|
Requirements
|
Data Input & output Interoperability activities |
Directors & Operators Legal Audit IT
|
Internal External |
System Spec Networks Communications |
Internal External |
Analysis and Design
|
System model Simulation Tests Benchmarks
|
Designers Analysts Focus Groups |
Input processes Operational processes Output processes |
Alternative solutions |
Audit Points Audit Specs |
System Build
|
System Specs Input Output |
Project management team |
Relationships with stakeholders |
Installation Testing Acceptance |
Audit Points Audit Specs |
Operations
|
Performance Capacity |
Operators Managers Users |
Day to Day Operations Availability Performance Maintenance
|
Hardware Operating System Software Communications |
Frequency and nature of audits |
Maintenance
|
Decision analysis Continue Enhance Replace
|
Directors Senior management Operators Users |
Maintenance processes |
System Transfers Backups Contingencies |
Maintenance audit |
Table 2
12 / 16 |