Assessment T-1.8.1 Details of Assessment Term and Year Time allowed N/A Assessment No 1 of 2 Assessment Weighting 50% Assessment Type Written, Project Due Date Week 8 Room Details of Subject...

Assessment
T-1.8.1
    Details of Assessment
    Term and Yea
    
    Time allowed
    N/A
    Assessment No
    1 of 2
    Assessment Weighting
    50%
    Assessment Type
    Written, Project
    Due Date
    Week 8
    Room
    
    Details of Subject
    Qualification
    ICT40115Certificate IV in Information Technology
    Subject Name
    Object Oriented Programming I
    Details of Unit(s) of competency
    Unit Code
    ICTPRG406 Apply introductory object-oriented language skills
    Details of Student
    Student Name
    
    College
    
    Student ID
    
    Student Declaration: I declare that the work submitted is my own, and has not been copied or plagiarised from any person or source.
    Signature: ___________________________
Date: _______/________/_______________
    Details of Assesso
    Assessor’s Name
    
    Assessment Outcome
    Results
    
XXXXXXXXXXCompetent XXXXXXXXXXNot Yet Competent
    
     /50
    FEEDBACK TO STUDENT
Progressive feedback to students, identifying gaps in competency and comments on positive improvements:
    ________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
    Student Declaration: I declare that I have been assessed in this unit, and I have been advised of my result. I also am aware of my appeal rights and reassessment procedure.
Signature:     ____________________________
Date:     ____/_____/_____
    Assessor Declaration: I declare that I have conducted a fair, valid, reliable and flexible assessment with this student, and I have provided appropriate feedback
Student did not attend the feedback session.
XXXXXXXXXXFeedback provided on assessment.
Signature:     ____________________________
Date:     ____/_____/_____
    Purpose of the Assessment
    The purpose of this assessment is to assess the student in the following learning outcomes:
    Competent
(C)
    Not Yet Competent
(NYC)
    Performance Criteria for Competency Code ICTPRG406
    1.2 Select and use language data types, operators and expressions, in order to create clear and concise code
    
    
    3.1 Use the language debugging facilities of an integrated development environment (IDE)
    
    
    3.2 Interpret the compiler or interpreter messages to resolve syntax e
ors, and use debugging techniques to resolve logic e
ors
    
    
    4.1 Follow organisational guidelines for developing maintainable code, and adhere to the provided coding standards, when documenting activities
    
    
    4.2 Apply internal documentation to all the code created, and use the documentation tools available in the target language, when documenting activities
    
    
    5.1 Create and conduct simple tests, to confirm that the code meets the design specification
    
    
    5.2 Document the tests performed and the results achieved
    
    
    6.1 Develop a solution, when provided with a basic object-oriented design document
    
    
    6.2 Refer to the appropriate documentation for the language
    
    
    Assessment/evidence gathering conditions
    Each assessment component is recorded as either Competent (C) or Not Yet Competent (NYC). A student can only achieve competence when all assessment components listed under “Purpose of the assessment” section are recorded as competent. Your trainer will give you feedback after the completion of each assessment. A student who is assessed as NYC (Not Yet Competent) is eligible for re-assessment.
    Resources required for this assessment
    1. Computer with relevant software applications and access to internet
1. Weekly eLearning notes relevant to the tasks/questions
    Instructions for Students
    Please read the following instructions carefully
· This assessment has to be completed |X| In class |X| At home
· The assessment is to be completed according to the instructions given by your assessor.
· Feedback on each task will be provided to enable you to determine how your work could be improved. You will be provided with feedback on your work within two weeks of the assessment due date. All other feedback will be provided by the end of the term.
· Should you not answer the questions co
ectly, you will be given feedback on the results and your gaps in knowledge. You will be given another opportunity to demonstrate your knowledge and skills to be deemed competent for this unit of competency.
· If you are not sure about any aspect of this assessment, please ask for clarification from your assessor.
· Please refer to the College re-assessment for more information (Student handbook).
    Assessment - Marking Sheet
    Marking List
    Marks
    Written/Practical
    Task 1
    /8
    Task 2
    /8
    Task 3
    /8
    Task 4
    /8
    Task 5
    /10
    Task 6
    /8
    TOTAL
    /50
    Assessment – Written/Practical
