Document for Design

COMPUTER EDUCATION CENTER
FPT - APTECH
--- o0o ---

Document for Design
Project Name:

DTO Solution

( Driving Test Online Solution )

Class
: C0605M
Course
: HDSE
Group
: I (Oak Group)
Members join 1. Lam Truong Giang (Leader)
2.
3.
4.
5.

Nguyen Thi Mai Chinh
Nguyen Minh Hai
Nguyen Thuy Tien
Le Quang Viet

Email of team leader:
Teacher guides: Tran Dinh Tri

Ha Noi 11.2008 : Copyright 2008 by Oak Group


Table of Content
FormNo1:

Problem Definition..........................................................................................................................1
Problem Definition......................................................................................................................2
Customer Requirements Specification............................................................................................4
Problem Definition......................................................................................................................4
Customer Requirements Specification........................................................................................6
Type of question..............................................................................................................................8
Description.......................................................................................................................................8
Type of degree.................................................................................................................................8
Number of question.........................................................................................................................8
Rate of question...............................................................................................................................8
Type of Degree................................................................................................................................9
Total question...................................................................................................................................9
Testing time.....................................................................................................................................9
Type of degree.................................................................................................................................9
Total question...................................................................................................................................9
Pass conditional...............................................................................................................................9
Requirement Analysis....................................................................................................................11
Requirement Analysis................................................................................................................11
I.Agent: .................................................................................................................................11
II.Use Case for DTO Solution (Driving Test Online Solution)............................................11
Requirement Analysis................................................................................................................13
III.Analysis chart Usecase of system:...................................................................................15
Requirement Analysis................................................................................................................16

(A5): System displays information about teacher who administrator needs find................21
Entity Relationship Diagrams........................................................................................................64
Requirement Analysi.................................................................................................................64
Entity Relationship Diagrams....................................................................................................65
Entity Relationship Diagrams....................................................................................................83
Document about design database table.....................................................................................84
Database Diagram..........................................................................................................................90
Design Detail.................................................................................................................................91
Design Detail.............................................................................................................................94
Task Sheet....................................................................................................................................182
Design Detail...........................................................................................................................182
Main Task....................................................................................................................................182
Task name....................................................................................................................................182
Task Sheet................................................................................................................................183
Coding Convention Guide...........................................................................................................185
Coding Convention..................................................................................................................185
1. About the C# Coding Style Guide...........................................................................................185
2. File Organization.....................................................................................................................185
2.1 C# Sourcefiles...............................................................................................................185
2.2 Directory Layout...........................................................................................................185
3. Indentation...............................................................................................................................185
3.1 Wrapping Lines.............................................................................................................185
3.2 White Spaces.................................................................................................................186
Don't use spaces for indentation - use tabs!............................................................................186
4. Comments................................................................................................................................186
i


4.1 Block Comments...........................................................................................................186
4.2 Single Line Comments..................................................................................................186

4.3 Documentation Comments............................................................................................187
5. Declarations.............................................................................................................................187
5.1 Number of Declarations per Line..................................................................................187
5.2 Initialization...................................................................................................................188
5.3 Class and Interface Declarations...................................................................................188
6. Statements................................................................................................................................189
6.1 Simple Statements.........................................................................................................189
6.2 Return Statements..........................................................................................................189
6.3 If, if-else, if else-if else Statements...............................................................................189
6.4 For / Foreach Statements...............................................................................................190
6.5 While/do-while Statements...........................................................................................190
6.6 Switch Statements.........................................................................................................190
6.7 Try-catch Statements.....................................................................................................191
7. White Space.............................................................................................................................191
7.1 Blank Lines....................................................................................................................191
7.2 Inter-term spacing..........................................................................................................191
7.3 Table like formatting.....................................................................................................192
8. Naming Conventions...............................................................................................................192
8.1 Capitalization Styles......................................................................................................192
8.1.1 Pascal Casing..............................................................................................................192
8.1.2 Camel Casing..............................................................................................................192
8.1.3 Upper case..................................................................................................................192
8.2. Naming Guidelines.......................................................................................................192
8.2.1 Class Naming Guidelines...........................................................................................193
8.2.2 Interface Naming Guidelines.....................................................................................193
8.2.3 Enum Naming Guidelines..........................................................................................193
8.2.4 ReadOnly and Const Field Names.............................................................................193
8.2.5 Parameter/non const field Names..............................................................................193
8.2.6 Variable Names..........................................................................................................193
8.2.7 Method Names............................................................................................................193

