The UML Modeling Techniques Computer Science Essay

Published:

As this is Soccer League, we should create a system that is needed to for there daily transactions. In this assignment we have to just identify certain important details that would help us to complete the assignment successfully. There are 6 tasks to complete in this assignment. We have to use many modeling techniques to complete this assignment.

In the first task we have to do tables and DSDs and PSDs.

The task 02 is flow chart.

The task 03 is pseudo code.

In the task 04 we should test the pseudo code.

In the task 05 we should use many UML modeling techniques to complete the task successfully.

Task 01

Task 01

In this task, 3 tables should be created according to the scenario given. Tables are below:

League table

Matches table

Score table.

And according to that I can easily create league report and results report. Task 01 is actually the foundation for the whole system. Here we concern about what are the user requirements and according to that we can plan our system manually. After that we can build the system efficiently and effectively.

Lady using a tablet
Lady using a tablet

Professional

Essay Writers

Lady Using Tablet

Get your grade
or your money back

using our Essay Writing Service!

Essay Writing Service

Actually Jackson Structure Program (JSP) techniques and methodology can use to analyze the requirements for reports we have to draw using the each table we used. Using these techniques we can show the step-wise progression.

The utility of these techniques are we can easily write pseudo codes for the system. If we consider about the Preliminary program structures (PSD s) there are two parts of the PSD such as function list and condition list.

Designing The Required Tables

League Table

League Table

League No

Team no

Team Name

Address

Contact No

001

101

Pokkiri

Kurunegala

0734555454

002

102

Spartons

Colombo

0714545455

003

103

Black belt

Nuwera Eliya

0715855855

004

104

Pooh

Baticoloa

0778168941

001

105

Avatar

Colombo

0714155415

002

106

Gigoe

Jafna

0771692585

003

107

Vettikaran

Colombo

0786252552

004

108

Sivakasi

Kandy

0774865285

001

109

Mann

Colombo

0752645855

001

110

Veil

Galle

0775285552

match Table

Match Table

Match no

Referee no

Team No

Location

Played Date

Status

M01

21

101

Home

30/02/2010

Win

M02

22

102

Opponent ground

30/03/2010

Draw

M03

23

103

Home

30/02/2010

Loss

M04

24

104

Opponent ground

30/03/2010

Draw

M05

25

105

Home

30/01/2010

Win

M06

26

106

Opponent ground

30/12/2010

Win

M07

27

107

Home

30/12/2010

Loss

M08

28

108

Opponent ground

30/01/2010

Draw

M09

29

109

Home

30/11/2010

Loss

M10

30

110

Opponent ground

30/12/2010

Win

Score Table

Score Table

Team No

No of points

Tot_goals_scored

Tot_goals_conceded

101

3

5

3

102

1

3

3

103

0

4

2

104

1

2

0

105

3

4

2

106

3

7

4

107

0

8

4

108

1

5

3

109

0

6

3

110

1

3

2

Reports

League Report

League No

Team no

Team name

Address

Contact no

002

102

Spartons

Colombo

0719074019

003

103

Black belt

Nuwera Eliya

0715855855

004

104

Pooh

Baticoloa

0778168941

001

105

Avatar

Colombo

0714155415

002

106

Gigoe

Jafna

0771692585

003

107

Vettikaran

Colombo

0786252552

004

108

Sivakasi

Kandy

0774865285

001

109

Mann

Colombo

0752645855

001

110

Veil

Galle

0775285552

Report 01

Report 02

Lady using a tablet
Lady using a tablet

Comprehensive

Writing Services

Lady Using Tablet

Plagiarism-free
Always on Time

Marked to Standard

Order Now

Results Report

League No

Team No

Match No

Played Date

No of Points

Goals Difference

001

101

M01

30/02/2010

3

2

002

102

M02

30/03/2010

1

0

003

103

M03

30/02/2010

0

2

004

104

M04

30/03/2010

1

2

001

105

M05

30/01/2010

3

2

002

106

M06

30/12/2010

3

3

003

107

M07

30/12/2010

0

4

004

108

M08

30/01/2010

1

2

001

109

M09

30/11/2010

0

3

001

110

M10

30/12/2010

1

1

