Java Script Days to GO
Goals and Topics
The assignment problem is straightforward. All necessary details have been supplied. The solution of the problem will be straight line code which will use the programming concepts and strategies covered in Workshops 1-3. The subgoals are:
- Understanding values, variables and constants, Objects, Operations, and Functions
- Translating simple design into JavaScript code
- The mechanics of editing, interpreting, building and running your program
- Testing your program
- Commenting your source code
- Becoming condent and comfortable with programming in small problems
Your Task
Days-to-Go" is an interesting and useful feature in website design. It shows up the remaining number of days (or even with hours, minutes, and seconds) towards an event. For example, at anytime you visit the ocial website of Rio 2016 Olympic Game1, you will see such a feature
showing the number of days, hours, minutes and seconds towards the starting date of Rio 2016. In this assignment, you are going to write a JavaScript program to implement the \Days-To-Go" feature.
The Concept of Time in JavaScript
In JavaScript a time is dened as a Date Object. Each date object stores its state as a time value, which is a primitive number that encodes a date as milliseconds since 1 January 1970 00:00:00 UTC.
Thus, a date later than 1 January 1970 00:00:00 UTC will have a positive time value, whereas an earlier date will have a negative time value. On the basis of the common timeline (which we all live on), the distance between any two dates can be calculated using their time values in milliseconds.
Figure 1 illustrates the concept, where C is a date earlier than 1 January 1970 00:00:00 UTC, and A and B are later with B being further than A. CSC1401 Assignment 1 Specication { Days-To-Go 2
Figure 1: The Dierence Between Two Date Instances Functional Requirements Constants and Variables Within the script section, create constants and variables following professional conventions and initialise them using right values. Some constants and variables have been suggested in the following tables. You should create more when necessary.
Table 1: Constants
Description Value
Number of milliseconds in a day 1000*60*60*24
Number of milliseconds in an hour 1000*60*60
Number of milliseconds in a minute 1000*60
Number of milliseconds in a second 1000
Table 2: Variables
Description Initialising value description Type
Name of the event The name of Rio 2016 Olympic Game String
Year of the event The year of Rio 2016 Olympic Game Number
Month of the event The month of Rio 2016 Olympic Game Number
Day of the event The day of Rio 2016 Olympic Game Number
Calculation
1. Create a Date object for the date of the event by using the variables created previously. Send the object constructor the variables (not values) for year, month, and day of the event; Mind the order of arguments sent to the constructor;
2. Create a Date object for the current time. No arguments need to be supplied to the constructor.
3. Calculate the dierence between the current time and the event time: CSC1401 Assignment 1 Specication { Days-To-Go 3 Use the getTime() member function to get a Date object's time value in milliseconds Deduct the time value of current time by using the value of event time.
4. Calculate the number of days to the event: Divide the time value dierence by the number of milliseconds in a day. Use the Math.
oor() function to reduce the result number to an integer.
5. Calculate the number of hours, minutes, and seconds in the remaining time value:
(a) Mod the time value dierence by the number of milliseconds in a day;
(b) Divide the mod result by the number of milliseconds in an hour;
(c) Use the Math.
oor() function to reduce the number to an integer for the number of
hours;
(d) Repeat Steps (a) to (c) to calculate the number of minutes and seconds. You may need
to update the calculating formula accordingly.
Presentation
Figure 2: Illustration of the Output
Figure 2 shows a sample output when running the \Days- To-Go" program. Note that
- the information should be displayed using the alert() function;
- wherever possible you should use variables in expres- sions instead of explicit values (e.g., literals and num- bers), for example, using the variable created for the event name instead of a string value of \RIO 2016";
- the layout of output may vary depending on web browsers. Testing Test your program by comparing its calculating results to the Days-To-Go feature on the ocial
Such a dierence is not an error and is acceptable.
Non-functional Requirements
Structure of the Source Code
- All code should appear in the script section in the head of the HTML document. CSC1401 Assignment 1 Specication { Days-To-Go 4
- Do not write any code in the HTML body. All functionality are delivered by JavaScript.
- In the script order your code as follows:
(a) Constants;
(b) Variables and objects (declared and initialised);
(c) Other statements.
Comments
- You are required to add at least three comments to the source code.
- Do not comment every single line, instead, comment on blocks of code with a common purpose.
- Do not simply translate the syntax into English for comments, instead, describe the purpose of blocks of code. Submission What You Need to Submit { Two Files For a complete submission you need to submit two les as specied below. You can submit them individually or compress them and submit a common .zip (or .rar) le. The assignment submission system will accept only the les with extensions specied in this section.
1. Statement of Completeness in a le saved in .doc, .docx, .odt, .rtf or .txt format in 200-300 of your own words describes:
- The state of your assignment, such as, any known functionality that has not been implemented, etc. (It is expected that most people will implement all of the functionality of this assignment.)
- Problems encountered, such as, any problems that you encountered during the as- signment work and how you dealt with them;
- Re ection, such as, any lessons learnt in doing the assignment and suggestions to future
programming work.
2. The program in a le saved with an .html extension contains the source code implemented following the functional and non-functional requirements.
Late Submission and Extension Request
Please refer to USQ Policy Library - Assessment Procedure for information on the late submission policy and USQ Policy Library - Assessment of Compassionate and Compelling Circumstances Procedure for considerable special circumstances in extension request.
The Extension Request Form is available on the course's StudyDesk. Should you need to request an extension please ll the form and email it to the Course Examiner with supportive documents
(e.g., medical certicate or endorsement letter from supervisor in workplace) prior to the due date . Please note that any requests without supportive documents will be declined
straigthway without consideration.