8.2.8 Property Names..........................................................................................................193
8.2.9 Event Names...............................................................................................................193
8.2.10 Capitalization summary............................................................................................194
9. Programming Practices............................................................................................................194
9.1 Visibility........................................................................................................................194
9.2 No 'magic' Numbers......................................................................................................194
10. Code Examples......................................................................................................................194
10.1 Brace placement example............................................................................................194
10.2 Variable naming example............................................................................................195

ii


Class: C0605M
Course: HDSE
Group: I (OAK Group)
Document Name: Problem Definition
Document Sign: Form No.1 / PD / Ver. 2.0

Problem Definition
1. Project Abstract
1.1.

Function of Project Abstract:
DTOSolution (Driving Test Online Solution) is the project of “OAK Group” is done with
purpose support Driving Test Center in Vietnam organize Driving Test Exam:
•

It helps person who joins this exam can do “Online” one way quickly and effect,
avoid some difficult and bother of traditional exam.

•

Support Driving Test Center can simplify and synchronous in manage test,
candidate, day – time exam and result after finish exam.

•

Decrease making work, increase effect and professional for making exam in some
Driving Test Center in whole country.

1.2.

Sphere of system is used:

•

Using for some Driving Test Center confer driving degree (Car- Motorbike).

•

Support for some Driving Test Center in organizes test traffic theory program.

1.3.

Who uses it:

•

A person who join the Driving Test Exam (Candidate).

•

Official Center organizes confer driving degree (Administrator).

2. Proposed System
2.1.

Overview status:

•

Nowadays, with development of Vietnam Economic is very quickly and increase quickly of
traffic vehicle service for a lot of different work in social, and specially is two vehicles is
Car and Motorbike.

•

With increase above is need very big for training and confer driving degree for two
vehicles above.

•

And with traditional and old exam, as a result a lot of Driving Test Centre fell overload
the fuse with needing of today.
Figure 1: A few picture waiting for queue and traditional exam of candidate.

DrivingTestOnline

V1.0 © 2007 OakGroup

Page 1 of 200


FormNo1/PD/Ver 2.0
Problem Definition
2.2.

Purpose of project:
“OAKGroup” construct this project with purpose is help people who join Driving Test Exam

can testing one way easily and professional with trend development of Vietnam Economic and
Social. In additional, decrease overload at Driving Test Center in makes organize some exam.
Helps some exam becomes quickly, exactly, and equally than. DTO Solution is developed after
OAK Group invested and researched work at No 1 Bac Giang Driving Test Center and Gia LamHanoi Air Driving Test Center. As a result some function in DTO Solution is done with work project
(A Index) was agreed by two centers above. DTO Solution will have some function following:

•

Sign in and doing test: In time testing, candidate is provided one Account

(include of user name and password) can sign in DTO Solution and do testing.

•

Manage questions bank: This function helps Driving Test Center can manage (Add,
Insert, Delete) any the question have at questions bank of Driving Test Center. Each center
can add new question or delete old question to suit with current law.

•

Manage person who uses DTO Solution: this function help for Center can manage each
person who joins the exam, supervisor, and official center.

•

Manage testing room and day- time exam: Official Center can arrange day- time exam
for each candidate before testing.

•

Automatic making test: Provides function automatic making test for each candidate with
quantity and type of question suits each driving degree.

•

Organizes testing Online: In time testing, DTO Solution will confer test for Client and
each candidate can sign in and begin do testing.

