SUFFOLK COUNTY COMMUNITY COLLEGE

WESTERN CAMPUS

STUDENT COURSE OUTLINE


COURSE TITLE:

Programming GUIs (Graphical User Interfaces) in Visual Basic .NET

CATALOG #:

CST131

CREDITS:

4





INSTRUCTOR:

Prof. B. A. Martin ("BAM")

SEMESTER:

2009 Fall

E-MAIL:

bam@suffolk.li



OFFICE HOURS:

Before and/or after class and by appointment. (Department phone is 851-6770.)





COURSE DESCRIPTION:

Covers concepts enabling programmers to write user interfaces for Windows environments. Advanced Visual Basic features presented and used. Designed for students who know basics of a programming language and have experience with Windows.

PREREQUISITES:

CST112 (or permission of the department).


TEXTBOOK:

Programming in Visual Basic 2008
by Julia Case Bradley & Anita C. Millsbaugh
[McGraw Hill Technology Education ]
ISBN 978-0-07-351720-0 ( MHID 0-07-351720-8 )

SOFTWARE NOTE:

This course uses Microsoft “Visual Basic .NET” If you use other products to develop code elsewhere, always check your work using computers on-campus. This software is available on computers in the computer lab in Caumsett Hall, room 211.

NOTE:   A free version, known as Visual Basic "Express" edition, is available at:

http://www.microsoft.com/express/vb/



OBJECTIVES:

After completing this course, a student will be able to:

  • program user interfaces for the Windows environment using the Microsoft Visual BASIC language.

  • write object oriented programs emphasizing object reusability.

  • build state-of-the-art user interfaces for their programs.

  • write programs with client/server capabilities using OLE.

  • write programs that interact as clients and servers with respect to a database.

  • create Graphical User Interfaces that hide the programming and problem solving complexity from the users.



PROCEDURES TO ACCOMPLISH THESE OBJECTIVES:


  • Class lectures and discussions. (Questions are encouraged.)

  • In-class demonstrations, using projector to show instructor's video screen.

  • Laboratory work in VB.

  • Homework assignments and projects (collected and/or examined in class)


STUDENT REQUIREMENTS FOR COMPLETION OF THE COURSE:

To successfully complete this course, you must submit required homeworks and programming assignmentsts, and demonstrate proficiency on all exams and projects. All work submitted must be neatly presented clearly labeled and identified as to the assignment and what has been accomplished.



GRADING POLICY:


  • Examinations (two).

  • Comprehensive Final Examination

  • Assignments and projects completed.

  • Participation and demonstrated understanding, in class.

40%

30%

30%

+/- 10%


SPECIAL NOTE REGARDING PROGRAMMING ASSIGNMENTS & LABORATORY TIME:

In-class laboratory time is NOT intended for students to do most of their work on the programming assignments and projects; these assignments are to be done between classes, and are expected to require a minimum of 6 hours per week to complete – independently, at your own pace.

In-class laboratory time is intended for announced tutorial exercises and also for obtaining instructor help with problems in programming assignments that have been worked on between classes.

Also, please note:  In-class laboratory time is NOT intended for computer activites unrelated to the college curriculum (such as games, entertainment, "instant messager", "surfing the web", etc.) Use of classroom computers for unrelated activities may result in loss of privileges.


ATTENDANCE POLICY: Attention is directed to the following statement of college policy:

"The college expects that each student will exercise personal responsibility with regard to class attendance. All students are expected to attend every class session of each course for which they are registered. Students are responsible for all that transpires in class whether or not they are in attendance."

Consequently, each student in this course is strongly advised to make standing arrangements with another individual student to take detailed notes, collect handouts, relay announcements, etc., in the event 'e doesn't show up at class. While you are encouraged to contact the instructor for advice before (or after) missing a class, it is more effective to have your "buddy" take detailed notes, and the student remains responsible for "all that transpires in class". Find a "buddy" to cover for you! Do it now, not after missing a class.


This instructor does not give credit for mere attendance, nor is credit lost for absence. Attendance is not a direct factor in grading policy, but it may indirectly affect the “participation” component.


College policy defines "Excessive Absence or Lateness" as "more than the equivalent of one week of class meetings". While attendance is not a component of grading policy for this class, a student missing more than one week of consecutive classes - without making any contact with the instructor - may be removed from the class roster and given either a “W” or an “F grade, at the instuctor's option.



*** PLEASE TAKE NOTE ***

SCCC STUDENT CODE OF CONDUCT


... Although not all-inclusive, the following actions, activities or behaviors are expressly prohibited:

"Unauthorized or illegal use of College computer facilities or equipment, such as hacking; duplication or unauthorized use of copyrighted software; destruction, unauthorized transfer or alteration of files; unauthorized use of another individual's identification, password or work."
Any student guilty of the above may receive a failing grade in that class, be dismissed from class

and/or be referred to the Dean of Students for further discipline proceedings.