[eOvB] rapport sjabloon - Joinup · Functional Design Message Box Service Directive Author Arjaan Peree Version 1.13 Status Definitive The Hague, 02-07-2009

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Functional DesignMessage Box Service Directive

Author Arjaan PereeVersion 1.13Status DefinitiveThe Hague, 02-07-2009

Functional Design 2/55

•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Document information

Author Status

Arjaan Peree DefinitiveProject Date

Message Box Service guidelines 02-07-2009Organisation Classification

ICTUTitle Location

Functional DesignVersion

1.13

HistoryDate Version Amendment Status Processed by

29-02-2008 0.1 Creation of document Arjaan Peree07-03-2008 0.2 Amendments after comments, further

additionsArjaan Peree

11-03-2008 0.3 Amendments after review 0.2 Arjaan Peree18-03-2008 0.4 Modified screen designs, added

parameters, worked out data model.Arjaan Peree

31-03-2008 0.5 Processed Screen Design Eden Arjaan Peree01-04-2008 0.6 Amendments after 0.5 review and

incorporated latest version of Eden screen designs.

Arjaan Peree

07-04-2008 0.7 Incorporated comments after 0.6 review

Arjaan Peree

14-04-2008 1.0 Incorporated comments after latest review. Created approval version.

Arjaan Peree

21/04/08 1.1 Incorporated comments after approval version

Arjaan Peree

24/04/08 1.2 Amendment to screen for reading message when a message is opened from the bin. In that situation it is not possible to delete a message again.

Arjaan Peree

02/10/08 1.3 PO Amendments Message box1st six must haves.

Freek Driesenaar

14-10-08 1.4 Adding other wanted functions Indra Henneman

13/01/09 1.5 Incorporating comments after discussion with Marieke

Arjaan Peree

21/01/09 1.6 Small amendments to text Arjaan Peree

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

10/02/09 1.7 Amendments to use cases, screens and data model

Arjaan Peree

12/02/09 1.8 Added latest version of data model Arjaan Peree25/02/09 1.9 Amendments after review round ICTU Arjaan Peree16/03/09 1.10 Amendments after meeting with EZ

and review Project DirectorsArjaan Peree

23-06-2009 1.11 Amendments after review Laura Ouwehand (PDL1) and Kristel Nieuwenhuys (TO) , draw up in new house style

Arjaan Peree

24-06-2009 1.12 Amendments after re-review from Laura Ouwehand.

Final version Arjaan Peree

02-07-2009 1.13 Amendments after re-review from Laura Ouwehand. Brought in line with screen design

Final version Arjaan Peree

Distribution listDate Distribution Presentation Version

06-03-2008 Bart Kooijman Developer 0.1Ria Volkers Project manager 0.1

07-03-2008 Bart Kooijman Developer 0.2Ria Volkers Project manager 0.2Daniel El Helou Environment team 0.2

01-04-2008 Ria Volkers Project manager 0.7Daniel El Helou Environment team 0.7Nathalie Looijmans Team leader 0.7

21/01/2009 Marieke Polderman Project manager 1.512/02/2009 Marieke Polderman Project manager 1.8

Willem Kossen Team Architect 1.8Jochem Knoops Technical team leader 1.8Peter de Wolff Project manager realisation 1.8Nathalie Looijmans Team leader 1.8Geert Moouwen Functional Designer 1.8Dirk-Jan de Groot Interaction Designer 1.8

10-03-2009 Laura Ouwehand Project management 1.9Laura Ouwehand Project management 1.10Kristel Nieuwenhuys Technical designer 1.10

24-06-2009 Laura Ouwehand Project management 1.1125-06-2009 Laura Ouwehand Project management 1.1202-07-2009 Laura Ouwehand Project management 1.13

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

ApprovalDate Name Version

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Introduction

The aim of the message box is to allow entrepeneursentrepreneurs and competent authorities to safely exchange messages intended for the execution of procedures and to allow them to exchange formalities with each other. The message box's origins can be found in the Services Act, which includes a description of the message box for this aim.Entrepeneurs and competent authorities have to log in to gain access to their message box. When they receive a message, the application will alert them by sending an email or sms text message.

In addition to the web interface, an interface will be created which allows competent authorities to exchange messages with the message box directly via their back office systems.

When this Functional Design is formally accepted, it will serve as a guiding document for the acceptance of the system by the client.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Content

1 Introduction1.1 Scope 71.1.1 Structure of the document 7

2 Operators 8

3 Functional Requirements: Use Cases 9

4 Non-functional requirements 18

5 Screen designs 195.1 Inbox / sent messages 195.2 Read message 225.3 Export message 245.4 Compose message 255.4.2 Subfunction find Competent Authorities as addressee 285.4.3 Subfunction enter addressee (by competent authority) 305.5 Select standard message 305.6 Add signature 315.7 Reply to message 325.8 Forward message 345.9 Move message to folder 365.10 Manage folders 365.11 Create new folder and change folder 385.12 Bin 395.13 Administrate settings 415.13.1 Administrate notification settings 415.13.2 Administrate standard messages 425.13.3 Overview of standard messages 435.13.4 Create new standard message 455.13.5 Administrate signature 465.14 Notification message entrepeneur 475.15 Notification message competent authority 47

6 Logging 49

7 Interface 507.1 Retrieve new messages 507.2 Retrieve all messages 507.3 Send messages 507.4 Delete messages 517.5 Retrieve address list of competent authorities 517.6 Authentication, Authorisation and Confidentiality 51

8 Rolls and rights 52

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

8.1 Rolls structure 528.2 Rights 52

9 Integration and the dutch PSC 58

10 Class Diagram 5910.1 Description of the classes 6010.2 Authentication 60

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

1 IntroductionThe primary aim of this designn is to describe the function of the message box

