assessment web view · 2017-12-14written, project. due date. week 8. room. details of...

T-1.8.1

Details of AssessmentTerm and Year Time allowed N/A

Assessment No 2 Assessment Weighting 50%Assessment Type Written, ProjectDue Date Week 8 Room

Details of SubjectQualification ICT50115 Diploma of Information Technology

Subject Name Object Oriented Programming II

Details of Unit(s) of competencyUnit Code ICTPRG527 Apply intermediate object-oriented language skills

Details of StudentStudent 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 AssessorAssessor’s Name

Assessment Outcome

Results Competent Not Yet Competent Marks /50

FEEDBACK TO STUDENTProgressive 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.

Feedback provided on assessment.

Signature: ____________________________

Date: ____/_____/_____

Object Oriented Programming II, Assessment 2,v4.0

T-1.8.1

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

1.1 Review the program requirements

1.2 Divide multiple source-code files into logical units and packages

1.3 Use at least two of the utilities of the target language, allowing for the internal storage of collections of data

1.4 Use the utilities of the target language, providing internal data-sorting and searching facilities

1.5 Employ integrated-development environment facilities, to make files to automate program building

1.6 Follow the guidelines for developing maintainable code, adhering to coding standards

1.7 Use the facilities in the language for persisting objects to binary files

1.8 Use the operator and function or method overloading facilities available in the language, at an introductory level

1.9 Use exception-handling techniques to ensure program stability

1.10 Use of a class that is based on multiple inheritances

2.1 Design and implement programs that connect to a database

2.2 Design and implement programs that use the language facilities to extract, update, and delete data stored in a database

2.3 Design and implement programs that use the language facilities to manipulate database structure (query, create and delete)

2.4 Write programs that deliver transactional integrity

3.1 Employ the graphical user interface (GUI) framework, or text windowing interface, appropriate to the chosen language


T-1.8.1

3.2 Use standard GUI components

3.3 Use the facilities within the language for GUI objects to respond to user and program-generated events

4.1 Use stand-alone debugging tools, or tools provided by the integrated development environment, to examine variables, and trace the running code

4.2 Use the debugger to detect logical and coding errors

4.3 Use the tracing of code and examination of variable contents during execution, to detect and correct errors

5.1 Design and document limited tests of code

5.2 Undertake limited testing of the produced code to ensure that it complies with the program specification

5.3 Capture and document the test results

6.1 Read and interpret the supplied design document, to create the code

6.2 Create and maintain program documentation

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

Computer with relevant software applications and access to internet

Weekly eLearning notes relevant to the tasks/questions

Instructions for Students

Please read the following instructions carefully This assessment has to be completed In class 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 correctly, 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).


T-1.8.1

Assessment marking and observation sheet for the trainers

Marking List Marks

PART A – Written Task (5 Marks)

Task Criteria 1 of 1 /5

SUB TOTAL /5

PART B – Assignment/Project (30 Marks)

Task Criteria 1 /4

Task Criteria 2 /4

Task Criteria 3 /4

Task Criteria 4 /4

Task Criteria 5 /4

Task Criteria 6 /4

Task Criteria 7 /3

Task Criteria 8 /3

SUB TOTAL /30

PART C – Written Task (15 Marks)

Task Criteria 1 /6

Task Criteria 2 /9

SUB TOTAL /15

TOTAL /50

Case Study

(Please refer to the Appendix.)

Note: the case is the same case or the continuation of the case of Object Oriented Programming I of Certificate IV (Please refer to the appendix). The major difference is a database are implemented so that the values of the webpages can be managed by the client through a user friendly GUI (Graphic User Interface). As well as the Web Design Company is to demonstrate more professional methods in project documentation and debugging/testing in project commencing.

Assessment – Written (5 Marks)

Part A. Written Task (5 Marks)


T-1.8.1

Instructions: Please produce the following written document:

Write a simple Design Project Proposal call proposal.docx including:

Case Description; Navigation Diagram and storyboard Database table structure

(You are allowed to use one of the Design Project Proposals you developed as a template from the previous subjects you finished or any online standard royalty free web design project proposal template you find from online resources.)

Assessment (30 Marks) – Assignment / Project

Assessment description

Part B. Assignment/Project (30 marks)

Complete the project coding in your Lab PHP and MySQL developing environment: (i.e. Dreamweaver, XAMPP)

Please confirm your project will covers the following items:

Task Criteria Marks

1PHP/MySQL website file and project documentation (the website folder, comments, proposal, testing plan files achieve and maintenance, for submission)

4

2PHP Class Coding; PHP inc file (including file) use; Array, Control Structure use.

4

3PHP implementation of MySQL insert and update syntax; search syntax with ordered by feature;

4

4Use of Dreamweaver built-in PHP/MySQL integrated feature to automatically build PHP/MySQL query implementation.

4

5Following programming good practices for a team friendly maintainable code, and adhere to coding standards (indentation, logical grouping, commenting, naming, re-useable coding models/frameworks)

4

6Saving to objects of the PHP into binary files when need instead of plain text files to save physical space in the coding; use PHP overloading and exception handling when needed at the beginner level.

4

7The class being implemented to both index.php and about_use.php page objects.

3

8Backend database interface, including a user friendly designed GUI page for the client to maintain the content elements of both index.php and about_use.php

3

Assessment – Written (15 Marks)

