SISAT

School of Information Systems and Technology

Faculty of Informatics

                                                                                                                                                              

BUSS201 – User-Centred Information Systems Programming

Subject Outline

Autumn Session 2007

                                                                                                                                                              

Head of School –Associate Professor Peter Hyland, Student Resource Centre, Tel: (02) 4221 3606

 

General Information

 

Dr Ghassan Beydoun

Telephone Number:

4221 4037

Email:

beydoun@uow.edu.au

Location:

40.238

 

Dr Beydoun’s Consultation Times During Session


Day

Time

Thursday

Friday

9:30-11:30

9:30-11:30

 


Subject Organisation

Session:

Autumn session, Wollongong Campus

Credit Points

6 credit points

Contact hours per week:

2hrs lecture, 2 hrs lab

Lecture Times & Location:

Lecture

Fri

13:30

15:30

19.G016

Tutorial Day, Time and Location can be found at:

http://www.uow.edu.au/student/sols/timetables/index.html

 


 

Students should check the subject’s web site regularly as important information, including details of unavoidable changes in assessment requirements will be posted from time to time.  Any information posted to the web site is deemed to have been notified to all students.

 

Content

The aim of this subject is to provide students with an in-depth knowledge of user-centered application design using various visual programming concepts and techniques. The subject will provide students with the opportunity to understand and use the principles of user-centered design and computer-user interface design with visual programming tools and techniques and to understand and use the techniques of Joint Application Development and Rapid Application Development for visual program design. Students will learn to program visually utilising appropriate techniques in a commonly available visual programming environment

 

Objectives

On successful completion of this subject students should be able to: understand and apply various visual programming concepts, tools and techniques as well as the principles of user-centered design and computer-user interface design; develop a Joint and Rapid Application Development project with visual programming tools and techniques.

 

Attendance Requirements

It is the responsibility of students to attend all lectures/tutorials/labs/seminars/practical work for subjects for which you are enrolled.

 

Attendance and participation in lectures, tutorials and web-mediated activities is a requirement for the successful completion of this course.  Failure to do so may result in a fail grade being recorded.  A good indicator of satisfactory attendance is approximately 80% of the allocated contact hours.  Attendance per se is not an assessable component of the course.

 

It should be noted that according to Course Rule 003{Interpretation Point 2 (t)} each credit point for a single session subject has the value of about two hours per week including class attendance.  Therefore, the amount of time spent on each 6 credit point subject should be at least 12 hours per week, which includes lectures/tutorials/labs etc


 



Method of Presentation

In addition to attending the lectures, students are expected to attend a 2 hours lab session every week where they will be exposed to practical exercises that will form part of their assessment.


 


 

Subject Materials

 


Required textbook:

 

Zak, 2004, Microsoft Visual Basic .NET: RELOADED, Thomson.

 

The textbook includes VisualStudio.NET so that you can install that software on your home machine.

 

Recommended Background and Further Reading:

 

  1. Harold, D., 2003. Visual Basic .Net for Windows, Peachpit press
  2. Tsay, J., 2004. Visual Basic .Net Programming: Business Applications with a Design Perspective, Prentice Hall.
  3. Kent, J., 2002. Visual Basic.NET: a beginner’s guide, McGraw Hill.
  4. Koneman P.A., 2004. Visual Basic.NET Programming for Business, Prentice Hall.
  5. Pressman, R. S., 2005, Software Engineering: A Practitioner’s Approach, McGraw Hill.

 


These readings/references are recommended only and are not intended to be an exhaustive list.  Students are encouraged to use the library catalogue and databases to locate additional readings

 
Assessment

This subject has the following assessment components.

Assessment Items & Format

Percentage of Final Mark

Due Date


Lab 1

5%

Week 3 Lab

Lab 2

5%

Week 4 Lab

Lab 3

5%

Week 5 Lab

Midterm

20%

1 hour in Week 6 lectures

Lab 4

10%

Week 7 Lab

