Register of Security Interests in Movable Property Use ...O1_03 Request for a new username and...

NORWAY REGISTERS DEVELOPMENT AS

Rwanda Business Registry Project

Register of Security Interests in Movable Property

Use Case Specification

Version: 1.1

March 3rd, 2010


SecT System Use Case Specification v1.1

of 51

Table of Contents 1. Introduction .............................................................................................................................. 7

2. Actor Summary ........................................................................................................................ 7 3. Use Case: 1 Actors Diagram ................................................................................................ 9 4. Use Case: 2 Component diagram Diagram .................................................................... 10

5. Use Case: 3 NR Notice registration Diagram ................................................................ 11 5.1. B1_01 Create a journal record Use Case ..................................................................... 11

5.2. B1_02 Create a notice Use Case .................................................................................. 13 5.3. B1_03 Edit a notice Use Case ....................................................................................... 16

5.4. B1_04 Register decision Use Case ............................................................................... 17 5.5. B1_05 Generate Journal number Use Case ............................................................... 18

5.6. B1_06 Generate and print receipt slip Use Case ........................................................ 19

5.7. B1_07 Enter debtor Use Case ....................................................................................... 19 5.8. B1_08 Enter collateral Use Case ................................................................................... 20

5.9. B1_09 Enter max amount Use Case ............................................................................. 20 5.10. B1_10 Enter secured party Use Case ....................................................................... 21

5.11. B1_11 Upload attachments Use Case ...................................................................... 21 5.12. B1_12 Save a notice Use Case .................................................................................. 21 5.13. B1_13 Validate data Use Case .................................................................................. 22

5.14. B1_14 Submit a notice Use Case .............................................................................. 22 5.15. B1_15 View a notice Use Case .................................................................................. 23

5.16. B1_16 Lock/unlock record Use Case ........................................................................ 23 5.17. B1_17 Generate notice registration number Use Case .......................................... 24

5.18. B1_18 Send for correction Use Case ........................................................................ 24 5.19. B1_19 Generate and print certificate Use Case ...................................................... 25

5.20. B1_20 Generate and print rejection letter Use Case ............................................. 25

5.21. B1_21 Show early warning Use Case ....................................................................... 26

5.22. B1_22 Copy all data of a notice Use Case .............................................................. 26

5.23. B1_23 Generate and send document by email Use Case ..................................... 26

6. Use Case: 4 USM User and system maintenance Diagram ....................................... 27

6.1. B2_01 Create LBRO Use Case ..................................................................................... 27

6.2. B2_02 Edit LBRO Use Case ........................................................................................... 28 6.3. B2_03 Enable/disable LBRO Use Case ....................................................................... 28

6.4. B2_04 Create predefined data Use Case ..................................................................... 29

6.5. B2_05 Edit predefined data Use Case .......................................................................... 29

6.6. B2_06 Delete predefined data Use Case ..................................................................... 30

6.7. B2_07 Create user Use Case ......................................................................................... 30

6.8. B2_08 Edit user Use Case .............................................................................................. 31 6.9. B2_10 Enable/disable user Use Case .......................................................................... 31 6.10. B2_11 Change password Use Case .......................................................................... 32

6.11. B2_12 Edit own data Use Case .................................................................................. 32

6.12. B2_13 Change assigned user Use Case .................................................................. 33

7. Use Case: 5 RGP Report generation and printing Diagram ...................................... 33 7.1. B3_01 Generate report Use Case ................................................................................. 33

7.2. B3_02 Print report Use Case .......................................................................................... 34 8. Use Case: 6 UM On-line user maintenance Diagram .................................................. 35

8.1. O1_01 Register e-signature/user account Use Case ................................................. 35

8.2. O1_02 Edit own data Use Case ..................................................................................... 36 8.3. O1_03 Request for a new username and password Use Case ................................ 37

8.4. O1_05 Enable/disable user Use Case .......................................................................... 37



of 51

8.5. O1_06 Confirm request for e-signature/user account Use Case .............................. 38

9. Use Case: 7 ONR On-line notice registration Diagram ............................................... 38

9.1. O2_01 Create notice on-line Use Case ........................................................................ 39 9.2. O2_02 Enter debtor on-line Use Case .......................................................................... 42 9.3. O2_03 Enter collateral on-line Use Case ..................................................................... 42

9.4. O2_04 Enter max amount on-line Use Case ............................................................... 42 9.5. O2_05 Enter secured party on-line Use Case ............................................................. 43

9.6. O2_06 Upload attachments on-line Use Case ............................................................ 43 9.7. O2_07 Edit notice on-line Use Case ............................................................................. 44

9.8. O2_08 Save notice on-line Use Case ........................................................................... 44 9.9. O2_09 View notice on-line Use Case ........................................................................... 45

9.10. O2_10 Validate data on-line Use Case ..................................................................... 45

9.11. O2_11 Delete notice on-line Use Case ..................................................................... 46 9.12. O2_12 Prepare notice on-line Use Case .................................................................. 46

9.13. O2_13 Generate reference number Use Case ........................................................ 47 10. Use Case: 8 IND Information delivery Diagram ......................................................... 47

