IMS 1502 Studio 2: Information Systems Foundations 2

1
IMS 1502Studio 2 Information Systems
Foundations 2

• Seminar 1
• Introduction to IMS1502
• Specifying a System
• Semester 2, 2005

2
Seminar Objectives

• At the end of this seminar you should
• understand the administration, objectives and
  structure of IMS1502
• be aware of the content outline of the unit
• understand the purpose of the System Requirements
  Specification

3
Overview

• Introducing the academic staff
• Tutorial staff
• Unit objectives
• Semester structure
• Text books
• Workload
• Assessment
• Plagiarism
• Your responsibilities
• Unit framework

4
Unit Staff

• Studio Academics
• Chris Gonsalvez (Unit Leader)
• S7.22, ext. 32554, chris.gonsalvez_at_infotech.monash
  .edu.au
• Kathy Lynch
• S4.04, ext. 32583, kathy.lynch_at_infotech.monash.edu
  .au
• Steve Wright
• S7.14, ext. 32994, steve.wright_at_infotech.monash.ed
  u.au
• Tutors
• Paschalis Kalogeras
• T1.26, paschalis.kalogeras_at_infotech.monash.edu.au
• Ken Lin
• T1.26, ken.lin_at_infotech.monash.edu.au
• Natalia Tame
• T1.26, natalia.tame_at_infotech.monash.edu.au

5
IMS1502 Unit Objectives

• IMS1502 aims to
• apply and integrate fundamental knowledge from
  other first year units in the BIS program
• extend students' skills in the use of
  productivity applications
• expose students to network fundamentals
• provide opportunities for students to work in
  small groups and further develop their skills in
  system development, communication, team work and
  project management

6
Semester structure

• Seminars
• Monday 3 pm 4 pm, Building S Link Theatre
• Purpose
• Studio
• As per your allocated studio
• Purpose
• Academic tutor roles
• Past experiences
• Student attendance participation

7
IMS1501 Performance

• Exam Mark

• Unit Final Mark

41 lt 50 Fail
28 50 59 Pass
24 60 69 Credit
7 70 Distinction
15 N
11 P
42 C
24 D
4 HD
4 WH
8
Studio sessions

• All studio sessions will be held in Studio T 1.26
• Studio 4 Tuesday 2 pm 5 pm
• Steve Wright Natalia Tame
• Studio 2 Wednesday 1 pm 4 pm
• Kathy Lynch Ken Lin
• Studio 6 Thursday 11 am 2 pm
• Chris Gonsalvez Paschalis Kalogeras
• Studio academics will attend one hour of their
  studio session

9
Textbooks

• Recommended texts
• Martin, E.W., Brown, C.V., DeHayes, D.W., Hoffer,
  J.A. and Perkins, W.C. (2004) Managing
  Information Technology, 5th ed. New Jersey
  Prentice Hall International, Inc. ISBN
  0-13-043244X
• Benson, S. and Standing, C. (2001) Information
  Systems A Business Approach, John Wiley and
  Sons, Singapore. ISBN 0-470-80003-8
• Eunson, B. (2004) Communicating in the 21st
  Century, John Wiley and Sons. ISBN 0-470-80349-5

10
Anticipated Workload

• 1 hour seminar
• 3 hour per week studio session
• 8 hours per week reading, preparation for
  seminars and studio sessions, and completion of
  assignment work

11
Assessment

• IMS1502 is a 6-point, single semester unit.
• The assessment comprises
• 70 - assignment - combination of individual
• and group items
• 10 - reflective work
• 20 - examination
• Rules
• a pass requires a final mark of 50 or more
• hurdle - you must earn a minimum of 40 for the
  exam AND a minimum of 40 for the assignments
• see unit outline for further details

12
Example of assessment hurdle

• Practical mark 60/80 75
• Exam mark 6/20 30
• Total mark 66/100 FAIL !!
• Because the Exam mark is less than 40 the
  officially recorded result will be a failed
  result of 44

13
Exam

• The exam will be held during the formal
  examination period
• Details about the format and content of the exam
  will be discussed in Week 13 Revision session.
  

14
Plagiarism/cheating

• The university and the school have various
  policies regarding plagiarism