•

Automatic making mark and Manage test result: After finished exam, DTO

Solution will automatic making mark for each candidate and test result of
candidate will save on Database and is managed by official of center.

Figure 2: Candidate joins Driving Test Online Solution

DTO Solution

V2.0 © 2008 Oak Group

Page 2 of 200


FormNo1/PD/Ver 2.0
Problem Definition

System name:

2.3.

•
2.4.

DTOSolution : Driving Test Online Solution
Environment for development

2.4.1. Hardware
2.4.1.1. Server:
•

CPU Pentium IV 2.66GHZ , Ram 512MB , HDD 40GB, Card NIC,

Modem

56K, Hub(Switch) 25 Port, wire net.
2.4.1.2.

Client:

•

2.4.2.

CPU Pentium III 1.7GHZ Ram 256, HDD 40GB, Card NIC, wire net.

Software

2.4.2.1.

Server:
•

Window Server 2003 sp 3

•

SQL Server 2000 Person Editor Service Pack 4.

•

.Net framework 2.0.

2.4.2.2.

Client:

•
•
2.5.

Window XP SP2.
.Net framework 2.0.

Tool is used for development:
•

•

Technology: Window form, .Net Remoting, ADO .Net, DCOM;

•

Database: MS SQL Server 2000.

•

Tool for design: Visual Studio 2005.

•

DTO Solution

Environment runs: .Net framework 2.0.

•

•

Languages are used: C# .Net

Tool for Interface: Adobe Photoshop.

Tool for makes UML: Rational Rose, Visio 2003, Smart Draw 2007.

V2.0 © 2008 Oak Group

Page 3 of 200


C0605M
Class:
FormNo1/PD/Ver 2.0
Course: HDSE

Group: I (OAK Group)

Problem Definition

Document Name: Customer Requirements Specification
Document Sign: Form No.2 / CRS / Ver. 2.0

Customer Requirements Specification
•

Person who uses DTO Solution:
o

Candidate

o

Official of Driving Test Center (Administrator).

1. Function for candidate:
1.1.

Guide for using DTO Solution:

•

Candidate hasn’t to sign in when uses this function.

•

Helps for candidate understands using each function of DTO Solution.

1.2.

Sign in DTO Solution:

•

In the testing, candidate can sign in application to doing test.

•

Candidate uses Username and Password is provided to sign in.

•

System will check username and password of candidate. If right it will allow begin doing
test, and if wrong application will require candidate sign in again.

•

Only some candidates is allowed doing test (status of candidate is normal) so this
candidate will have permit sign in DTO Solution and doing test.

1.3.
•

Doing Test:
After candidate signed in DTO Solution, question and answers list are appeared,
candidate can begin doing test, and Server side will begin set up testing time of
candidate.

•

Each times when candidate selected one answer, immediately it will is sent to Server and
Server will solve and save it on Database to backup data when client side have problem.

1.4.
•

Finish:
When candidate selected finish option or exam time up, test of candidate won’t have
validity. Application at Client Side will is clocked.

•

This time, status of candidate will change to finish and sent require making mark for
Server.

1.5.

•

Control Client side in testing time:
In testing time, Client sides will is controlled by Server side, any action is wrong with
exam regular (such as: using USB to read document, run another application) won’t do it.

2. Function for Administrator:
2.1.

•

DTO Solution

Sign in to manage system:
Official of center signed in before use permit their management.

V2.0 © 2008 Oak Group

Page 4 of 200


FormNo1/PD/Ver 2.0
Problem Definition
•

DTO Solution

Official of center needs provide Username and Password for system tests

V2.0 © 2008 Oak Group

Page 5 of 200


FormNo2/CRS/Ver 2.0
Customer Requirements Specification

•

Only each official have status is active (Or property status of official is normal) can sign in
DTO Solution.

•
2.2.

Administrator only can use some function which is permitted by system.
Manage official uses system:

