Marker's Comments:: Programming Methods

Award: International Diploma in Computer Studies
Module Title: PROGRAMMING METHODS
Assignment Title : Rugby Union Club
Examination Cycle: September 2009
Candidate Name: CHRIS OSEI MIREKU
NCC Education
Candidate No:
Submission Date: 6TH AUGUST 2009
Marker’s comments:
Moderator’s comments:
Mark:
Moderated Final
Mark: Mark:
PROGRAMMING METHODS Page 1

Statement and Confirmation of Own Work
Program/Qualification name: International Diploma in Computer Studies
All NCC Education assessed assignments submitted by students must have this statement
as the cover page or it will not be accepted for marking. Please ensure that this statement is
either firmly attached to the cover of the assignment or electronically inserted into the front
of the assignment.
Student Declaration
I have read and understood NCC Education’s Policy on Academic Dishonesty and
Plagiarism. I can confirm the following details:
Student ID/Registration number:
Name: CHRIS OSEI MIREKU
Centre Name: LABONE IPMC
Module Name: STRUCTURED PROGRAMING METHODS
Module Leader: MR. NKANSAH
Number of words:
I confirm that this is my own work and that I have not plagiarized any part of it. I have also
noted the assessment criteria and pass mark for assignments.
Due Date:6TH AUGUST 2009
Student Signature:
Submitted Date: 6TH AUGUST 2009

PM
TASK 1
The club secretary would like the following report on a regular basic;
Report 1 A list of all the paid-up member names and contact number by
membership level, with totals for each level
Report 2 A list of players a of each of the four teams for the current season
with details of number of matches played for each teams (a player
may play for more than one team), tries scored, penalties scored
and conversions scored, with the players listed in alphabetical
order.
Using JSP techniques and methodology, analyse the requirements for both reports.
Produce diagrams for each report showing the step-wise progression. Diagrams should
include logical data structure diagrams (DSD) and preliminary program structures (PSDs) as
will as detailed program specification for each report.
Report 1
Adult level Non-member level

Junior level
Name Contact Name Contact Name Contact

Section 1.1 Logical (DSD) Data structure diagrams
Stepwise refinement 1
Paid up Members report
Header Report body Footer
Line of report *

Paid up Members
report
Line of report *
Adult record o o
Junior record Non-players record

Paid up Members report
Line of report *
Adult record Junior record Non-players

record
Name Contact Name Contact
Name Contact

Report 1
Section 1.2 Program structure data
Paid up members report

program
Initialisation Processing Termination


program
Initialisation Processing Termination
Open files Print file heading Close all files Print file heading
by level by level
Read a record *


program
Termination
Initialisation Processing
Close all files Print file heading

Open files Print file heading
by level
by level
Read a record *
level=Adult level= junior level=non-playing
Process record
Process record Process record
Print accumulate
Print accumulate Print accumulate
report total level
report total level report total level
details
details details
Name Contact
Name Contact Name Contact
Add 1 to Add 1 to
Add 1 to
level total level total
level total

Report 1
Section 1.3 Program specification
CLIENT NAME: CLUB SECRETARY
PURPOSE OF PROGRAM:
THE PROGRAMME PRODUCES A REPORT BASED ON LIST OF

PAID-UP MEMBERS NAMES AND CONTACT NUMBERS BY
MEMBERSHIP LEVEL.
DUE DATE: 21ST MAY 2009
PROGRAMMER: CHRIS OSEI MIREKU
HOW THE PROGRAMME WORKS
The program is expected to Initialize, Process and Close. This would be based on the
processing. The program will be carried out in three phases. These are INITIALISING,
PROCESSING and CLOSING.
INITIALISATION: Here, files (input and output) are opened, read from and written to at this
stage.
PROCESSING: The detailed step in running the program shown at this stage. The program
reads the first record which is the record of member. Until End- of-File condition is reached
If member is an Adult, Junior or Non-playing level. Paid–up members Names and contact
numbers by membership level are printed with totals for each level.
TERMINATION: All files that were opened and printed are closed

