[Monash Home][Monash Info][News and Events][Campuses and Faculties] [Monash University]
SiMS Home
SiMS HomeAbout UsCourses & SubjectsStaffResearchContact
SiMS Home
 
Handbook   Overview   Lectures   Tutorials   Readings   Assessment   Staff

Faculty of Information Technology, School of Information Management and Systems
Semester 2, 2005

UNIT OUTLINE:

CSE1205, Information Systems 2

IMS1002, Information Systems 2

DOWNLOAD UNIT OUTLINE HERE (Outline.doc) (Outline.pdf)

Handbook entry:

 

 

 

The Handbook entry for CSE1205 can be found at: http://www.monash.edu.au/pubs/handbooks/subjects/cse1205.html

The Handbook entry for IMS1002 can be found at: http://www.monash.edu.au/pubs/handbooks/subjects/ims1002.html

Unit webpage:

http://www3.sims.monash.edu.au/subjects/cse1205

http://www3.sims.monash.edu.au/subjects/ims1002.html

Lecturers:

 

 

 

 

Barry Atkinson
Room S4.01 (Level 4, Building S)
Caulfield Campus)
Phone: 9903 2399
barry.atkinson@infotech.monash.edu.au

Faculty of Information Technology (South Africa)
Phone: +21 11 950 4036

Tutors:

 

 

 

Barry Atkinson
barry.atkinson@infotech.monash.edu.au

Katherine Knight
katherine.knight@infotech.monash.edu.au

Yuzhou Lin
yuzhou.lin@infotech.monash.edu.au

Contacting staff:

 

Outside the scheduled class contact hours, you can contact teaching staff by email, phone, during their consultation hours (available on unit webpage or at SIMS Frontdesk) or by making an appointment.
If you need a staff member urgently and are unable to contact them, please contact:
SIMS Frontdesk, Level 7 – Building S, Ph: 9903 2208

Aim:

 

To introduce students to the relative complexity of information requirements, systems analysis and design within a business organisation, and to introduce students to the concepts, formal
techniques, tools and methods used in the analysis, design and implementation of information systems

Objectives:

 

 

 

At the completion of this unit the students will have knowledge of:

  • The phases, activities and deliverables of the system development life cycle
  • The basic techniques of initiation, systems analysis, design and implimentation
  • The roles and responsibilities of the systems analyst

Have an understanding of:

  • The ourpose of each phase, activity and deliverable of the development life cycle and their nimportance to the overall process of systems development
  • The way in which the need for different models used in the system development process arise out of differences in the system development environments
  • The place and use of some of the primary techniques of initiation, analysis, design and implientation within the system development process
  • The roles and responsibities of the systems analyst within each phase of the systems development life cycle, and the attibutes characteristics, and competencies needed by the systems analyst in order to carry out their tasks and responsibilities successfully

Have the skills to:

  • Perform an analysis and design for a specific case study using the methods, tools and techniques of structured approaches to the development of information systems
  • Argue the need for different models during the systems development process
  • Develop requirements specifications and generate design alternatives, test strategies and implementation plans

Have developed attitudes which enabe them to:

  • Develop appropriate models for the analysis and design of a proposed system
  • Practice and communicate the roles and responsibilities of the systems analyst during the system development process
Pre-requisite knowledge :

Completion of IMS1001/CSE1204 Systems Analysis and Design 1 or equivalent

Texts and software:

Hoffer, J.A., George, J.F. and Valacich, J.S. (2004) Modern Systems Analysis and Design (4th edition) Pearson Prentice Hall, New Jersey, USA.

Recommended texts:

 

 

 

 

 

 

 

 

 

Alter. S. 1996. Information Systems: A Management Perspective (2nd
edition) Benjamin-Cummings Publishing Company. Meno Park: CA, USA.

Checkland, P.B. 1993. Systems Thinking, Systems Practice John Wiley &
Sons, Chichester. England.

Combs, MR. 1995. Information Systems for Business Management Pitman Publishing, London. England,Curtis, G. 1998,