10.1. S1_01 Request report service Use Case .................................................................. 47 10.2. S1_02 Request official extract Use Case ................................................................. 49 10.3. S1_03 View service delivery log Use Case .............................................................. 50

11. Use Case: 9 OP order processing Diagram ................................................................ 50 11.1. S2_01 Process order Use Case ................................................................................. 50



of 51

Index of use case Use Case Page

B1_01 Create a journal record 11

B1_02 Create a notice 13

B1_03 Edit a notice 16

B1_04 Register decision 17

B1_05 Generate Journal number 18

B1_06 Generate and print receipt slip 19

B1_07 Enter debtor 19

B1_08 Enter collateral 20

B1_09 Enter max amount 20

B1_10 Enter secured party 21

B1_11 Upload attachments 21

B1_12 Save a notice 21

B1_13 Validate data 22

B1_14 Submit a notice 22

B1_15 View a notice 23

B1_16 Lock/unlock record 23

B1_17 Generate notice registration number 24

B1_18 Send for correction 24

B1_19 Generate and print certificate 25

B1_20 Generate and print rejection letter 25

B1_21 Show early warning 26

B1_22 Copy all data of a notice 26

B1_23 Generate and send document by email 26

B2_01 Create LBRO 27

B2_02 Edit LBRO 28

B2_03 Enable/disable LBRO 28

B2_04 Create predefined data 29



of 51

B2_05 Edit predefined data 29

B2_06 Delete predefined data 30

B2_07 Create user 30

B2_08 Edit user 31

B2_10 Enable/disable user 31

B2_11 Change password 32

B2_12 Edit own data 32

B2_13 Change assigned user 33

B3_01 Generate report 33

B3_02 Print report 34

O1_01 Register e-signature/user account 35

O1_02 Edit own data 36

O1_03 Request for a new username and password 37

O1_05 Enable/disable user 37

O1_06 Confirm request for e-signature/user account 38

O2_01 Create notice on-line 39

O2_02 Enter debtor on-line 42

O2_03 Enter collateral on-line 42

O2_04 Enter max amount on-line 42

O2_05 Enter secured party on-line 43

O2_06 Upload attachments on-line 43

O2_07 Edit notice on-line 44

O2_08 Save notice on-line 44

O2_09 View notice on-line 45

O2_10 Validate data on-line 45

O2_11 Delete notice on-line 46

O2_12 Prepare notice on-line 46

O2_13 Generate reference number 47



of 51

S1_01 Request report service 47

S1_02 Request official extract 49

S1_03 View service delivery log 50

S2_01 Process order 50



of 51

1. Introduction This document is the use case system specification of the Register of Security Interests in Movable

Property. The Register of Security Interests in Movable Property covers procedures for:

OP1 Registration of a new security interest

OP2 Registration of the amendments to the previously registered security interest |--- OP21 Change of particulars

|--- OP22 Order of correction

|--- OP23 Notice of discharge

|--- OP24 Order of restoration

|--- OP25 Request of possession and sale

|--- OP26 Request for sale

|--- OP27 Court order

2. Actor Summary

Primary Actor Functionality

Administrator The employee of the ORG who is registered in the SecT system as an administrator can: • maintain SecT users; • maintain predefined data lists; • access and review historical data; • change user assigned to the notice; • edit help text. Functionality:

B2_01 Create LBRO

B2_02 Edit LBRO

B2_03 Enable/disable LBRO

B2_04 Create predefined data

B2_05 Edit predefined data

B2_06 Delete predefined data

B2_07 Create user

B2_08 Edit user

B2_09 Delete user

B2_10 Enable/disable user

B2_13 Change assigned user

O1_05 Enable/disable user

O1_06 Confirm request for e-signature/user account

O1_06 Delete user

Data entry Clerk The employee of ORG who is registered in the SecT system as a data entry clerk

can:

• process the application;

• review, search and print notices;

• generate and print reports on statistics;

• process an order for information service and print request results.

Functionality:

B1_02 Create a notice

B1_03 Edit a notice

B1_12 Save a notice



of 51

B1_13 Validate data

B1_14 Submit a notice

B1_15 View a notice

NR 04 Complete order

S2_01 Process order

Debtor Debtor or owner of the collateral.

Journalizing Clerk The employee of ORG who is registered in the SecT system as a journalizing

clerk can journalize the application and issue a receipt slip to the registering

party.

Functionality:

B1_01 Create a journal record

B1_06 Generate and print receipt slip

Public user Any person interested in the information stored in the SecT system can:

• register e-signature/user account;

• search for registered information by criteria, like debtor, creditor, security

interest registration number, motor vehicle registration number;

• request for information on-line;

• receive requested information on-line;

• place an order for the verified information printout.

Functionality:

O1_01 Register e-signature/user account

O1_02 Edit own data

O1_03 Request for a new username and password

O1_04 Change password

O2_01 Create notice on-line

O2_07 Edit notice on-line

O2_08 Save notice on-line

O2_09 View notice on-line

O2_10 Validate data on-line

