need coding for this assignment
as soon as possible
The University of the South Pacific
Faculty of Science, Technology, and Environment
School of Computing, Information and Mathematical Sciences
IS122 Information Systems II
Assignment 1 Semester 2, 2016
Weight: 15% Due Date: Sunday, 28th August, 2016; 5 PM (Fiji Time)
The World Olympic Committee (WOC) together with the Pacific Island Football Association
(PIFA) has decided to embark on a project to automate their score board keeping for soccer
tournament results. This program would be tested and used in the current Olympic Soccer
tournament and then later could be used in the major soccer tournaments around the pacific
island countries. The WOC has hired you and has provided you with the following information
about the current Olympic soccer tournament rules and how results are maintained manually at
Your program will record scores from each game in the tournament and calculate which two
teams qualify for the finals.
In each game, the winning team receives 3 points and the losing team 0 points. If teams draw,
they each receive 1 point. Each team?s cumulative goal differential (goals scored ? goals
allowed) is also recorded.
The two teams with the highest number of points qualify for the finals. If two teams have an
equal number of points, ties are resolved by seeing which team has the highest goal differential.
(If two teams have equal points and an equal goal differential, your program can choose either.)
Specific program requirements: There are only four teams participating ? Fiji, Samoa, Tonga and Vanuatu.
You do not have to manage which teams play against each other in which game. For
example, you can allow 3 games of Fiji vs. Tonga to be entered.
You do have to check that no game involves a team playing itself (Fiji vs. Fiji). The interface should have: Places to enter the names of the teams and their score against each other. (Your interface
should only have space for entering results from one game at a time.) You can design this in
either of the two ways described below.
A button to enter/submit the scores (results) of the game. When this button is pressed,
your program should clear the places where information about that game was entered. If
the information for a game is incomplete or incorrect (~like a team playing itself), your
program should warn the user in a message box and not save the scores.
A button to display the two finalists. Remember this button could be pressed any time to
display the two finalists. (Logically after results of at least one game is entered).
A place /or places to display the two finalists.
A button to exit your program. Game Entry interface options:
o Have text boxes for the names and scores where the user will type in the names of
the teams and their scores manually. In this case, only entries that match names of
teams participating in the tournament should be accepted.
Team A: Team A score: Team B: Team B score: Option2
o Have option buttons for team names and text boxes for the scores.
Vanuatu Team B: Fiji v/s
Samoa Tonga Vanuatu Score A: Score B: Example of tournament scoring:
E.g. 1: Score table after Fiji v/s Tonga match. Fiji won by 2 goals to 1.
0 If a team wins, it is awarded 3 points where as the losing team gets nothing. In this
case, 3 is added to Fiji?s total points and 1 win so far.
If teams draw then both are awarded 1 point each. (D = D + 1)
Goal difference (Diff) for a team is calculated as the existing GoalDiff(Diff) the team
already has, added to the number of goals the team scores (in the current game)
minus the number of goals allowed against itself in the game being entered. In this
case existing goal difference for Fiji is nil and it had scored 2 while allowing 1 against
itself. Hence 0+2-1 = 1 (Diff). For Tonga it would be 1 goal scored minus 2 scored
against it, (0+1-2= -1). E.g. 2: The above table after Tonga plays against Vanuatu. Tonga 3 Vanuatu 0.
o o Draw(D)
0 Points For Tonga:
o Win(W) = 3
o GoalDiff(Diff) = -1 + 3 ? 0 = 2
o GoalDiff(Diff) = 0+0-3 = -3 3
-3 E.g. 3: The above table after Tonga v/s Samoa. Both teams drew 2 all.
1. This is an individual assignment.
2. This assignment is to be done using Microsoft Visual Basic 2010 Express Edition.
3. How to Submit:
Archive or compress all your VB project files using archiving software such as Winzip or WinRAR.
Name your archive file using the following file naming convention: Assignment1_YourID, where
YourID is your student Id number e.g. Assignment1_S01234561. Make sure you include all the files
created by Visual Basic IDE into your archive. Then submit this archive file in Moodle Assignment 1
Drop box by 5pm Sunday 28th August (Fiji Standard Time). You cannot ?undo? your submissions in
Moodle, so be sure that you submit the assignment only when you?re totally satisfied. We will not
accept ?corrected versions? submitted through other channels, nor will we accept late assignments.
4. Partial Credit:
Even if your program doesn?t work perfectly, you?ll receive credit for each part you get to work.
For this and other work in IS 122, it?s essential that you avoid plagiarism. Not only do you expose
yourself to possibly serious disciplinary consequences, but you?ll also cheat yourself of a proper
understanding of the concepts emphasized in the project. You?ll almost certainly fail the midterm
and/or the final, which will test your understanding of the project. It?s not plagiarism to discuss the
assignment with your friends and consider solutions to the problems together. However, it is
plagiarism for you to copy all or part of each others? programs. How can you avoid plagiarism? Any
time you work on all or part of the program with someone else, you should rewrite whatever code
you come up with on your own without referring to any of the same materials. The best way to
avoid this is to rewrite the solution without looking at any of the notes you might have taken while
working together ? that way you?re guaranteed that your work will be original. Even if your program
doesn?t work perfectly, avoid the urge to copy someone else?s. We?ll give partial credit if it?s obvious
you worked hard on your own. Any student posting code for this project on Moodle will be
considered to be committing plagiarism. Don?t submit your code to any discussion group or mail it to
anyone except the lecturers or tutors.
Get started early, especially if you are doing several courses. By week 7 there will be many other
assessments and test due for other courses and it?ll be very hard to complete your project if it?s not
already finished. While you?ll have time in your lab section, it won?t be enough to complete this
assignment. Try to make sure you have the interface designed by your next lab session next week.
That way you can show it to your tutor and get feedback if you should change it.
7. Submitting late:
Your score will be penalized by 20% for each 12 hour period it?s late, starting Sunday, 28 August, 5
PM (FST). Remember, you?re submitting through Moodle, so we?ll know the exact time of your