Current Season Report
PLAYERS MATHCH DETAILS

DETAILS
Name Team Matches Tries Penalties Conversions

scored scored scored
1st 2nd Junior Junior

Team Team 1st 2nd
Team Team
Report 2
A list of players for each of the three teams for the current season with details of number of
matches played for each team (a player may play for more than one team), tries scored,
penalties scored, and conversions scored with the players listed in alphabetical order.

Section 2.1 Logical (DSD) Data structure diagrams
Current season
Header Player body Footer
Line of report

Current season
Line of report
Player
Match details *

Current season
Line of report
Player
Match details *
Name Teams Matches Tries scored Penalties

played scored
Conversions
scored

Current season
Line of report
Player
Match details *
Name Teams Matches Tries scored Penalties

played scored
Conversions
scored
1st Team 2nd Team Junior 1st Junior 2nd

Team Team

Section 2.2 Program structure data
Current season
Initialisation Processes Termination

Current season
Until EOF Close file

Open file
Read and process Player *

record

Current season
Until EOF Close file

Open file

record
Current season
Print report
Player details Match details *
[Alphabetical order]

Current season
Until EOF
Close file
Open file
record
Current season details
Player details Print report

Match details *
Name Team Match Tries Penalties

played scored scored
Conversion
scored

Current season
Until EOF
Open file Close file

record
Current season details
Player details Print report

Match details *
Name Team Match Penalties

Tries
played scored scored
Conversion
1ST Team 2ND Team Junior 1ST Junior 2nd scored
Team Team

Report 2
Section 2.3 Program specification
CLIENT NAME: CLUB SECRETARY
PURPOSE OF PROGRAM:
THE PROGRAMME PRODUCES A REPORT BASED ON LIST OF

PLAYERS FOR EACH OF THE FOUR TEAMS FOR THE CURRENT
SEASON WITH DETAILS OF NUMBER OF MATCHES PLAYED FOR
EACH TEAM,TRIES SCORED, PENALTIES SCORED, CONVERSION
SCORED, WITH THE PLAYER LIST IN APHABETICAL ORDER.
DUE DATE: 21ST MAY 2009
PROGRAMMER: CHRIS OSEI MIREKU
HOW THE PROGRAMME WORKS
The program is expected to Initialize, Process and Close. This would be based on the
processing. The program will be carried out in three phases. These are INITIALISING,
PROCESSING and CLOSING.
INITIALISATION: Here, files (input and output) are opened, read from and written to at this
stage.
PROCESSING: The detailed step in running the program shown at this stage. The program
reads and process player current season record until end of file. Player name is processed,
matche details is processed, teams player played[1ST team, 2ND team, Junior 1ST team , Junior
2ND team ], matches played, tries scored, penalties scored, conversions scored and printer in
alphabetical order.
TERMINATION: All files that were opened and printed are close
Reference
Data Structure chapter 3, page 3-22, 3-37

TASK 2
Flowchart Report 1
Start
Open input and output

file
Total Adult = 0
Total junior = 0
Total Non-memders = 0
Print member level heading in output files
Read a line of record

from input file
Are there more records in the in

False
put file
True

Print name and contact
under Adult level head
Add one
Level Adult to total
Print Adult level total
Adult
Print name and

contact underJunior
Print Junior level total Level Junior Add one
level head
to total
Junior
Print name and contact

Level Non-member
under Non-member
level head Add one
Print Non-member level to total
total Non-
member
v
Close all files
Close

start
REPORT TWO
Open member records
Arrange records in
alphabetical order
Read first records
Matches played: =0
Tries scored: =0
Total penalties_scored: =0
Read member[n]. Read next

team_played member records
Open club’s season

details
Read first team

records
Read next match
details
Member[n].member_no
No Match[y].member_no
Yes
No Match[y].team_played=first
Yes