O2_11 Delete notice on-line

O2_12 Prepare notice on-line

S1_01 Request report service

S1_03 View service delivery log

Registering party Registering party (user) can be the creditor (secured party), the debtor or the

owner of the asset(s). Registering party can access registration services online

and

and submit data, required for registration of a new notice or an amendment to the

previously registered notice.

Registrar The employee of ORG who is registered in the SecT system as a registrar can:

• Make a decision in the registration process and issue corresponding document

(certificate, rejection letter, etc.)

• Search, review, print the information from the register.

Functionality:

B1_04 Register decision

B1_19 Generate and print certificate

B1_20 Generate and print rejection letter

Sect system

processor

Functionality:

B1_21 Show early warning



of 51

B1_22 Copy all data of a notice

B1_23 Generate and send document by email

Secured party Secured party or creditor of the collateral.

User A user of the SecT system.

Functionality:

B2_11 Change password

B2_12 Edit own data

B3_01 Generate report

3. Use Case: 1 Actors Diagram



of 51

4. Use Case: 2 Component diagram Diagram



of 51

5. Use Case: 3 NR Notice registration Diagram

5.1. B1_01 Create a journal record Use Case Use Case Name B1_01 Create a journal record ID

Description This use case describes steps performed by journalizing clerk in order to record the admission of the dossier.

Actors Journalizing Clerk

Goal To record the admission of the dossier to the journal.

Pre Condition User is registered and authenticated

Post Condition Admission of the dossier is journalized

Relations

Association Journalizing Clerk Actor

Include B1_05 Generate Journal number Requirements Use Case

Extend

Generalization

Scenarios

Basic Flow of Events Diagrams

Create journal record - amendment

Create journal record - new registration

State machine




of 51

Create journal record - amendment (Activity Diagram) [Basic-registration::NR Notice registration::B1_01 Create a journal record::Create journal record - amendment ]



of 51

Create journal record - new registration (Activity Diagram) [Basic-registration::NR Notice registration::B1_01 Create a journal record::Create journal record - new registration]

5.2. B1_02 Create a notice Use Case Use Case Name B1_02 Create a notice ID

Description This use case describes steps performed by data entry clerk in order to create notice in the registration system.

Actors Data entry Clerk

Goal To capture data from the dossier to the system

Pre Condition User is registered and authenticated, notice is journalized

Post Condition Notice is created

Relations

Association Data entry Clerk Actor

Include B1_07 Enter debtor Requirements Use Case

B1_08 Enter collateral Requirements Use Case

B1_09 Enter max amount Requirements Use Case

B1_10 Enter secured party Requirements Use Case

B1_11 Upload attachments Requirements Use Case

B1_21 Show early warning Requirements Use Case

Extend

Generalization



of 51

Scenarios


Create notice activities - new registration

Create notice activities - registration of amendment

Notice states diagram

State machine

Basic Flow of Events Diagrams Create notice activities - new registration (Activity Diagram) [Basic-registration::NR Notice registration::B1_02 Create a notice::Create notice activities - new registration]



of 51

Create notice activities - registration of amendment (Activity Diagram) [Basic-registration::NR Notice registration::B1_02 Create a notice::Create notice activities - registration of amendment]



of 51

Notice states diagram (State Machine Diagram) [Basic-registration::Notice states diagram]

5.3. B1_03 Edit a notice Use Case Use Case Name B1_03 Edit a notice ID

Description Edit a notice has the same functionality as Create a notice. Edit a notice is applied when a notice is created and saved with Create a notice, but not submitted. Until the notice is submitted, clerk is allowed to edit the record as many times as necessary. After submission for decision, editing of the notice is not allowed.


Goal To edit data before it is submitted

Pre Condition User is registered and authenticated, notice is created

Post Condition Notice data is edited

Relations


Include B1_21 Show early warning Requirements Use Case

Extend

Generalization

Scenarios


State machine



of 51

5.4. B1_04 Register decision Use Case Use Case Name B1_04 Register decision ID

Description This use case describes steps performed by registrar in order to register decision to the system.

Actors Registrar

Goal To register decision

Pre Condition User is registered and authenticated, notice is submitted

Post Condition Decision is registered

Relations

Association Registrar Actor

Include B1_21 Show early warning Requirements Use Case

Extend

Generalization

Scenarios


Register decision activities

State machine




of 51

Register decision activities (Activity Diagram) [Basic-registration::NR Notice registration::B1_04 Register decision::Register decision activities]

5.5. B1_05 Generate Journal number Use Case Use Case Name B1_05 Generate

Journal number ID

Description This use case describes generation of the journal number, which will be used to reference the particular dossier. Structure of the journal number: IJ-XXXXXXXX, where X - digit.

Actors Goal To generate a unique journal number

Pre Condition User is registered and authenticated, journal record is saved

Post Condition Journal number is generated

Relations

Association

Include



of 51

Extend

Generalization

Scenarios


State machine

5.6. B1_06 Generate and print receipt slip Use Case Use Case Name B1_06 Generate and

print receipt slip ID

