i

ARDHI UNIVERSITY

SCHOOL OF GEOSPATIAL SCIENCE AND TECHNOLOGY

BSC. IN INFORMATION SYSTEM MANAGEMENT

RUGBY CLUB SYSTEM

SUPERVISORS:

NAME SIGNATURE

DR BUBERWA ……………….

MS DOMINA ……………….

ii

RUGBY CLUB SYSTEM

GROUP MEMBERS:

NAME REG NO: SIGNATURE

1. SALEH NAJIM 5155/T.2013 ……………….

2. SHOCKA ZAHRA 5958/T.2013 ……………….

3. BURETTA JAMES 5923/T.2013 ……………….

4. TARIMO EVANCE 5961/T.2013 ……………….

5. NGODA ISRAEL 5951/T.2013 ……………….

6. LAURENT LOYCE B. 6463/T.2013 ……………….

iii

ACKNOWLEDGEMENT

First and foremost, we would like to thank ourselves for being such a cooperative group of six (6)

students full of energy and desire to accomplish such kind of interesting project tasks. We would

also like thank Mr. Buberwa and Miss Domina for giving us the foundations and basics of system

analysis and design which helped us tremendously in completing this project in a professional

manner.

Secondly for supplying us with a CASE tool, Microsoft Visio 2007 setups which helped us prepare

and translate our drawings and design in an intellectual way.

Lastly we would like to thank ARDHI UNIVERSITY for giving us this opportunity to work in a

great environment and also we thank all ISM 2 students being such a lovely group to study, learn

and grow with. Also thank to all those whose names may not have appeared here but whose

contribution has not gone unnoticed. We would like to thank all of them, for their help in various

ways.

iv

ABSTRACT

Currently we live in a Computer age and so the importance of computerized system to run various

business and social life activities cannot be overlooked. Companies and communities with a

common goal of operation or existence have now realized that a computerized system, although it

is very expensive at the developing and set-up stage, can make the business operations run

smoothly, effectively and efficiently thus making it cost effective in its undertakings and give it a

competitive edge in its market (sphere of operations).

Much like any other organization, a sport club can also take a shot at developing up and lastly

making the most of a computerized system which can be profoundly help the club satisfy its

stockholder’s needs.

1

Table of Contents

ACKNOWLEDGEMENT ......................................................................................................................... iii

ABSTRACT ................................................................................................................................................ iv

FIGURES ..................................................................................................................................................... 3

1.0 INTRODUCTION ................................................................................................................................. 4

1.1 Objective ............................................................................................................................................ 4

1.2 Scope .................................................................................................................................................. 5

2.0 METHODOLOGY ............................................................................................................................... 6

2.1 Description ......................................................................................................................................... 6

2.2 Strength .............................................................................................................................................. 6

2.3 Weaknesses ........................................................................................................................................ 6

3.0 DATA FLOW DIAGRAM ................................................................................................................... 7

3.1 Context Diagram ............................................................................................................................... 7

3.2 Level 0 – Data Flow Diagram......................................................................................................... 10

3.2.1 Process Description .................................................................................................................. 11

3.2.2 Data Flow description .............................................................................................................. 12

3.2.3 Data store contents ................................................................................................................... 13

3.2.4 External Entities description ................................................................................................... 13

4.0 ENTITY RELATIONSHIP DIAGRAM (ERD) ............................................................................... 14

4.1 Tools ................................................................................................................................................. 14

4.2 Entities and their attributes ........................................................................................................... 14

4.3 Diagram ........................................................................................................................................... 18

5.0 PROTOTYPE ...................................................................................................................................... 19

Description ............................................................................................................................................. 19

6.0 ENTITY LIFE HISTORY (ELH) ..................................................................................................... 21

6.1 Technique used ................................................................................................................................ 21

References .................................................................................................................................................. 22

2

Milestones .................................................................................................................................................. 23

3

FIGURES Figure 1: Context Diagram of Rugby Club System ................................................................................. 9

Figure 2 Level-0 Data Flow Diagram ...................................................................................................... 10

Figure 3: Entity Relationship Diagram (ERD) ............................................................................................. 18

Figure 4: Rugby Club System Interface ...................................................................................................... 19

Figure 5: Rugby Club System form for creation fixtures ........................................................................... 20

Figure 6: Rugby Club System form for adding new member .................................................................... 20

Figure 7: JSD for entity life history of fixtures ...................................................................................... 21

4

1.0 INTRODUCTION

Today is the modern era where we have the technology to assist us in every possible way. As we

have seen the transformation of the work which was manually executed and now by the

introduction of technology everything has changed around us, we are able to work efficiently and

within short span of time investing a little effort. The most amazing development has been in the

field of computers, it has made our life easy by automating the manual work.

In the given scenario, there is a Rugby club that was manually operated and due to the development

of technology the founders (elected committee) have decided to invest in a new information

management system (Rugby Club System). The system will have to perform the following main

tasks:

(i) Registration of new members

(ii) Renewal of membership

(iii) Creation of fixtures and other necessary requirements

(iv) Producing club management report

The system will benefit the club in many ways; it will help to control the overall processes going