2.2.1.

•

Add new account for administrator:
Administrator who has the highest permit can add new account for different

administrator for official at Driving Test Center.

•

New information of new administrator will add on database with some permit is
provided which suit for their work.

2.2.2.

•
2.2.3.

•

Change account of administrator:
Can update again information, also provides permission for administrator.
Delete account of administrator:
Account of each official don’t work at center or don’t have task manage on system
can delete.

2.3.

Manage supervisor:

2.3.1.

•

Add new supervisor:
With each the exam will have one official of Transport and Traffic Ministry monitors

with two officials of Driving Test Center.

•

Some information of supervisor will is added and is managed by administrator of
Driving Test Center.

2.3.2.

•

Change information of supervisor:
Any information of supervisor is wrong or not right can is changed by administrator of
Driving Test Center.

2.3.3.

•

Delete information of supervisor:
Information of some supervisor didn’t have any times monitor can is deleted on
Database.

•

Each supervisor has more one time monitor can’t delete. If that supervisor don’t have
permit monitor in the future, administrator will update their status (Their status will is
“Freeze”).

2.4.

Manage class and day-time test:

2.4.1.

DTO Solution

Add new test class:

V2.0 © 2008 Oak Group

Page 6 of 200


FormNo2/CRS/Ver 2.0
Customer Requirements Specification
•

The administrator can add new test class with detail test time, type of driving
base on candidate list.

2.4.2.
•

Change test class:
Some information of test class not suitable or wrong by insert data can change
to suit (When system automatics generate test, some information of test class
can’t change).

2.4.3.

•
2.5.

Delete test class:
Each test class don’t have candidate can delete.

Manage candidate:

2.5.1.

Add new account for candidate:

•

Before testing time, administrator need create new account for candidate.

•

Account

of

candidate

include

of

Username,

Password

and

some

their

information, such as name, code personal, and birthday.
•

Username of one candidate is unique on Database. Password was born
automatic by DTO Solution.

2.5.2.

Change account of candidate:

•

Each account has information is wrong can is changed by administrator.

•

Allow candidate can test a lot of times by way change test class without recreate new account for that candidate.

2.5.3.
•

Delete account of candidate:

Only allow delete account of candidate when they didn’t join testing. When they
begin do testing or after they finish test, administrator can’t delete their
account.

2.6.

Manage type of driving degree

2.6.1.
•

Add new type of driving degree:
Can add new type of driving degree (A1, A2, B1, B2, C, D, E), with each type of
driving degree will has quantity question, number of question and rate pass is
suitable.

2.6.2.
•

Change type of driving degree:
Information for type of driving degree and rate question of each type of driving
degree can change to suit with current law.

•

When one type of driving degree is deployed for exam, some information for
type of driving degree mustn’t repair.

2.6.3.
•

DTO Solution

Delete type of driving degree:
Each type of driving degree haven’t ever tested, can delete.

V2.0 © 2008 Oak Group

Page 7 of 200


FormNo2/CRS/Ver 2.0
Customer Requirements Specification
Manage question bank:

2.7.
2.7.1.

Add new question:

•

Administrator can add new question with type of question.

•

Type of question following:

Type of question

Description

Traffic Law
Road Traffic Sign
Figure
Speed
Expert
Drive Engineering
Car constructing
Car repairing
• Level of difficult
•

Question about road traffic
Question about type of road traffic sign
Each situation when vehicle joins traffic in real life.
Question about vehicle speeding
Question about traffic transport expert
Question about drive engineering
Question about car constructing
Question about general car repairing
question is same.

Each question only has one answer sentence.

2.7.2.
Change question:
• Each question on question bank can change by administrator have this permission.
2.7.3.
Delete question:

• Each question didn’t have in test can delete by administrator.
2.8. Automatic confer test:
•

Before testing time, official of Driving Test Center can press button to system
automatics confer test for candidate.

•

DTO Solution will generate number of test correspond with number of candidate in
test classing.

•

Each candidate will have different test. Also, each question in one test is not same.

•

Each test has one particular format suit type of driving degree.
Number of

Type of degree

questi

Rate of question

on
A1, A2

15

6 questions traffic law, 1 question car speeding, 5
questions road traffic sign, 3 questions figure.
9 questions road traffic law (10 questions for B1)
10 questions road traffic sign.
7 question figure

B1, B2, C, D, E

30

1 question traffic transport expert for B2, C, D, E
1 question drive engineering
1 question car constructing.
1 question general car repairing.

•

Only select each question has status is active (Each question suits with current law,
if each question not suits with current law will has status is “Freeze”).

DTO Solution

V2.0 © 2008 Oak Group

Page 8 of 200


FormNo2/CRS/Ver 2.0

Customer Requirements Specification
•

Only generate test for some test class has candidate.

2.9. Organize and manage test online:
•

Before testing time, administrator will print account lists for candidates can join
exam (Account contains username and password). And candidate list (Supervisor
will this list to candidate signs and supervisor can check number of candidate joins
exam).

•

When administrator actives status of exam, candidate can sign in client side (use
user and password) and begin doing test.

•

Begin set up time, and count time when candidate sign in.

•

Regular testing time
Type of Degree

Testing time

A1, A2

B1, B2, C
D, E
•

Total question
15
30
30

10 minutes
25 minutes
20 minutes

After signed in, candidate can’t run any different application. Each action is wrong
or not suit with exam rule will sign out immediately.

•

After singed in, screen of candidate will display question and some answer.

•

Candidate only choose one correct answer for one question.

•

After candidate chooses one answer, Client side will sent this answer to Server side.
Server side will save all answer of candidate on Database to backup when Client
side has a problem.

•

When Client side is running, Server side needs manage status of all client side.

•

When over time or candidate press button “Finish”, application will automatics close
and sent require making make to Server side.

2.10.

Automatic making mark:

•

When is required (each times when candidate finished early or overtime), Server
side will automatic making mark, making mark for each candidate base on correct
answer have on Database.

•

After making mark finish, Server side will automatic make result for each candidate,
also confirm (fail or pass) for candidate.

Type of degree
A1
A2
B1, B2
C, D, E

DTO Solution

Total question

Pass conditional

15
15
30
30

V2.0 © 2008 Oak Group

12
14
26
28

/
/
/
/

15
15
30
30

Page 9 of 200

FormNo2/CRS/Ver 2.0
Customer Requirements Specification
•

After has result, system will automatic print one record to candidate confirm fail or
pass to candidate can know to join practice test.
Manage test result:

2.11.
•

After Server side made mark is successful, test result of candidate will save on
Database and is managed by Administrator.

•

Test result can’t change, repair or delete.

•

Can print test result and detail exercise of candidate when needs (For example:
When candidate claim for test result).

•

Test result will save for a long time. After that time, test result will automatic delete
on Database.

2.12.

Search each subject:

•

With each function on system need construct detail search function to official of
Center can search information easily.

2.13.

Figure of System:

•

Provides for administrator have this option function when they work in DTO
Solution. With this function, administrator doesn’t need run application by unique
format. For example: Administrator can option method to manage exam is automatic
or manual, also they can change type of view of application, such as font or themes.

2.14.

Manage when system has a problem:

•

When candidate doing test, Client side has a problem: Supervisor will notice for
administrator to backup exam status of candidate.

DTO Solution

V2.0 © 2008 Oak Group

Page 10 of 200


C0605M
Class:

FormNo3/RA/Ver 2.0
Course: HDSE
Group: I (OAK Group)

Requirement Analysis

Document Name: Requirement Analysis
Document Sign: Form No.3 / RA / Ver. 2.0

Requirement Analysis
I.

Agent:




II.

System management
Teacher
Candidate

Use Case for DTO Solution (Driving Test Online Solution)
1. System management:
•

Manage teacher’s account

•

Sign in system

•

Add new account for teacher

•

Repair information about teacher

•

Delete teacher’s account

•

View teacher’s list

•

Search information about teacher

2. Teacher:

•
•

Manage candidate

•

Add new candidate

•

Repair information about candidate

•

Delete information candidate’s account

•

View candidate’s list

•

Print candidate’s list

•


Sign in DTO Solution

Search information about candidate

Manage supervisor:
•
•

Repair information about supervisor

•

Delete information about supervisor

•

View supervisor’s list

•


Add new supervisor

Search information about supervisor

Manage exam class:
•

Repair information about exam class

•

Delete information about exam class

•

View list of exam class

•

DTO Solution

Add new exam class

•

Search exam class

V2.0 © 2008 Oak Group

Page 11 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis



Manage type of license:

•
•

Repair information about type of license

•

Delete information about type of license

•

View type of license’s list

•


Add new type of license

Search type of license

Manage question bank:
•

Repair question

•

Delete question

•

View type of question’s list

•


Add new question

•

Search type of question

Manage type of question:
•
•

Repair type of question

•

Delete question types

•

View list of question types

•


Add new type of question

Search question types

Manage answer:
•
•

Repair answer

•


Add new answer
Delete answer

Manage exam results:
•

Search exam results

•

Print exam results



Make mark



Organize- Manage test online:

3. Candidate



DTO Solution

Sign in DTO Solution
Test online

V2.0 © 2008 Oak Group

Page 12 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis

DIAGRAM USE CASE OF SYSTEM

DTO Solution

V2.0 © 2008 Oak Group

Page 13 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis

DTO Solution

V2.0 © 2008 Oak Group

Page 14 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis

III.

Analysis chart Usecase of system:
1. Usecase Sign in DTO Solution

DTO Solution

V2.0 © 2008 Oak Group

Page 15 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis
a. Describe UseCase: “Sign in”
UseCase Name

Sign in

Description

UseCase “Sign in” supports teacher sings in DTO Solution

Actor

System management, teacher, candidate

Requirement

Sign in system

Pre – Conditions

Have to permit to sign in system

Post – Conditions

Don’t have

Result

After sign in system, application have to display form have some function of
DTO Solution

Main – Flows

(A1): System displays requirement form Agent enters user, password and
permit using system.
(A2): Agent enters user, password and permit using on requirement form.

(A3): System checks user, password and permit using system of Agent. If
not validation, system will do stream (B1).
(A4): System displays some function of DTO Solution; Agent chooses the
function need do.
(A5): Finish Usecase

Sub – Flows

(B1): Name sign in, password or permit access of Agent not validation.
System will have error message. Agent can sign in again or finish Usecase.

b. Describe Usecase: “Change password”
UseCase Name

Change password

Description

UseCase “Change password” suppors Agent can change password

Actor

System management, teacher, candidate

Requirement
Pre – Conditions

Change password
Agent has to in their session.

Post – Conditions

 Don’t have

Result

 Old password is changed, confirm new password into Database.

Main – Flows

(A1): System displays sign in form, password and permit using system
requires Agent enters user, password and permit using system.
(A2): Agent enters user, password and permit using in requirement form.
(A3): System checks user, password and permit using system of Agent. If not
validation, system will do stream (B1).
(A4): Agent chooses “Change password”. System displays Change Password
Form includes:
+ Account: Display name’s accout (This field has status is disable)
+ Old password: Require Agent enters password is using
+ New password: Require Ageng enters new password
+ Confirm password: Require Agent enters again new password one more
+ Button “Cancel” : Agent chooses this button to cancel change password
+ Button “Accept”: Agent chooses this button to accept change
(A5): System checks password of Agent is validation or not. If not validation,
system will do stream (B2).
(A6): System checks “Confirm new password” matchs with “new password” or

DTO Solution

V2.0 © 2008 Oak Group

Page 16 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis

Sub – Flows

not? If same, system will successful message and save new information into
Database.
(A7): Finish UseCase.
(B1): Username, password or permit access of teacher not validation. System
generates error message. Teacher can sign in again or finishes Usecase.
(B2): System show enquirement message to enter again. Agent can enter
again or finishes Usecase.

2. UseCase Mange teacher’s account

DTO Solution

V2.0 © 2008 Oak Group

Page 17 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis
a. Describe UseCase: “Register information Teacher”
UseCase Name

Registered teacher

Description

Usecase “Registered teacher” supports teacher registers new teacher into
database.

Actor

System management.

Requirement

Registerd some information about teacher

Pre – Conditions

 Administrator have to sign in system
 Administrator have to have permit register for teacher

Post – Conditions

Don’t have

Result

 Information about new teacher is saved into database

Main – Flows

(A1): When system displays some functions of DTO Solution, Administrator
chooses function need do.
(A2): Administrator chooses function “Registered teacher” (B1)
(A3): System displays new teacher register form.
 adminName

 adminPass

 adminUser

 status

(A4): Administrator enters some information about teacher in register form.
Then, if administrator chooses “Add new” do stream (A5). In contrast, if
administrator chooses “Reset” do stream (B2)
(A5): System checks ensure of each information about new teacher is entered
into database, if has error, system will do stream (B3)
(A6): System saves some information about new teacher into database
(A7): Finish UseCase
Sub – Flows

(B1): Administrator doesn’t have permission to register new teacher. System
show error message. Finish Usecase.
(B2): System will format again new teacher register form. Administrator can
enter again or stop Usecase.
(B3): If one of some information about new teacher doesn’t match, system
will show error message:
 Name of new teacher is entered is blank. System will show a message
“adminName of new teacher can’t blank”. Administrator can enter

again or finish Usecase.
 adminUser of new teacher is enter is blank. System will show a
message “adminUser of new teacher can’t blank”. Administrator can
enter again or finish Usecase.
 adminPass of new teacher is entered is blank. System will show a
message “adminPass of new teacher can’t blank”. Administrator can
enter again or finish Usecase.

b. Describe UseCase: “Repair information about Teacher”

DTO Solution

V2.0 © 2008 Oak Group

Page 18 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis

UseCase Name

Repair information about teacher

Description

Usecase “Repair information about teacher” supports administrator can repair
some informations of teacher.

Actor

Teacher

Requirement

Repaired some informations about teacher

Pre – Conditions

 Administrator has to sign in system
 UseCase “Search teacher” or Usecase “View teacher’s list” have to do
before.
 Administrator has to change information of teacher

Post – Conditions

 Don’t have

Result

 Each information about teach after changed, is save into database.

Main – Flows

(A1): When system displays some functions of DTO Solution, Administrator
chooses function needs do.
(A2): Administrator chooses function “Search information about teacher” (B1)
or the function “View teacher’ list”.
(A3): System displays information about teacher which administrator requires
with some function as:

 Repair information teacher
 Delete information teacher
(A4): Teacher chooses the function “Repair information teacher” (B3)
(A5): System displays form repair information of teacher order to
administrator can begin repair.
 adminName

 adminPass

 adminUser

 status

(A6): Administrator chooses information about the teacher needs repair and
begin repair information. Then if the teacher chooses “Update”, system will
do stream (A7). In contrast, if the teacher chooses “Cancel”, system will do
stream (B4).
(A7): System checks well-validation of each information which teacher
repaired (B5)
(A8): System save some information is changed for the teacher into database
(A9): Finish UseCase.
Sub – Flows

DTO Solution

(B1): System doesn’t find any information about teacher who administrator
need find. System shows message. Administrator can find again or finish
Usecase.
(B3): Administrator only has permission to see information about difference
teacher, doesn’t have permission to change information. System show error

message. End Usecase.
(B4): System will save some information about teacher as initial.
Administrator can repair again or end usecase.
(B5): If one of some information about teacher after repaired not validation,
system will show error message:
 adminName teacher has changed is white sign. System will show
message “adminName of teacher can’t blank”. Administrator can
enter again or finish Usecase.
 adminUser of teacher has changed is white sign. System will show
message “adminUser of teacher can’t blank”. Administrator can enter

V2.0 © 2008 Oak Group

Page 19 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis
again or end Usecase.
 adminPass of teacher has changed is white sign. System will show
message “adminPass of teacher can’t blank”. Administrator can enter
again or end Usecase.

c. Describe UseCase: “Delete information about teacher”
UseCase Name

Delete teacher

Description

When any teacher removes a difference place, information of this teacher is
deleted to free memory.

Actor

Teacher

Requirement

Don’t have

Pre – Conditions

 Administrator have to sign in system

 UseCase “Search teacher” or Usecase “View teacher’s list” have to done
before.
Post – Conditions

 Don’t have

Result

 Information about teacher won’t save in database else.

Main – Flows

(A1): When system displays some function of DTO Solution, Administrator
chooses the function needs do.
(A2): Administrator chooses the function “Search information about teacher”

(B1) or the function “View teacher’s list”
(A3): System displays information about teacher which administrator requires
with some information as:
 Repair information about teacher
 Delete teacher
(A4): Administrator chooses the function “Delete information teacher” (B2)
(A5): System shows a message “You want to delete information about this
teacher, don’t you?”. If the teacher chooses “Ok”, will do stream (A6). In
contrast, if the teacher chooses “Cancel”, will do stream (B3).
(A6): System deleted whole information about teacher out of database
(A7): End UseCase.

Sub – Flows

(B1): System didn’t find any information about teacher which administrator
need. System shows a message. The teacher can find again or end Usecase.
(B2): Administrator only has a permission to see information about teacher,
doesn’t have a permission to delete. System gives a error message. End
Usecase.
(B3): System will save some information about
Administrator can choose again or finish Usecase.

teacher

as initial.

d. Describe UseCase: “Search information about teacher”
UseCase Name

Search teacher

Description

UseCase “Searched teacher” will support teacher find information teacher

Actor

Teacher

Requirement

Can find information about teacher in database

Pre – Conditions

 Teacher has to sign in system

DTO Solution

V2.0 © 2008 Oak Group

Page 20 of 200


FormNo3/RA/Ver 2.0
Requirement Analysis
 Teacher has to have a permission to see information of teacher
Post – Conditions

 Don’t have

Result

 If system will display information about teacher which administrator
needs find. In contrast, if system doesn’t find any information about
teacher, it will show a message.

Main – Flows

(A1): When system displays some function of DTO Solution, administrator
chooses the function need do.
(A2): Administrator chooses the function “Search information about teacher”
(A3): System displays search form about teacher
 adminID

 adminName

(A4): Administrator enters information about teacher need find (B1)
(A5): System displays information about teacher who administrator needs
find.
(A6): End UseCase.
Sub – Flows

(B1): System doesn’t find any information about teacher which administrator
needs. System shows a message. Administrator can find again or end
Usecase

e. Describe UseCase: “View teacher’s list”
UseCase Name
Description

Actor
Requirement
Pre – Conditions
Post – Conditions
Result
Main – Flows

View teacher’s list
Usecase “View teacher’s list” will support the teacher can see teacher’s list
who registered system.
Teacher
Don’t have
 Teacher has to sign in system
 Teacher has to have a permission to see teacher’s list
 Don’t have
 Display teacher’s list
(A1): When system shows some functions of DTO Solution, teacher chooses
the function need do.
(A2): Teacher chooses the function “View teacher’s list” (B1).
(A3): System displays teacher’s list who registered with system.
 adminID
 status

Sub – Flows

 adminName

(A4): End UseCase.
(B1): Teacher doesn’t have a permission to see teacher’s list. System shows a
message. End Usecase.

3. UseCase: Manage candidate

DTO Solution

V2.0 © 2008 Oak Group

Page 21 of 200