The functional design has two aims:Firstly, it explains to the client how the system works and marks the boundaries of the system.Secondly, the design provides the basis for the Developers who are involved in the realisation phase of the project.

1.1 ScopeThis document describes the message box as it is going to be realised to comply with the Services Act. This message box will be implemented as part of the personalised part of antwoordvoorbedrijven.nl, the Dutch single point of contact. The function of the message box will be of a sufficiently generic nature to allow it to be used in other environments as well.

1.1.1 Structure of the documentThe functional design can roughly be divided in two parts: The requirements and the detailed design. These parts can then be subdivided into:

RequirementsOperatorsFunctional specifications in the shape of Use case outline

Detailed designscreen designsroles and rightslogging

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

2 OperatorsThe following operators are recognised

● entrepeneurs, the term for an entrepeneur in the Services Act. In this document we also use the term entrepeneurs.

● employees of a competent authority. In the services directive, the term competent authority is used. This term will also be used in this document

● administrators● system of competent authority (user of the interface)

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

3 Functional Requirements: Use CasesThe functional requirements are set down in use cases. A choice is made to only include a short description of the use case in this FD, a so-called Use Case Outline. The reason for this is that the example screens needed to be developed very soon. Extensive Use Cases offer little added value in relation to the required time investment.

The use cases are prioritised in accordance with the MoSCoW method:

Must have: Function which is essential for the working of the system. Without this function, the system is useless.

Should have: Important for the users, but not to the extent that the system is not usable when the function is missing

Could have: Function which makes working with the system more pleasant for the user, but not important. Also called Nice To Have

Would like to have, but not this time around: Function which has been deemed to offer added value, but a decision has been made that the function will not form part of the system for the time being. A reason for this might be that some good ideas came up during the design process which were not important enough to work out further, or of which it has not become clear yet how to develop them further.

In the first phase only the must and should haves are realised. Could haves are realised in their order of importance, if this fits in the planning.

Number

Name Aim and how it works MoSCoW

General Use Cases

BA01 User opens message box

The user opens his message box so he can start the other actions from there. In order to open the message box, the user has to log in first via the temporary facility eAuthentication (BA02). Should the user not have an account yet, the system provides a link to apply for an account at eAuthentication (BA03a).If the user does have an account with eAuthentication but has not used the message box before, the user will have to run through a registration (BA03b)After logging in, the system shows the user's inbox.

must have

Functional Design

| |

http://en.wikipedia.org/wiki/MoSCoW_Method


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

BA02 User logs in In order to gain access This happens via the temporary eAuthentication facility. The manner of logging in is part of the eAuthentication system, but the following steps are run through: The user enters his username, followed by his password and then chooses the organisation (s)he wants to work for, if needed. A user may be authorised to use different organisations' mailboxes. As soon as the user is logged in, the system shows the inbox of the relevant organisation.

must have

BA03a User registers an eAuthentication account

If the user does not have an eAuthentication account yet, he can follow a link to the facility at eAuthentication in order to open an account. After opening an account, the user can log in to the message box. The use case BA03b will then probably have to be carried out.

BA03b The user then registers in the message box

If an organisation's user uses the message box for the first time after registration, the user will have to customise a number of important settings, like the way in which he wishes to be notified. After filling in the data, the user can use the message box. After registering, the system shows the folder with received messages. (BA04).

must have

BA04 User opens folder When the user selects a folder from the list of folders, the system will show a summary of all the messages in that folder. As a standard, the folder is sorted by date, descending. After the user logs in, the system automatically opens the received messages folder.

must have

Exchanging messages

BU01a Entrepeneur composes a new message

The entrepeneur wants to send a new message to one of the affiliated organisations. He composes a new message. He can choose one of the affiliated organisations as an addressee or search for an affiliated organisation on the basis of information from the Cooperating Catalogues. He can add one or more attachments to every message. Any attached documents will be scanned for viruses. If the system suspects that an attachment contains a

must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

virus, the sender and the recipient will be notified. The user can decide to send the message despite the warning.The message is delivered to the inbox of the affiliated organisation. When sending a message, the time of receipt is recorded. The time of receipt is the moment the message becomes available to the recipient.

BU01b Authority composes a new message

An authority also has to be able to start a message. To do so, the authority can enter the entrepeneur's unique account at AvB as addressee. He can add one or more attachments to every message. Any attached documents will be scanned for viruses. If the system suspects the attachments contains a virus, the sender and the recipient will be notified. The message is delivered to the inbox of the entrepeneur. When sending a message, the time of receipt is recorded.

must have

BU01c Competent authority chooses a standard message

A competent authority can select to send a standard message composed by the organisation. The reason for this might be that a certain message is sent many times (a confirmation of receipt for instance).

should have

BU01d competent authority administrates standard messages

The competent authority can compose, edit and delete messages itself. These messages can be chosen when a competent authority composes a new message or replies to a message.

should have

BU01e System adds signature to a competent authority's message

A competent authority can set up its own signature. The system adds this signature to any message the competent authority composes and when forwarding and answering messages. The signature text will appear at the bottom of the message and can be edited in that message by the user.

should have

BU01f Competent authority administrates signatures

The competent authority can compose, edit and delete signatures itself.

should have

BU02 User reads a message. The user wants to read a message. In order to do so, he selects a message in the message box and opens it. Any attachments can be downloaded to the user's system.

must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

BU03 User replies to a message.

The user has received a message and wishes to send a reply. He selects and/or opens the relevant message and selects the reply option. The system now behaves the same as when composing a new message. The earlier conversation is included in the message.

must have

BU04a Competent authority forwards a message to another competent authority

The competent authority wants to forward a message it has received from an entrepeneur to another competent authority. There are two possible reasons for this:

1. The message is intended for another competent authority.

2. The competent authority wishes to gather information from another competent authority.

