IST430: E-Commerce
Course Syllabus
Spring 2002, TR
|
Instructor |
: Brian M. Morgan |
|
Office |
: Prichard
Hall 212 |
|
Phone Number |
: (304) 696-6469 |
|
Fax Number |
: (304) 696-6533 |
|
Office Hours |
: MWF: TR: MW: |
|
E-Mail |
Textbooks:
The following textbook is required for the course:
Beginning Active Server Pages 3.0, by Buser, Kauffman, Libre, Francis, Sussman, Ullman, & Duckett; Wrox; ISBN: 1-861003-38-2, 1999.
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.0 or higher or Internet Explorer 5.0 or higher) and Adobe
Acrobat Reader (available for download through the class WebCT site).
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, exams, and a semester-based project. Students will participate in a
project that illustrates the implementation of concepts in a general Electronic
Commerce application.
Pre/co-requisites:
IST231 & IST260 (Instrumentation II) 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 per week. A semester long
project covering the major topics is part of the course. Students may work on their assignments in
University computing facilities.
Evaluation method:
Evaluation of student's performance will be based on the quality of your
performance on the semester-based project, and exams.
Grading Policy:
Final grades are based on performance in assignments and exams as indicated
below.
|
Midterm |
20% |
|
Final Exam |
20% |
|
Semester Project (1-5%, 2-10%, 3-10%, 4-15%, 5-20%) |
60% |
|
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. 20% will be deducted for poorly documented and/or
poorly indented code.
3.
Code that contains errors will receive a grade of 0.
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:
|
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:
Programming assignments: The course includes a number of programming
assignments working toward the overall semester project completion. All
assignments are due at
Exams:
There are two exams: Mid-term (during the 8th week) and a Final exam (as
scheduled). Exact dates and times of exams 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:
For the first time, 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 2002 is
University Holidays:
The class is officially dismissed on the following dates:
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 15 |
Review of Syllabus Introduction to WebCT |
|
January 17 |
What makes an E-Commerce site a good site? Assign Semester Project #1 (Business Plan) |
|
January 22 |
E-Commerce Sites in General Where do I store my projects? |
|
January 24 |
Chapters 1 and 2 |
|
January 29 |
Chapter 3 |
|
January 31 |
Chapter 4 |
|
February 5 |
Chapter 5 |
|
February 7 |
Chapter 6 Semester Project #1 Due Assign Semester Project #2 (E-Commerce Site
Database Design) |
|
February 12 |
E-Commerce Database Design Brief SQL Discussion |
|
February 14 |
Chapter 7 |
|
February 19 |
Chapter 7 |
|
February 21 |
Chapter 8 |
|
February 26 |
Chapter 12Semester Project #2 Due Assign Semester Project #3 (Sites Product
Listing) |
|
February 28 |
Chapter 12 Review for Midterm |
|
March 5 |
Midterm Exam |
|
March 7 |
Chapter 13 |
|
March 12 |
Chapter 14 |
|
March 14 |
Chapter 14 |
|
March 19 |
Chapter 9 Semester Project #3 Due Assign Semester Project #4 (Shopping Cart) |
|
March 21 |
Chapter 10 |
|
March 26 |
Chapter 11 |
|
March 28 |
Chapter 16 |
|
April 9 |
Chapter 16 |
|
April 11 |
Semester Project #4 Due Assign Semester Project #5 (Customer Checkout) |
|
April 16 |
Chapter 15 |
|
April 18 |
Chapter 15 |
|
April 23 |
Chapter 15 |
|
April 25 |
Project Work Q&A |
|
April 30 |
Project Work Q&A |
|
May 2 |
Dead Week Review for Final Exam Semester Project #5 Due |
|
May 9 |
Final Exam (10:15 AM 12:15 PM) |
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.