Description
Aim
The objectives of this assignment includes: • Learning about procedural programming, control structures, arrays, dynamic memory allocation and handling input/output
• Apply the concepts learnt by developing a Weather Information Processing System
Background
Your software company, Virtual Solutions, has just won a $1m contract to design a build a prototype Weather Information Processing System (WIPS).
For this assignment, you take on the role of a software architect. You are supplied with sample input weather data (kindly provided by the meteorological station), and you need to develop a program that does the following:
1 ) read in and process a configuration file
2) display city map
3) display cloud coverage map (cloudiness index)
4) display cloud coverage map (I-MH symbols) 5) display atmospheric pressure map (pressure index)
6) display atmospheric pressure map (I-MH sym bols)
7) show weather forecast summary report
The program should be compiled as ‘csci251 al . exe’ and run in Ubuntu 14.04 (Linux OS). The next section describes the requirements for the program
Task Requirements
A) Upon startup, the program should prompt user to enter a ‘configuration’ filename. The program then proceeds to read the contents (of the entered filename) to further initialize its own program parameters / data structures. Please refer to Appendix A, which provides details on the configuration file and its usage.
B) The meteorological station has adopted a map-grid coordinate system upon which it overlays all other weather data. With regards to display city map option, please refer to Appendix B, which elaborates on this coordinate system, the unit representation, the relative positioning of different cities and its display requirements.
C) For the display requirements of cloud coverage (cloudiness index), AND cloud coverage (I-MH symbols) (i.e. options 3) & 4)), please refer to Appendix C, which will discuss about the interpretation of cloud cover input data, its subsequent processing algorithm and output format requirements.
D) For the display requirements of atmospheric pressure (pressure index) AND atmospheric pressure (I-MH symbols) (i.e. options 5) & 6)), please refer to Appendix D, which will discuss about the interpretation of pressure input data, its subsequent processing algorithm and output format requirements.
E) For the display requirements of weather forecast summary report, please refer to Appendix E, which will provide details about the kind of summarized weather data to be displayed, processing algorithm to compute the probability of rain and its graphical display form at.
F) Refer to Appendix F, for a description of the program’s main menu requirements
H) You are not allowed to declare your own C++ classes for this program, as this is a purely procedural (not Object Oriented) programming assignment!
Deliverables
1 ) The deliverables include the following:
b) A softcopy word document that elaborates on.
(Interpreted) requirements of the program
Diagram / Illustrations of program design
Summary of implementation of each module in your program
Reflections on program development (e.g. assumptions made, difficulties faced, what could have been done better, possible enhancements in future, what have you learnt, etc)
2) IMP T: Please follow closely, to the submission instructions in Appendix G, which contains details about what to subm it, file naming conventions, when to submit, where to subm it, etc.
3) The software demo / testing will be held during lab session where you are supposed to submit your assignment. Some time will be allocated for you to present / demonstrate your program’s capabilities during the session.
Grading
Student’s deliverable will be graded according to the following criteria:
Program fulfills all the basic requirements stipulated by the assignment
(ii) Successful demonstration of a working program, clarity of explanation / presentation and satisfactory answers provided during Q & A session.
(iii) Additional effort (e.g. enhancing the program with relevant features over and above task requirements, impressive, ‘killer’ presentation)
In the real working world, satisfactory completion of your tasks is no longer enough. The capability, efficiency and robustness of your system to operate under different testing conditions, and the ability to add value, communicate and/or demonstrate your ideas with clarity is just as important as correct functioning of your program. The grading criteria is set to imitate such requirements on a ‘smaller scale’
APPENDIX A
Processing Configuration File Info
Upon startup, program should prompt user for the following
Please enter config filename : config.txt
When user presses ‘Enter’, the program should perform File I/O to read in the contents in the stated filename (e.g. in this case ‘config.txt’)
The config.txt contains data like size of grid-map area (indicated by index-ranges), as well as a series of filenames, which your program should further access, in order to read in the various relevant weather data provided by the Meteorological Station. Figure A-I below provides a sample of the actual contents within this configuration file.
// The range of ‘horizontal’ indices, inclusive
// E.g. if the range is 0—4, then the indices are GridX IdxRange=0—8
// The range of ‘vertical’ indices, inclusive
// E.g. if the range is 0—3, then the indices are GridY IdxRange=0—8
// [x, y] grid—areas which are occupied by cities city location. txt
// “next day” forecasted cloud coverage ( ) for // each [x, y] grid—area cloudcover . txt
// “next day” forecasted atmospheric pressure // each [x, y] grid—area pressure . txt o,
o,
intensity 1 ,
1 , 2 , 3 , 4
2 , 3
) for
Fig. A-I
Note : The ranges for both ‘GridX IdxRange’ and ‘GridY IdxRange ‘ will determine the size of the display map. The ranges’ values are editable!
Regarding the interpretation of each input files’ data format, please refer to subsequent Appendices.
APPENDIX B
Map-Grid Coordinate System (used by Meteorological Station)
City Map Input Data & Output Requirements
Figure B-l below provides a sample of the actual contents within the input file (e.g. city location. txt), storing city-occupied grid areas.
[1 ,
[ 1 ,
[ 1 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 7 , 1] -3—Big
2 ] -3—Big
3 ] -3—Big
1 ] -3—Big
2] -3-Big
3] -3-Big
7 ] -2 —Mid
8 ] -2 —Mid
1] -3-Big
2] -3-Big
3] -3-Big
7 ] -2 —Mid
8 ] -2 —Mid
7 ] -1 —Small City
City
City
City
City
City
City
City
City
City
City
City
City
City
Fig. B-l
Student’s INPUT Clata (in graphical form)
[ Highlighted in Bright Yellow ] – Grid Area(s) occupied by each city
[ Highlighted in Light Yellow ] – Grid Area(s) surrounding each city
8 Mid-Cit
7 Mid-City Mid-City Small—Ci
6
5
4
3 3Big_City 3-
Elig_City 3Elig_City
2 Big_City
Big_City Big_City
o 2 3 4 5 6 7 8
To aid in the visualization and understanding of how the city location input data will look like, in a 2D graphical format, please refer to the figure B-2 below.
Each [x, y] read in from the input file (see earlier Fig. B-1) describes the indices ofthe LOWER LEFT corner of a grid area
I E.g. [3, 8] refers to the
Lower Left corner of this grid area
[0, 0] origin refers to the
Lower Left corner of this grid area
: The range of (horizontal) indices to be shown on the :
I map ranges from 0-8 I (inclusive)
This info is retrieved from
: the value stored in the configuration file (see Appendix A, Fig. A-I),
‘GridX IdxRange’
I The same treatment applies for the variable ‘GridY IdxRange’, for
I the range of vertical
: indices
Note :
Mid City
a) Bright Yellow grid areas indicate the ACTUAL Grid Area occupied by a particular city. For example, in the fig. B-2 above, the city named occupies the following grid areas : [2, 7], [2, 8], [3, 7], [3, 8]
I b) Light Yellow grid areas indicate the grid areas surrounding the perimeter of EACH city. For example, in fig. B-2 above, the city named Mid Cit ‘ has the following grid areas surrounding its perimeter : [1, 6], [1, 7], [1, 8], [2, 6], [3, 6],
The grid areas [1, 9], [2, 9], [3, 9], [4, 9] are not shown as they are BEYOND the upper limits of the vertical GridY IdxRange !
Processing requirements – Display City Map
Realistically, there is limited graphical display capabilities available when you are constrained to displaying output on Ubuntu shell’s terminal. Figure B-3 below illustrates the agtual_gjsp.lay formattinq requirements when user selects the “Display City Map” option from your program’s menu.
a) As discussed in earlier Appendix A, Fig. A-I the range values for variables ‘GridX IdxRange’ and ‘GridY IdxRange’ can vary.
This implies the size and shape of your map display can change as well (e.g. it is possible to have a large ‘rectangular’ shaped grid-area map! ).
Therefore, please do not assume / “hard code” any constant values for your array sizes to store your map data!
b) You must make use of basic C++ array, and dynamic memory allocation ( research on how to use ‘new’ ) to initialize the size of your arrays during program runtime, to store all relevant weather map data.
c) The type of the array (e.g. int, double, struct, etc) is up to you, and there is no restriction on how many arrays you think is necessary to store all the relevant weather data.
d) Before your program exit, you must deallocate all memory that was dynam ically allocated by you during runtime ( research on how to use ‘delete’ ). Failure to do so results in memory leak … and marks deduction!
APPENDIX C
(Cloud Cover Input Data & Output Requirements)
Figure C-1 below provides a sample of the actual contents within the input file (e.g. cloudcover . txt), storing the cloud cover input data, for each grid area in the map.
Fig. C-la Fig. C-lb
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 0 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 2 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 ,
[ 3 , 0 ] -41
1 1 -93
2 ] -90
4 1 -70
5] -39
6] -47
7 1 -35
8 ] -83
0 ] -38
1 1 – 66
2 1 —45
31 -11
4 1 -53
5] -35
6] -8 8
7 1 -75
8 ] -21
0 ] -56
1 ] 81
3 ] 7 6
4 1 -53
6] 70
7 ] 38
8 ] 32
0 ] 8 6
1 ] -13
2 ] -23
3 ] 93
4] 68
5] 2 6
6] 53
7 1 -52
8 1 29
[4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
1 ] –
2 ] —43
3 ] -82
4 ] -4 0
5] -72
6] —48
7 ] -2 9
8 ] -75
0 ] -1 6
1 ] —49
2 ] -3 6
3 ] -53
4 ] -1 8
5] -47
6] -27
7 ] -98
8 ] -7 8
0 ] – 68
1 ] 63
2 ] 33
3 ] 92
4 ] -27
5] —48
6] -13
7 ] -15
8 ] 37
0 ] -47
1 ] 3
2 ] 8
3 ] -17
4 ] 62
5] 62
— 14
7 ] 35
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 , 7
1 ] -23
2 ] 63
4 ] 37
5] -1 8
7 ] 6
8 ] -1 8
: Interpretation of each line .
Data item #1 .
[x, y] the grid indices of the “lowerI left” corner of a grid area
: Delimiter char between data items #1 and #2
;4Data item #2 •
76 the “next day” forecast of cloud cover for the grid area.
: Max value : 99
: – means the grid area is forecasted to be entirely covered with thick clouds!
I Min value : 0
– means not a single wisp of cloud – “clear
: blue skies” for the grid area
Fig. c-lc
To aid in the visualization and understanding of how the cloud cover input data will look like, in a 2D graphical format, please refer to the figure C-2 below.
Student’s INPUT Data (in graphical form)
Forecasted Cloud Coverage (Z) for EACH Grid Area
83 21 32 75 78 37 84 11B
35 75 15 35
70 53 27 13 14 44
33 35 44 26 72 41B 62 la
70 53 53 40 la 62 37
24 11 76 33 53 24
30 45 34 23 43 36 33 63
33 al 13 43 63 23
41 56
Referring to the FIRST
I LINE shown in earlier Fig.
C-la, the grid area [0, 0]
: has a cloud cover value of 1 41, which is shown here.
Refering to the FIRST
I LINE shown in earlier Fig.
C-lb, the grid area [0, 4]
: has a cloud cover value of
1 76, which is shown here.
Fig. C-2
Note :
Mid_Cit
b) Bright Yellow grid areas indicate the ACTUAL Grid Area ccupied by a particular city. For example, in the fig. C-2 above, the city named occupies the following grid areas :
c) Light Yellow grid areas indicate the grid areas surrounding the perimeter of EACH city. For example, in fig. C-2 above, the city named ‘Mid_City’ has the following grid areas surrounding its perimeter : [1, 6], [1, 7], [1, 8], [2, 6], [3, 6], [4, 6], [4, 7], [4, 8]
The grid areas [1, 9], [2, 9], [3, 9], [4, 9] are not shown as they are BEYOND the upper limits of the vertical GridY IdxRange ! As a result, they are not included in the ACC computation (see below) as well …
d) For each city, the AVERAGE CLOUD COVER (ACC) value is derived, by the following :
‘Mid Cit
ACC = SUM (cloud cover values of city + surrounding grid areas) / Total # of grid areas For example, for the city named
ACC +32+ 52+ 29) + (88 +75 + 21 + 70 +53 + 48 + 29+ 75) 12
= 50.83
Processing requirements – display cloud coverage map (cloudiness index)
Figure C-3 below illustrates the actual display formattinq requirements when user selects the “Display Cloud Coverage Map (cloudiness index)” option from your program’s menu.
vrnw ubuntu@vmwubuntu: -/TEMP/CSC1251/Assn1
Note :
8 8 2 3 2 7 7 3 8
7 3 7 3 5 2 9 1 3 All the cloud cover input
6 4 8 7 5 4 2 1 1 4 values (shown in Fig. C-2)
5 3 3 4 2 7 4 4 6 has been reduced to a
4 7 5 5 6 4 1 2 6 3 SINGLE-DIGIT
3 2 1 7 9 8 5 9 1 2 “cloudiness index” value 2 9 4 3 2 4 3 3 6 ranging from 0 to 9!
6 8 1 6 4 6 o 2
O 4 3 5 8 7 1 6 4 (ii)
Refer to Fig. C-2, the o 1 2 3 4 5 6 7 8 origin grid area [0, 0] previously have a value of
vmw ubuntu@vmwubuntu : /TEMP/CSC1251/Assn1$ I transformed into a singledigit “cloudiness index”
Fig. C-3 4 value = 4 !!!
a) To generate the cloudiness index values for each grid area, all original cloud cover input values (for each grid area shown in fig. C-2) should be processed as follows:
For each grid area [x, y], if original cloud cover value falls within the range Then the corresponding
“cloudiness index” value is
1 value 10
2 10 value 20 1
3 value 30 2
4 value 40 3
5 value 50 4
6 value 60 5
7 value 70 6
8 value 80 7
9 value 90 8
10 value 100 9
Processing requirements – display cloud coverage map (I-MH sym bols)
Figure C-4 below illustrates the actual display formattinq requirements when user selects the “Display Cloud Coverage Map (I-MH symbols)” option from your program’s menu.
a) To generate the I-MH cloudiness symbol values for each grid area, all original cloud cover input values (for each grid area shown in fig. C-2) should be processed as follows:
For each grid area [x, y], if original cloud cover value falls within the range Then the corresponding
“cloudiness symbol” value is
1 value 35 L (Low)
2 value 65 M (Mid)
3 value 100 H (High)
APPENDIX D
(Atmospheric Pressure Input Data & Output Requirements)
Figure D-1 below provides a sample of the actual contents within the input file (e.g. pressure . txt), storing the atmospheric pressure input data, for each grid area in the map.
Fig. D-la Fig. D-lb
[ 0,
[ 0,
[ 0,
[ 0,
[ 0,
[ 0,
[ 0,
[ 0,
[ 0,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[ 1 ,
[2 ,
[2 ,
[2 ,
[2 ,
[2 ,
[2 ,
[2 ,
[2 ,
[2 ,
[ 3,
[ 3,
[ 3,
[ 3,
[ 3,
[ 3,
[ 3,
[ 3,
[ 3 , 0 ] -36
1 1 -32
2 ] -38
5] -62
6] -56
7 ] -41
8 ] -56
1 1 -65
2 ] -27
3 ] -27
4 1 -85
5] -83
7 1 -38
8 ] -82
0 ] -72
1 ] -42
2 1 -17
3 ] -15
4] 79
5] -11
6] -10
7 ] -47
8 ] 39
0 ] -53
1 ] 8 6
2 ] 33
3 ] -13
4] -15
5] -59
6] -1 6
7 ] 39
81 38
[4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 4 ,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 5,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 6,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
[ 7 ,
0] -15
1 ] –
2 ] -58
4 ] -47
5] -78
6] -68
7 ] -69
8 ] -25
0 ] -52
1 ] -36
2 ] -35
3 ] -40
4 ] -65
5] -40
6] -83
7 ] -50
8 ] -23
0 ] -27
1 ] -59
2 ] -42
3 ] -42
4 ] 63
5] -51
7 ] 90
8 ] 83
0 ] 36
1 ] -53
2 ] 63
3 ] 77
4 ] 78
5] -50
6] 8 6
81 33
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 ,
[ 8 , 0 ] -70
1 ] 32
2 ] 71
3] -18
4 ] -29
5] 73
6] -40
7 ] 80
8 ] -78
Fig. D-lc
To aid in the visualization and understanding of how the atmospheric pressure input data will look like, in a 2D graphical format, please refer to the figure D-2 below.
Light Yellow grid areas indicate the grid areas surrounding the perimeter of EACH city. For example, in fig. D-2 above, the city named ‘Mid Cit ‘ has the following grid areas surrounding its perimeter : [1, 6], [1, 7], [1, 8], [2, 6], [3, 6], [4, 6], [4, 7], [4, 8]
The grid areas [1, 9], [2, 9], [3, 9], [4, 9] are not shown as they are BEYOND the upper limits of the vertical GridY IdxRange ! As a result, they are not included in the AP computation (see below) as well …
For each city, the AVERAGE PRESSURE (AP) value is derived, by the following :
‘Mid_City
= SUM (pressure values of cit + surrounding grid areas) / Total # of grid areas For example, for the city named
AP = ( (47 + 39 + 39 + 38) + (6 + 38 + 82 + 10+ 16 + 68 + 69 + 25) ) / 12 = 39.75
Processing requirements – display atmospheric pressure map (pressure index)
Figure D-3 below illustrates the actual display formattinq requirements when user selects the “Display Atmospheric Pressure Map (pressure index)” option from your program’s menu.
a) To generate the pressure index values for each grid area, all original atmospheric pressure input values (for each grid area shown in fig. D-2) should be processed as follows:
For each grid area [x, y], if original pressure value falls within the range Then the corresponding “pressure index” value is
1 value 10
2 10 value 20 1
3 value 30 2
4 value 40 3
5 value 50 4
6 value 60 5
7 value 70 6
8 value 80 7
9 value 90 8
10 value 100 9
Processing requirements – display atmospheric pressure map (I-MH symbols)
Figure D-4 below illustrates the actual display formattinq requirements when user selects the ” Display Atmospheric Pressure Map (I-MH symbols)” option from your program’s menu.
a) To generate the I-MH pressure symbol values for each grid area, all original atmospheric pressure input values (for each grid area shown in fig. D-2) should be processed as follows:
For each grid area [x, y], if original pressure value falls within the range Then the corresponding “pressure symbol” value is
1 value 35 L (Low)
2 value 65 M (Mid)
3 value 100 H (High)
APPENDIX E
(Weather Forecast Summary Report)
Figure E-l below illustrates the actual display requirements when user selects the “Show Weather Forecast Summary Report” option from your program’s menu.
Referring to Appendix B, Fig B-1, described in the sample input file citylocation. txt), display the city’s name, id, ACC, AP, Probability of Rain and its corresponding ASCII graphics!
: Weather Forecast Summary
City Name Big City Report Note :
city ID 3 For Ave. Cloud Cover (ACC)
Ave. Cloud Cover (ACC) 56 . 60 (M) I computation, please refer to Note: part
Ave. Pressure 43 . 60 (M) c) section (below Fig. C-2) in
Probability of Rain ( % 50 . 00 Appendix C
(ii)
For Ave. Pressure (AP) computation, please refer to Note: part c) section
City Name : Mid City city ID 2 (below Fig. D-2) in Appendix D
Ave. Cloud Cover (ACC) 50 . 83 I (iii)
Ave. Pressure 39 . 75 The L/M/H symbol for ACC is
: Probability of Rain ( % 50 . 00 computed based on table (below Fig. C-4) in Appendix C
(iv)
City Name Small City The L/M/H symbol for AP is computed based on table (below Fig.
city ID 1
Ave. Cloud Cover (ACC) 29 . 56 I D-4) in Appendix D
Ave. Pressure 57 . 67 (M)
: Probability of Rain ( % 40 . 00
Fig. E-l
Determ ination of Probability of Rain ( 0/0) value
With reference to earlier fig. E-1, for each city, note down their L/M/H symbols for ACC and AP respectively. Based on the combination of ACC and AP symbols, lookup the respective Probability of Rain ( 0/0) value from the table below.
City’s forecasted Estd.
Probability of Rain ( 0/0) Associated ASCII graphics (to be displayed)
Ave.
Pressure
(AP) value Ave. Cloud
Cover (ACC) value
90
80
70
60
50
40
30
20
10
Note : Air will always flow from areas of High pressure, to areas of Low pressure, and this is manifested as ‘Wind”. If the city is forecasted to have Low pressure, then wind (bringing along additional clouds & moisture), is predicted to flow into that city on the next day!
APPENDIX F
(Main Menu Requirements)
Student ID : 1234567
Student Name : Tan Ah Meng Elvis
Welcome to Weather Information Processing System!
1) Read in and process a configuration file
2) Display city map
3) Display cloud coverage map (cloudiness index)
4) Display cloud coverage map (I-MH symbols)
5) Display atmospheñc pressure map (pressure index)
6) Display atmospheric pressure map (I-MH symbols)
7) Show neather forecast summary report
8) Quit
Please enter your choice : 1
[ Read in and process a configuration file ] Please enter config filename : config.txt
Reading in GridX_/dxRange : 0-8 … done! Reading in GridY_/dxRange : 0-8 … done!
Storing data from input file citylocation.txt … done! cloudcover.txt … done! pressure.txt … done!
All records successfully stored. GoRg back to main menu
Student ID : 1234567
Student Name : Tan Ah Meng Elvis
Welcome to Weather Information Processing System!
1) Read in and process a configuration file
Impt !! Please include your:
1. (JOW Student ID
2. Student Name
every time you display your Main Menu. Marks will be deducted if the required info is not shown.
Note : if user selects option .
2) Display City Map as described by Appendix B, Fig. B-3
3) Display Cloud Coverage Map (cloudiness index) as described by Appendix C, Fig. C-3
4) Display Cloud Coverage Map (I-MH symbols) as described by Appendix C, Fig. C-4 5) Display Atmospheric Pressure Map (pressure index) as described by Appendix D, Fig. D-3
6) Display Atmospheric Pressure Map (I-MH symbols) as described by Appendix D, Fig. D-3
7) Show Weather Forecast Summary Report as described by Appendix E, Fig. E-l
Press <enteÞ to go back to main menu .
For options 2) to 7), always prompt user ” so that when user is done viewing the output, he can hit <enter> to continue
APPENDIX G
Submission Instructions (V. IMPT!!)
1) Deliverables
a) All submissions should be in softcopy, unless otherwise instructed
b) For the actual files to be subm itted, you typically need to include the following:
word document report (e.g. *.doc), save as MS Word 97-2003 format the source file(s), (e.g. *.h, *.0, or *.cpp files)
the executable file, (using Ubuntu g++ compiler), compile into an executable filename with *.exe (e.g. csci251 al exe)
2) How to package
Compress all your assignment files into a single zip file. Please use the following nam ing format .
Example . FT TutGrp3 Al 1234567 JohnDoeAnderson.zip
< FTI Use for Full-Time student if you are Part-Time student
<Your Grp refers to your SIM tutorial group (e.g. TutGrp1 / TutGrp2 / TutGrp3 /
Al if you are submitting assignment 1, A2 if subm itting assignment 2 etc.
<Stud. No.> refers to your I-JOW student number (e.g. 1234567)
<Name> refers to your I-JOW registered name (e.g. JohnDoeAnderson)
3) Where to submit
Please submit your assignment via Moodle el-earning site.
IMPORTANT NOTE :
To minimize the chances of encountering UNFORSEEN SITUATIONS (mentioned below), please do an EARLY SUBMISSION via Moodle.
In the event of UNFORSEEN SITUATIONS :
[email protected] for FULL TIME students [email protected] for PART TIME students
In your email subject line, type in the following information
<FTIPT> <Your Grp <assignment inf0> <student number> and Fname>
Subject
Note 1 :
Note 2 : FT TutGrp3 Al 1234567 JohnDoeAnderson
After email submission, your mailbox’s sent folder would have a
Example:
4) When to submit
a) Depending on the time-table, a software demo / testinq / presentation for your assignment will be scheduled during the:
3rd – 5th lab session for the semester (i.e. lab 3 – 5), for Full Time ( ) students
2 nd – 4th lab session for the semester (i.e. lab 2 – 4), for Part Time (P T) students
b) Please refer to the following table on the different deliverables, subm ission events & deadlines
(check Moodle for
Testing (test cases), during … Email Test Case Result files by :
1 Lab 2 Lab 3 Lab 2(PT), Lab 3(FD End of Lab 2(PT), Lab 3(FT)
2 Lab 3 Lab 4 Lab 3(PT), Lab 4(FT) End of Lab 3(PD, Lab 4(FD
3 Lab 4 Lab 5 Lab 4(PD, Lab 5(FD End of Lab 4(PT), Lab 5(F1)
5) Please help by paying attention to the following .
! VERY IMPORTANT !
PLEASE FOLLOW ALL THE GUIDELINES / REQUIREMENTS IN ALL ASSIGNMENT APPENDICES
PLEASE FOLLOW ALL THE SUBMISSION INSTRUCTIONS FROM 1 TO 4
IF YOU ARE NOT SURE
OR
MARKS WILL BE DEDUCTED IF YOU FAIL TO FOLLOW INSTRUCTIONS
Examples of marks deduction
Your deliverables / zip file does not follow nam ing convention
You have no email subject / or do not following naming convention
Wrong nam ing or misleading information given
(e.g. putting “A2” in email subject, when you are submitting “Al “)
(e.g. naming “Al ” in your zip file, but inside contains A2 files )
Your submission cannot be downloaded and unzipped
Your program cannot be re-compiled and/or executable file cannot run Your report / testing files cannot be opened by Microsoft Word / Excel 2003 You did not submit / incomplete subm ission of software demo / testing files etc
6) Re-submission administration
<Step 1> Prepare 2 zip files as follows
Zip up for re-subm ission, proqram files according to the following format
Resubmit <Your Grp Al <Stud. No.> <Name>.zip
Example : Resubmit FT TutGrp3 Al 1234567 JohnDoeAnderson.zip
Zip up for re-subm ission, test case results files according to the following format
Resubmit <Your Grp Al TCResults <Stud. No.> <Name>.zip
Example : Resubmit FT TutGrp3 Al TCResuIts_1234567 JohnDoeAnderson.zip
< FTIPT> Use for Full-Time student if you are Part-Time student < Your Grp refers to your SIM tutorial group (e.g. TutGrp1 / TutGrp2 / TutGrp3 / etc.)
Al if you are submitting assignment 1, A2 if subm itting assignment 2 etc.
<Stud. No.> refers to your I-JOW student number (e.g. 1234567)
<Name> refers to your I-JOW registered name (e.g. JohnDoeAnderson)
< Step 2>
In your email subject line, type in the following information
Subject Resubmit FT TutGrp3 Al 1234567 JohnDoeAnderson
Resubmit <FTIPT> <Your Grp <assignment inf0> <student number> and
Example:
IMPORTANT NOTE
Non-subm ission of any of the above mentioned files, or failure to adhere to submission instructions will result in ZERO marks!