Data Structure Diagrams (DSD) For Each Report

Report 01

LDSD

League No

Team No

Team Name

Contact no

Address

League

League No

Team No

Team Name

Contact no

Address

Report

League Details

Header

"League"

Body

Footer

*

League

PDSD

Report 02

LDSD

Results

League No

Team No

Match no

Goals difference

Played date

No of_points

PDSD

Report

Result Details

Header

"Results"

Body

Footer

*

Results

League No

Team No

Match no

Goals difference

Played date

No_of_points

Program Structure Diagrams (PSD) For Each Report

Report 01

Condition List

WHILE eof-lea = FALSE DO 6

Function List

Start

Declare variables

RECORD lea

eof-lea

OPEN "League"

PRINT "League report"

PRINT "league no", "team no", "team name" ,"address", "contact no"

READ "League" RECORD INTO "Lea"(eof-lea)

CLOSE

Stop

6

a

WHILE

7, 8

Program 01

BODY

Begin

End

*

1, 2, 3, 4

Report 02

Function List

Start

Declare variables

RECORD mat

RECORD sco

eof-mat, eof-sco

OPEN "Match", OPEN "Score"

PRINT "Results report"

PRINT "League no", "Team no" ,"match no", "played date", "number of points", "goals difference"

READ "Match"RECORD INTO "mat"(eof-mat)

READ "Score" RECORD INTO "sco"(eof-sco)

G_dif=mat.tot_goals_scored-mat.tot_goals_conceded

PRINT "Goals differnce is ", G_dif

CLOSE

Stop

Condition List

WHILE eof-mem = FALSE DO 6, a

WHILE eof-sco=FALSE DO

7, d

IF mat.team_no=sco.team_no

THEN

8

ELSE __

ELSE

c

o

o

o

o

IF

7

6

WHILE

b

a

WHILE

9, 10, 11

Program 02

BODY

Begin

End

*

1, 2, 3, 4, 5

8

Program Specification

To create a system to a Soccer league we have to consider about the teams of the each division, day to day matches and score of each team. And also we should consider about the teams. If we have perfect teams we can maintain a good name for the soccer league. There for we should keep all records of the matches and how teams played in the matches. Actually that's why we should create a very effective and efficient system for the league.

In my system I created three tables :

League table

Match table

Score table

There are two reports :

Report 01

This report contains league details for each division, contact numbers by team level. Therefore we can use league table to create this report.

Before we start the create system we should plan our system. How the system interacts with user is must to consider. That's why we use Jackson Structure Charts (JSP)

Lady using a tablet
Lady using a tablet

This Essay is

a Student's Work

Lady Using Tablet

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Examples of our work

In here we have to design Data Structure Diagrams (DSDs) and Preliminary Structures Diagram. In DSD we have to consider about whether there is a calculation or not. If there is a calculation we should draw Physical Data Structure Diagram (PDSD). Like wise according to the situation we have to draw each diagram.

Data structure diagram is always Physical data structure diagrams. And also I drew program structure diagrams using report 1. According to the function list and condition list I drew the diagram for program 1. Those are the information about for report 1.

Report 02

This report should contain league no, team no, match no, played date, number of points and goals difference. Therefore have to use two or more tables for report two. Here we have to use match table and score table to create report 02. . To use tables for report 02 also we have to use primary key and foreign key concept. Primary key means we specify particular record as primary key in each two tables. Then if we want to connect with those tables we can use that particular primary key as foreign key.

Here also I drew physical data structure diagram (PDSD) for report 02. In Preliminary Structure Diagrams, after we write function list and condition list I depict it using chart. Actually that is the method of the PSD. In here we have to calculate goals difference. We have to find about the teams who are playing well. As I mentioned earlier if we have to calculate some value we should draw PDSD.

Finally the system should work according to the user requirements. It is mission critical and crucial thing for my system. After this analyzing part, actually I can easily start to create the system as follows.

Task 02

Introduction To Task 02

In this task should draw the flow chart according to the reports and tables done in task 01. The flow chart is being drawn to show the flow of the future system. The flow chart can be drawn in many ways according to our scenario.

==

Flow Chart

Start

Declare Variables

OPEN "League"

PRINT