The competent authority can add text to the message before forwarding it, but cannot edit the original text. A competent authority can also add or remove attachments. In turn, the competent authority which receives the forwarded message can forward this again. When replying, it can choose between the competent authority from whom it received the message or the entrepeneur who sent the original message.

must have

BU04b Entrepeneur forwards a message to competent authority

The entrepeneur wishes to forward a message he received earlier or composed himself to an authority. The functionality is the same as replying to a message. The user can select a new address of a different competent authority. Choosing an address is the same function that the entrepeneur has for addressing a competent authority.

must have

BU05 User exports a message

The user can export a message from the message box to his own system so that he can archive it digitally in his own organisation. The exported format is PDF/A.

must have

BU06 User composes a draft

When composing a message, the user can save the message as a draft to send later. These are saved in a standard drafts folder.

Could have

BU07 opens a concept and sends it.

The user opens a message from the drafts folder. The system displays the message and the user can edit the message and then send it.

Could have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

BU09 User marks a message as read/unread.

Where relevant, the user can mark a message as read or unread

Could have

Administrate messages and settings

BB01 User deletes one or more messages

The user wants to delete one or more (sent or received) messages. The reason for this might be that the entrepeneur wants to create clarity in his message box and wants remove old conversations. Deleted messages are moved to a bin. When a user wants to remove an unread message, the system will give a warning. The user may decide to remove the message(s) anyway, or to cancel the action.

must have

BB02 User moves a deleted message back

Deleted messages are moved to a bin. The user can move deleted message back to the folder from which they were deleted. If that folder has also been removed, the messages are moved back to the received or sent messages folder respectively.

must have

BB03 User moves one or more messages to a different folder

The user wants to move one or more message(s) which he composed or received to a certain folder. The reason for this might be that the user wants to create clarity in his message box and wants to put message regarding a certain subject together. (in relation to BB04)

should have

BB04 User administrates folders

The user can also create his own folders in addition to the standard folders (in, sent, bin and settled). The folders which are created by the user can be deleted and renamed. The standard folder (in, sent, bin and settled) cannot be deleted. A folder cannot be moved inside other folders. If a user deletes a folder which still contains messages all the messages in it will also be deleted, after a confirmation from the user.

should have

BB05 User sets notifications The user can set how he receives notifications. The entrepeneur always receives an email notification. In addition to this he can also choose to receive an SMS text message. Competent authorities can only select email. The competent authority can set the interval between notifications.

must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

BB06 User permanently deletes a message

A user can permanently delete a message from the bin. The message is physically removed from the system and cannot be retrieved by any party.

must have

Search Messages

BZ01 User sorts messages The user wants to find a message. He can do this by sorting the messages in his box.

should have

BZ01 User searches messages

The user searches for messages by using a keyword. The system shows messages sorted by relevance.

Won't have

Notification

BN01 System notifies entrepeneur

The entrepeneur receives an email or SMS text message as soon as a message for the entrepeneur arrives in his inbox. The subject is stated in the message, and a link to the site.

must have

BN02 System notifiescompetent authority

The competent authority periodically receives a notification with the number of new message in the most recent period. The competent authority is able to set the interval between two notifications.The notification message states the number of new messages since last checking.

Basic flow1. Entrepeneur sends a message to

competent authority 2. The system periodically checks

whether messages have been sent to the competent authority. If this is the case, the system sends a notification email to the registered email address of the competent authority. The interval is set by the employee on the site .

The competent authority does not receive notification by SMS text message.

must have

Interface

BK01 Competent authority's system retrieves new

The competent authority's system authenticates itself via the interface. The message box delivers all messages to the

Must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

message via the interface

competent authority's system via the interface which have not yet been retrieved via the interface. The message box marks the messages which have been retrieved via the interface as ‘read via interface’ and puts a timestamp of the moment these messages were retrieved from the interface on these messages. The messages are not deleted when this is carried out.

BK02 Competent authority's system retrieves all message via the interface

The competent authority's system authenticates itself via the interface. Via the interface, the message box delivers all the received messages to the competent authority’s system which are in the competent authority’s message box. The message box marks the messages which have been retrieved via the interface as ‘read via interface’ and puts a timestamp of the moment these messages were retrieved from the interface on these messages, but only does this for messages which have not yet been stamped. The messages are not deleted when this is carried out.

must have

BK03 Competent authority's system sends message interface

The competent authority's system authenticates itself via the interface. The system then delivers one or more messages to the message box, via the interface. The message box then sees to the virus scanning and the delivery of the messages. In view of the potentially lengthy processing time of the delivered messages, the message box does not give direct feedback on the results of the virus scan and the delivery. If a message is deemed harmful by the virus scanner, or an addressee cannot be found, the message box will place a message in the competent authority’s inbox with a notification and a reference to the message. The message will not be delivered to the intended addressee. The recipient can see that the system has detected a possible virus when reading the message.

must have

BK04 System BI permanently deletes messages from

The competent authority's system authenticates itself via the interface. The competent authority’s system then indicates

must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

message box which messages are to be removed from the message box. The message box deletes these messages permanently so it does not move these messages to the recycle bin. The message box indicates whether each message was successfully deleted or not.

BK05 Competent authority's system retrieves list of affiliated competent authorities

The competent authority's system authenticates itself via the interface. The message box returns a list of affiliated institutions. This list can be used to address other competent authorities in order to send a message to another competent authority.

must have

User maintenance

MCO-015

user records manager blocks account

If an organisation's complete account details have been lost, or there is a fear of a security breach, the access to the mail box has to be blocked temporarily. It does still have to be possible for third parties to send messages to the organisation's message box.If an organisation has not accepted the authorised person declaration within four weeks, the account has to be blocked temporarily as long as this has not been signed.It only concerns the changing of the password for competent authorities.It does not involve the complete removal of an account.The integrity of the report of abuse of lost details is checked by using a unique code which has been supplied to an authorised person. This has to be produced when reporting abuse or loss.