Description This use case describes steps performed by journalizing clerk in order to generate and print receipt slip. 1. Preview receipt slip; 2. Generate receipt slip; 3. Print receipt slip.

Actors Journalizing Clerk

Goal To generate and print receipt slip, which is an evidence of the admission of the

dossier.

Pre Condition User is registered and authenticated, journal record is saved

Post Condition Generated and printed receipt slip

Relations

Association Journalizing Clerk Actor

Include

Extend

Generalization

Scenarios


State machine

5.7. B1_07 Enter debtor Use Case Use Case Name B1_07 Enter debtor ID

Description This use case describes steps performed by data entry clerk in order to enter debtor data into the registration system. 1. Enter debtor data; 2. Check the debtor data; 3. Save the debtor data.

Actors Goal To enter debtor data from the dossier


Post Condition Debtor data entered into the system

Relations

Association

Include

Extend B1_03 Edit a notice Requirements Use Case

Generalization

Scenarios



of 51


State machine

5.8. B1_08 Enter collateral Use Case Use Case Name B1_08 Enter collateral ID

Description This use case describes steps performed by data entry clerk in order to enter collateral data into the registration system. 1. Enter collateral data; 2. Check the collateral data; 3. Save the collateral data.

Actors Goal To enter collateral data from the dossier


Post Condition Collateral data entered into the system

Relations

Association

Include


Generalization

Scenarios


State machine

5.9. B1_09 Enter max amount Use Case Use Case Name B1_09 Enter max amount ID

Description This use case describes steps performed by data entry clerk in order to enter max amount data into the registration system. 1. Enter max amount data; 2. Check the max amount data; 3. Save the max amount data.

Actors Goal To enter max amount data from the dossier


Post Condition Max amount data entered into the system

Relations

Association

Include


Generalization

Scenarios


State machine



of 51

5.10. B1_10 Enter secured party Use Case Use Case Name B1_10 Enter secured

party ID

Description This use case describes steps performed by data entry clerk in order to enter secured party data into the registration system. 1. Enter secured party data; 2. Check the secured party data; 3. Save the secured party data.

Actors Goal To enter secured party data from the dossier


Post Condition Secured party data entered into the system

Relations

Association

Include


Generalization

Scenarios


State machine

5.11. B1_11 Upload attachments Use Case Use Case Name B1_11 Upload

attachments ID

Description This use case describes steps performed by data entry clerk in order to upload attachments into the registration system. 1. Choose attachment; 2. Upload attachment.

Actors Goal To upload attachments, provided in the dossier


Post Condition Attachments uploaded into the system

Relations

Association

Include


Generalization

Scenarios


State machine

5.12. B1_12 Save a notice Use Case Use Case Name B1_12 Save a notice ID

Description This use case describes steps performed by data entry clerk in order to save notice data into the registration system. 1. Enter notice data; 2. Check the notice data;



of 51

3. Save the notice data.


Goal To save the entered data


Post Condition Data saved in the system

Relations


Include B1_16 Lock/unlock record Requirements Use Case

Extend

Generalization

Scenarios


State machine

5.13. B1_13 Validate data Use Case Use Case Name B1_13 Validate data ID

Description This use case describes steps performed by data entry clerk in order to validate notice data with legal framework. 1. Generate validation report; 2. Check the validation report.


Goal To validate the entered data with legal framework


Post Condition Validation report

Relations



Extend

Generalization

Scenarios


State machine

5.14. B1_14 Submit a notice Use Case Use Case Name B1_14 Submit a notice ID

Description This use case describes steps performed by data entry clerk in order to suggest decision and submit notice for decision making. 1. Review notice data; 2. Suggest decision; 3. Submit notice.




of 51

Goal To suggest decision and submit notice for the decision making


Post Condition Notice is submitted

Relations



Extend

Generalization

Scenarios


State machine

5.15. B1_15 View a notice Use Case Use Case Name B1_15 View a notice ID

Description This use case describes steps performed by user in order to view particular notice. 1. Search particular notice; 2. View particular notice.


Goal To view data of a particular notice

Pre Condition User is registered and authenticated, notice is stored in the system

Post Condition Particular notice is viewed

Relations


Include

Extend

Generalization

Scenarios


State machine

5.16. B1_16 Lock/unlock record Use Case Use Case Name B1_16 Lock/unlock

record ID

Description This use case describes steps performed by data entry clerk in order to lock/unlock notice record. 1. Search notice record; 2. Lock/unlock notice record.

Actors Goal To restrict processing of the single notice to one user only


Post Condition Record is locked/unlocked



of 51

Relations

Association

Include

Extend

Generalization

Scenarios


State machine

5.17. B1_17 Generate notice registration number Use Case Use Case Name B1_17 Generate notice

registration number ID

Description This use case describes generation of the registration number, which will be used to reference the particular security interest. Structure of the registration number: REG-XXXXXXXX, where X - digit.

Actors Goal To generate a unique notice registration number only for new registration. For the

amendment will be used the registration number of the previously registered notice.

Pre Condition User is registered and authenticated, notice is stored in the system

Post Condition Registration number is generated

Relations

