CIS380 Visual Basic Syllabus

Objectives:

- to review and implement appropriate principles of design, documentation and coding

- to learn to use event-driven programming skills

- to learn to use the Visual Basic programming language

Textbook:

Using Visual Basic 5, Special Edition, Second Edition, by McKelvy, Spotts and Siler, Que, 1997

Topics:

Program and system design: event-driven programming; objects, properties, methods; documentation; screen design, testing; debugging; efficiency; style; Visual Basic

Exams:

Midterm: Thursday, October 22

Final: Tuesday, December 15, 6:00

Grading:

Exams (2): 50%

Programming project: 50%

Other considerations:

- all students will participate in a self-evaluation and an evaluation of the team at the end of the term

- students are responsible for the information covered in CIS120 and CIS121 Business Applications Programming I and II

- there will be no makeup exams; if an exam is missed for a valid reason, the final exam percentage will be used for the missing exam grade

- deadlines are to be strictly observed; all teams are to hand in their portfolios on the due dates; you will be evaluated on what is presented on those dates

- each team will need a binder to hold all programs and documentation, each with appropriate marker tabs

Project Calendar:

System Design - Due Thursday, October 1

complete system design:

system narrative

forms layouts

data dictionaries

relationships diagram

program specifications (including screen captures)

report formats

 

File Creation - Due Thursday, October 29

menu programs completed

file creation

inquiry programs completed

 

File Modifications - Due Monday, November 23

add, update, delete programs completed

cross-validation/multiple files required

 

Advanced Features - Due Thursday, December 10

advanced features incorporated

documentation updated and completed

system completely tested and working

 

 

 

 

 

Project Considerations:

The following are comments and guidelines concerning the programming project for this session. There is no specific order to these comments.

U 2 or 3 people per team; spread the work out evenly; one person should be designated as the team leader; the team leader will help coordinate meetings, timelines, walkthroughs, etc.

U include as many advanced features as possible in each of the programs: you will be graded on the quantity and quality of advanced options that you (individually) use

U features must include:

- Windows based system

- multiple forms per program

- database interfaces

- add, delete, modification of records

- access of multiple data subsystems from one online program

- multiple transactions/screen

U use good documentation techniques; documentation must include:

System: narrative (system description)

data dictionaries (one for each file)

user's guide

relationship diagram

Programs: program overview - specifications

form layouts

program listings and printed outputs

data input forms

report printouts

the system narrative provides an overall picture of the system: the background of the system, how all the processing is done: from first step to last; descriptions of the programs, files, reports; this document should include the WHY as well as the WHAT and HOW

documentation for each program/form should include:

screen capture

narrative description / specifications

events / actions

database tables used

code listing (commented, highlighted)

do not include properties listing

other documentation aids (e.g. from CIS220) are encouraged

U each program should have comments in the general declarations module that include:

- what system the program belongs to

- what part of the system it is and how it interfaces with the rest

- what its purpose is

- who was involved in the program: documentation, specification, coding, testing

- what special features the program uses

- the usual listing of inputs, processing, outputs

- room for modification documentation

U you must include some forms/reports with calculations, graphs, summarizations, forecasts, ... (not just echoing what is in the files record by record)

U name all files and records in a descriptive way (not just Master File or Input Record or Disk File)

U everything output to the printer must be formatted

U all programs that are not interactive must produce a printed report

U all reports must include descriptive headings, including the program name, date run, report title, report date, page numbers, descriptive column headings

U good programming style is required in all programs

U use practical, various and "good" test cases; must PROVE that the programs work

U use a binder to organize all programs and documentation; ALL PREVIOUS REVIEW SHEETS MUST BE KEPT WITH THE DOCUMENTATION; all team members are responsible for the portfolio; every name referencing the same item in the portfolio must match

TENTATIVE COURSE CALENDAR:

Tuesday, 1/19/99 Introduction, Chapter 1

Thursday, 1/21/99 Chapter 2

Tuesday, 1/26/99

Thursday, 1/28/99

Tuesday, 2/2/99

Thursday, 2/4/99 Chapter 3

Tuesday, 2/9/99 Chapter 4

Thursday, 2/11/99 Chapter 6

Tuesday, 2/16/99 Chapter 7

Thursday, 2/18/99 Exam 1

Tuesday, 2/23/99 Chapter 8

Thursday, 2/25/99 Chapter 5

Tuesday, 3/2/99 Spring Break

Thursday, 3/4/99 Spring Break Chapters 9, 10

Tuesday, 3/9/99 Chapters 11,12

Thursday, 3/11/99 Chapter 13

Tuesday, 3/16/99

Thursday, 3/18/99 Chapter 2

Tuesday, 3/23/99

Thursday, 3/25/99 Chapter 2

Tuesday, 3/30/99

Thursday, 4/199 Easter Break

Tuesday, 4/6/99

Thursday, 4/8/99

Tuesday, 4/13/99

Thursday, 4/15/99 Exam 2

Tuesday, 4/20/99

Thursday, 4/22/99

Tuesday, 4/27/99 Chapter 8

Thursday, 4/29/99 Chapter 5

Tuesday, 5/4/99 Lab

Thursday, 5/6/99 [Access project due] [Comparative analysis due] [Oral reports due]

Monday, 5/10/99 Comprehensive Final Exam 3:15 p.m.