must have

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

4 Non-functional requirementsRequirements for the quality of the system play a role in the development of information systems, as well as functional requirements. These are often actually decisive for the success of the implementation and acceptance of the system.

The Non-functional requirements are part of the Supplementary Specifications. For more on this, see the document "Supplementary Specifications Message Box v0.1.odt"

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5 Screen designsIn this chapter, the functionality of the message box is described by referring to screen designs. These designs are of a functional nature. This means that the elements which are displayed will be part of the screen, but their position and the design may differ in the graphic screen designs.

5.1 Inbox / sent messages

The inbox and the sent messages folder show the messages which the user has received and sent, respectively. Functionally, the inbox and the sent messages folder are the same, for the most part. The only difference is that in the inbox, the sender of each message is indicated, while in thesent messages folder ; the adressee of each message is indicated.

Supporting use cases● BA01 Open message box● BB01: Delete message● BZ01: Sort message● BB04: Move message

Screen design

Clarification fields

name description type

From (“To” in the sent messages folder)

Sender of message (addressee of the message)

label

date Date on which the message is delivered to the user's inbox (moment of receipt)

Label, date (dd-mm-yyyy)

subject Subject of the message label

attachments Indicated whether there are one or more attachments with the message, by showing an icon

image

Sent/received An icon shows whether the message was received or sent. This is particularly useful in the bin and the folders the user has made himself.

image

Read An icon shows whether the message has been read or not. A message can be read via the web interface and the interface.

image

Functional Design

| |

@

Inbox

Sent messages

Bin

Message box

Settled

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

*

Date

The Municipality of Amsterdam Application for business paking permit in process

Date

Maintain folders w

*

c

*

RE: CWIorem Ipsum is simply dummy text of sdsd sd fsdf sand typesetting industry. Lorem Ipsum hDatec

+

CWIorem Ipsum is simply dummy text of sdsd sd fsdf sand typesetting industry. Lorem Ipsum hDatec

+

RE: Province of North Hollandorem Ipsum is simply dummy text of sdsd sd fsdf sand typesetting industry. Lorem Ipsum hDatec

+


c

@

@

@

Select:

Selected messages:

Or move to folder: Select a folder q

To bin

All None Read Unread

From Subject

New messageInbox

Next >1 2 3 4 5

1

1

1

1

1

1

Move


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

A maximum of 10 messages are displayed in the label, sorted by date, with the most recent at the top. If there are more messages, a link will appear at the bottom left of the page in order to navigate to the previous and next pages. No link to the previous page will appear on the first page, and on the last page there will be no link to the next page.

Clarification Action elements

name description type validations

(checkbox) Select the line for an action. If the checkbox in the title line is checked, all messages on the screen are selected.

checkbox

To bin Moves all selected messages to the bin

button At least one message selected.Check on unread messages, warning, choice of continuing or cancelling.

Select a folder Selection list with folders Drop down

move Moves all selected messages to the selected folder

Button At least one message selected.

(table rule) Opens the message hyperlink

Column headers

Sorts the messages, with attachment and read unread only descending, date, from and subject descending and ascending

hyperlink

New message Allows user to create a new message.

button

Everything Select all messages on screen button

Nothing Deselects all messages on screen button

Read Only selects the read messages on the screen

button

Unread Only selects the unread messages on the screen

button

5.2 Read message

The user wants to read a message. In order to do this, he selects a message in the message box and opens it. Any attachments can be downloaded to the user's system.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Supporting use cases● BU02: read message● BU03: reply to message● BB01: delete message● BB04: forward message● BB05: export message

Screen design



from Sender label

subject Subject of message label

date Date and time message was received label

Message content Body of the message Multi line label/text

Functional Design

| |

From

Subject

Attachment(s) tmb

tmb

filename.ext

f ilename.ext

Municipality of Utrecht

RE: Query regarding dog license

Kb

Kb

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Message

Reply

Date dd mm yyyy at 00:00h

Forw ard

Lorem Ipsum is simply dummy text of the printingand typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, w hen an unknow n printer took a galley of type and scrambled it to make a type specimen book. It has survived not only f ive centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It w as popularised in the 1960s w ith the release of Letraset sheets containing Lorem Ipsum passages.

Maintain folders w

Inbox

Sent messages

Bin

Settled

Read message

Save as PDFExport message

1

1

1

1

1

1

messages


To bin

Move


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Attachments List of attachments hyperlink

tmb Icon of file type image

Kb Size of file in KB text

Message message text text



Reply Write a reply to this message button

Forward Forward message to other organisation for information or handling.

attachment List of attachments enclosed. When clicking on the attachment the default action for that type of file is carried out by the browser (downloading or opening in a registered application)

hyperlink

Save as PDF Export the message as PDF/A, see 'Export Message'.

To bin Move message to bin. This button does not appear when the message has been opened from the bin. Check on unread messages, warning, choice of continuing or cancelling.

Button

Select a folder Selection list with folders Drop down

move Moves all selected messages to the selected folder

Button

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.3 Export message

The user wants to export a message. He selects a message in the message box and clicks the 'Save as PDF' button. Any attachments will not be exported. The user can download these to his system in the usual manner (see read message).

Supporting use cases● BU05: export message

Screen designExporting a message is an integral part of the screens for the reading of a message.



file name: name of the file in which the message is exportedPre-completed with: “<ABB-accountname sender>_<date>_<time>_<subject>'.<extension>”

2. <date>: <yyyymmdd> Timestamp received3. <time>: <hhmmss> Timestamp received4. <extension>: dependent on file classification

link/button

file classification: file classification.pre-completed with 'PDF/A' (extension: 'pdf')

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.4 Compose Message