Association

Include

Extend B1_04 Register decision Requirements Use Case

Generalization

Scenarios


State machine

5.18. B1_18 Send for correction Use Case Use Case Name B1_18 Send for correction ID

Description This use case describes steps performed by registrar in order to send notice for correction. 1. Review notice data; 2. Send notice for corrections.

Actors Goal To send the notice for correction, when during decision making process a clerical

mistakes have been identified.

Pre Condition User is registered and authenticated, notice is submitted

Post Condition Notice is sent for corrections

Relations

Association

Include

Extend B1_04 Register decision Requirements Use Case

Generalization



of 51

Scenarios


State machine

5.19. B1_19 Generate and print certificate Use Case Use Case Name B1_19 Generate and print certificate ID

Description This use case describes steps performed by registrar in order to generate and print certificate. 1. Generate certificate; 2. Print certificate.

Actors Registrar

Goal To generate and print certificate, which is an evidence of the successful

registration

Pre Condition User is registered and authenticated, notice is approved

Post Condition Generated and printed certificate

Relations


Include

Extend

Generalization

Scenarios


State machine

5.20. B1_20 Generate and print rejection letter Use Case Use Case Name B1_20 Generate and

print rejection letter ID

Description This use case describes steps performed by registrar in order to generate and print rejection letter. 1. Generate rejection letter; 2. Print rejection letter.

Actors Registrar

Goal To generate and print rejection letter, which is an evidence of the rejection to

record the notice in the register

Pre Condition User is registered and authenticated, notice is rejected

Post Condition Generated and printed rejection letter

Relations


Include

Extend

Generalization

Scenarios


State machine



of 51

5.21. B1_21 Show early warning Use Case Use Case Name B1_21 Show early warning ID

Description This use case describes early warning - indication that there are applications under processing for the particular debtor.

Actors Sect system processor

Goal To show early warning


Post Condition Early warning is shown

Relations

Association Sect system processor Actor

Include

Extend

Generalization

Scenarios


State machine

5.22. B1_22 Copy all data of a notice Use Case Use Case Name B1_22 Copy all data of a notice ID

Description This use case describes steps performed by Sect system processor in order to notice all data. 1. Search notice; 2. Copy notice all data.


Goal To copy all the data of a notice

Pre Condition Notice is stored in the system

Post Condition Notice all data is copied

Relations


Include

Extend

Generalization

Scenarios


State machine

5.23. B1_23 Generate and send document by email Use Case Use Case Name B1_23 Generate and send document

by email ID

Description This use case describes steps performed by Sect system processor in order to



of 51

generate and send document by email. 1. Generated document; 2. Send document by email.


Goal To generate document and send it by email.

Pre Condition Notice is approved

Post Condition Document is generated and send by email

Relations


Include

Extend

Generalization

Scenarios


State machine

6. Use Case: 4 USM User and system maintenance Diagram

6.1. B2_01 Create LBRO Use Case Use Case Name B2_01 Create LBRO ID

Description This use case describes steps performed by administrator in order to create LBRO in the registration system. 1. Enter LBRO data; 2. Check the LBRO data; 3. Save the LBRO data.

Actors Administrator



of 51

Goal To create LBRO


Post Condition LBRO is created

Relations

Association Administrator Actor

Include

Extend B2_02 Edit LBRO Requirements Use Case

Generalization

Scenarios


State machine

6.2. B2_02 Edit LBRO Use Case Use Case Name B2_02 Edit LBRO ID

Description This use case describes detailed information how the administrator can change the LBRO data. 1. Change the LBRO data; 2. Check the LBRO data; 3. Save the LBRO data.


Goal To edit LBRO data

Pre Condition User is registered and authenticated, LBRO is created

Post Condition LBRO data is edited

Relations


Include

Extend

Generalization

Scenarios


State machine

6.3. B2_03 Enable/disable LBRO Use Case Use Case Name B2_03 Enable/disable LBRO ID

Description This use case describes the steps how the SECT administrator can enable/disable LBRO. 1. Search the LBRO; 2. Choose the LBRO record for enabling/disabling; 3. Enable/disable the LBRO.


Goal To enable/disable LBRO

Pre Condition LBRO is created



of 51

Post Condition LBRO is enabled/disabled

Relations


Include

Extend

Generalization

Scenarios


State machine

6.4. B2_04 Create predefined data Use Case Use Case Name B2_04 Create predefined data ID

Description This use case describes steps performed by administrator in order to enter predefined data into the registration system. 1. Enter predefined data; 2. Check the predefined data; 3. Save the predefined data.


Goal To create predefined data


Post Condition Predefined data is created

Relations


Include

Extend B2_05 Edit predefined data Requirements Use Case

Generalization

Scenarios


State machine

6.5. B2_05 Edit predefined data Use Case Use Case Name B2_05 Edit predefined data ID

Description This use case describes detailed information how the administrator can change the predefined data. 1. Change the predefined data; 2. Check the predefined data; 3. Save the predefined data.


Goal To edit predefined data

Pre Condition Predefined data is stored

Post Condition Predefined data is edited

