Reference no: EM132318101

Apply Introductory Object-Oriented Language Skills Assignment -

Purpose of the Assessment - The purpose of this assessment is to assess the student in the following learning outcomes:

• Select and use language data types, operators and expressions, in order to create clear and concise code.
• Use the language debugging facilities of an integrated development environment (IDE).
• Interpret the compiler or interpreter messages to resolve syntax errors, and use debugging techniques to resolve logic errors.
• Follow organisational guidelines for developing maintainable code, and adhere to the provided coding standards, when documenting activities.
• Apply internal documentation to all the code created, and use the documentation tools available in the target language, when documenting activities.
• Create and conduct simple tests, to confirm that the code meets the design specification.
• Document the tests performed and the results achieved.
• Develop a solution, when provided with a basic object-oriented design document.
• Refer to the appropriate documentation for the language.

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 browser 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.

Task 2 - As you have experienced in the class exercise debugging, when you type something in error by mistake or have other kind of mistakes in PHP page coding, the PHP page when browsed in the Internet browser, will show the line number of which the error is most likely located. You need to take a screenshots of this error 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 error fixed until the step that shows the error is gone.

Task 3 - Describe by example how you based on the error message (normally with line number to where the error is located) solved the error (both syntax error, e.g. typing mistakes and logical error, e.g. mistakes in control structure if, else if), there need to be descriptions and screenshots of the steps for the evidence.

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:

a. 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 brief 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 //

b. 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. 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 correctly coded; and finally the delivery group is to check if those pages run correctly in live view.

(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 1232.166785 to round up as 1232.17. You 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 correctly write the syntax. Please use less than 5 screenshots to document the steps on how you do all this correctly, with the last screenshot showing the number is correct rounded up to 1232.17.

Attachment:- Assignment File.rar