"League Report"

PRINT "league no", "team no", "team name" ,"address", "contact no"

WHILE eof-lea = FALSE

DO

Close "League"

Stop

FALSE

TRUE

READ "League" RECORD INTO "lea" (eof-lea)

READ "Member"RECORD INTO "mem"(eof-mem)

READ "Scores" RECORD INTO "sco" (eof-sco)

Report 01

Start

Declare Variables

OPEN "Match", OPEN "Score"

OPEN

"Members",

"Scores"

PRINT

"Results Report"

PRINT

"League no", "Team no" ,"match no", "played date", "number of points", "goals difference"

WHILE

eof-mat=

FALSE

DO

Close

Stop

FALSE

TRUE

READ "Match"RECORD INTO "mat" (eof-mat)

A

B

C

Report 02

A

WHILE eof- sco= FALSE DO

WHILE

eof-mem=

FALSE

DO

B

FALSE

READ "Score" RECORD INTO "sco" (eof-sco)

READ "Member"RECORD INTO "mem"(eof-mem)

READ "Scores" RECORD INTO "sco" (eof-sco)

TRUE

IF mat.team no=sco.team no

THEN

C

TRUE

G_dif=mat.tot_goals_scored-mat.tot_goals_conceded

PRINT "Goals difference is ", G_dif

FALSE

Task 03

Introduction To Task 03

In this task I have to write the pseudo code according to the scenario. The scenario is the report and the tables. The pseudo code has to be written to the way of how the payment is happening in the system. First a procedure has to be written and the procedure has to be called in the report 01 pseudo code. The pseudo code has to written for the main menu of the report.

Procedure

Procedure Pro ()

Use variables: team no, tot_points, no_of_points, tot_goals_scored,tot_goals_conceded, g_dif of TYPE Integer

DISPLAY "Input team no"

ACCEPT team no

while eof=score

DO

Tot_points=no_of_points+tot_points

DISPLAY "Total points" tot_points

G_dif= tot_goals_scored-tot_goals_conceded

DISPLAY "Goal difference is" G_dif

END PROCEDURE

Pseudo code For The Two Reports

Report 01

BEGIN

Use variables: RECORD lea

HAS FIELDS

League no: Integer

Team no: Integer

Team name:String

Address: String

Contact no: Integer

END RECORD

- - Call Procedure

Call Procedure Pro ()

PRINT "League report"

eof-lea, OF TYPE Boolean

OPEN "league"

READ "league" RECORD INTO "lea" (eof-lea)

WHILE eof-lea =FALSE DO

PRINT "league no", "team no", "team name" ,"address", "contact no"

READ "League" RECORD INTO "Lea"(eof-lea)

CLOSE

END PROGRAMME

Pseudo Code For The Reports Main Menu

BEGIN

Use variables: Username of type String

Password of type Integer

Option of type Character

DISPLAY "Enter Username"

ACCEPT Username

DISPLAY "Enter password"

ACCEPT Password

IF (Username="Soccer") AND (Password= ******) Then

DISPLAY "Main Menu"

DISPLAY "R = Register"

DISPLAY "M = Matches"

DISPLAY "A = Attendance"

DISPLAY "T = "Scores"

DISPLAY "P = Print Report"

DISPLAY "C = Cancel"

DISPLAY "Select Option"

Accept Option

Case option = "R"

Register member ()

Case option = "M"

Matched played ()

Case option = "A"

Check attendance ()

Case option = "T"

Check score ()

Case option = "P"

Print report ()

Case option = "C"

Close ()

ENDCASE

END PROGRAM

Task 04

Introduction To Task 04

In the task 04 we should do the testing for the report and the pseudo code we wrote in Task 03. There are 3 ways given to do the testing such as test plan, desk checks and dry runs. These test souls should be done successfully according to the pseudo code.

Pseudo Code Testing

Desk Check For The Pseudo Code

Listed Variables

Variable Names

Data Type

Declaration

Used

Remark

Username

String

Yes

Yes

The variable is used the verify the users entered name

Password

Integer

Yes

Yes

To protect form unauthorized access

Option

Character

Yes

Yes

To allow selection in the options

Dry Run For The Pseudo Code

Username