Part C. Written Task (10 Marks)

Instructions: Please produce the following written document:


T-1.8.1

Write the project testing plan with standards items to test and signing off page. Save to a Microsoft Word files called test.docx

Task Criteria Marks

1 Please list the stand-alone debugging tools you plan to use. Please providing evidence (i.e. screenshots) and a brief description of an example on how to identified an error of logical/coding, and then located where the error occurred, and solved the problem. Then the evidence the error is gone.

6

2 Please use the sample templates given in the resource folder that comes with assessment 2; or, you can find and use your own templates. You should however make sure you included the following part from the standard testing plan items shown in the given template. Please include the one page signing off page as the last page.

9

Submission Guide:

You need to submit this assessment document itself of course, with your student’s detail and relevant information filled properly; the questions or tasks need to be answered directly inside this assessment documented if and when you are instructed so.

For Part A, you need to submit an Word document called proposal.docx For Part B, you need to submit the website folder itself.

Then you need to have a Word file called setting.docx, this will shows how to set up the site inside your coding tools, ie. Dreamweaver, and the database connected successfully during the coding for previewing and testing. Then you need to have another Word file called evidence.docx. It contains all the screenshots of all finished PHP webpage in display view in the web browsers. Since your PHP publishing folder directory in the PHP server is instructed to have your studentID in it, your published view screenshot will have your studentID in the address bar of the browser. This screenshot will be valid evidence the page is coded and made by you.

For Part C, you need to submt a Word files called test.docx. Student must submit by sending the assessment in a zip (not rar) compressed format by the

due date, by sending it to the submission email. (Email address is provided inside eLearning of each subject. Note: important! Assessment submission email address is not trainers’ staff email address)

Appendix: Case Study

Note: the case is the same case or the continuation of the case of Object Oriented Programming I of Certificate IV. The major difference is a database are implemented so that the values of the webpages can be managed by the client through a user friendly GUI (Graphic User Interface). As well as the Web Design Company is to demonstrate more professional methods in project documentation and debugging/testing in project commencing.

Case Introduction:

Fashionwave is a small company of designed apparels.

The company are constructed by 20 middle aged women who design and produce the clothes for women and men. They would like to have their own website, so there will be this company’s online identity and information exposure online. This is the first stage of their online plan. They will eventually have a full-fledged eCommerce website, which will allow them to be able to sell their clothes directly from online.


T-1.8.1

For the time being, the company's owner decided that the project will be just categorised into just men and women two simple categories. Each category will have at least 8 most current products in it for a start. Namely, 8 men's clothes in men category, and 8 women's clothes in women category. The website will have 5 pages. Homepage, Category, Service Policy, About Us, Contact. The Homepage will have welcome information, and some highlights of company current sale information; The category page will of course have the link to the two categories, therefore the two categories will be two subpages of this page; Service Policy page will have company service policy, such as shipping information, return policy, service guarantee, etc; About us page the company introduction and a gallery of photos showing the company have being participating a recent apparel fair, the page will also include the icons to the social media, i.e. FaceBook, Pinterest, Twitter, etc; Finally the contact page will have the contact information of the company and the embedded Google map. The men and women products pages are two subpages of the category page, they will each contact 8 or more products, with the products icons, product names, and prices.

The project after planned and proposed needs to be approved by the project manager and the client. Before the delivery of the website, the testing report need to be sighted and approved by the project manager and the client.

Figure 1: A sample navigation structure diagram you need to include in design project proposal

Figure 2: Sample design of an apparel website


T-1.8.1

Figure 3 A sample storyboard of the website

Due to the time limitation. This subject doesn’t requires you to program and include the dynamic features of shopping of the website. You are required only to develop the two static content pages, ie. index.php and about_us.php. You are required to transfer/represent the content components of the page and store them into a database. Late, you will need to build an interface where the client can easily change the content of the page by themselves.

In terms of the page class coding and the database structuring, as demonstrated in the above sample storyboard, the webpage can be abstracted into serval areas (web elements that need to be represented in the class and in the database). Some of these areas are of course comment to all pages, e.g, Title bar, Navigation bar, Side bar, and Disclaimer.

In the Fashionwave’s design case, for GUI interface of the client content maintenance, you can just concentrate on the ‘un-comment’ areas/parts of the page. Those comment ones mentioned above can be static information, they don’t need to be maintainable in the GUI. This is to because of the limitation of the time for this subject. Therefore the scope of content management tasks is restricted like so, so that the project can be finished by the time of the due date at the end of this subject.

Scenario Problem Summary:

The current problem of the website is that, the content information of the webpages requires periodical updating. It is not convenient for the client to out-source these tasks to a web design company, as most of task is just changing text and image. Therefore, the client would like to have a easy to use interface, where they can change the information displayed on the webpage. Therefore, a CMS (content management system) need to be established with the current website. The company’s current staff is not very IT savvy, therefore user-friendliness of the interface is highly treasured. Due to the scope of the website, the customization of an open-source CMS is too time consuming, and too sophisticated for the client’s need. Therefore, more practical way to solve the problem is to setup a tailor made database structure as the content information need of the webpage per client’s request. Therefore, before framework and structure the database and late the page representation class, the client need to be requested on exactly what contents of which page need to be maintained.


assessment web view · 2017-12-14written, project. due date. week 8. room. details of...

Documents