IFS320 – Web Development
W. R. Eddins, Ph.D.
Mission Statement: The Department of Business Administration at York College provides distinctive, high
caliber business education that prepares individuals for successful careers and personal growth. We provide
students with an education that encourages intellectual development while also meeting the specific needs of
the business community through a dynamic, experiential business curriculum.
Vision Statement: The Department of Business Administration at York College will be recognized as a
leading business educator in the Mid-Atlantic region. Our business students will be regarded as the best and
most sought after graduates due to exceptional academic preparation, professionalism and integrated business
problem-solving experiences.
Course
Semester
Faculty
Title
Office Location
Office Hours
Email
Website
Days, Times & Room
Prerequisites
Credit Hours
Textbook
Additional Resources
IFS320-Web Development
Fall 2014
W. R. Eddins, Ph.D.
Professor of Information Systems
WBC 201
As posted on Moodle and on the instructor’s website
weddins@ycp.edu
http://faculty.ycp.edu/~weddins and Moodle
TT 12:30-1:45p in WBC304
IFS225 or other introductory programming course with a grade of 2 or better
3 credit hours
Murach’s ASP.NET 4.5 web programming with C# 5th by J. Delamater & A. Boehm
Paper folder (for projects) and # 2 pencils (for tests)
Description (from College Catalog):
This course is an introduction to web-based system development methods. Emphasis will be placed on
designing and building data-based solutions to common web-based, interactive e-commerce, and
collaborative information systems. Languages used include Java, Perl, VB, C#, ASP, PHP, SQL, JavaScript,
VBScript, XHTML, CSS and/or others at the discretion of the instructor.
Instructor's Educational Philosophy:
“And gladly would he learn and gladly teach” by Geoffrey Chaucer. Also, see my papers link.
Core Learning Outcomes:
Upon completing this course, the student will be able to …
1. Demonstrate knowledge of web-based programming and database concepts using Visual Studio.
2. Write programs that use HTML, CSS, C#, ASP.NET, and SQL Server in aspx pages.
3. Discuss and apply data management techniques including collections, multi-dimensional and
associative arrays, external data files, and database tables or queries,
4. Manage a relational database using SQL Server and integrate dynamic data into web pages.
5. Build and discuss simple ecommerce and collaboration information systems.
IFS320-WebDev Syllabus
Fall 2014
Page 1
Class Assessment and Schedule:
Assessment Item
Exams (3 @ 100 points each)
Programming Assignments (4 @ 100 points each)
Participation and Quizzes
Class Assessment
Value to You
45% of your test points divided by 300
45% of your programming points divided by 400
10% of your participation points divided by total participation points
Participation points are given for in-class exercises such as chapter quizzes, group discussions, and other
activities. The quizzes are based upon the concepts on the page in parentheses below next to the number of
the chapter. You must be present to receive participation points. Participation points cannot be made up.
Schedule of Activities for IFS320 Fall 2014
Week
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Tues Date
8/26/2013
9/2/2013
9/9/2013
9/16/2013
9/23/2013
9/30/2013
10/7/2013
10/14/2013
10/21/2013
10/28/2013
11/4/2013
11/11/2013
11/18/2013
11/25/2013
12/2/2013
12/9/2013
12/16/2013
Activity ('C' is Chapter and 'P' is Programming assignment)
C1(10) - Intro to ASP.NET, Syllabus, Give P1 & Lab 1
C2(32) - One-page App & C3(84) - Intro to HTML and CSS
C4(136) - Multi-page App, P1 Due & Give P2
C5(178) - Testing and Debugging
Test 1 (C1-5), C6(192) - Standard Server Controls
C7(232) - Validation Controls
C8(272) - State, C9(296) - Master Pages, P2 Due & Give P3
Fall Break on Tues, C10(326) - Themes
Test 2 (C6-10), C11(342) - Site Navigation
C12(378) - Intro to DB
C13(404) - SQL Data Source, P3 Due & Give P4
C14(442) - Gridview Control
C14(442) - Gridview Control
Thanksgiving begins Tues @ 10p, C15(482) - DetailsView and FormView
C15(482) - DetailsView and FormView
Last Class & P4 Due
Test 3 (C11-15) during Finals Period
Note: this schedule is subject to change. You will be notified by the instructor of changes. Programming
assignments will be given in separate documents and will include due dates as well as other requirements.
Grading Policy:
Final Grade
4 (Excellent)
% Range
100.0 –
90.0
3.5 (Very Good)
89.9 –
87.0
3 (Good)
86.9 –
80.0
79.9 –
77.0
76.9 –
70.0
69.9 –
60.0
2.5 (Above
Average)
2 (Average)
1 (Below Average)
IFS320-WebDev Syllabus
Description
This grade denotes accomplishment that is truly distinctive and decidedly outstanding. It represents a high
degree of attainment and is a grade that demands evidence of originality, independent work, an open and
discriminating mind, and completeness and accuracy of knowledge, as well as an effective use of the
knowledge.
This grade denotes mastery of the subject matter. It represents very good achievement in many aspects of the
work, such as initiative, serious and determined industry, the ability to organize work, and the ability to
comprehend and retain subject matter and to apply it to new problems and contexts.
This grade denotes considerable understanding of the subject matter. It represents a strong grasp and clear
understanding of the subject matter and the ability to comprehend and retain course content.
This grade denotes above average understanding of the subject matter. It represents a good grasp of the subject
matter and the ability to comprehend and retain course content.
This grade denotes average understanding of the subject matter. It represents the grade that may be expected of
a student of normal ability who gives the work a reasonable amount of time and effort.
This grade denotes below average understanding of the subject matter. It represents work that falls below the
acceptable standard.
Fall 2014
Page 2
0 (Failure)
59.9 – 0
I (Incomplete)
N/A
W (Withdrawal)
N/A
P (Pass)
F (Fail)
AU (Audit)
N/A
N/A
N/A
This grade denotes inadequate understanding of the subject matter. It signifies an absence of meaningful
engagement with the subject matter and that the student is not capable of doing or understanding the work or
has made little or no effort to do so.
The student may request permission from the instructor to receive an incomplete prior to the final examination
and must present extraordinary reasons for the petition. The Instructor should indicate on the Attendance/Final
Grade Record the required work the student must do to complete the course. Any grades of “I” not removed
within two calendar months after the end of the semester will automatically be changed to “0” in the Records
Office. Grades of incomplete should only be provided to students who have completed a substantial portion of
all course requirements.
Students are permitted to withdraw from courses without penalty up to the ninth Friday of the fall or spring
semester. Corresponding deadlines are set for all other semesters (e.g., summer sessions). Withdrawal after that
time shall result in a grade of “0.”
This grade denotes passing in special Pass/Fail courses.
This grade denotes failure in special Pass/Fail courses.
This grade indicates that a student is registered for a course but receives no credit.
Academic Integrity:
York College’s mission statement stipulates that strict adherence to principles of academic honesty is expected of all students.
Therefore, academic dishonesty will not be tolerated at York College. Academic dishonesty refers to actions such as, but not
limited to, cheating, plagiarism, fabricating research, falsifying academic documents, etc., and includes all situations where
students make use of the work of others and claim such work as their own.
When a faculty member believes a student has committed an act of academic dishonesty, the faculty member must inform the
student in writing and then has ten business days from that written notification to the student to report the incident to the Dean
of Academic Affairs and the Department Chair. Documentation related to instances of academic dishonesty will be kept on file
in the student’s permanent record. If the academic dishonesty is the student’s first offense, the faculty member will have the
discretion to decide on a suitable sanction up to a grade of 0 for the course. Students are not permitted to withdraw from a
course in which they have been accused of academic dishonesty.
Students who believe they have been unjustly charged or sanctioned (in cases involving a first offense) must discuss the
situation with the faculty member and have 10 business days thereafter to submit an appeal to Student Welfare Committee
through the Dean of Academic Affairs. If an appeal is filed, the Student Welfare Committee will then conduct a hearing to
review the charge and/or sanction. In cases of a first offense, the faculty member may request that the Student Welfare
Committee conduct a hearing and decide on the sanction, which can involve academic suspension or dismissal from the College,
if the faculty member believes the offense to be of an extremely egregious nature.
If the Dean of Academic Affairs determines that the academic dishonesty is the student’s second offense, the Dean will provide
written notification to the student, the faculty member, and the Department Chair. The Student Welfare Committee will
automatically conduct a hearing to review the charge and decide on an appropriate sanction, which will involve academic
suspension or dismissal from the College. Students who believe the Student Welfare Committee has unjustly sanctioned them
may submit a written appeal to the Dean of Academic Affairs within 72 hours of receiving notification of the Student Welfare
Committee’s sanction.
Late Submission of Course Materials:
Students will be assigned programming assignments throughout the course to enhance the student's
understanding of the material presented and its application. Programming Assignments will be prepared
and submitted both in hardcopy and via Blackboard prior to the beginning of the class period on the date
due. Sufficient time is allowed for students to complete problem assignments prior to their due date.
Assignments will be reviewed and discussed in class prior to the due date and on the due date; therefore
assignments turned in late will NOT be accepted and NO credit will be given without prior approval of the
instructor. Assignments must be word-processed and/or the appropriate computer software utilized and
submitted in a folder and electronically via Blackboard--assignments will NOT be accepted in other
delivery formats such as email. Part of the required learning for this course will be the ability to submit
assignments electronically on time and in the designated manner. Programming assignments and the
acceptable format for the preparation and submission will be distributed separately and discussed in class.
Each student must work on the assignments individually (on your own). Submission of another's work or
significant collaboration that indicates that the work submitted is not the sole effort of the student
submitting the work will be considered as cheating. However, you are permitted to collaborate with other
IFS320-WebDev Syllabus
Fall 2014
Page 3
students provided that you do your own typing, create your own files and folders, and, in general, operate
the computer that you are working at. Please note! Make sure to submit a copy of your work, not the
original file(s) of your work and ensure that when you submit your work that you are finished and this is
version you want graded.
Classroom Code of Conduct:
 Arrive on time.
 Don’t skip classes.
 Cell phone use is prohibited.
 In class use of laptop or notebook computers is encouraged.
 Participation is essential.
 Ask questions.
 No music players of any type.
 No electronic devices will interrupt the class. That means, turn off the sound of your mobile