Business Information Systems: Analysis, Design and Practice (3rd edition) Addison-Wesley Longman Publshing Company, 1Harlow, England.

Gelinas, U.J., Sutton, S..G. and Oram, A.E, 1999. Accounting Information Systems (4th edition) South-Western College Publishing, Cincinnati, USA.

Hoffer, J.A., George, J.F. and Valacich, J.S. (2004) Modern Systems Analysis and Design (4th edition) Pearson Prentice Hall, New Jersey, USA.

Schön, DA 1991. The Reflective Practitioner: How Professionals Think in Action. Arena Ashgate Publishing Lld. Aldershot, England.

Whitten, J.L., Bentley, L.D., and Dittman, K.C. (2001) Systems Analysis and Design Methods, 5th ed. New York: Irwin/ McGraw Hill

Study materials:

 

It is essential for all students to have a textbook or access to a copy of it.
We provide:
• Assignment specifications
• Lecture Notes available for download from www.
• Sample examination paper (previous years) through Library.

Lecture Outline:

WEEK

LECTURE TOPIC

TUTORIAL TOPIC

ASSIGNMENT

Week 1

Introduction and Review of SDLC

No Tutorial Week 1

 

Week 2

Data Modelling Entity Relationship Diagrams

Tutorial: Review of the SDLC

 

Week 3

Data Modelling Entity Relationship
Diagrams

 

Tutorial: Entity relationship modelling

 

Week 4

Detailed Data Modelling attribute collection and normalisation

 

Tutorial: Entity relationship modelling continued  
Week 5

Normalisation

 

Tutorial: Normalisation of data  

Week 6

Review of Process Modelling structured design, design of processes and procedures

 

Tutorial: Normalisation of data - continued

 

Week 7

Generating Design Alternatives System Architecture Overview

 

Tutorial: Generating Design Alternatives

System Architecture Overview

 

Week 8

Interface Design

 

Tutorial: Interface Design - Forms and Reports

Assignment 1: Report due

Week 9

Alternative Development Strategies

 

Tutorial: Interface Design

 

Week 10

Implementation

Tutorial: Alternative Development Strategies

 

  September 26 30 Mid-semester break    

Week 11

 

Maintenance


Tutorial: Alternative Development Strategies and Implemetation Issues

 

Week 12

The Initiation Phase

Tutorial: Implemetation Issues and Maintenance

 

Week 13

Revision

Tutorial: Revision

Assignment: System Interface Design - due

NB. This information is subject to change

 

Workload:

 

 

 

 

 

This is a six point unit which, according to University guidelines, requires you to spend 12 hours per week (a total of at least 156 hours per semester).
The anticipated workload is:
This is a six point unit which, according to University guidelines, requires you to spend 12 hours per week (a total of at least 156 hours per semester).
The anticipated workload is:
• 1 hour preparation for lecture
• 2 hours per week lecture
• 1 hour preparation for tutorial
• 2 hours per week tutorials
• 4 hours per week preparation and assignment
• 2 hours per week reading

Assessment:

 

 

 

 

 

 

 

 

 

 

The assignments (40% weighting) and a three hour examination (60% weighting) will be used to assess whether you have achieved the objectives of this subject. Three individual assignments (total assessment value 40%)

Assignment Task 1, Value 25%, Due Weeks 8 , Data Requirements and Data modellling
Assignment Task 2, Value 15%, Due Week 13, User Interface design and User Manual preparation

Assignments should be delivered during tutorial sessions on or before the due week. Late submissions will be penalised at the rate of 5% per day overdue. If you believe that your assignment will be delayed because of circumstances beyond your control such as illness you should apply for an extension before the due date. Medical certificates or certification supporting your application may be required.

Note:
• Assignments in this unit are no less important than those of other units. Your inability to manage your time or computing resources will not be accepted as a valid excuse. (Several assignments falling due at the same time is often unavoidable.)
• Backup copies are required to be made of all assignments and retained for 12 months, in case of loss.
• Hardware failures are not normally recognised as a valid reason for obtaining an extension or handing in a late assignment.

Formal supervised assessment:

 

 

A "closed book" examination, 3 hours, (assessment value 60%).

The formal supervised assessment for this unit will be an exam scheduled in the formal examination period following the last week of semester. You are required to be available for the exam and any necessary supplementary assessment procedures until the end of the assessment period. Alternative times for exams will not be approved without a medical certificate for a significant illness, or equivalent evidence.) The examination will test to see whether you have met the objectives of this subject.

NOTE:

 

 

 

You must perform satisfactorily on both the examination and the assignments in order to pass this subject.In order to pass the subject, students must obtain at least 50% of the available marks for the subject. In addition, there is a hurdle requirement that students must obtain at least 40% of the marks allocated for assignment work AND at least 40% of the marks allocated for the examination. If a student fails one of the hurdle requirements a fail mark up to a maximum of 44% will be returned to the Board of Examiners, even if the numeric total of a student’s mark is greater than 44%.

Assessment Notes:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1 Acknowledgment of sources
Each time you complete any assessment, please refer to and make yourself familiar with the most current information regarding acknowledgement of sources, plagiarism and academic conduct contained in the SIMS Policy website.
http://www.sims.monash.edu.au/policies


2. Assignments

2.1 Standards for presentation
All printed assignment work must be word processed and meet the standards set out in the assignment. Refer also to the School of Information Management and Systems guidelines for writing assignments for additional information on presentation standards:
http://www.sims.monash.edu.au/resources/style.html

2.2 All assignments must include an appropriate signed SIMS assignment cover page.

See the SIMS web site for downloadable (PDF) copies of SIMS assignment cover pages
http://www.sims.monash.edu.au/resources/assessment.html

2.3 Extensions
If you believe that your assignment will be delayed because of circumstances beyond your control such as illness, you should apply for an extension prior to the due date. All applications for extensions must be made in writing to your lecturer. Medical certificates or other supporting documentation will be required.
Late assignments submitted without an approved extension may be accepted at the discretion of your lecturer, but will be penalised at the rate of 10% of total assignment marks per day (including weekends). Example:
Total marks available for the assignment = 100 marks
Marks received for the assignment = 70 marks
Marks deducted for 2 days late submission (20% of 100) = 20 marks
Final mark received for assignment = 50 marks


2.4 Submission of assignments
Assignments should be received by your tutor on or before the due date. In the absence of other instructions, all assignments are to be submitted to your tutor during your allocated tutorial.
2.5 Return of assignments
Assignments will either be returned in specified tutorials during semester or via the SIMS Frontdesk collection system outside semester.
In general, assignments will be returned within two to three weeks of the due date.


3 Student Academic Grievance Procedure

If you have a concern or issue about aspects of your assessment or other academic matters, you are encouraged to follow the SIMS Student Academic Grievance Procedure: http://www.sims.monash.edu.au/policies

4. Pass requirements
The 40% rule applies to units and determines the final result for a student where the student's performance in either the examination or assignment component of the unit is unsatisfactory. Students need to be aware of the 40% rule which is:
In order to pass a unit, a student must gain all of the following:
• at least 40% of the marks available for the examination component: i.e. the final examination and any tests performed under exam conditions, taken as a whole
• at least 40% of the marks available for the assignment component: i.e. the assignments and any other assessment tasks (such as presentations) taken as a whole
• at least 50% of the total marks for the unit
Where a student gains less than 40% for either the examination or assignment component, the final result for the unit will be no greater than ‘44-N’.

5. Grades
The grades awarded by the Faculty of Information Technology are:
Grade Code Marks
High Distinction HD 80-100
Distinction D 70-79
Credit C 60-69
Pass P 50-59
Fail N 0-49
Near Pass NP 45-49 (may be awarded by Board of Examiners only)
Deferred DEF -
Withheld WH -

 

 
HelpContactsSite MapStaff DirectorySearch

Return to the Top of the PageMonash University ABN 12 377 614 012. Copyright 1994-2001 Monash University - Caution - Privacy
SIMS is part of the Faculty of Information Technology -

Authorised by: Head of School. Maintained by: Barry Atkinson