• http//www.sims.monash.edu.au/resources/index.html
  
• My advice Dont do it
• You will get caught

15
Academic grievance

• If you have a problem LET US KNOW
• Tutor
• Studio Academic
• Studio Year Leader (Ms. Chris Gonsalvez)
• Director of Undergraduate Studies (Dr. Kathy
  Lynch)
• Associate Head of School (Ms. Chris Gonsalvez)
• Head of School (Assoc. Prof. Graham Farr)
• We cannot help if we dont know about it
• Please let us know before it is too late
• The university and the School have various
  policies regarding academic grievance
• http//www.sims.monash.edu.au/resources/index.html
  

16
In Conclusion Your responsibilities

• You are responsible for your own learning
• Lessons learnt in this unit will serve you well
  throughout your course
• We help you with information and services
• You must
• read widely, ask questions, think, actively
  participate
• practice what you learn
• manage your time well
• ask when you do not know
• have fun and enjoy your learning this is the
  best time of your life (really)

17
What is this unit about?

• Systems Development
• Analysing the System
• Data Gathering interviewing, document analysis
• Writing the specification, promotional documents
• Presenting to the stakeholders
• Designing the System
• Information and IT Architecture
• Human Computer Interaction Principles,
  Prototyping
• Managing the Process
• Project Management
• Quality

18
IMS1502 Unit framework
Documentation
Ethics
Efficiency Tools
Developing Information Systems
System Development Methods
Initiation
Analysis
System Development Life Cycle
Information System Fundamentals
Design
Implementation
Review
Maintenance
Project Management
Group work
Communication
19
Specifying a System

• When specifying a system we try to
• understand WHAT it is that the user wants
• show them that we understand what it is that they
  want
• understand/establish the scope of the system
• the constraints that the system must work within
• Provide a foundation on which to design and build
  the system
• We do this by producing a System Requirements
  Specification during the Analysis phase of the
  SDLC

20
Systems requirements include

• functional aspects
• the activities that the system must perform
  that is, the business uses to which the system
  will be applied
• (Satzinger et al. 2004 119)
• non-functional aspects
• technical matters, performance, usability,
  reliability, security
• (Satzinger et al. 2004 120)

21
System Requirements Specification Typical
contents

• Front matter
• Introduction
• System overview
• Functional requirements
• Data requirements
• Quality requirements
• Constraints physical, business, technical,
  legal
• Appendices
• Ref http//www.donald-firesmith.com/index.html?Co
  mponents/WorkProducts/RequirementsSet/SystemRequir
  ementsSpecification/SystemRequirementsSpecificatio
  n.htmlContents

22
Functional requirements analysis

• In many ways, the functional specification is
  the most important document we produce during
  the Analysis phase (Blethyn Parker 1990 67)
• Requirements determination is the least
  well-defined phase in the systems development
  process. One reason for this is that it is the
  least technical, and therefore the most
  organisation dependent another is that
  requirements frequently change once systems
  development is underway (Flynn 1998 131)

23
Functional requirements analysis entails

• Studying the system
• Determining the logically required tasks
• Determining the most appropriate solution(s)
• Presenting tentative solutions to users
• (This will be covered in IMS1805)

24
Assignment

• Preparing a Requirements specification will be
  the focus of the first part of your assignment

25
References

• IMS1502 Unit Outline
• SIMS home page http//www.sims.monash.edu.au/
• Benson, S. and Standing, C. (2001) Information
  Systems A Business Approach, John Wiley and
  Sons, Singapore., Chapter 20.
• Blethyn C. Parker, C. (1990) Designing
  Information Systems. London Butterworth-Heinemann
  .
• Flynn, D. (1998) Information systems
  requirements determination and analysis. 2nd
  edition. London McGraw-Hill.
• Martin, E.W., Brown, C.V., DeHayes, D.W., Hoffer,
  J.A. and Perkins, W.C. (2004) Managing
  Information Technology, 5th ed. New Jersey
  Prentice Hall International, Inc. , Chapter 10.
• Satzinger, J. Jackson, R. Burd, S. (2004)
  System Analysis Design in a Changing World. 3rd
  edition. Boston Thomson.