Skip to content | Change text size

M O N A T A R

InfoTech Unit Avatar

FIT2021 Business Process Modelling

Chief Examiner

This field records the Chief Examiner for unit approval purposes. It does not publish, and can only be edited by Faculty Office staff

To update the published Chief Examiner, you will need to update the Faculty Information/Contact Person field below.

NB: This view restricted to entries modified on or after 19990401000000

Unit Code, Name, Abbreviation

FIT2021 Business Process Modelling (21 Sep 2006, 11:59am) [BUS PROC MODELLING (27 Sep 2006, 5:13pm)]

Reasons for Introduction

Reasons for Introduction (21 Sep 2006, 12:56pm)

The Faculty of Business and Economics specifies that BBusCom students with a major in eBusiness are to take four electives from the Faculty of Information Techology offerings. This unit is designed to raise awareness and understanding of the techniques commonly used for carrying out the analysis and specification of requirements for an information system as they might be applied by a business person rather than an application developer. The unit provides a focus on system analysis and design as a communicative process between people with expertise in distinct domains: managers (a specific organisational environment) and application developers/system integrators (information technology), and is oriented to students who see their future in the management domain.

Reasons for Change (26 May 2005, 10:09am)

The introduction of FIT 2001 into the common core, with a pre-requisite of FIT 1004 (DBMS), has created a need for an analysis and design unit suitable for students from other faculties who are interested in gaining a fundamental knowledge and understanding of the disciplinary content areas that underpin the field of information technology.

Role of Unit (26 May 2005, 11:13am)

This unit builds upon the foundation established in FIT 1003 (IT in Organisations) or MKW 1601 (Introduction to eBusiness), and provides pre-requisite knowledge for more advanced units including FIT3021 (Infrastructure for eBusiness) and BEW 3640 (Project Management for Electronic Commerce).

Relationship of Unit (21 Sep 2006, 12:38pm)

Like FIT2001, this unit offers theoretical knowledge and practical application of system analysis and design methodologies. The fundamental differences lie in the assumptions of pre-requisite knowledge and a 'technology for managers' approach. As a 2nd-year core unit, FIT2001 is properly oriented to application development, and can work with the implicit assumption that students have taken 1st-year core units beyond FIT1004 (the specific pre-requisite). This unit has been developed with input from the School of Business and Economics to introduce students with a minimal IT background (including no knowledge of programming at all) to the way IT specialists communicate using standard graphic representations.

Relevance of Unit (26 May 2005, 10:11am)

Information systems analysis and design is clearly considered to be a core competency of the FIT; it is therefore consistent with the Faculty's strategic and educational objectives to offer this to students pursuing degrees in other Faculties.

Objectives

Knowledge and Understanding (Cognitive Domain Objectives) (10 Jun 2005, 1:56pm)

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

  1. The purpose and objectives of the systems analysis and preliminary design phases of the systems development life cycle, and the tasks which are required to carry them out;
  2. The key issues involved in gathering data about requirements, planning and problem definition for information systems;
  3. The main types of modelling techniques which are used in systems analysis (process, data, and object modelling), and the purpose for which each is used;
  4. The core concepts of client/server application design, and the need to maintain familiarity with current application development tools.

Attitudes, Values and Beliefs (Affective Domain Objectives) (26 May 2005, 10:16am)

