Sunteți pe pagina 1din 4

International Diploma in Business E-Commerce

INTERNATIONAL DIPLOMA
IN
COMPUTER STUDIES

MODULE:
PROGRAMMING METHODS
ASSIGNMENT TITLE:
Rugby Union Club

SEPTEMBER 2009
Important Notes:
™ Please refer to the Assignment Presentation Requirements for advice on how to set out
your assignment. These can be found on the NCC Education Campus. Scroll down the left
hand side of the screen until you reach Personal Support. Click on this, and then on Policies
and Advice. You will find the Assignment Presentation Requirements under the Advice
section.
™ You must familiarise yourself with the NCC Education Academic Dishonesty and Plagiarism
Policy and ensure that you acknowledge all the sources which you use in your work. The
policy is available on Campus. Follow the instructions above, but click on Policies rather than
Advice.
™ You must complete the ‘Statement and Confirmation of Own Work’. The form is
available on the Policies section of Campus. Scroll down the left hand side until you reach
Personal Support. Click on this and then click on Policies and Advice.
™ Please make a note of the recommended word count. You could lose marks if you write
10% more or less than this.
™ You must submit a paper copy and digital copy (on disk or similarly acceptable medium).
Media containing viruses, or media which cannot be run directly, will result in a fail grade
being awarded for this module.
™ All electronic media will be checked for plagiarism.

Marker's comments:

Moderator's comments:

Mark: Moderated Final


Mark: Mark:

Programming Methods September 2009 Final ©NCC Education 2009


Introduction
The assignment allows the candidate to demonstrate the ability to use various modelling methods
and techniques when developing computer programs.

This assignment is based on the analysis and design of a computerised membership system for a
local rugby union club.

If you require some background information about rugby union please visit http://www.irb.com.

The Scenario
The membership details of all members of the rugby club are currently monitored using a manual
list. At club meetings the membership list is checked by the club secretary and no person may enter
the meeting who is not on the list. Members must pay an annual subscription which is at adult
player level, junior player level (under 16 years of age on 1 September of that season) or non-
playing level. Details of all player members are registered with the local rugby union to enable
them to play in matches. The information currently stored in the list includes the following:
• member name
• member number
• address
• contact telephone number
• membership level (adult/junior/non-playing)
• date of payment.

The membership list is also made available to the treasurer who monitors the membership and
subscriptions. The club runs four teams, 1st team, 2nd team, junior 1st team and junior 2nd team. The
coaches of each team also have access to the membership list so that they can select players for
matches against other clubs. The club secretary also records the number of matches played by each
member including team played for, tries scored, penalties scored and conversions scored by each
player. This information is recorded after each match played.

The club officials have requested that the membership system be computerised. The aim is to speed
up the production of regular monitoring reports on players and meet the local rugby union’s
requirements regarding player records and data protection.

Programming Methods September 2009 Final ©NCC Education 2009


Task 1 – 20 Marks
The club secretary would like the following reports on a regular basis:

Report 1 A list of all the paid-up member names and contact numbers by membership level,
with totals for each level.

Report 2 A list of players for each of the four 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.

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 (DSDs) and preliminary program structures (PSDs) as well as the detailed
program specification for each report.

Task 2 - 12 Marks
Draw a flowchart for each of the two reports specified in Task 1.

Task 3 – 20 Marks
a) Write a procedure that will check for paid-up members. 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 reports described 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 code to navigate the menu is required.

Task 4 – 6 Marks
Test the pseudocode written in Task 3b) by producing test plans, desks checks and dry runs.

Task 5 – 34 Marks
This task involves using the UML modelling technique.
a) Create a high-level class diagram (Domain analysis) for the membership system.
b) Carry out a high level use case analysis and produce a use case diagram that shows the actors
and any stereotyped dependencies.
c) Develop use case diagrams and use case specifications for each of the following scenarios:
• Checking member details.
• Renewing the annual subscription of a member.
• Deleting a member from the database.
• Printing a report.
d) Develop a sequence diagram for each of the scenarios described in 5c). Develop a collaboration
diagram for the scenarios described in 5c).

Programming Methods September 2009 Final ©NCC Education 2009


Task 6 – 8 Marks
In no more than 500 words, write a review of your work. Describe any assumptions you have made
and any changes you could introduce to improve your work. For the different methods and
techniques you have used in Tasks 1 - 5, discuss which would be most suitable for an object-
oriented programming language.

Guidance
Work through each task, making copies of the diagrams and code as you complete them. These will be
required in your submission. The diagrams should be produced using appropriate tools.

Take regular backups of your work. This will enable you to recover quickly should the system fail and also
allow you to backtrack if your development goes badly wrong.

Discuss your designs (giving the reasons for the choices you are making) with your tutor/lecturer, who may
give advice. Document your choices as you progress. Update all your documentation as changes are made.
Any refinement process should produce a series of improved designs.

For each task write a brief commentary on your design explaining why you have designed it this way, and
discuss possible alternatives.

Submission Requirements
A word-processed document of no more than 4000 words (+/- 10%) that contains the solutions to the six
tasks. Documentation should include DSDs, PSDs, pseudocode, flowcharts, test results, UML diagrams,
sample content and output, and the review.

Warning: All media must be virus free!


Media containing viruses, or media which cannot be run directly, will result in a FAIL grade being awarded
for this module.

You must read and understand NCC Education’s policy on ‘Academic Dishonesty and
Plagiarism’.
You must complete the ‘Statement and Confirmation of Own Work’ form and attach the
completed form to your assignment.

Programming Methods September 2009 Final ©NCC Education 2009

S-ar putea să vă placă și