Relations




of 51

Include

Extend

Generalization

Scenarios


State machine

6.6. B2_06 Delete predefined data Use Case Use Case Name B2_06 Delete predefined data ID

Description This use case describes steps performed by administrator in order to delete predefined data. 1. Search predefined data; 2. Choose the record for deleting; 3. Delete the predefined data.


Goal To delete predefined data

Pre Condition Predefined data is created

Post Condition Predefined data is deleted

Relations


Include

Extend

Generalization

Scenarios


State machine

6.7. B2_07 Create user Use Case Use Case Name B2_07 Create user ID

Description This use case describes steps performed by administrator in order to create user. 1. Enter user data; 2. Check the user data; 3. Save the user data.


Goal To create user


Post Condition User is created

Relations


Include

Extend B2_08 Edit user Requirements Use Case

Generalization



of 51

Scenarios


State machine

6.8. B2_08 Edit user Use Case Use Case Name B2_08 Edit user ID

Description This use case describes steps performed by administrator in order to edit user data. 1. Search the user; 2. Edit the user data; 3. Save the user data.


Goal To edit user data

Pre Condition User is registered and authenticated, user is created

Post Condition User data is edited

Relations


Include

Extend

Generalization

Scenarios


State machine

6.9. B2_10 Enable/disable user Use Case Use Case Name B2_10 Enable/disable user ID

Description This use case describes the steps how the SECT administrator can enable/disable the user data. Disabled the user can’t log into the SECT. 1. Search for the user data in the on-line users list; 2. Choose the user record for enabling/disabling; 3. Enable/disable the user data.


Goal To enable/disable user

Pre Condition User is registered

Post Condition User is enabled/disabled

Relations


Include

Extend

Generalization

Scenarios


State machine



of 51

6.10. B2_11 Change password Use Case Use Case Name B2_11 Change password ID

Description This use case describes the steps how the user can change own password. 1. Enter the user old password; 2. Enter the user new password; 3. Check old password and new password; 4. Save new password.

Actors User

Goal To change password


Post Condition Password is changed

Relations

Association User Actor

Include

Extend

Generalization

Scenarios


State machine

6.11. B2_12 Edit own data Use Case Use Case Name B2_12 Edit own data ID

Description This use case describes the steps performed by the user to edit own data in the SECT. 1. Change the user data; 2. Check the user data; 3. Save the user data.

Actors User

Goal To edit own data


Post Condition Own data is edited

Relations


Include

Extend

Generalization

Scenarios


State machine



of 51

6.12. B2_13 Change assigned user Use Case Use Case Name B2_13 Change assigned user ID

Description This use case describes steps performed by administrator in order to change user assigned to the notice. 1. Search notice; 2. Change assigned user.


Goal To change assigned user


Post Condition Assigned user is changed

Relations


Include

Extend

Generalization

Scenarios


State machine

7. Use Case: 5 RGP Report generation and printing Diagram

7.1. B3_01 Generate report Use Case Use Case Name B3_01 Generate report ID

Description This use case describes the steps performed by the user to generate report.

Actors User



of 51

Goal To generate requested report


Post Condition Report is generated

Relations


Include

Extend B3_02 Print report Requirements Use Case

Generalization

Scenarios


Generate report

State machine

Basic Flow of Events Diagrams Generate report (Activity Diagram) [Basic-registration::RGP Report generation and printing::B3_01 Generate report::Generate report]

7.2. B3_02 Print report Use Case Use Case Name B3_02 Print report ID

Description This use case describes steps performed by user in order to print report. 1. Generate report; 2. Print report.

Actors Goal To print requested report


Post Condition Report is printed

Relations



of 51

Association

Include

Extend

Generalization

Scenarios


State machine

8. Use Case: 6 UM On-line user maintenance Diagram

8.1. O1_01 Register e-signature/user account Use Case Use Case Name O1_01 Register e-signature/user

account ID

Description This use case describes the steps performed by the on-line user to register e-signature/user account.

Actors Public user

Goal To register e-signature/user account

Pre Condition User has valid e-mail

Post Condition Registered e-signature/user account

Relations

Association Public user Actor

Include

Extend

Generalization

Scenarios



of 51


Register e-signature/user account

State machine

Basic Flow of Events Diagrams Register e-signature/user account (Activity Diagram) [On-line registration::OUM On-line user maintenance::O1_01 Register e-signature/user account::Register e-signature/user account]

8.2. O1_02 Edit own data Use Case Use Case Name O1_02 Edit own data ID

Description This use case describes the steps performed by the on-line user to edit own data in the SECT. 1. Change the on-line user data; 2. Check the on-line user data; 3. Save the on-line user data.

Actors Public user

Goal To edit own data


Post Condition Own data is edited

Relations


Include

Extend

Generalization

Scenarios

Basic Flow of Events



of 51

Diagrams

State machine

8.3. O1_03 Request for a new username and password Use Case Use Case Name O1_03 Request for a new username

and password ID

Description This use case describes the steps for the on-line user to request for a new username and password in the SECT. 1. Enter the e-mail; 2. Check the e-mail; 3. Send the new username and password by e-mail.

