Professional Documents
Culture Documents
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Submission requirements.
Submit (1) a word document (this file with your answers and listing of any program & copy and paste its run-log in a
professional and presentable format and style) and (2) a zip file of a folder which will contain all the codes (all the source
codes and executables and the instruction for how to compile and run) and a document file (.doc or .docx).
This word document (this file) is your documentation (as a basis to add your answers) to be included here - all your answers, all your
program-listings, instructions to compile and run [screen-shots, terminal text, or session log] to show your work done, including how
to compile and run for each cases.
The word file should also have (1) in header with the course & section number, your name (Name: last name, first name), your netID
(email), and Assignment #, (2) in footer with page number, (3) line number (restart from each page in left margin. Page Layout =>
Line Numbers). (4) Your program should have some comments (minimal or reasonable), to tell the code-reader what a segment of
code is doing, and with the comment in the front/head of the program about you, this course and assignment, etc. (you may copy and
paste some out of this document for your comment).
** Your executable codes (that you submit) should run in csgrads1.utdallas.edu without any change or recompilation.
** Upload this document file (with your answers) and a zip file (containing all the codes [source and binary etc.].
Scoresheet
parts
Part1 70% #1 #2 #3 #4 Demo
Labs Week07 Lab12 Week07 Lab13 Week08 Lab14 Week08 Lab15 & documentation
PHP Arrays * PHP OOP PHP SQL Error&Validation Demo
superglobal & documentation
#5 #6 #7
Week09 Lab16 Week09 Lab19 Week09 Lab21
Manage States Web Services WordPress
Note: CLO means Student Course Learning Objectives/Outcomes (listed in the course syllabus)
Deduction/Penalty
(1) Documentation (this .doc file) and upload.
Max -10% if your documentation not done or poorly prepared.
1
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Note. Any "poor" documentation (that is, this document with your answers etc.) may result in a
penalty (up to -10%).
Upload this document file (this file with your answers) and a zip file (containing all the codes
[source and binary etc.] and its run log or results. All the code should run in csgrads1 without any
change).
2
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Part 1. Labs
Part1 #1 #2 #3 #4 Demo
Labs Week07 Lab12 Week07 Lab13 Week08 Lab14 Week08 Lab15 & documentation
PHP Arrays * PHP OOP PHP SQL Error&Validation
superglobal
Have you done your
#5 #6 #7 demo with TA? State
Week09 Lab16 Week09 Lab19 Week09 Lab21 below the date & time
Manage States Web Services WordPress of your demo for this
lab with TA
Create a folder for each lab (e.g., "lab12" folder provided for lab12) and do and place all the work artifacts (codes,
program, data, etc.) of the lab. When done, submit a zip file (only .zip file) containing all the folders of the assignment.
Place screenshots of each lab (when it is done by part or by exercise) with heading (e.g., the result of Lab3 exercise1,
…). Make sure your presentation "reader-friendly" and "professionally done" for each lab to show that you have done
your work. That is, TA can see what you have done with ease as TA reads through your work done (with the heading and
screenshots).
3
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
4
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
5
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
6
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
7
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
8
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
9
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
10
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Part 2. Tutorials
Part2 #1 Week09 Tutorial #1 #2 Week09 Tutorial #2 #3 Week09 Tutorial #3
Tutorials Instant PHP Web Scraping PHP Web Services Linux System Admin -
configure Apache Server
Part2 Tutorial#1
Week09 Tutorial #1 Instant PHP Web Scraping (A short book with 1 chapter)
Try a few sample codes (provided in the sample codes in the zip file): 1-hello.php, 2-curl-request.php, …
Place a few screenshots of each tutorials including the runs of sample code or the screenshot of the video tutorial
with heading (e.g., the result of the tutorial #1, …), to show that you have done (studied or viewed) all of the
tutorial.
1) Hello world.php
2) Curl-request.
The script was not working with original url so I just changed url to www.google.com to show that
scrapping was working.
11
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
3) Xpath-scraping.php
4) Pattern-recognition
This script did not worked cause it was not able to scrape email address from ’
http://www.packtpub.com/contact’ . Hence I was getting empty array as output.
6) Verfying.data
7) Scraping-images.php
12
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
8) Submitting-form
9) Traversing-multiple pages
13
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Part2 Tutorial#2
Week09 Tutorial #2 PHP Web Services (video tutorial)
Try a few sample codes (provided in the sample codes in the zip file).
Place a few screenshots of each tutorials including the runs of sample code or the screenshot of the video tutorial
with heading (e.g., the result of the tutorial #1, …), to show that you have done (studied or viewed) all of the
tutorial.
Tutorial 2
14
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
Part2 Tutorial#3
Week09 Tutorial #3 Linux System Admin - configure Apache Server (video tutorial).
View the video tutorial only.
Place a few screenshots of each tutorials including the runs of sample code or the screenshot of the video tutorial
with heading (e.g., the result of the tutorial #1, …), to show that you have done (studied or viewed) all of the
tutorial.
Tutorial 3
15
CS 6314 Name (Last, First): _Shah, Meet_______________________ Email:
___mxs170053@utdallas.edu
©2020 Richard K. Min. The University of Texas at Dallas
16