You need to provide evidence (use screenshots) to proof you have covered the following aspects:
Task 1. Take a screenshot of your code interface (with coding view in display), showing you are following the language syntax rules and best practices. Take another screenshot of the published webpage, namely index.php, with the web
owser address bar showing the published address. Since the recommended directory folder name contains your student ID, this will proof the published page is actually made by you.
(8 marks)
(
Screenshot showing the software interface of the PHP coding and authoring tool (i.e. Dreamweaver)
Displaying the area where you type and edit the coding inside the authoring tool
)
(
Page Content View.
Address bar of a published PHP page with your stuID in the directory.
)
Task 2. (
Screenshots and description of the steps you take to fix this e
or.
) (
Screenshot of a PHP page live view, with an e
or message saying there is e
or in the page, and the indication of the line number where the e
or is located.
)As you have experienced in the class exercise debugging, when you type something in e
or by mistake or have other kind of mistakes in PHP page coding, the PHP page when
owsed in the Internet
owser, will show the line number of which the e
or is most likely located. You need to take a screenshots of this e
or message. As a proof of your debugging process, you need to show through the screenshots and their description the steps you take to get that identified e
or fixed until the step that shows the e
or is gone.
(8 marks)
Task 3. (
Screenshots and description of the steps you take to fix this e
or.
Similar Task 2, only that for this task, in order fix the e
or, you
steps include that you
have checked the webpage where you find the co
ect
syntax of the PHP or SQL feature that are having problem.
)Describe by example how you based on the e
or message (normally with line number to where the e
or is located) solved the e
or (both syntax e
or, e.g. typing mistakes and logical e
or, e.g. mistakes in control structure if, else if), there need to be descriptions and screenshots of the steps for the evidence.
(Note: for the debugging, please refer to the resource of PHP syntax from http:
www.w3schools.com/php/ or http:
php.net/manual/en/ with the former being possibly easier and quicker to retrieve.)
(8 marks)
Task 4. Programming documentation (inline comment): You need to provide the evidence (screenshots) that you have use two types of programming comments define as follows:
(8 marks, 2 marks each for the following 4 sub tasks.)
a. (
Screensho
t
showing the use of
!-- --> commenting in HTML coding.
)Project Description comment for project team/organization use. (What the project is about; version; date started; team member of the project – in this case just you; a list of
ief summary of daily changes and/or achievement. This is at the beginning of index.php page. Notice if the comment is inside HTML, it is . If it is inside PHP, it is /* */ or
(
Screensho
t
showing the use of
* */
commenting in PHP coding.
)
(
Screensho
t
showing the use of

commenting in PHP coding.
)
. (
S
imilar s
creensho
ts
of
* */ and

commenting in PHP coding. Only these type of comments normally appears inside the code, whereas the project description comment appears at the beginning of the code page.
)Coding notation comment: These are comments helping you or other team members to understand what each parts of the coding are programmed for. These comments are normally are scattered everywhere in all pages.
c. Please create a “php coding guidelines and coding standard checklist” in a table below.
d. (
S
imilar s
creensho
ts
of
* */ and

commenting to a, and b.
Only in here the comments are made by you. Whereas in a and b, the comments are from the sample pages made by programmers.
)Take a screenshot of both comment types you made.
Task 5. Make a testing checklist document in word file for a PHP project. There must be 3 categories of items to check – design, authoring, and delivery. For each categories you must come up with no less than 5 items. The first group for checking – the design group is to check if the features that you plan to design are all covered by all the pages you developed; The authoring group is to check if those pages are co
ectly coded; and finally the delivery group is to check if those pages run co
ectly in live view.
(10 marks)
(Note: the recommended targeting project for testing is task 2 in your assessment. Therefore, you can do a tentative testing check based on that programming task. When you are phrasing your testing items you can be as specific as down to the tasks and requirements of that programming task. e.g. In the authoring group, you can list something like “Is the coding indentation/nesting being strictly followed per the programming routine, in both index.php and page2.php, etc.”. You can also do a search and study from the eLearning resource or an online PHP resource, for a coding test plan template, and find and summarise the testing procedure and routine in PHP coding. Which will all help you to draft your own list in the test table.)
Task 6. The referencing in programming: Let’s presume you are coding a PHP page, when suddenly you cannot remember how to do the PHP function for number_format to make the number XXXXXXXXXXto round up as XXXXXXXXXXYou then go to w3school.com/php doing a number_function search on the top right side of the page. You will need to find out the webpage where it shows to syntax definition for the function; and based on the example in that page you can co
ectly write the syntax. Please use less than 5 screenshots to document the steps on how you do all this co
ectly, with the last screenshot showing the number is co
ect rounded up to XXXXXXXXXX.
(8 marks)
    Submission
Put all of your submission inside a folder called “oopI_(studentID)_(firstname)_1”, make it into a zip file (not rar file). Email it to the submission email according to the