device.
 No exiting and reentering the classroom during test periods without the permission of the
instructor.
Attendance Policy:
Attendance may be recorded at the beginning of each class period. Instruction that the student misses due to
an absence or late arrival must be made up by the student on his/her own.
Additional Information:
How to succeed:
 Come to ALL classes. The lectures and demonstrations are designed to present the material you need
to know as you need to know it to successfully complete programming assignments.
 Keep abreast of the Schedule of Activities to know what is coming up and when programming
assignments are due.
 Work on the programming assignments as soon as you get the requirements—the longer you wait, the
less you remember of the in-class discussion. Once you fall behind it is unlikely that you will be able
to catch up.
Appropriate use of E-mail: e-mail is a valuable tool for student/instructor communication. Following are
does and don’ts:
USE E-mail for:
 Clarification of the details of programming assignments or general project requirements.
 Arranging appointments when office hours are in conflict with the student's schedule.
 Apprising the instructor of interesting resources that may be useful for enhancing the class.
DO NOT use E-mail for:
 Submitting programming assignments (will result in a grade of zero for the assignment).
 Anything grade related.
 Requesting information 'Re-lecture' material because of missing a class.
Finally, when you ask a class related question in an E-mail, be sure to include your class and section, the
project or assignment to which you are referring and a specific question relating to the problem you are
addressing. If you are asking a question regarding a bug in a programming assignment, please zip up the
entire project and upload the zip to the Trouble Shooting link on Blackboard.
IFS320-WebDev Syllabus
Fall 2014
Page 4