Actors Public user

Goal To request new username and password

Pre Condition User has e-signature/user account

Post Condition New username and password are generated and sent by email

Relations


Include

Extend

Generalization

Scenarios


State machine

8.4. O1_05 Enable/disable user Use Case Use Case Name O1_05 Enable/disable user ID

Description This use case describes the steps how the SECT administrator can enable/disable the on-line user data. Disabled the on-line user can’t log into the SECT. 1. Search for the on-line user data in the on-line users list; 2. Choose the on-line user record for enabling/disabling; 3. Enable/disable the on-line user data.


Goal To enable/disable user

Pre Condition User is registered

Post Condition User is enabled/disabled

Relations


Include

Extend

Generalization

Scenarios


State machine



of 51

8.5. O1_06 Confirm request for e-signature/user account Use Case Use Case Name O1_06 Confirm request for

e-signature/user account ID

Description This use case describes the steps for the administrator to confirm request for e-signature/user account in the SECT. 1. Search for e-signature/user account in the list; 2. Choose the record for confirmation; 3. Review and validate data; 3. Confirm request for e-signature/user account.


Goal To confirm/reject user e-signature/user account

Pre Condition On-line user requested for e-signature/user account

Post Condition E-signature/user account is confirmed

Relations


Include

Extend

Generalization

Scenarios


State machine

9. Use Case: 7 ONR On-line notice registration Diagram



of 51

9.1. O2_01 Create notice on-line Use Case Use Case Name O2_01 Create notice on-line ID

Description This use case describes steps performed by on-line user in order to enter an on-line notice into the system.

Actors Public user

Goal To enter on-line notice


Post Condition Notice is entered on-line

Relations


Include O2_02 Enter debtor on-line Requirements Use Case

O2_03 Enter collateral on-line Requirements Use Case

O2_04 Enter max amount on-line Requirements Use Case

O2_05 Enter secured party on-line Requirements Use Case

O2_06 Upload attachments on-line Requirements Use Case

Extend

Generalization

Scenarios


Create notice on-line - amendment

Create notice on-line - new registration

On-line notice states diagram

State machine




of 51

Create notice on-line - amendment (Activity Diagram) [On-line registration::ONR On-line notice registration::O2_01 Create notice on-line::Create notice on-line - amendment]



of 51

Create notice on-line - new registration (Activity Diagram) [On-line registration::ONR On-line notice registration::O2_01 Create notice on-line::Create notice on-line - new registration]

On-line notice states diagram (State Machine Diagram) [On-line registration::On-line notice states diagram]



of 51

9.2. O2_02 Enter debtor on-line Use Case Use Case Name O2_02 Enter debtor on-line ID

Description This use case describes steps performed by on-line user in order to enter debtor data on-line. 1. Enter debtor data on-line; 2. Check debtor data on-line; 3. Save debtor data on-line.

Actors Goal To enter debtor data on-line


Post Condition Debtor data entered on-line

Relations

Association

Include

Extend O2_07 Edit notice on-line Requirements Use Case

Generalization

Scenarios


State machine

9.3. O2_03 Enter collateral on-line Use Case Use Case Name O2_03 Enter collateral on-line ID

Description This use case describes steps performed by on-line user in order to enter collateral data on-line. 1. Enter collateral data on-line; 2. Check the collateral data on-line; 3. Save the collateral data on-line.

Actors Goal To enter collateral data on-line


Post Condition Collateral data entered on-line

Relations

Association

Include


Generalization

Scenarios


State machine

9.4. O2_04 Enter max amount on-line Use Case Use Case Name O2_04 Enter max amount on-line ID

Description This use case describes steps performed by on-line user in order to enter max amount data on-line.



of 51

1. Enter max amount data on-line; 2. Check the max amount data on-line; 3. Save the max amount data on-line.

Actors Goal To enter max amount data on-line


Post Condition Max amount data entered on-line

Relations

Association

Include


Generalization

Scenarios


State machine

9.5. O2_05 Enter secured party on-line Use Case Use Case Name O2_05 Enter secured party on-line ID

Description This use case describes steps performed by on-line user in order to enter secured party data on-line. 1. Enter secured party data on-line; 2. Check the secured party data on-line; 3. Save the secured party data on-line.

Actors Goal To enter secured party data on-line


Post Condition Secured party data entered on-line

Relations

Association

Include


Generalization

Scenarios


State machine

9.6. O2_06 Upload attachments on-line Use Case Use Case Name O2_06 Upload attachments on-line ID

Description This use case describes steps performed by on-line user in order to upload attachments on-line. 1. Choose attachment on-line; 2. Upload attachment on-line.

Actors Goal To upload attachments on-line



of 51


Post Condition Attachments uploaded on-line

Relations

Association

Include


Generalization

Scenarios


State machine

9.7. O2_07 Edit notice on-line Use Case Use Case Name O2_07 Edit notice on-line ID