Total match: =total_match+1
Total tries scored: = total_tries scored +match[y].tries scored
Total penalties scored: =total_penalties+match[y].penalties_scored
End of member records?

No
Yes
Print total matches_played
Print total tries_scored
Print total penalties_scored
End of member No
records?
Read first records
Matches played: =0
Total tries_scored: =0
Read member[n].
team_played Read next
member records

details
Read first team

records
Read next match
details
Member[x].member_no
No
Match[y].member _no
Yes
No
Match[y].team _played=second
Total tries: = total_tries+match[y].tries_scored
Total penalties_scored: =total_penalties+match[y].penaltie_scored
Print total penalties_scored_cards

End of member
records?
Read first records
Matches played: =0
Tries_scored: =0
Read member[n].
team_played Read next
member records

details
Read first team

records
Read next match
details
Member[n].member no
No Match[y].member no
Yes
No Match[y].team_played=junior
Yes
Total tries_scored: = total_tries+match[y].tries_scored
Total penalties_scored: =total_penalties+match[y].penalties_scored

No
Yes
Print total penalties_scored_cards
End of member
records? No
Yes
End
Reference
Flowchart chapter 2, page 2-13 to 2-32

Task 3
a) Write a procedure that will check for paid-up member. This procedure will be
included in the program that the club secretary will use when checking if people are
allowed into meetings.
b) Write pseudocode for the two report in Task 1. Include in your code the procedure
written in 3a).
c) Write pseudocode for a reports main menu. Note you are not expected to write
pseudocode for the options, only the codes to navigate the menu is required.
Report 1
Procedure for paid_up_member( )
Use variable counter OF TPYE Integer
RECORD : member
HAS FIELDS name : string
contact : string
level : string
status : string
MEMBERS (100) : Array OF TPYE members
Comment : The membership file was assume to contain a member record of 100 of type
integer. Reading one record at a time and decide in the status
For ( counter = 1, counter <=100, + counter )

IF member (counter) . level = is ‘’Adult’’ AND member (counter) . status =
‘’paid’’.
Print member (counter) . Name
Print member (counter) . contact
Print member (counter) . level
Print member (counter) . status
Adult total = Adult total + 1
END IF
ELSE IF member (counter) . level = is ‘’Junior’’ AND member (counter) . status
= ‘’paid’’.
Print_Record ( member (counter) )
Junior total = Junior total + 1
END IF
ELSE IF member (counter) . level = is ‘’Non-playing’’ AND member (counter) .
status = ‘’paid’’.
Non-playing total = Junior total + 1

END IF
END PROCEDURE
PROCEDURE Print_Record (Record new record)

Record OF TYPE string
END PROCEDURE
Task 3b
MAIN PROCEDURE
Use variables Adult total, Junior total and Non-playing total OF TYPE integer
Print heading name, contact, level, status in output file
Paid_up_member.
Print ‘’total paid_up_member. Adult members are’’
Adult total
Print ‘’total paid_up_member. Junior members are’’
Junior total
Print ‘’total paid_up_member. Non-playing members are’’
Non-playing total
End procedure
Procedure for paid_up_member( )
Use variable counter OF TPYE Integer
RECORD : member
HAS FIELDS name : string
contact : string
level : string
status : string
MEMBERS (100) : Array OF TPYE members
Comment : Reading one record at a time and decide in the status
For ( counter = 1, counter <=100, + counter )

IF member (counter) . level = is ‘’Adult’’ AND member (counter) . status =
‘’paid’’.