The entrepeneur wishes to send a new message to an affiliated organisation or an employee of a competent authority wishes to send a message to an entrepeneur. He composes a new message. He can add one or more attachments to every message. The message is delivered to the inbox of the entrepeneur.

Supporting use cases● BU01: compose message

screen design

Functional Design

| |

To *

Subject *

Attachments i

Send >

tmb

tmb

tmb

filename.ext

f ilename.ext

f ilename.ext

Kb

Kb

Kb

Kb

X

X

X

Brow se Add

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Search

Message *

* mandatory f ield

Maintain folders w

Good afternoon,

orem Ipsum is simply dummy text of sdsd sd fsdf s

Kind regards,Max Tabbert

Inbox

Sent messages

Bin

Settled

New message

Choose a standard message q1

1

1

1

1

1

Add

< Cancel


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Example of validation message:



to Addressee. Text

subject Subject of the message Text

Message content Body of the message. Multi line text

attachments List of attachments label



send Sends the message button Address, subject and message text are mandatory.

cancel Does not send the button

Functional Design

| |

To *

Subject *

Attachment(s)

Send >

tmb

tmb

tmb

filename.ext

f ilename.ext

f ilename.ext


Kb

Kb

Kb

X

X

X

Brow se Add

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Edit

Use standard AvB error message

Use standard AvB error message

Message *

Maintain folders w

Inbox

Sent messages

Bin

Settled

New message

1

1

1

1

1

1

< Cancel


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

message , rejects all changes

to List with all possible addressees.

Drop down

searchstart subfunction addressee search.

button

Delete (x) Deletes an attachment Button/ hyperlink

Browse The users browses on his system for a file he wants to add as an attachment.

Button/ hyperlink

Add Add the selected attachment.

Button/ hyperlink

A maximum of 15 attachments can be added, of up to 100 MB in size.

The system validates whether it is possible to add a file. If not, the system displays the following message. 'Select a file to add with the Browse button:

5.4.1

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.4.2 Subfunction find Competent Authorities as addressee

A user can search for (only) affiliated organisations on the basis of information from Cooperative Catalogue. The classification from the cooperative catalogue is used. It is not possible to select competent authorities on the basis of products from the cooperative catalogue. The basic principle is that a user knows which competent authority he needs before he uses the message box. Other services, such as the Dutch PSC provide that type of information.

Comment: In the following screen designs there is option of selecting categories and searching for the name of the organisation. The searching by name is a Could Have. In the final screen designs this has been incorporated as follows

Screen design

Functional Design

| |

To


Utrecht

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Search

Province of Utrecht

Public Cleansing Utrecht

Parking company Utrecht

Tax off ice Utrecht

Etc.

Max 25 results per page

Municipalities (1)

Water boards (50)

Provinces (1)Other (24)

All (125)

Maintain folders w

Inbox

Sent messages

Bin

Settled

New message

1

1

1

1

1

1Next >1 2 3 4 5


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••



Government type (tabs left)

CC government typeThe tabs of types of government contain the names of the types of government

Organisations List of found affiliated organisations hyperlinks, alphabetically sorted

search field Term which has to be searched on in the list of organisations. The term has to be in the title exactly, not case sensitive. A search can also be done on part of the name of the organisation.

text field



search Search organisation and fill list with Organisations

button At least 1 government type selected or postcode entered. The results only show affiliated organisations.

cancel do not search, return to compose Message screen.

button

Government type

Tabs with government types

Next Displays next (max) 25 organisations found.

Button/ hyperlink

This button will not be displayed at the end of the list.

Previous Displays 25 previous found organisations.

Button/ hyperlink

This button will not be displayed at the start of the list.

Organisations Click on an affiliated organisation found: back to compose message, but

Hyperlink

Functional Design

| |

To Utrecht

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Search


Municipalities (1)Water boards (50)

Provinces (1)Other (24)

All (125)

Maintain folders w

Inbox

Sent messages

Bin

Settled

New message

1

1

1

1

1

1


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

addressed to the selected organisation.

5.4.3 Subfunction enter addressee (by competent authority)

The competent authority can forward messages to other competent authorities and send new messages to entrepeneurs who have indicated they wish to communicate via the message box. If a competent authority wants to forward a message the user has the same address options as described above. If the competent authority wants to send a new message to an entrepeneur, the user will complete the entrepeneur's (unique) account name. The system checks whether the user exists, during sending. If the user does not exist, the system will display an error message.

5.5 Select standard message

The employee of the competent authority can choose from one of the standard messages which the competent authority has composed itself, when replying to a message. After selecting a standard text, this can still be edited before the message is sent. The changes are not saved in the standard message, this is what the administrate standard messages function is for.

The screen design is part of compose message

5.6 Add signature

When an employee of a competent authority composes a new message, replies to a message, or forwards a message, the system adds a signature to the message. The text of the signature is added to the bottom of the message, but when replying or forwarding, always above the original text.This signature is part of the message and can be edited by the user before the message is sent.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.7 Reply to message

The user wants to reply to a message. He opens a message from the inbox and selects to reply to a message. The function of this use case is largely the same as the composing of a message

Supporting use cases● BU03: Reply to message

screen designThe screen design is broadly the same as composing a message. The fields which differ are described below

Functional Design

| |

To *

Subject *

Attachments i

Send >

tmb

tmb

tmb

filename.ext

f ilename.ext

f ilename.ext

Kb

Kb

Kb

Kb

X

X

X

Brow se Add

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Message *

* mandatory f ield

Maintain folders w

Hello,

Thank you for your request for information

Yours sincerely,J. JansenICTUWilhelmina van Pruisenweg 1041122AA Den Haag070 888 0000---------------------------------------------------------------------------------------------------------------From: Name Surname - Company nameSent: dd-mm-yyyy hh:mmTo: Government nameSubject: Subject

