DeVry University

6600 Dumbarton Circle, Fremont, California

Course Syllabus (2005 Fall Semester, Oct – Feb)

Course Title: Business Systems Programming I with Lab

Course No: CIS430 Contact Hours: 4 Credit Hours: 4

Course No: CIS430L Contact Hours: 2 Credit Hours: 1

Course Instructor: Dr. George Lai Office Phone: 510 574-1133

E-mail Address: [email protected]

Office Hours: Tuesdays, Wednesdays & Fridays 10:00am – 11:00am

Thursdays 3:00pm – 4:00pm

Class Meetings: Tuesdays 8:00 am to 9:50pm Rm217

Wednesdays 8:00 am to 9:50am Rm217

Fridays 8:00 am to 9:50am Rm217

Course Description

Building on analysis, programming and database skills developed in previous courses, this course introduces students to fundamental principles and concepts of developing programs that support typical business processing activities and needs such as transaction processing and report generation. Students develop business-oriented programs that deal with error handling, data validation and file handling.

Prerequisite: CIS-349 / 6-0-5

Terminal Course Objectives

1. Given a business systems application requiring reading data from an existing sequential file and producing formatted, printed output: design, code and document a program to implement the application.

2. Given a business systems application program: compile, test and debug the program to eliminate syntax errors, logic error, due to unexpected hardware and software events, and ensure the program executes according to specifications.

3. Given a business systems application that requires input of data from a given file, the manipulation of that data and formatted printed output: design, code and document a program to implement the application.

4. Given a business systems application requiring data validation, such as a customer file update: design and code a program that validates the data and creates error and valid data listings.

5. Given a business systems application requiring the transformation of user data from a file by table (array) processing, such as creating an employee’s payroll data by using tax tables based on employee gross income, marital status, and number of deductions to produce a payroll report: design and code a program that reads the file, transforms the data and produces the report.

6. Given a business systems application requiring a sorted customer file: design and code a program that sorts the file and creates output in sorted order.

7. Given a business systems application requiring detail reporting and summarization of sorted user data, such as creating a sales report from a sorted customer file, involving control break logic: design and code a program that produces a report that includes both detail lines and control totals in the appropriate format.

8. Given a more complex business systems application requiring multilevel control breaks, such as creating a sales report from a sorted sales transaction file with control breaks by salesperson within location: design and code a program that produces a report that includes totals for each control level and final totals at the end in the appropriate format.

9. Given a business systems program involving the processing of sequential input master and transaction files, such as developing and maintaining an employee master file from employee transaction records: design and code Java program instructions to maintain the master file (using ADD, CHANGE and DELETE transaction processing) and generate valid transactions and an error listing.

Schedule Plan

Week	Topics	TCO	Reading	Lab	Due
1	Review of console input & output	1, 2	Ref: Chaps 1-3	#1a	Friday Week 1
2	Strings, Class & Inheritance	1, 2	Ref Chaps 4-6	# 2a,b	Friday Week 2
3	Window program with label	3	Text Chaps 1-3	# 3a,b	Friday Week 3
4	Window program with text field	4	Text Chaps 4-6	# 4a,b	Friday Week 4
5	Window program with buttons	3, 4	Text Chaps 7-9	# 5	Friday Week 5
6	Window program & Check Box	3, 4	Text Chaps 10-11	# 6a, b	Friday Week 6
7	More on Check Boxes	4, 5	Text Chaps 12-13	# 7	Friday Week 7
8	Review and Midterm		Review and Test	#8	Friday Week 8
9	Window and Radio Buttons	5, 6	Text Chaps 15-17	# 9	Friday Week 9
10	Use of Menu Bar	7	Text Chaps 18-19	# 10a,b	Friday Week 10
11	Window Application	8	Text Chap 24	#11	Friday Week 11
12	SAF file & RAF files	4, 9	Text Chaps 25-26	Proj 12	Friday Week14
13	Web Application	9	Text Chaps 29-30	#13	Friday Week 13
14	More Web Application & Review	9	Text Chap 31	#14	Friday Week 14
15	Final		All Chaps Covered

Text Book

Deitel & Deitel

Simply Java Programming ISBN 0-13-142648-6

Prentice Hall, Upper Saddle River, New Jersey 07458

Ref Book

Daniel Liang

Introduction to Java Programming, Second Edition, ISBN 0-13-033364-6

Prentice Hall, Upper Saddle River, New Jersey 07458

Quick Start Java Labs. Liu, Lin, Neiman, E-Publication Company, ISBN 097062851X

Grading Policy

Quizzes & Examinations 50%

Lab Work 20%

Final 30%

Grade:

A >= 90

90 < B <= 80

80 < C <= 70

70 < D <= 60

F < 60

Attendance and Classroom Policy

All students are expected to attend all their scheduled class sessions.

No drinks and food are allowed in class.

Attendance and Class Participation

According to DeVry policy, each student is required to attend every lecture in the course.

If a student misses a lecture, then it is the responsibility of the student to determine what work was missed.

Be aware that some exam material may come from lectures, in-class assignments, and class discussion that are not covered in your text. You are responsible for notifying your instructor of planned absences, and for fulfilling course requirements missed during an absence.

Academic Integrity

Working with your classmates to discuss and solve the homework is strongly encouraged. However, the submitted solutions must be your own work, using your own words. Academic misconduct (i.e. cheating, plagiarism, etc.) will NOT be tolerated with regards to labs, homework assignments, quizzes or exams during the course! If a student violates the academic integrity policy by gaining advantage over others through unfair means, he or she will earn a non-pass grade. All students are expected to follow the academic honesty policy.

What IS cheating?

Sending another student your entire or any portion of your source code.
Leaving your source code within an open area, or on a computer that is accessible to other students.
Showing another student your source code for the purposes of copying and/or “to see exactly how you did it”.
Receiving any portion of another student’s source code in any manner listed in (1-3).

What is NOT cheating?

Helping another student find logical and/or syntactical bugs/errors in their program (not do it for them)
Receiving help from another student by allowing that student to help you (not do it for you) find logical and/or syntactical bugs/errors in their program.

Student Academic Integrity Policy

All students are expected to follow the academic honesty. Academic honesty is violated when students gain advantage over other students through unfair means.

When students violate the academic honesty, they get a non-passed grade.

For more details, refer to DeVry Student Handbook.