Password

User name=

"Soccer"

Password=

"456321"

Option

procedure

Soccer

456321

True

True

-

Main Menu

Soccer

456321

True

True

R

Register ()

Soccer

456321

True

True

M

Matches()

Soccer

456321

True

True

A

Attendance ()

Soccer

456321

True

True

T

Check score()

Soccer

456321

True

True

P

Print Report()

Soccer

456321

True

True

C

Cancel ()

Task 05

Introduction To Task 05

In the task 05 we have to draw many UML modeling techniques such as class diagrams, use case diagrams and sequence diagrams.

UML Modeling Techniques

High Level Class Diagram

1

1

1

1

1

1

*

*

*

League

Name:

Address:

Telno:

Type:

Handle soccer matches( )

Secretary

Name:

Address:

Telno:

Gender:

Handle all functions ( )

Regular team

New Team

Team

Team no:

Name:

Address:

Telno:

Play soccer ( )

Match

Match no:

Referee no:

Played date:

Play matches()

Referee

Ref no:

Name:

address:

tel:

Judge matches( )

Send socre to secretary ()

*

Use Case Diagram & Use Case Specifications

Adding a new match result

Referee

Secretary

Judge the match

Asking for the details

Providing the details

Check result accuracy

Add the new result

3.2 Adding a new team to the league

<<Include>>

<<Include>>

<<Include>>

<<Include>>

Secretary

Add team details to league table

Check application form

Check payment

Check history of the team

Accept team from the league

Add details

<<Extend>>

3.3 Printing Report

Printing Report

Print report

Choose the correct fields

Check the details from tables

Secretary

<<Include>>

<<Include>>

<<Include>>

Sequence Diagram

4.1 Adding a new match result

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

Score

Referee

Secretary

Time line

Judge the match

Asking details

Providing details

Check result accuracy

Add the new result

4.2 Adding a new team to the league

|

|

|

Add details of new team

Check application form

Check payment

Check history of the team

Accept team from the league

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

|

Register form

League table

Time

line

Secretary

|

|

|

|

|

|

|

|

|

|

|

4.3 Printing a Report

Task 06

Introduction To Task 06

In this task we have to produce a review of the whole assignment form task 1 to 5, all the work what I have done. I should also describe the methods and techniques what I used in the assignment.

Review Of The Whole Assignment

In this assignment form the beginning to the end there many diagrams to draw and codes to write. As is there many types of designing techniques and coding ways, I have used some of those to complete my assignment in a successful manner. To complete this assignment I came across many difficulties and I overcame all in a great difficult.

In task 01 I had to create tables such as League Table, Match Table and Score Table. These tables are created to make the report. In task 01 I had to make 2 reports such as League Report and Results Report. These two reports are very helpful to do rest of the assignment, which means the assignment is based on these 2 reports. I drawn DSD diagrams and LDSDs, PDSDs, at last I had to draw the PSD diagrams and write the program specification.

In task 02 I drew the flow charts. There are 2 flow charts that have to be drawn according to the reports. Flow chart is diagram which shows the flow of the future system.

In task 03 I have written the pseudo code according to the questions. First I had to write the procedure and then only I wrote the pseudo codes and I called the procedure in 1st pseudo code that is written according to the report 01. I wrote 2 pseudo according to the 2 reports in task 01. In task 03 they had ask to write a pseudo code for a reports main menu.

In task 04 I did the testing to the pseudo codes written in task 03. I used three desk checks and dry runs ways of testing.

In task 05 there are many different types of UML modeling techniques to draw and describe. As I have many techniques such as high-level class diagrams (domain analysis), use case diagrams and sequence diagrams.

In the high-level class diagrams they not ask to draw sub diagrams. After drawing the high level use case diagrams, I had to draw 4 different diagrams according to the questions such as to check the member details, to renew the annual subscription of a member, to delete a member from the database, and to print a report. I have drawn these diagrams according to my knowledge and also according to the scenario. We should draw the sequence diagrams according the 4 use diagrams mentioned above.

When considering to these types of UML modeling techniques, the most suitable UML techniques is class diagrams. Since in the class diagrams we have mention all the attributes and operations, it seems most suitable for Object Oriented Language.