Adult total = Adult total + 1
END IF
ELSE IF member (counter) . level = is ‘’Junior’’ AND member (counter) . status
= ‘’paid’’.
Junior total = Junior total + 1
END IF
ELSE IF member (counter) . level = is ‘’Non-playing’’ AND member (counter) .
status = ‘’paid’’.
Non-playing total = Junior total + 1
END IF
END PROCEDURE
PROCEDURE Print_Record (Record new record)
Record OF TYPE string
END PROCEDURE
REPORT TWO
PROGRAM season_details
RECORD club_members
HAS FIELDS member_name: String
contact_number: String
_ _ _ Trailer record linking club_members
RECORD team_matches
HAS FIELDS member_list: String
match_no: Integer
tries_scored: Integer
penalties_scored: Integer
conversions_scored: Integer
team_played: String
match_list[50]: ARRAY OF TYPE club_matches
member_list[100]:ARRAY OF TYPE club_members
total_match, total_tries, total_penalties_scored, total_conversions_scored OF TYPE Integer

number, count OF TYPE Integer
FOR (number: =1, number=50, +1)
total_matches:=0
total_tries_scored:=0
total_penalties_scored:=0
total_conversions_scored:=0
FOR (count: =1, count=50, +1)
IF member_list[number}.member_no=
match_list[count].member_number AND match_list[count].team_played:= “First”
THEN total_match:=total_match+1
total_goals:=total_tries+match_list[count].tries_scored
total_penalties_scored=total_penalties_scored+match_list[count].penalties_scored
total_conversions_scored:=total_conversions_scored+match_list[count].conversions_scored
END IF
END FOR
Print_ totals(season_details)
FOR (count: =1, count=100, +1)
match_list[count].member_number AND match_list[count].team_played:= “second”
total_tries scored:=total_tries_scored+match_list[count].tries_scored
total_penalties_scored:=total_penalties_scored+match_list[count].penalties_scored
total_conversions _scored:= total_conversions_scored+match_list[count].conversions_scored
END IF
END FOR
FOR (count:=1,count=100, +1)
match_list[count].member_number AND match_list[count].team_played:= “junior”
total_tries scored:=total_tries+match_list[count].tries_scored
total_penalties_scored:=total_penalties+match_list[count].penalties_scored
total_conversions_scored:=total_conversions+match_list[count].conversion_scored
END IF
END FOR
End Program

PROCEDURE Print_ totals(season_details)
season_details OF TYPE string
Print total_matches
Print total penalties_scored
Print total conversions_scored
END PROCEDURE
Task 3c
REPORT MAIN MENU
Use variables select OF TYPE integer
Display ‘’type 1 to print paid_up_member total report’’
Display ‘’type 2 to print playing by team for current season’’
Display ‘’type 3 to quit
Accept select
IF select = 1
paid_up_member
ELSE IF select = 2
Team played
ELSE IF select = 3
Quit
END IF
Reference
Pseudocode chapter 4, page 4-4 to 4-24

Task 4
Test Plan for Report 1
This test is to check if the pseudo code written in Task 3b) report 1, a list of paid_up_member
Test Purpose level, name, contact and status.
The data needed to do this test is the members subscription file with contain field name,
Test Data contact, level and status.
The Database is read for each membership level to check whether is paid. The status is also
checked whether the member has paid which is done by the paid procedure. The total record of
Test Condition each level is also to be tested, accumulated and displayed.
Adult level Non-player level

Junior level
Expected
Outcome Chris 0262526458 Filexpina 0246526458 Mama 0244630033
On running the codes in a dynamic test, the actual output of the program was found to be the
same as that which was expected.
Actual
outcome
Adult level Non-player level

Junior level
Chris 0262526458 Filexpina 0246526458 Mama 0244630033
Therefore, the program worked well
Dry checking
1.Variables

All the following variables have been checked and found that they were properly declared at
the beginning of the pseudocode and that are of the correct data type
Variable Data type