Description Edit a notice on-line has the same functionality as Create notice on-line. Edit a notice on-line is applied when a notice on-line is created and saved with Create notice on-line, but not prepared. Until the notice is prepared, clerk is allowed to edit the record as many times as necessary. After preparation of the notice, editing of the notice is not allowed.

Actors Public user

Goal To edit data before it is prepared


Post Condition Notice data is edited

Relations


Include

Extend

Generalization

Scenarios


State machine

9.8. O2_08 Save notice on-line Use Case Use Case Name O2_08 Save notice on-line ID

Description This use case describes steps performed by on-line user in order to save notice data on-line. 1. Enter notice data on-line; 2. Check the notice data on-line; 3. Save the notice data on-line.

Actors Public user

Goal To save the entered data on-line


Post Condition Data saved on-line



of 51

Relations


Include

Extend

Generalization

Scenarios


State machine

9.9. O2_09 View notice on-line Use Case Use Case Name O2_09 View notice on-line ID

Description This use case describes steps performed by on-line user in order to view particular notice. 1. Search particular notice on-line; 2. View particular notice on-line.

Actors Public user

Goal To view data of a particular notice on-line

Pre Condition User is registered and authenticated, notice is stored on-line

Post Condition Particular notice is viewed on-line

Relations


Include

Extend

Generalization

Scenarios


State machine

9.10. O2_10 Validate data on-line Use Case Use Case Name O2_10 Validate data on-line ID

Description This use case describes steps performed by on-line user in order to validate notice data on-line with legal framework. 1. Generate validation report on-line; 2. Check the validation report on-line.

Actors Public user

Goal To validate the entered data on-line with legal framework

Pre Condition User is registered and authenticated, notice is created on-line

Post Condition Validation report on-line

Relations


Include

Extend



of 51

Generalization

Scenarios


State machine

9.11. O2_11 Delete notice on-line Use Case Use Case Name O2_11 Delete notice on-line ID

Description This use case describes steps performed by on-line user in order to delete particular notice. 1. Search particular notice on-line; 2. Delete particular notice on-line.

Actors Public user

Goal To delete particular notice on-line


Post Condition Particular notice is deleted on-line

Relations


Include

Extend

Generalization

Scenarios


State machine

9.12. O2_12 Prepare notice on-line Use Case Use Case Name O2_12 Prepare notice on-line ID

Description This use case describes steps performed by on-line user in order to prepare notice for basic registration. 1. Review notice data on-line; 2. Prepare notice on-line.

Actors Public user

Goal To prepare notice on-line for basic registration

Pre Condition User is registered and authenticated, notice is created on-line

Post Condition Notice is prepared on-line

Relations


Include

Extend

Generalization

Scenarios


State machine



of 51

9.13. O2_13 Generate reference number Use Case Use Case Name O2_13 Generate reference number ID

Description This use case describes generation of the reference number, which will be used to reference the particular on-line notice. Structure of the reference number: ON-XXXXXXXX, where X - digit.

Actors Goal To generate a unique on-line notice reference number


Post Condition Reference number is generated

Relations

Association

Include

Extend O2_12 Prepare notice on-line Requirements Use Case

Generalization

Scenarios


State machine

10. Use Case: 8 IND Information delivery Diagram

10.1. S1_01 Request report service Use Case Use Case Name S1_01 Request report service ID

Description This use case describes steps performed by public user in order to request report service.

Actors Public user



of 51

Goal To get requested information


Post Condition Requested information is got

Relations


Include S1_02 Request official extract Requirements Use Case

Extend

Generalization

Scenarios


Request and report service

Request and report service 2

State machine

Basic Flow of Events Diagrams Request and report service (Activity Diagram) [Information services::IND Information delivery::S1_01 Request report service::Request and report service]



of 51

Request and report service 2 (Activity Diagram) [Information services::IND Information delivery::S1_01 Request report service::Request and report service 2]

10.2. S1_02 Request official extract Use Case Use Case Name S1_02 Request official extract ID

Description This use case describes steps performed by public user in order to request official extract. 1. Request report service; 2. Request official extract.

Actors Goal To request official extract


Post Condition Official extract is requested

Relations

Association

Include

Extend

Generalization

Scenarios


State machine



of 51

10.3. S1_03 View service delivery log Use Case Use Case Name S1_03 View service delivery log ID

Description This use case describes steps performed by public user in order to view service delivery log. 1. Search in service delivery log; 2. View service result.

Actors Public user

Goal To review service delivery log


Post Condition Service delivery log is reviewed

Relations


Include

Extend

Generalization

Scenarios


State machine

11. Use Case: 9 OP order processing Diagram

11.1. S2_01 Process order Use Case Use Case Name S2_01 Process order ID

Description This use case describes steps performed by data entry clerk in order to process order of the official extract. 1. View order;



of 51

2. Print official extract; 3. Mark order as completed.


Goal To complete order

Pre Condition User is registered and authenticated, order is stored in the system

Post Condition Order is completed

Relations


Include

Extend

Generalization

Scenarios


State machine

Register of Security Interests in Movable Property Use ...O1_03 Request for a new username and...

Documents

Transcript of Register of Security Interests in Movable Property Use ...O1_03 Request for a new username and...