|
||||||
COURSE:
|
IS 304, Fundamentals of Business
Programming
Section 2, T R 8:00 – 9:15 a.m., SSS 208
|
|||||
|
|
|
|||||
INSTRUCTOR:
Office:
Office hours:
E-mail:
Phone:
|
Dr. Thomas S. E. Hilton
SSS 401
Daily 3:30-4:30 p.m. or by
appointment
HiltonTS@uwec.edu
715/836-3416
|
|||||
|
|
|
|||||
PREREQUISITE:
|
IS 240, Information Systems in
Business
|
|||||
|
|
|
|||||
TEXT:
|
None |
|||||
|
|
|
|||||
COMPUTER:
|
Personal laptop computers will
be used. Wireless access to the UWEC network is required with configured
links to network storage (H: and W: drives)
|
|||||
|
|
|
|||||
SOFTWARE:
|
Required:
|
Visual Studio.NET Professional
2010, MS Word 2010, MS PowerPoint 2010
VMware View client for virtual
lab PC
|
||||
|
|
|
|||||
TECH SUPPORT:
|
Monday:
Tuesday:
Wednesday:
|
08:00a - 10:00a, 12:00p-2:00p
09:00a - 11:00a
12:00n - 02:00p
|
Thursday:
Friday:
|
09:00a - 11:00a, 2:00p –
4:00p
Sorry, none
|
||
|
|
|
|||||
COURSE
|
An introduction to event-driven
structured programming for business in an object-oriented context for IS
majors, IS minors, and IS certificate students
|
|||||
|
|
|
|||||
UNIVERSITY
LEARNING
GOALS:
|
·
Creative
and Critical Thinking (skill): UW-Eau Claire students will
develop and use critical thinking skills in academic and social contexts.
·
Effective
Communication: UW-Eau Claire students will
effectively write, read, speak and listen in
academic and social contexts.
|
|||||
|
|
|
|||||
IS PROGRAM
GOALS:
|
·
Acquire technical skills
·
Effectively write and speak to
both technical and business audiences
|
|||||
|
|
|
|||||
COURSE
|
1. Apply fundamental software design principles when
developing applications. 2. Design and construct user interfaces with sensitivity
to accessibility and cultural differences of users. 3. Apply procedural code and objects to solve
business problems and meet business requirements. 4. Use an integrated development environment
effectively and efficiently. 5. Write appropriate documentation and use
conventions to facilitate program maintenance. 6. Acquire skill in writing procedural code
structures in what many consider a fourth generation language (4GL). |
|||||
|
|
|
|||||
COURSE
|
Learning programming is an interactive
endeavor. Concepts are frequently illustrated through practical application.
Students are expected to practice and review concepts outside of class
meetings. Assignments are designed to reinforce and extend concepts presented
in the classroom.
|
|||||
|
|
|
|||||
COURSE
POLICIES:
|
||||||
General
|
1. Students will check their University email
account on a daily basis. 2. Students will attend class and obtain adequate
notes, code exercises, and handouts. A high standard of preparation is
expected for class. 3. Students will make a back-up copy of every
assignment or project. 4. Students will ensure that all necessary files are
submitted for each program or assignment. |
|||||
|
|
||||||
Plagiarism
|
In addition to the College
of Business Code of Conduct, the following policies apply to plagiarism
(which is copying someone else’s assignment or code, in whole or in
part, and passing it off as your own). Plagiarized work will be given a score
of 0. Further, a formal report will be made to the University which may
result in 1. a
note of the offence being added to your student record and/or 2. further penalties being imposed by the University up to
and including expulsion. |
|||||
|
|
||||||
Late
Work
|
Work is late if it is delivered to the instructor
after the due time and date. 1. If
the instructor has been informed in advance and has approved the late
submission, ·
The work will be graded with no penalty. Approval
is often given for serious illness or accident and events such as serious
illness or worse in the immediate family. If in doubt, talk to the instructor. 2. If
the instructor has not been informed in advance and the student has a good
reason for the late work, i.e., illness or accident of a serious nature and
can provide documentation (e.g., medical documentation), ·
The work will be graded with no penalty. Approval
is often given for serious illness and events such as serious illness or
worse in the immediate family. If in doubt, talk to the instructor. 3. If
the instructor has not been informed in advance, the student has no good
reason, and ·
Work is 1 - 24 hours late: The work will be
graded and the final score halved. The maximum score will be 50% of the
credit available. ·
Work is 25-48 hours late: The work will be graded
and the final score quartered. The maximum score will be 25% of the credit
available. ·
Work is more than 48 hours late: The work will
not be graded and a score of 0 will be recorded for the work. |
|||||
|
|
||||||
Assignment
|
1.
File loading error or media error ·
This
is not your fault or responsibility.
The instructor will e-mail the student at their University e-mail address.
The student will have 48 hours from the time the email is sent to send
replacement files. If the student supplies the replacement files in a timely
manner, the assignment will be graded on a full-credit basis. If the files
are not received in the allowed time, the assignment will be graded as-is. 2.
Assignment has missing files ·
This
is your fault and your responsibility.
The instructor will e-mail the student at their University e-mail address as
soon as the problem is discovered. No matter what time the instructor informs
you of this problem, you will be under the policies that relate to
late assignments (see above). |
|||||
|
|
||||||
Exams
|
Exams are to be taken at the scheduled time and
place. No exam may be taken at any other time for credit. Exceptions to this
policy are granted for serious illness or accident to the student or
immediate family. If in doubt, talk to the instructor. |
|||||
|
|
||||||
Accommodation of Disabilities
|
Students with disabilities are encouraged to
discuss their needs with the instructor, preferably during the first week of
class. All reasonable accommodations will be made to see that disabilities do
not restrict a student's opportunity to learn. Help is also available from
the Office for Services to Students with Disabilities (Old Library 2136,
phone 715/836-4542). |
|||||
|
|
||||||
Grading
|
Percentages refer to overall percentage using
scores from all required exams, projects, and homework: |
|||||
|
A 93%
- 100% A- 90%
- 92% B+ 87%
- 89% B 83%
- 86% B- 80%
- 82% C+ 77%
- 79% |
C 73%
- 76% C- 70%
- 72% D+ 67%
- 69% D 63%
- 66% D- 60%
- 62% F 0% - 59% |
|||||
|
|
||||||
|
Student |
The following assignments and exams will be used
to calculate course grades: 45% 5 Program Assignments @ 9%
each 5% 1 Program Assignment
6% 1 Assignment 15% Midterm Exam 10% 10 quizzes @ 1% each 19% Final Exam 100% Total |
|||||
|
|
|
|||||
QUIZZES:
|
Quizzes are taken
during the first 10 minutes of class on the days noted in the schedule.
Prepare for them by studying your notes, the PowerPoint files, and other
relevant resources since the last quiz.
Select and Take
Get Scores
Change Password
|
|||||
|
|
|
|||||
OTHER
|
Using
the W: Drive
Protocol
to Start a Visual Studio Assignment
Protocol
to Submit a Visual Studio Assignment
What time is it at the
Server?
Code
Examples
YouTube
Video on Counting and Converting Decimal (0:00), Octal (3:45), and Binary
(7:18)
Debugging
Example (Winzipped)
MSDN
Visual Studio Online Help (or you might like this VB tutorial)
ASCII/ANSI
Code Table
VB.NET
Naming Conventions
VB.NET
File Types
Binary Encoding Site
(external site)
Wisconsin Integrated
Software Catalog (external site)
Microsoft Academic
Alliance Store (external site)
|
|||||
|
|
|
|||||
SCHEDULE:
|
Topic
|
Work Due |
||||
|
Tue Jan 24 |
Intro |
Review syllabus |
-
|
||||
|
Thu Jan 26 |
Binary coding -
ASCII/ANSI | .ppt |
- |
||||
|
Tue Jan 31 |
Binary coding -
Numbers & the Rest | .ppt |
Quiz 1:
Syllabus |
||||
|
Thu Feb 2 |
.NET IDE - Compile,
Interpret (source vs .exe) | .ppt |
- |
||||
|
Tue Feb 7 |
.NET IDE - features,
solution setup protocol | .ppt |
Quiz 2:
Binary & Graphics |
||||
|
Thu Feb 9 |
Event Driven
Program: Hello World - design & implement |
- |
||||
|
Tue Feb 14 |
Interface Classes I
- Basic I/O (lbl, txt, btn,
frm) |.ppt |
Quiz 3: .NET IDE |
||||
|
Thu Feb 16 |
Interface Design -
conventions & guidelines | .ppt |
Program I: IY |
||||
|
Tue Feb 21 |
Variables - Defined, References & Data Types | .ppt |
|||||
|
Midterm
Exam: Bring straight edge, 2 pens, 2 pencils, five sheets of paper, and a
calculator. |
||||||