on in the club. The system will provide numerous facilities such as it will help to register new

members and it will manage activities conducted by elected committee and event secretary such

as creation of fixtures, set-up sessions and selection of team captain. We are looking forward to

make a system using SDLC steps and using appropriate methodology which will be best suited for

the system after we will be done of the system analysis.

1.1 Objective

The main objective of designing this system is to computerize all the works that was previously

done manually. That is public member can register for a membership of the club through a

computerized system and all the registered members can access the diary of all matches and other

club events including results of the matches. The system can enable the committee to create

fixtures and setting up sessions and publishing results in general.

5

1.2 Scope

The scope of the system is shown on the context diagram. The system registers public members

who are interested to be either social members or public members of our system and before

registering these public member have to pay their application/ registration fee.

After the public member is become a member and all their information are stored in the member

file. The members who have their membership expired are notified by the system so that they may

renew their membership. It is normally after a year has passed since registration period.

The system allow the coach to allocate the team and request for the club events from the system

so that he may be able to know the progress of the team through club events like match results

and also prepare the team for training sessions.

The system also allow team captain to publish and record match results which are then stored into

their respective file which is match result file, ready to prepare rugby club management repost.

Finally the elected committee which is part of our system, can provide information about all the

club events such as fixtures list, planned sessions and captain list which are stored separately. The

data files for each information provided by the elected committee is then aggregated and accessed

by various external entities in our system.

6

2.0 METHODOLOGY

2.1 Description

The methodology used in the system is Structured System Analysis and Design Methodology

(SSADM). SSADM is a systematic approach for developing an information system, the

methodology was developed for the CCTA (Central Computing and Telecommunication Agency)

which is responsible for computer training and procurement for UK civil service. It is sometimes

described as a data driven methodology because of its emphasis on data modelling and the

construction of databases. SSADM is a systematic approach to the design and implementation of

large scale information projects

2.2 Strength

SSADM provides a systematic method for development of the system and the progress can

be effectively monitored

It facilitate a quick and accurate development of code and data structures

SSADM produce system which is well documented and easy to maintain

Produce a system within an appropriate time limit and at an acceptable cost

2.3 Weaknesses

The methodology is too cumbersome and add to complexity rather than simplifying it

The methodology over-value the knowledge of the analyst and under-value the experience

of the user.

The methodology assumes that requirements can be found and then effectively frozen

7

3.0 DATA FLOW DIAGRAM

3.1 Context Diagram

Main external entities

1. Public

2. Elected committee

3. Coach

4. Team Captain

5. Member

Main flows

1. Public

- The main flows from the public to the rugby club system are as follows

a. Membership application request

b. Membership type

c. Initial fee

-The main flows from the rugby club system to the system

a. Membership request acceptance

2. Elected committee

-The main flows from the elected committee to the rugby system are as follows

a. Fixtures list

b. Captain list

c. Planned sessions

-The main flows from the rugby club system to elected committee are as follows

a. Club management report

3. Coach

- The main flows from the coach to the rugby club system are as follows

a. Allocated/ selected team

b. Club event request

-The main flows from the rugby club system to elected committee are as follows

8

a. Club event

4. Team Captain

-The main flows from the team captain to the rugby club system are as follows

a. Matches results

5. Member

-The main flows from member to the rugby club system are as follows

a. Renewal fee

b. Member ID

-The main flows from the rugby club system to member are as follows

a. Club events

b. Renewal notification.

9

Figure 1: Context Diagram of Rugby Club System

10

3.2 Level 0 – Data Flow Diagram

Figure 2 Level-0 Data Flow Diagram

11

3.2.1 Process Description

Process refers to work or actions performed on data inside the system, so that they are transformed,

stored or distributed.

Update Planned Session file- the process updates the planned session file by the information

received from elected committee.

Update Captain List file - the process update captain list file from elected committee.

Update Fixture list file - the process update fixture list file from elected committee.

Process and transform request and fee payment- it process and transform membership request and

fees paid by public member who wants to join the club.

Update registration fees collected file - it updates the registration fees file from the fee paid by the

new members applying for membership.

Approve and validate members file - the process updates members file after receiving the

applicants details and validate them.

Access Registration Fee file - the process retrieve information on registration fees from registration

fee file.

Notifying member status - the process retrieve member status information from members file and

sends a notification to members concerning their membership status so that they can renew.

Process membership details - it process members information (renewal fee and member ID) from

members so that they can update their membership status.

Process and update fees file - it process renewal fees from the members that wanted to update their

membership after a year has passed and update fees file.

Determining paying members - the process determine members who paid renewal fee.

Updating membership status - the process updates membership status.

Access renewal fees file - the process retrieve renewal fee file so that the club management report

can me produced.

Updates allocated team file - the process updates allocated team file.

12

Access team file - the process retrieve information from allocated team file for producing

management report.

Recording and updating match results file - the process records match result and update match

results file.

Access match result file - the process retrieve match results for club event.

Access planned session file - the process access planned session for club events.

Access fixture file - the process retrieve fixture list for club event.

Access captain list file - the process retrieve captain list for club event.

Aggregating club events - the process aggregate all club events.

Producing club management report - the process produces club management report after the

aggregation of each file and action of each process took place, and the report is mainly dedicated

to elected committee.

3.2.2 Data Flow description

Data flow are arrows depicting movement of data, labeled with a meaningful name for the data

in motion.

Public request for membership of the club, the request go through the club committee. When the

club committee accept the application, the member information is stored in the database.

Elected committee run the rugby club, it create and manage fixture lists, captain list, planned

sessions and these information are stored in the fixture list file, captain list file, and session file

and also receive the club management report.

Coach allocate the team by selecting player among the playing member of the club and the

committee elects a captain from amongst the players of each team then team information will be

stored in the team database.

Team captain collect the record all matches result then result information will be stored in result

database for published on the notice board.

13

Member renews membership after paying renewal fee and their information is recorded in the

member database after renewal fee being processed. And also the member can access club events

from system.

3.2.3 Data store contents Data store is data at rest inside the system. Is the repository of data that is accessed or changed.

Fixture File: Fixture data store can be used to store or contain a list of all fixtures created.

Captain list data store: it stores or contains list of all captains in the club.

Registration fees file: it contains or store all registration fees for different membership type.

Planned sessions: stores all the planned sessions organized by elected committee (like training

sessions, advertising training sessions)

Allocated team file: it stores or contains all teams selected by coach.

Match results file: stores all match results.

Renewal fee file: stores all renewal fees for renewing membership.

Member file: it stores or contains all registered members, including social and playing members.

3.2.4 External Entities description

External entity is the source or destination of data outside the system.

The main external entities are coach, elected committee, member, public, and team captain.

14

4.0 ENTITY RELATIONSHIP DIAGRAM (ERD)

4.1 Tools

Many modelling tools are in use today but one of the most popular modelling tools is CROW

FOOT tool. Microsoft Visio uses Crow foot modelling tool.

The tool's notation were proposed by Gordon Everestt.

4.2 Entities and their attributes

Entity

Attributes

The following are the identified entities that interact with the system in one way or another

1. Coach

2. Elected Committee

3. Sessions

4. Team Captain

5. Member

15

6. Team

7. Club Event

8. Fixtures

9. Registration

The following are the identified entities with their corresponding attributes\

1. Coach

Coach_ID (pk)

First_Name

Last_Name

D.O.B

Level

2. Elected Committee

SSN (pk)

First_Name

Last_Name

Email_Address

Position

3. Session

Session_ID (pk)

Session_Time

Session_Date

Type

Coach_ID

4. Team Captain

Captain_ID (pk)

First_Name

Last_Name

Level

D.O.B

16

5. Member

Member_ID (pk)

First_Name

Last_Name

Email_Address

Type

D.O.B

Membership_ID

6. Team

Team_ID (pk)

Level

Number_of_Players

Coach_ID

Captain_ID

7. Club Event

ID (pk)

Name

Time

Location

8. Fixture

Fixture_ID (pk)

Date

Time

Venue

Opponents_Name

Results

9. Registration

Registration_Number (pk)

Date

Fee

17

First_Name

Last_Name

Age

Gender

Registrar_Name

18

4.3 Diagram

Figure 3: Entity Relationship Diagram (ERD)

19

5.0 PROTOTYPE

Description

The prototype is made up of user interface (Figure 4) which is made up of buttons having various

functionalities as show below:

Member Button - These button as the functionality to add a new member into our system since it provides

public with a form (Figure 6) to register as member and these form is linked to our database.

Fixture Button - These button as the functionality to add fixtures into our system by allowing the elected

committee to gain access to a form (Figure 5) which is linked to our database.

Close Button - These button as the functionality to allow the user of our system to exit from the form

interface.

Exit Button - These button as the functionality to allow the user to exit from our entire Rugby club system.

Figure 4: Rugby Club System Interface

20

Figure 5: Rugby Club System form for creation fixtures

Figure 6: Rugby Club System form for adding new member

21

6.0 ENTITY LIFE HISTORY (ELH)

6.1 Technique used

The technique used is called Jackson Structured Diagraming (JSD). This technique uses

rectangular boxes to represent information. The Diagrams normally reveal 3 control structures

which are SEQUENCE, SELECTION AND ITERATION.

SEQUENCE is shown by boxes in parallel to each other just below the main name of the entity

that the diagram is trying to describe. SELECTION is shown by small empty circles in the top

right corner of the rectangular box. ITERATION is shown by an asterisk, also in the top right

corner of a rectangular box.

Figure 7: JSD for entity life history of fixtures

22

References Dr Buberwa and Miss Domina. (n.d.). System Analysis and Design Lectures (1-3).

Joseph S. Valacich, Joey F. George, Jeffrey A. Hoffer. (n.d.). Essentials of Systems Analysis and Design

(5th ed.).

Joseph S. Valacich, Joey F. George, Jeffrey A. Hoffer. (n.d.). Modern System Analysis and Design (4th

Edition ed.).

ssadm. (n.d.). Retrieved 5 31, 2015, from http://www.chris-

kimble.com/courses/sdm/presentation/sdm5.pdf

23

Milestones