At the completion of this unit students will have developed attitudes that enable them to:

  • A1. Approach the analysis and preliminary design of information systems
    as a communicative endeavour;
  • A2. Appreciate that a range of valid solutions exist for any given
    problem;
  • A3. Recognise the value of a systematic team-based approach to the
    development of information systems;
  • A4. Apply analytical techniques at different levels of abstraction
    and understand the effect this may have on a system specification;
  • A5. Evaluate alternatives and select an approach that is appropriate
    relative to the task at hand.
  • Practical Skills (Psychomotor Domain Objectives) (26 May 2005, 10:18am)

    At the completion of this unit students will have the skills to:

  • P1. Develop a data gathering strategy as part of an analysis of user
    needs for an information system;
  • P2. Isolate and categorise elements of business practice as business
    rules relevant to the design of a business information system;
  • P3. Interpret basic process, data, and object models of a
    straightforward business system
  • P4. Prepare basic process, data, and object models for a
    straightforward business system
  • P5. Sketch the preliminary design of a client/server application
    based on an analysis model.
  • Relationships, Communication and TeamWork (Social Domain Objectives) (26 May 2005, 10:19am)

    At the completion of this unit students will be able to:

  • S1. Recognise the interdependence and relationships between
    stake-holders in the systems development process (c.f. A4);
  • S2. Approach the analysis and preliminary design of information
    systems as a communicative endeavour (c.f. A1, P2, P4);
  • S3. Explain the value of a systematic team-based approach to the
    development of information systems (c.f. S1, A2, A3).
  • Unit Content

    Summary (23 Jun 2006, 10:22am)

    6 digit ASCED code for the unit: 020305

    This unit will introduce students to the nature of modelling as an analytical and a communicative process, and give a broad overview of the techniques commonly used for carrying out the analysis and specification of requirements for an information system. This unit is designed to raise awareness and understanding of the processes seen principally from the viewpoint of a business person, rather than from that of an information technologist.

    Key tasks in systems analysis will be studied as follows:

    * Data gathering and fact-finding: a review of the main methods used in gathering data about the user requirements for an information system; * System modelling: students will learn to interpret and understand models created with the most common techniques - process, data, and object modelling.

    Key concepts for preliminary design will be studied as follows:

    * Client/server systems: the conceptual division of processing tasks, and the practical implications of alternative schemes in terms of capacity planning and user interface; * Implementation tools: an overview of common development environments and application genenerators.

    Handbook Summary (23 Jun 2006, 10:20am)

    Modelling as an analytical and a communicative process. Introduction to standard analysis and design methodologies applied to business information systems. Data gathering and fact-finding. Process, data, and object modelling. Conceptual division of processing tasks.

    Recommended Reading (26 May 2005, 10:23am)

  • Dennis, A., Wixom, B.H. and D. Tegarden (2005) Systems Analysis and
    Design with UML Version 2.0: An Object-Oriented Approach, 2nd Edition, Wiley.
  • George, J.F., Batra, D., Valacich J.S. and J.A. Hoffer, (2004)
    Object-Oriented System Analysis and Design Prentice-Hall.
  • Hoffer, J.A., George, J.F. and J.S. Valacich (2001) Modern Systems
    Analysis and Design 3rd Edition, Prentice Hall.
  • Maciaszek, L. (2004) Requirements Analysis and System Design,
    2nd Edition, Addison-Wesley.
  • Page-Jones, M. (1988) The Practical Guide to Structured Systems Design
    2nd Edition, Prentice-Hall.
  • Page-Jones, M. (2000) Fundamentals of Object-Oriented Design in UML
    Addison-Wesley.
  • Satzinger, J. W., Jackson, R.B., Burd, S.D. and R. Johnson (2004)
    Systems Analysis and Design in a Changing World, 3rd Edition, Thomsen Course Technology.
  • Teaching Methods

    Mode (26 May 2005, 10:25am)

    Initially available in on-campus mode

    Strategies of Teaching (26 May 2005, 10:25am)

  • Lectures (2 hours per week)
  • Tutorials and Lab exercises (2 hours per week)
  • Assessment through assignments
  • Teaching Methods Relationship to Objectives (26 May 2005, 10:27am)

  • Lectures: C1 through C4, A2, A3, S1.
  • Tutorials: A1, A4, A5, S2, S3
  • Assignments and Lab exercises: P1 through P5.
  • Lectures will support the cognitive objectives by providing an overall theoretical and conceptual picture of systems analysis and the basic techniques which are used to do it. Lectures will support affective and social domain objectives by offering demonstrations to students of the way in which systems analysis contributes to the systems development process.

    Tutorials will include practical exercises and case studies which will require students to discuss and evaluate alternative system analysis approaches. This will support affective and social domain objectives through engaging students in the formulation of solutions to problems in conjunction with peers.

    Assignments and lab exercises will require the students to carry out analytical tasks for straigntforward business systems. These tasks will support the psychomotor objectives by assessing and providing feedback to students about their ability to carry out analytical tasks.

    Assessment

    Strategies of Assessment (26 May 2005, 10:28am)

    Assignments: 40% Final exam (3 hours): 60%

    To pass this unit students must:

  • attempt all assignments and the examination
  • score at least 50% of the possible marks for the unit
  • achieve no less than 40% of the total available marks for the assignments overall
  • achieve no less than 40% of the total available marks for the examination
  • Where a student achieves less than 40% for either the examination or assignment component, the final result for the unit will be no greater than '44-N'.

    Assessment Relationship to Objectives (26 May 2005, 10:29am)

    Assignments will explicitly emphasise the psychomotor objectives, implicitly recognising that these are closely tied to the cognitive and affective objectives.

    The examination will assess the application of knowledge and concepts through factually based questions (cognitive objectives) and questions requiring interpretation/critical evaluation (affective and social objectives).

    Workloads

    Workload Requirement (26 May 2005, 10:30am)

    12 hours per week

    Resource Requirements

    Lecture Requirements (26 May 2005, 10:30am)

    On-campus mode will require lecture rooms with personal computer, data display, and internet connection.

    Tutorial Requirements (26 May 2005, 10:31am)

    Tutorials are listed in Strategies of Teaching above; unlikely requirements are Nil.

    Laboratory Requirements (26 May 2005, 10:31am)

    Laboratory sessions will normally require a lab equipped with the standard operating environment

    Staff Requirements (26 May 2005, 10:32am)

  • 1 EFT lecturer for 2 hours per week for 13 weeks for each unit offering
  • 1 tutor for every 20 enrolled students for 2 hours per week for 12 weeks
  • Software Requirements (23 Jun 2006, 10:48am)

    Software used in FIT2001/FIT2002 will be appropriate for this unit.

    Library Requirements (26 May 2005, 10:34am)

    There are no additional requirements as the unit content is already covered in existing units which are adequately catered for by existing library resources.

    Teaching Responsibility (Callista Entry) (23 Jun 2006, 10:29am)

    The unit will be presented by School of IT staff.

    Interfaculty Involvement (26 May 2005, 10:39am)

    Unit objectives have been developed in conjunction with SBE (Malaysia) HOS and BBusCom course director; they will continue to monitor the detailed design of the unit. Summaries of these discussions are being provided to the SIT (Malaysia) School Education Committee for minuting.

    Interschool Involvement (26 May 2005, 10:47am)

    Staff in Malaysia will take primary responsibility for detailed design and implementation of the unit, in conjunction with relevant staff at GSCIT and other participants in the broader Faculty dialogue regarding service units.

    Prerequisites

    Prerequisite Units (26 May 2005, 10:48am)

    FIT1003 IT in Organizations or MKW1601 Introduction to eBusiness

    Prohibitions (23 Jun 2006, 10:28am)

    FIT2001

    Level (26 May 2005, 10:50am)

    Level 2

    Proposed year of Introduction (for new units) (23 Jun 2006, 10:30am)

    Semester 1, 2008

    Frequency of Offering (26 May 2005, 10:52am)

    Annually, in Semester 1

    Location of Offering (26 May 2005, 10:52am)

    Initially, Malaysia Campus Only

    Faculty Information

    Proposer

    Thomas ODaniel

    Contact Person (26 May 2005, 10:54am)

    thomas.odaniel@infotech.monash.edu.my

    Approvals

    School:
    Faculty Education Committee:
    Faculty Board:
    ADT:
    Faculty Manager:
    Dean's Advisory Council:
    Other:

    Version History

    26 May 2005 Thomas ODaniel Initial Draft; modified UnitName; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RChange; modified ReasonsForIntroduction/RRole; modified ReasonsForIntroduction/RRelation; modified ReasonsForIntroduction/RRelevance; modified UnitObjectives/ObjCognitive; modified UnitObjectives/ObjAffective; modified UnitObjectives/ObjPsychomotor; modified UnitObjectives/ObjSocial; modified Classification; modified UnitContent/Summary; modified UnitContent/RecommendedReading; modified Teaching/Mode; modified Teaching/Strategies; modified Teaching/Objectives; modified Assessment/Strategies; modified Assessment/Objectives; modified Workload/WorkHours; modified ResourceReqs/LectureReqs; modified ResourceReqs/TutorialReqs; modified ResourceReqs/LabReqs; modified ResourceReqs/StaffReqs; modified ResourceReqs/SoftwareReqs; modified ResourceReqs/LibraryReqs; modified ResourceReqs/InterFaculty; modified ResourceReqs/IntraFaculty; modified Prerequisites/PreReqUnits; modified Prohibitions; modified Level; modified DateOfIntroduction; modified Frequency; modified LocationOfOffering; modified FacultyInformation/FIContact
    26 May 2005 Thomas ODaniel modified ReasonsForIntroduction/RRole
    17 Oct 2005 David Sole Added Software requrirements template
    21 Oct 2005 David Sole Updated requirements template to new format
    23 Jun 2006 Thomas ODaniel modified UnitContent/HandbookSummary; modified UnitContent/Summary; modified UnitObjectives/ObjText; modified Prohibitions; modified ResourceReqs/SchoolReqs; modified DateOfIntroduction
    23 Jun 2006 Thomas ODaniel
    23 Jun 2006 Thomas ODaniel modified ResourceReqs/SoftwareReqs
    21 Sep 2006 John Betts
    21 Sep 2006 Thomas ODaniel modified UnitName; modified Abbreviation; modified ReasonsForIntroduction/RIntro; modified ReasonsForIntroduction/RRelation; modified ReasonsForIntroduction/RIntro
    27 Sep 2006 Jean Wee modified Abbreviation

    This version: