RIGA TECHNICAL UNIVERSITY

Faculty of Computer Science and Information Technology

Study project with in the course

Object-Oriented System Analysis

(prof. Oksana Nikiforova)

<<Color>>

Authors (team members):

…
Table of Content
Problem Domain Description for Learning in
Driving school
Driving School

The driving school has several classrooms in several locations and several teachers (and
driving instructors), both registered in Road Traffic Safety Department (RTSD). The director of
driving school assigns learning sessions for new groups based on a predefined schedule.

When the applicant comes to driving school, the administrator of the school offers him a list of
available groups for learning and helps to select the most appropriate group location, time
schedule and teacher.

After at least three applicants were assigned for learning, the group is registered in RTSD. At
the moment the start date of learning is defined in a particular group, then the applicant starts
learning in theory and receives the driving card to start learning in driving.

Driving instructor is attached to no more than 10 pupils. Each driving lesson is registered in
the driving card.

When theory learning is finished, pupil passes an exam in theory in the school. During
examination pupil has to answer 30 test questions, where he has to select one from 2-5
answers. If pupil has 3 or less mistakes the exam is passed, if more than 3 mistakes, the exam
is failed.

Driving exam is organised in two parts. Pupil has to show his skill in “parking”, “bridge”,
“garage”, “u-turns” and then drive through the city. City driving becomes along the exact route,
which is randomly selected before the exam from 30 predefine routes. During the route pupil
collects penalty points, if he collects more then 10 points before the finish, the exam is failed.

If both examinations are passed the pupil receives the school licence and goes to RTSD to
pass state exams in order to receive the driving licence.

Process model of learning in Driving school

(Authors)

Use Case Modelling

Identification of Actors and Use Cases (Authors)
List of Uses Cases:
UC ID UC name Actor UC priority UC points UC designer

Draft of Use Case Diagram (Authors)

Scenarios of Use Cases

Use Case #01. Name (Author)

Actors:

Goal:

Short description:

Priority:

Reference:

Basic flow of events:

Actor’s action: System reaction:

1
.
Alternative flows:
Step No Step description What to do

Use Case #01. UI Mockup (Author)

Use Case #02. Name (Author)

Actors:

Goal:

Short description:

Priority:

Reference:

Basic flow of events:

Actor’s action: System reaction:

1.
Alternative flows:
Step No Step description What to do

Use Case #02. UI Mockup (Author)

Final Use Case Diagram (Authors)

Conceptual modeling

Identification of classes - Nouns from problem description

(Authors)
Motivation to remove:

Redundant classes

Irrelevant classes - those unrelated to the problem

Vague classes - ill-defined boundary, very broad in scope

Attributes - things that describe an object

Operations - things that manipulate objects

Implementation constructs - extraneous to real world must be eliminated from analysis model,
needed during design, but not now.

Class candidate +/ Motivation to remove

-
1 driving school +

2 classroom +

3 location - attribute

4 teacher +

1
0

1
1
1
2

1
3

1
4

1
5

1
6

1
7

1
8

1
9

2
0

Identification of classes – by Larman’s cathegories

Cathegory Classes (Authors)
Physical or tangible objects

Specifications, designs, or descriptions

Places

Transactions
Transaction line items

Roles of people

Containers

Contained items

Other collaborating systems

Abstract nouns concepts

Organizations

Events

Processes

Rules and policies

Catalogs

Records of finance, work, contracts, legal matters

Manuals, schedules, documents, references

Financial instruments and services

Identification of classes - Nouns from Use Case scenarious

“…” (Author)
Class candidate +/- Motivation to remove

4
Identification of classes - Nouns from Use Case scenarious
“…” (Author)
Class candidate +/- Motivation to remove

Glossary of the Final list of classes

Class Name Definition (Authors)
DrivingSchool

ClassRoom

Teacher

Conceptual class diagram (Authors)

 Modelling of object interaction

No Use Author of use Author of Evaluation of how scenario is suitable for

case case description sequence seq dia (0-1-2-3) (author of sequence
title diagram diagram evaluates the work of author of
scenario)

1.

2.

3.

4.

5.

6.

7.
8.

9.

10.

11.

12.

13.

14.

15.
16.

Sequence Diagram for Use Case #01.Name (Author)

Draft

Final

Sequence Diagram for Use Case #02.Name (Author)

Draft

Final

Communication Diagram (Authors)

Class Diagram