Hello,


Name Surname

Forwarded by: J. Jansen, ICTU

Inbox

Sent messages

Bin

Settled

Reply


1

1

1

1

1

Add

< Cancel

Max TabbertRe: Request for information


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••



to Addressee, sender of the original message. When a competent authority has forwarded a message, the user has the option between the original entrepeneur or the competent authority.

Text / drop down box

subject Subject of original message preceded by the text “Re: “

text field

Message content The body of the message, within which a dividing line appears, the following fields from the original message:

from:sent: to:subject:

the text of the original message.

Multi line text

Attachments These are the attachments which the user has newly added. When replying, the attachments of the original message are not sent along.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.8 Forward messageA message can be forwarded by the entrepeneur and by the competent authority. The aim of forwarding by the entrepeneur is that he wants to forward the answer he has been given by one competent authority to another competent authority.A competent authority may wish to forward a message for two reasons:

• Gaining information from another competent authority• Forwarding a wrongly addressed message to the correct organisation

A forwarded message which comes from a competent authority may be forwarded by the receiving competent authority. When answering a forwarded message the user can choose to either reply to the the entrepeneur or the competent authority from whom the user received the message. This choice can be made when replying.

Supporting use cases● BU04: Forward message

screen design

Functional Design

| |

To *

Subject *

Attachments i

Send >

tmb

tmb

tmb

filename.ext

f ilename.ext

f ilename.ext

FW: Original subject

Kb

Kb

Kb

Kb

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

Search

Message *

* mandatory f ield

Maintain folders w

From: Name Surname - Company nameSent: dd-mm-yyyy hh:mmTo: Government nameSubject: Subject

Hello,


Name Surname

Forwarded by: J. Jansen, ICTU

Inbox

Sent messages

Bin

Settled

Forw ard


1

1

1

1

1

Add

< Cancel

Hello,

I would like to forward the following message to you,

Yours sincerely,J. JansenICTUWilhelmina van Pruisenweg 1041122AA Den Haag070 888 0000


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••



to addressee Label (comment: there is a drop down list in the design, this is incorrect)

subject Subject of original message preceded by the text “FW: “

text

Extra information Option of adding additional information to the request

text

Message content The body of the message, within which a dividing line appears, with the following fields from the original message:

From:sent: to:subject:

the text of the original subject.

Forwarded by:

Multi line text, not editable

Attachments Attachments can be removed or added when forwarding

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.9 Move message to folderThe user is given the option to move the messages to a self-made folder. In the examples, the user has made his own "Settled" folder.

The user selects one or more message after which he can move the messages to the selected folder by using 'move to folder'.

5.10 Administrate foldersThe user can create, rename and delete folders himself. When a folder is deleted which still contains messages, these messages are moved to the bin after the user is asked for a confirmation.

screen design



New folder Opens the screen in which a new folder can be created

button

Edit Edits the folder concerned, opens the screen in which the folder can be edited.

button

Delete Deleted that folder after confirmation from the user

button

Functional Design

| |

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.Administrate folders w

Settled

B Fodler 2

C Folder 3

Inbox

Sent messages

Bin

Delete

Settled

New folder

Manage Folders

Name

Edit

DeleteEdit

DeleteEdit

1

1

1

1

1

1

1

1

1


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.11 Create new folder and edit folder



Name Name of the folder. This field is empty when creating a new folder and contains the name of the folder when editing the name of the folder

text



Save/Edit Depending on the action, this button saves or edits the label.

button The name of the folder is unique to the organisation of the user who is logged in.

cancel Do not create new folder / do not save changes. Shows the administrate folders screen.

button

5.12 Bin

Supporting use cases● BB02: move message back● BB06: permanently delete message● BZ01: sort messages

screen design



From / to Sender / addressee of message label

received Date on which message was received Label, date (dd-mm-yyyy)

subject Subject of the message label

attachments Indicates whether there are one or more attachments with the message, by showing an icon

image

Functional Design

| |

@

Inbox

Sent messages

Bin

Message box

Settled

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.

+

Date

RE: The Municipality of Am sterdam Application for business paking permit in process

Date

Administrate folders w

*

c

*

Jan Jansen – Com pany xorem Ipsum is simply dummy text of sdsd sd fsdf sand typesetting industry. Lorem Ipsum hDatec

+


+

RE: Province of North Hollandorem Ipsum is simply dummy text of sdsd sd fsdf sand typesetting industry. Lorem Ipsum hDatec

+


c

@

@

@

Select:

Selected messages:


All None Read Unread

From Subject

New messageBin

1

1

1

1

1

1

Move back

Move

Permanently delete

Next >1 2 3 4 5

Message box

B Fodler 2

C Folder 3

D Folder 4

E Folder 5

F Etc.Manage folders w

Inbox

Sent messages

Bin

Settled

New folder / Edit name

Name *

Save/Edit >

1

1

1

1

1

1

< Cancel


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••



(checkbox) Select the line for an action. checkbox

Move back Move the selected message back to the folder it originally came from. If that folder no longer exists a received message goes to the inbox, a sent message goes to sent messages.

button One or more messages have to be selected

(table rule) Opens the message hyperlink

Column headers

Sorts the messages.

Delete permanently

Delete selected messages permanently

button One or more messages have to be selected

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.13 Administrate settings

The user can administrate the settings in the message box which specifically apply to the message box. The settings which can be administrated are the notifications settings, standard messages and signature.

You can go to the temporary eAuthorization facility directly in order to change the password.

5.13.1 Administrate notifications settingsThe settings for notifications are different for the entrepeneur and the competent authority. The most important difference is that sms text notification is not available for competent authorities.

Notifications settings Service Provider


name description type validation

email address Mail address text Mandatory, valid email format