Adult total Integer
Junior total Integer
Non-player total Integer
Name String
Contact Integer
Level String
Status String
.
2. Subroutines and Functions
Procedure paid_up_member record was call by the main procedure.
Procedure member record was pass to the procedure in the correct order.
The name of the call procedure and the calling procedure are he same.
3. Constants
The membership file was assume to contain a member record of 100 of type integer.
4. Equation
Each record read was pass on successfully to the print record because the data type are the
same.
DRY RUN FOR REPORT 1
PASS
1 2 3
Name Chris Filexpina Mama
Contact 0262526458 0246526458 0244630033
Level Adult level Junior level Non-player
Status Paid Paid Paid
Total 1 1 1
Test Plan for Report 2

This test is to check if the pseudo code written in Task 3b) report 2, is to list players in
Test Purpose alphabetical order for each of the three teams for the current season with details of number of
matches played, tries scored, penalties scored and conversion scored.
The data needed to do this test is the

Test Data
The Database is read for each Variable: season_details , match_number, tries_scored,

penalties_scored, conversions_scored, team_played, number, match_no and count
Test Condition
PLAYERS MATHCH DETAILS

Expected DETAILS
Outcome Name Team Matches Tries Penalties Conversions
Team Team 1st 2nd
Team Team
Bob ---- 5 5 1 0
Nana ---- 4 12 5 8
Yaw ---- 2 12 8 6
Actual PLAYERS MATHCH DETAILS

outcome DETAILS
Name Team Matches Tries Penalties Conversions
Team Team 1st 2nd
Team Team
Bob 5 5 1 0
Nana ---- 4 12 5 8
2 12 8 6
On running the codes in a dynamic test, the actual output of the program was found to be the
same as that which was expected.
Therefore, the program worked well
DESK CHECKS FOR REPORT TWO
Variables

All variables in the pseudocode have been check and declared at the beginning of the pseudocode
and that they all are of correct data type
Subroutines and functions
All checking made to the procedure were correct and its parameters existed in the right order, of the
right number and data type.
Constants
There was no constant variable declared
Variable equation
No equated variables were declared in the pseudocode.
Dry running will be performed to test the pseudocode by examining each line and simulating a
computers action without making any assumptions at all. It is advisable that this is done by
somebody other than the programmer as it has been shown that programmers are most likely not to
notice bugs in their own code.
Reference
Test plan chapter 6, page 6-8, 6-16,6-17
TASK 5 (a)
High-level

Club secretary Membership Match
Subscription Treasure Coach
Club Meeting Team
Generalization

Club staff
Club secretary Treasure Coach
Official document
Membership Subscription Player membership
Association
Club secretary 1 checks * Membership

1 head 1
Coach Team
Secretary
1 record * Match
Coach
1 access * Player
Membership
1 paid 1
Membership Subscription
Treasure
1 monitors
* Membership
Clubs
1 organize
* Meeting
Treasure 1 monitors * Subscription
Club secretary
Clubs Treasure * 1 Team
Coach
runs
Name Name Name
Address
Address Team
Employee
Job title Job title Title
Check membership
PROGRAMMING METHODS Monitor membership
Page 41 Head team
Record matches
Monitor subscription Access membership
Print report
Membership Club Match
Name Team
Name
Address player
Address Date
Member ID
Tries scored
Member level Contact
Conversions scored
Contact
Run team
Penalties scored
Paid subscription
Organize meeting Match played
Matches player
Subscription
Name
Member level
Subscription year
Payment date
Amount
Check membership list
Record member
matche(s)
TASK 5b
Add player record

<<include>>
register player member
Delete player record

<<extend>
<<extend>
>>
<<include>> Update player record
<<include>>
Secretary
Print player record Check member level
log on <<include>>
Check member
<<include>> subscription
<<include>>
select player for match check player team

pay
Treasurer <<include>>
Secretary
<<include>> Record player match
details
log on
<<include>> Check member level

Coach
TASK 5c
Use case diagram checking member details.
Users of this system are; secretary, treasurer and coach.
Check member details
User
SCENARIO
1. log on to member system with password

2. System displays a menu of option
3. Select choice “ check member details”

