IMS2805 Systems Design and Implementation , Unit Information Guide (Semester 1, 2006)

Chief Examiner Dr Peta Darke
Lecturers
Caulfield : Dr Peta Darke
Outline

This unit will further the student's knowledge of the traditional systems development lifecycle, with a focus on the design and implementation phases. By the end of the unit, the student will know the principles of how to design and implement a system, and will have experience in using the basic structured techniques commonly used in these phases.

The unit will introduce students to the nature of systems design and implementation as phases within the systems development process.

Topics include:

  • Structured design and implementation principles and outcomes: the unit will identify and describe the basic requirements for good systems design and implementation. It will outline the outcomes which they should deliver, and their importance to the systems development process
  • Structured design and implementation tasks: the unit will give an outline of the main tasks which are typically required in the design and implementation phases of systems development, and the knowledge and skills needed to do them
  • Structured design and implementation techniques: the unit will introduce a variety of structured design techniques for specific information system elements, and give students practical experience in using these techniques to design elements of a simple business system
  •  

    Objectives Knowledge and Understanding

    C1. Understand the purpose and objectives of the systems design and implementation phases of the structured systems development lifecycle, and the activities which they involve

    C2. Know the main techniques which are used in systems design and implementation, and the purpose for which each is used

    C3. Understand the key issues involved in systems design and implementation

    Attitudes, Values and Beliefs

    A1. Recognise the value of a systematic team-based approach to the development of information systems

    A2. Recognise the importance of the systems design and implementation phases of the structured systems development lifecycle

    A3. Recognise the strengths and weaknesses of basic techniques for systems design and implementation

    Practical Skills

    P1. Determine design and implementation requirements and identify a suitable approach for design and implementation of a simple business system

    P2. Use basic design techniques in the development of elements of an information system

    P3. Prepare and present a design specification for a simple business system

    P4. Prepare and present an implementation plan for a simple business system

    Relationships, Communication and TeamWork

    S1. Be able to work as part of a team responsible for carrying out systems design and implementation for a business system

    Prerequisites Before attempting this unit you must have satisfactorily completed 

    IMS1805, IMS1906, IMS1907 or equivalent. You should have knowledge of

     

  • IMS1805 will provide students with basic knowledge of systems analysis, modelling techniques for describing systems, and the nature, form and purpose of a system requirements specification; this unit will build on these concepts to show how a system design derives from its specification at the analysis phase.
  • IMS1906 will provide students with an understanding of computer programming principles and basic programming techniques; this unit will draw on this conceptual understanding of programming as the basis for identifying the requirements for a program design specification
  • IMS1907 will provide students with an understanding of the principles of database and database modelling; this unit will draw on this understanding as the basis for identifying the requirements for a database design specification.
  •  

    Unit relationships IMS2805 is a core unit in  the Bachelor of Information Systems. Before attempting this unit you must have satisfactorily completed

    IMS1805, IMS1906, IMS1907 or equivalents

    You should have knowledge of

     

  • IMS1805 will provide students with basic knowledge of systems analysis, modelling techniques for describing systems, and the nature, form and purpose of a system requirements specification; this unit will build on these concepts to show how a system design derives from its specification at the analysis phase.
  • IMS1906 will provide students with an understanding of computer programming principles and basic programming techniques; this unit will draw on this conceptual understanding of programming as the basis for identifying the requirements for a program design specification
  • IMS1907 will provide students with an understanding of the principles of database and database modelling; this unit will draw on this understanding as the basis for identifying the requirements for a database design specification.
  •  

    Texts and software

    Required text(s)

    None required.

    Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

    Hardware requirements:

    Students studying off-campus are required to have the minimum system configuration specified by the faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook.

    Recommended reading

    Hoffer, J.A., et al. (2002). Modern Systems Analysis and Design,  (3rd  edition) Addison-Wesley, Reading MA, USA.

    Whitten, J.,Bentley, L. & Dittman K. (2001) Systems Analysis and Design Methods (5th edition), Irwin McGraw-Hill.


     Brooks. F. (1995). The mythical man-month. Addison-Wesley
  • Dahlbom B & Mathiassen L, (1993). Computers in context: The philosophy and practice of systems design. Blackwell
  • Nielsen J, (2000). Designing web usability. New Riders
  • Page-Jones M, (1999). Fundamentals of object-oriented design in UML. Addison-Wesley
  • Page-Jones M, (1988). The practical guide to structured systems design. Prentice Hall
  • Preece J Rogers Y & Sharp H. (2002). Interaction design. Wiley
  • Yourdon E & Constantine L, (1986). Structured design: Fundamentals of a discipline of computer program and system design
  •  

    Library access You may need to access the Monash library either personally to be able to satisfactorily complete the subject.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.
    Study resources

    Study resources for IMS2805 are:

    Lecture notes, tutorial exercises and assignment specifications will be available on the unit website.

    http://www.infotech.monash.edu.au/units/ims2805/study

    Structure and organisation

    Week

    Topics

    Study Guide

    1 Introduction and review: concepts of systems development, SDLC
    2 Systems design: selecting design options
    3 Systems design: interface design
    4 Systems design: interface design continued
    5 Systems design: process and task design
    6 Systems design: data design
    7 Systems design: system architecture
    Non-teaching
    8 Systems design: preparing design specifications
    9 Systems implementation
    10 Alternative strategies for systems implementation
    11 System documentation and automated development tools
    12 Post implementation: review and maintenance
    13 Revision
    Timetable

    The timetable for on-campus classes for this unit can be viewed in Allocate+

    Assessment

    Assessment for the unit consists of 2 assignments with a weighting of 40% and an examination with a weighting of 60%. Read this section VERY carefully.

    Assessment Policy

    To pass this unit you must:

    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, if any: 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’.

    Your score for the unit will be calculated by:

    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, if any: 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.

     

    Assessment Requirements

    Assessment

    Due Date

    Weighting

    Assignment 1 - Group Assignment: Interface Design 3rd April, 2006 15 %
    Assignment 2 - Group Assignment: Implementation of a Prototype 22 May,2006 25 %

    Assignment specifications will be made available on the IMS2805 website. Information about assignments will be published on the Unit's Notices Newsgroup.

    Assignment Submission Methods

    Submit the assignment to your tutor by the date specified in the assignment requirements with the appropriate cover sheet correctly filled out and attached. The due date is the date by which the submission must be received.

    Extensions and late submissions

    Late submission of assignments

    Late assignments submitted without an approved extension may be acceptedTotal 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

     

     

    This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment. 

    Extensions

    It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting 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.

     

    Grading of assessment

    Assignments, and the unit, will be marked and allocated a grade according to the following scale:

    HD High Distinction - very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
    In the 80+% range of marks for the assignment.
    D Distinction - high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
    In the 70-79% range.
    C Credit - sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
    In the 60-69% range.
    P Pass - acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
    In the 50-59% range.
    N Not satisfactory -  failure to meet the basic requirements of the assessment.
    Below 50%.

    We will aim to have assignment results made available to you within two weeks after assignment receipt.

    Feedback Feedback to you

    You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.

    Feedback from you

    You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.

    And if you are having problems

    It is essential that you take action immediately if you realise that you have a problem with your study. The semester is short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.

    Plagiarism and cheating

    Plagiarism and cheating are regarded as very serious offences. In cases where cheating  has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.

    In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work. 

    When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer. 

    Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.

    Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.

    Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.

    Communication

    Notices

    Consultation Times

    Consultation times are yet to be finalised and will be posted on the unit website by start of semester.

    If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:

    Dr Peta Darke
    Senior Lecturer
    Phone +61 3 990 32416

    All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.

    Last updated: Feb 27, 2006