telephone number

International telephone number format

text In accordance with International telephone number

Functional Design

| |

Profile

Save

Email address * i

Notif ications

Select a language qLanguage of notif ication *

Notif ications

Signature

Standard Messages

Cancel* mandatory f ield

When a new message has been received, a notif ication can automatically be sent to your e-mail address and/or an SMS text message can be sent to your mobile phone.

o Send to my mobile phone number:SMS Phone number

o Do not send me an SMS text notif ication


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

format Mandatory if notification by sms text message has been selected

Notification settings Competent Authority

Not in the screen design but part of the final design: The competent authority has to have the opportunity to set an interval from a previously defined list of possible intervals (e.g. every 5 minutes, half hour, hour, 2 hours, 4 hours, 8 hours, 16 hours, 24 hours)

5.13.2 Manage standard messages

The employee of the competent authority can compose, delete and edit standard messages.

Functional Design

| |

Profile

Save

Email address * i

Notif ications

Select a language qLanguage of notif ication *

Direct qInterval of notif ication *

Notif ications

Signature

Standard Messages

Cancel* mandatory f ield

When a new message has been received, a notif ication w ill automatically be sent to your email address.


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.13.3 List of standard messages



Name (Bold) Name of standard message. text

Message Content of the standard message, cut off at 40 characters

text



Create new standard message

Opens the screen in which a new folder can be created

button

Edit Edits that message, opens the screen in which the message can be edited.

button

Delete Deletes that message button

Functional Design

| |

Standard RepliesProfile

Notif ications

Signature

Standard messages

Compose new standard message

Application for parking perm it....Dear sir/madam {NAME}, your request for a parking permit on the {NAME OF STREET}

Edit

Delete

Edit

Delete

Edit

Delete

Edit

Delete





•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

after confirmation from the user.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

5.13.4 Create new standard message



name Name of standard message. This field is empty when composing a new message and filled in with the standard message when editing the message

text

Message Content of standard message. This field is empty when composing a new message and filled in with the standard message when editing the message

text



Save/Edit Depending on the action, this button has the label save or edit.

button The content of the name and the message text must not be empty .

cancel Do not create new folder / do not save changes. Shows the administrate standard messages screen.

button

5.13.5 Administrate signature

The employee of the competent authority can compose, and edit a signature.

Functional Design

| |

Compose new reply

Profile

Notif ications

Signature

Standard messages

Message *

SaveCancel

Name *


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••



Email signature Text of the email signature. text



Save Saves the changes button The content of the signature can be empty. This is a way of no longer adding a standard signature to the messages.

cancel The changes are not saved.

button

5.14 Notification message entrepeneur

Functional Design

| |

Profile

Email signature Yours sincerely,J. PieterseICTUWilhelmina v an Pruisenweg 1041122AA Den Haag070 888 0000

Signature

Save

Notif ications

Signature

Standard messagesCancel


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

The entrepeneur can be notified by sms text message and/or email. As soon as a message for the entrepeneur arrives in his inbox, a notification is sent.

Supporting use cases● BN01: Notification message entrepeneur

screen designthis is a system function without user interface

Content notification message

Every notification message has the following content

You have received a message in your My Reply message box for entrepeneurs.

From: <sender>Date: <date and time received>Subject: <subject of message>

Go to your message box in My Reply for entrepeneurs in order to read the message:<url>

5.15 Notification message competent authority

competent authorities receive an email notification about received message after an interval which they themselves have set.

Supporting use cases● BN02: Notification message competent authority

Screen designthis is a system function without user interface

Content notification message

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

New message(s) have been received for your organisation in the My Reply for entrepeneurs message box.

Go to your organisation's message box in My Reply for entrepeneurs to read the message(s):<url>

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

6 LoggingThe purpose of logging is to be able to trace who carried out what actions. The reason logging has to be done is to prove what actions users carried out in the message box.

The following actions are logged:

Action Logged details

Log in Time, organisationID, pseudoID

Send message time of sending, time of receipt, sent to who, sent by who, subject, forwarded, names of attachments.

Notification sent Time, notificationMethod (SMS, email) notificationAddress (email address, telephone number)

Read message Time or reading, time received, sender, addressee, subject, names of attachments

Retrieved via interface Time of retrieval, time received, sender, addressee, subject, names of attachments

Permanently delete message

Time of reading, time received, sender, addressee, subject, names of attachments

This system cannot log faulty log-in attempts because the authentication is done by an eAuthentication service. When a user does manage to log in through that service, the message box is not notified of this.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

7 Interface

The interface allows competent authorities to read and send messages via the message box without using the web interface. The interface was designed to allow users to switch back and forth between the web interface and the non-web based interface whilst using the service.

The interface allows competent authorities to realise a link with their own systems. Depending on the system which they are linking up with, an effort will be required from the competent authority in order to achieve the link. The message box offers an interface based on open standards.

The following services are offered via the interface:• retrieving messages, ‘new messages’ as well as ‘all messages’• sending messages• deleting messages• retrieving address list competent authorities

7.1 Retrieve new messages

The competent authority's system authenticates itself via the interface. The message box delivers all message to the competent authority's system via the interface which have not yet been retrieved via the interface. The message box marks the messages which have been retrieved via the interface as ‘read via interface’ and puts a timestamp of the moment these messages were retrieved from the interface on these messages. The messages are not deleted when this is carried out.

7.2 Retrieve all messages

The competent authority's system authenticates itself via the interface. Via the interface, the message box delivers all the received messages to the competent authority’s system which are in the competent authority’s message box. The message box marks the messages which have been retrieved via the interface as ‘read via interface’ and puts a timestamp of the moment these messages were retrieved from the interface on these messages, but only does this for messages which have not yet been stamped. The messages are not deleted when this is carried out.

7.3 Send message

The competent authority's system authenticates itself via the interface. The system then delivers one or more messages to the message box, via the interface. The message box then sees to the virus scanning and the delivery of the messages. In view of the potentially lengthy processing time of the delivered messages, the message box does not give direct feedback on the results of the virus scan and the delivery. If a message is deemed harmful by the virus

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

scanner, or an addressee cannot be found, the message box will place a message in the competent authority’s inbox with a notification and a reference to the message. The message will not be delivered to the intended addressee.

7.4 Delete messages

The competent authority's system authenticates itself via the interface. The competent authority’s system then indicates which messages are to be removed from the message box. The message box deletes these messages permanently so it does not move these messages to the recycle bin. The message box indicates whether each message was successfully deleted or not.

7.5 Retrieve address list competent authorities

The competent authority's system authenticates itself via the interface. The message box returns a list of affiliated institutions. This list can be used to address other competent authorities in order to send a message to another competent authority.

7.6 Authentication, Authorisation and Confidentiality

The following preconditions are part of the non-functional requirements, but for the sake of completeness they are explicitly stated here in relation to the interface.

The authentication has to be able to run automatically, without human interaction, every time a service is carried out via the interface. The authentication has to take place before every service is carried out and ends with the termination of the service.

The competent authority has the same rights via the interface as it does via the web interface.

The data which is exchanged via the interface may not be read by any third parties.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

8 Roles and rights

8.1 Role structure

Roles are provided so that certain users can easily be granted the same set of rights, and to allow you to administrate these.

The following roles are currently identified:

• Competent Authorities• Entrepeneurs• Administrators

8.2 Rights

Please find a list of Use Cases below with their sub functions. At each subfunction an "x" indicates whether a user with that role is permitted to carry out the function.

Entrepeneur Competent authority administrator

General Main Processes

Use case BA01: Open message box

● show message folders

x x

● show inbox x x

Use case BA02: user logs in

● log in x x

BA03: user registers

● Create account x

● Fill in profile data

x x

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Main process Exchange messages

use case BU01: compose messages (must have)

● enter text x x

● search for addressee

x

● select / enter addressee (government organisation)

x x

● Select standard messages

x

● enter subject x x

● add attachments

x x

● cancel composing message

x x

● send message x x

use case BU02: read message (must have)

● display message

x x

● display attachments

x x

● download attachments

x x

use case BU03: reply to message (must have)

● display original message text

x x

● change subject x x

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

● enter text x x

● cancel reply to message

x x


● select answer entrepeneur competent authority with a forwarded message

x

use case BU04: forward message

● Forward to entrepeneur

x

● Forward to competent authority

x x

● display original message text

x x

● change subject x x

● enter text x x

● cancel forwarding message

x x


● Add or remove attachments

x x

use case BU05: export message (must have)

● export message (in pdf/a)

x x

Main Process Administrate message box

Use Case BB01: delete

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

message

● select and then delete message

x x

● open and then delete message

x x

Use case BA02: move message back

● show bin x x

● open message x x

● select one or more messages

x x

● move message(s) back to folder they were removed from

x x

Use case BB03/ BB04: move message / create folders

● Show standard folders

x x

● move message to folder

x x

● Create folder x x

● Delete folder x x

● Rename folder x x

Use case BB06: permanently delete message(s)

● show bin x x

● open message x x

● select one or more messages

x x

● permanently delete message

x x

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

Main process Search messages

use case BZ01: Sort message

● click on column header to select messages

x x

Main process Notify

Use case BN01: Notification message entrepeneur

● send notification via email

x

● send notification via sms text message

x

Use case BN02 (and BB05): Notify government organisation

● send notification via email

x

● set notification interval

x

Main process Administration

Use Case MCO-015: Administrator blocks account

● Block account x

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

9 Integration and the Dutch PSCThe manner in which the message box is displayed in the Dutch PSC is not part of this functional design but will be documented in the "Synergy" project.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

10 Class Diagram

This chapter describes the objects which play a role in the message box. An object, or class, is a set of data which belongs together, which is stored together in the system. A characteristic of a class is an attribute.

In the description of the data model it is made clear in what units (entities) the data will be saved by the system and what their relations will be towards each other. These entities' relations and attributes are the basis for the way in which details are stored in a database or other storage data storage device.

The logical data model serves as a basis for the eventual storage structures in the realisation phase. The UML Class Diagram is used.

Functional Design

| |


•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••

10.1 Description of the classes

Class: OrganisationDescription: The organisation where the user works. The organisation can be entrepeneur as well as a competent authority

Class: UserDescription: Class which represents the user of the system. This user's data is stored in the (LDAP) profile

Class: RoleDescription: A user can have one of several roles.

Class: FunctionDescription: With a role several functions can be defined which the user with that role can carry out.

Class: MessageDescription: The messages which are sent and received by an organisation.

Class: Attachmentdescription: One or several files can be attached to a message. These attachments can have any (binary) format.

Class: FolderDescription: Messages that a user receives or sends are placed in a folder. A user has a number of standard folders (in, sent, settled and bin). In addition to this, the user himself can create a number of folders. Folders created by the user can be deleted, standard folders cannot.

Class: LoggingDescription: The details are logged of certain actions. For descriptions of that, see the chapter about logging.

10.2 AuthenticationAuthentication has not been included in the model because this is part of eAuthentication. The relationships with the eAuthentication account is on the basis of the the organisation's entrepeneur ID and user's pseudoID. These details are passed on from eAuthentication after the user has logged in. On the basis of these details the correct message box is displayed, logging takes place and possible authorisations on the basis of role are applied.

Functional Design

| |

Documents

[eOvB] rapport sjabloon - Joinup · Functional Design Message Box Service Directive Author Arjaan Peree Version 1.13 Status Definitive The Hague, 02-07-2009