Lab 5

10%

Week 9 Lab

Lab 6

10%

Week 11 Lab

Practical test

35%

Week 13 Lab


 


 

Notes on Assessment

 


 

Late submissions are not permitted.  However, students may submit a lab at the start of the following week if the marking queue is too long. A student cannot start next lab until a lab is awarded for the current lab.

Assessments will be marked in the final part of the lab.

 

All lab work is expected to be completed independently.  Plagiarism may result in a FAIL grade being recorded for that assignment.

 

 

 

Special consideration

An extension of time for the completion of an assignment may be granted in certain circumstances.  A request for an extension must be made to the Subject Coordinator via SOLs before the due date.


 

Scaling

Final results in this subject may be scaled. The scaling method that will be used in this subject is as follows.

If E is the student exam mark, and A is the student assignment mark, the student final mark will be determined as follows:

 

if E >= 40% of the maximum exam mark: then student final mark is E + A;

if 35% <= E < 40% of the maximum exam mark: then student final mark is /min/{E+A, 47};

       if E < 35% of the maximum exam mark: then student: final mark is /min/{E+A, 42}.

 

Additional Information

Students must refer to the Faculty Handbook or online references which contains a range of policies on educational issues and student matters.


 

Supplementary Exams

While the School normally grants supplementary exams when the student does not sit the standard exam for an acceptable reason, each case will be assessed on its own merit and there is no guarantee a supplementary exam will be granted. If a supplementary exam is granted the date will be determined by the University via ARD.  You will be notified via SOLS Mail the time and date of this supplementary exam. You must follow the instructions given in the email message.

 

Please note that if this is your last session and you are granted a supplementary exam, be aware that your results will not be processed in time to meet the graduation deadline.

 

Plagiarism

 

When you submit an assessment task, you are declaring the following

1.        It is your own work and you did not collaborate with or copy from others.

2.        You have read and understand your responsibilities under the University of Wollongong's policy on plagiarism.

3.        You have not plagiarised from published work (including the internet). Where you have used the work from others, you have referenced it in the text and provided a reference list at the end ot the assignment.

4.        Plagiarism will not be tolerated.

5.        Students are responsible for submitting original work for assessment, without plagiarising or cheating, abiding by the University’s policies on Plagiarism as set out in the Calendar under University Policies, and in Faculty handbooks and subject guides. Plagiarism has led to the expulsion from the University.

 

This outline should be read in conjunction with the following documents:

Code of Practice - Teaching and Assessment

http://www.uow.edu.au/handbook/codesofprac/teaching_code.html

Key Dates

http://www.uow.edu.au/student/dates.html

Code of Practice - Students

http://www.uow.edu.au/handbook/codesofprac/cop_students.html

Information Literacies Introduction Program

http://www.library.uow.edu.au/helptraining/workshops/ilip/

Acknowledgement Practice Plagiarism will not be tolerated

http://www.uow.edu.au/handbook/courserules/plagiarism.html

Student Academic Grievance Policy

http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8

Special Consideration Policy

http://www.uow.edu.au/handbook/courserules/specialconsideration.html

Code of Practice-Honours

http://www.uow.edu.au/handbook/honourscode.html

Non-Discriminatory Language Practice and Presentation

http://staff.uow.edu.au/eeo/nondiscrimlanguage.html

Intellectual Property Policy

http://www.uow.edu.au/research/researchmanagement/1998IP.html

Occupational Health and Safety

http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf

SISAT Internet Access & Student Resource Centre

http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml

SISAT Computer Usage Rules

http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml

SISAT Style Guide for Footnotes, Documentation, Essay and Report Writing

http://www.sitacs.uow.edu.au/info/current/styleguide.pdf

SISAT Student Guide

http://www.itacs.uow.edu.au/info/current/regulations.shtml

Informatics Faculty Librarian, Ms Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au

SISAT Subject Outlines

http://www.itacs.uow.edu.au/info/current/subject_outlines/