4. Enter member name to be checked
5. System begins to check
6. Member record is displayed
7. Close member record details
8. log off system
Use case diagram renewing the annual subscription of a member
Users of this system are; secretary and treasurer.
renew subscription of a member
User
SCENARIO

3. Select choice “renew subscription of a member”
4. Enter member name or ID to be checked
6. Display member record and member subscription is renewed
7. Close renew annual subscription
8. Log off system
Use case diagram deleting a member
User of this system is; secretary.
Deleting a member
User
SCENARIO

3. Select choice “delete member record ”

6. Member record is displayed
7. Select member record and delete
8. Close record
9. Log off system
Use case diagram printing a report
Users of this system are; secretary, treasurer and coach.
Printing a report
User
SCENARIO

3. Select choice “ print report ”
6. Report is extracted
7. Display report from database
8. Click on print report option
9. Log off system
TASK 5d
DELEVLOPING A SEQUENCE DIAGRAM
Checking member details.
System Windows System Menu Search Screen System Database
log on(name & password)
check
[name & password]
OK/NOT OK

Select option [check member ]
Open
Enter [ member name ]
check name
Return
result
[Record found]Display member detail
[Record not found]Display Not found
Log off
Feedback
Renewing the annual subscription of a member
check
[name & password]
OK/NOT OK

Select option [renew subscription ]
Open
search record
Return
result
[Record found]Display Found
Click Renew subscription

Update member record
Log off Update
Update successful
Database
Feedback
Deleting a member
check
[name & password]
OK/NOT OK

Select option [delete member ]
Open
search record
Return
result
[Record found]Display Found
Click Delete member

Update record
Log off Update
Update successful
Database
Feedback
Printing report.
System Windows System Menu Print Windows
check
[name & password]
OK/NOT OK

Select option [Print report ]
Select report option
Display report
click on print [ To print report ]
Feedback
Log off
Feedback
Collaboration diagram
1.Log on(name & password)
Check member records
2.Name & password OK
8.Display member record
9.Log off 3.Select option(check member record)
System Windows
7.Return result
System Database System Menu
4. Open application
5.Enter member name
Search Screen
6.Check member record.
Annual subscription of a member

9. Renew subscription
12. Update successful
13.Log off 3. Select option [subscription ]
System Windows 10.Select option [renew
subscription ]
7.Return result found

11.Update member record
System Database System Menu
Search Screen
6.Check member record. 4. Open application
5.Enter member name
9. Delete member
Deleting a member
12. Update successful
13.Log off
System Windows
3. Select option [delete]
10.Select option [delete member ]
7.Return result found

11.Update member record
System Database
System Menu

Search Screen
6.Check member record.
4. Open application
5.Enter member name
Printing report.
7. Print report
8.Log off 3. Select option [Print report]
System Windows 5. Select report option
6.Click on print [ To print report ]
System Menu
Print screen
4.Display report
TASK 6
A REVIEW, ASSUMPTIONS AND POSSIBLE CHANGES

This report contains review, assumptions and changes that could be introduced to
enhance the work. I encountered some challenges during the process of this project,
I made some assumptions. I assumed that 100 members were in the club . In order
for the program to execute in the main menu screen, it is assumed that a password
“Standard” must be entered to show authorization and authentication.
I also states the appropriate methods for different programming languages. The
methods used for the project can be applied with object oriented programming
Languages like java and C++. Pseudocode is useful within logical programming

languages like PROLOG. The pseudocode in Task 3b and Task 3c can be
implemented on Pascal, Java and C platforms.
It is believed that Unified Modeling Language (UML) will be most suitable for an
object-oriented programming language. The UML encourages the growth of the
Object-Oriented tool market.
TASK ONE of this project contains two reports. They are:

1. Report 1 displays a list of all the paid-up member names and contact number
by membership level, with totals for each level
2. Report 2 displays a list of players a of each of the four teams for the current
season with details of number of matches played for each teams (a player
may play for more than one team), tries scored, penalties scored and
conversions scored, with the players listed in alphabetical
What is need for both reports were analyzed using the JSP techniques and
methodology. These reports were produced using the Logical Data Structure
Diagrams (DSD) and Program Structure Diagrams (PSD) showing the logical top-
down stepwise progression involved. Detailed program specification reports were
also produced for each report.
TASK TWO is composed of the flowchart for the two reports specified in Task 1.
TASK THREE, a procedure for checking for paid-up members to allow members to
into meetings which is done by the club secretary. Pseudocode for both reports was
also produced for Task 1. Ignoring the options of the reports, pseudocode for the
reports main menu were produced and a code written to navigate the menu.
TASK FOUR has the test plans, test checks and dry runs for the pseudocode in Task
3b.
In TASK FIVE, using the UML modeling technique, a high-level class diagram
(Domain analysis) for the system was produced. A set of USE CASE diagrams that
showed actors and stereotyped dependencies were produced. All the given

scenarios (Checking member details, renewing the annual subscription of a member,
deleting a member from the database and printing a report) in the program had USE
CASE diagrams set produced. SEQUENCE diagrams and COLLABORATION
diagrams for the given scenarios was produced.
BIBLIOGRAPHY
Programming Methods, NCC(2007) International Diploma in Computer Studies 2008

version 1.1 NCC Education limited, UK.

Marker's Comments:: Programming Methods

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Marker's Comments:: Programming Methods

Hochgeladen von

Copyright:

Verfügbare Formate

Award: International Diploma in Computer Studies

Module Title: PROGRAMMING METHODS

Assignment Title : Rugby Union Club

Examination Cycle: September 2009

Candidate Name: CHRIS OSEI MIREKU

Submission Date: 6TH AUGUST 2009

PROGRAMMING METHODS Page 1

Program/Qualification name: International Diploma in Computer Studies

Student ID/Registration number:

Name: CHRIS OSEI MIREKU

Centre Name: LABONE IPMC

Module Name: STRUCTURED PROGRAMING METHODS

Module Leader: MR. NKANSAH

Due Date:6TH AUGUST 2009

Submitted Date: 6TH AUGUST 2009

PROGRAMMING METHODS Page 2

Adult level Non-member level

PROGRAMMING METHODS Page 4

Paid up Members report

Header Report body Footer

PROGRAMMING METHODS Page 5

Header Report body Footer

PROGRAMMING METHODS Page 6

Paid up Members report

Header Report body Footer

Adult record Junior record Non-players

Name Contact Name Contact

PROGRAMMING METHODS Page 7

Section 1.2 Program structure data

Paid up members report

Initialisation Processing Termination

PROGRAMMING METHODS Page 8

Paid up members report

Initialisation Processing Termination

PROGRAMMING METHODS Page 9

Paid up members report

Close all files Print file heading

level=Adult level= junior level=non-playing

PROGRAMMING METHODS Page 10

Section 1.3 Program specification

CLIENT NAME: CLUB SECRETARY

THE PROGRAMME PRODUCES A REPORT BASED ON LIST OF

DUE DATE: 21ST MAY 2009

PROGRAMMER: CHRIS OSEI MIREKU

HOW THE PROGRAMME WORKS

PROGRAMMING METHODS Page 11

PLAYERS MATHCH DETAILS

Name Team Matches Tries Penalties Conversions

1st 2nd Junior Junior

PROGRAMMING METHODS Page 12

Header Player body Footer

PROGRAMMING METHODS Page 13

Header Report body Footer

PROGRAMMING METHODS Page 14

Header Player body Footer

Name Teams Matches Tries scored Penalties

PROGRAMMING METHODS Page 15

Header Player body Footer

Name Teams Matches Tries scored Penalties

1st Team 2nd Team Junior 1st Junior 2nd

PROGRAMMING METHODS Page 16

Initialisation Processes Termination