IST430: E-Commerce
Course Syllabus
Spring 2003, MW
|
Instructor |
: Brian M. Morgan |
|
Office |
: Prichard
Hall 212 |
|
Phone Number |
: (304) 696-6469 |
|
Fax Number |
: (304) 696-6533 |
|
Office Hours |
: MWF: MW: TR: Other times by appointment ONLY |
|
E-Mail |
Textbooks:
There are no required textbooks for this course, but the following textbook are recommended:
Beginning Active Server Pages 3.0, by Buser, Kauffman, Libre, Francis, Sussman, Ullman, & Duckett; Wrox; ISBN: 1-861003-38-2, 1999.
Teach
Yourself E-Commerce Programming w/ASP in 21 Days, by Walther and Levine; Sams Publishing;
ISBN: 0-672-3198-9, 2000.
Professional
PHP4 Programming, by Rawat, Thomas, Choi, Sani, et al; Wrox Publishing; ISBN: 1-861006-91-8, 2002.
PHP Professional Projects, by Wilfred, Gupta, and Bhatnagar; Premier Press; ISBN: 1-931841-53-5, 2002;
Computer
Requirements:
Supplemental materials can be found contained within the WebCT environment (http://webct.marshall.edu/). I will be sending class announcements,
updates, etc. using your WebCT account (will discuss during the first lecture). Access to a WWW browser is required (Netscape
4.7 or higher or Internet Explorer 5.5 or higher) and Adobe Acrobat Reader
(available for download through the course WebCT site). It is also recommended that you download and
install mySQL, PHP, and ASP on your local computer to
work on course projects from your PC.
Links and instructions will be provided within WebCT.
Course
Description:
This course examines electronic commerce with group decision making and
collaborative applications through the Internet. Develop applications that
retrieve and store information in distributed databases.
Credit:
The course is three (3) credit hours. It includes classroom
lectures, an exam, and a number of programming projects utilizing mySQL, PHP, and ASP. Students will participate in projects that illustrates the implementation of concepts in a
general Electronic Commerce application.
Pre/co-requisites:
IST160 or permission.
Desired Objectives/Outcomes:
By the end of this course, you should be able to:
Instruction method:
There will be 3 contact hours of classroom lecture and hands-on development
projects each week. A number of projects throughout the semester will bring
together two complete E-commerce sites covering the major topics is part of the
course. Students may work on their
assignments in University computing facilities or from home.
Evaluation method:
Evaluation of student's performance will be based on the quality of your
performance on the course projects and a comprehensive final exam.
Grading Policy:
Final grades are based on performance on projects and a final exam as indicated
below.
|
Final Exam |
20% |
|
Project 1 E-Commerce Site Write-Up |
5% |
|
Project 2 Database Design |
10% |
|
Project 3 PHP Product Catalog |
5% |
|
Project 4 ASP Product Catalog |
5% |
|
Project 5 ASP Shopping Cart |
10% |
|
Project 6 PHP Shopping Cart |
10% |
|
Project 7 PHP Checkout System |
10% |
|
Project 8 ASP Checkout System |
10% |
|
Project 9 Administrative Interface (PHP or
ASP) |
15% |
|
Attendance & Participation |
0% |
Assessment
of Projects:
The
grading of all projects will take into account the following:
1.
Although the most important attribute of a project is
correctness, grading will take into consideration such items as efficiency, documentation,
etc.
2.
Programs must have proper inline documentation and
must be properly indented. 10% will be deducted for poorly documented and/or
poorly indented code.
3.
Code that contains syntax errors will receive a grade
of 0. Code that contains logic errors
will receive partial credit.
4.
Although interactions with other students are encouraged,
you must compose your own answers, unless otherwise noted.
Individuals
who utilize other peoples code, thoughts, or ideas must provide appropriate
references to said resources. Failure to
provide such documentation will result in a failing grade for the assignment,
and may result in a failing grade for the course.
In
determining the overall grade for a project, you can expect the following
grades based on performance:
A
Excellent work that meets and/or exceeds all of the requirements for a given
project, code works for multiple test samples, all code and associated files
are well-documented, and the code is written efficiently.
B Good
work that meets all of the requirements of the assignment, but may have errors
in documentation or coding, or contains code that may not work with all
possible data samples.
C
Average work that meets all of the requirements of the assignment, but is
missing one or more of the items in its entirety that is mentioned in terms of
an A grade.
D Below
average work which fails to meet one or more of the requirements of the
assignment.
F
Unacceptable work which fails to meet two or more requirements for an
assignment, or has code that will not compile and execute.
Final letter grades
are determined based on the following grading scale, or on the basis of an
acceptable contract made between the individual student and the instructor on
the first day of class, due no later than the beginning of the second class
meeting. This contract can not be
amended once that it has been accepted by both parties, meaning that a student
will either accept the grade achieved by the contract or by the grading
criteria contained within this syllabus:
|
90-100% |
A |
|
80-89% |
B |
|
70-79% |
C |
|
60-69% |
D |
|
Below 60 |
F |
The instructors reserve the right to change these values depending on the overall class performance and/or extenuating circumstances.
Policy Statement:
Assignments: The course includes a number of homework
assignments. All assignments are due BY
THE BEGINNING OF CLASS on their due date and must be submitted through the
WebCT Dropbox. NO
LATE ASSIGNMENTS WILL BE ACCEPTED.
Exams: There
will be only one exam this semester, a comprehensive final examination. The exact date of the exam will be announced
in class.
Make-up Exams and Late Penalty: Make‑up exams will not be given except under unusual
circumstances and satisfactory written justification. Any student who misses an exam due to an
unexcused absence will receive a grade of zero for that exam with no
opportunity for make-up or substitution.
University excused absences or those occurring with a good reason will
be excused. Make up exams must be taken
within one week of the original scheduled date.
The decision whether to give a make up exam rests with
the instructor.
Attendance Statement:
As with last semester, I am NOT making class attendance mandatory. However, I will keep a record of who is
attending and who is not. If you miss
class, it is your responsibility to catch up on material missed, and will not
be the responsibility of the instructor to catch you up on material missed
during my office hours.
Withdrawal Policy:
The University withdrawal policy is followed in this course.
The last day to drop an individual course for the Spring
of 2003 is
University Holidays:
The class is officially dismissed on the following dates:
MLK, Jr. Day:
Spring
Break:
Topics and Methodology:
The following outline delineates the tentative class schedule with topics to be
addressed during the course. Please
note this is a tentative schedule and it may change upon class progress:
|
January 13 |
Review of Syllabus Introduction to WebCT Where will I store my projects this semester? |
|
January 15 |
What makes an E-Commerce site a good site? |
|
January 22 |
E-commerce Database Fundamentals mySQL and SQL Fundamentals Project #1 Due |
|
January 27 |
Intro to HTML Forms Product Catalog Logic and Fundamentals |
|
January 29 |
PHP Fundamentals Variables, operators,
control structures, basic scripting |
|
February 3 |
PHP Fundamentals Arrays and Functions Project #2 Due |
|
February 5 |
PHP Fundamentals Integrating with mySQL |
|
February 10 |
Intro to ASP ASP Object Model, Basic
Scripting |
|
February 12 |
ASP Fundamentals Variables, Operators, Arrays, and Control Structures Project #3 Due |
|
February 17 |
ASP
Fundamentals - Response and Request Objects |
|
February 19 |
ASP Fundamentals Integrating with mySQL |
|
February 24 |
Logic for Shopping Carts |
|
February 26 |
Working with Cookies in ASP & PHP Sessions in PHP & ASP Project #4 Due |
|
March 3 |
Class Q/A - Project Work/Assistance on Logic |
|
March 5 |
Class Q/A - Project Work/Assistance on Logic Project #5 Due |
|
March 10 |
Customer Checkout Logic |
|
March 12 |
Class Q/A - Project Work/Assistance on Logic Project #6 Due |
|
March 24 |
Working with Files in PHP and ASP |
|
March 26 |
Regular Expressions in PHP |
|
March 31 |
Class Q/A - Project Work/Assistance on Logic |
|
April 2 |
Class Q/A - Project Work/Assistance on Logic Project #7 Due |
|
April 7 |
Error Handling in PHP and ASP |
|
April 9 |
Administrative Web Interface Fundamentals Topic Suggestions from Students |
|
April 14 |
Class Q/A - Project Work/Assistance on Logic Project#8 Due |
|
April 16 |
Student Topic #1 |
|
April 21 |
Student Topic #2 |
|
April 23 |
Student Topic #3 |
|
April 28 |
Class Q/A - Project Work/Assistance on Logic |
|
April 30 |
Project #9 Due Review for Final Exam |
|
May 5 |
Final Exam |
For each topic
discussed in the textbook, specific experience of other students and the
instructor will be discussed to enhance the characteristics involved. Programming projects for the course will be
based on creating a fully-functional E-Commerce solution. Additional material may also be covered in
the class.
Every student is
responsible for all materials presented in class, including lectures, notes, and
handouts. In case you are not present
for a class, it is your responsibility to contact the instructor and receive
information about the material presented in that class. Class attendance is very important.
Effort Required:
As a 400-level course, a considerable amount of development and research effort
is required of the student. For every
one hour in class, the student is expected to put in an effort of at least 3
hours outside the class for studying and programming. Upon background and preparedness, some
students may have to put in additional effort.
Communication:
The Bulletin Board facility of WebCT and private E-mail will be used to make
any general announcements, last minute changes, etc. It is mandatory that you monitor your WebCT
course messages at least once a day.