Your SlideShare is downloading. ×
1. Aims
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

1. Aims

3,990
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,990
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Curtin Business School School of Information Systems Analysis (Systems Analysis) 200 Unit Outline Semester 1 2006 Unit Index Number 305477 Hours per Week 4 hours One 1.5-hour lecture Weekly Tuition Pattern + One 1.5-hour tutorial + One 1-hour computer laboratory Credit Value 25 credits 305476 Analysis (Problem Analysis) 150 OR Pre-requisites 305457 Design (User Interface and Web Design) 150 Co-requisites None 010605 Systems Modelling 102 Anti-requisites 013602 Systems Analysis and Design 201 Alternate requisites None Unit Controller Dr Vanessa Chang Unit Controller’s office 408.3040 Unit Controller’s email Vanessa.Chang@cbs.curtin.edu.au Contact Telephone Numbers 9266 4487 School Telephone & Fax Numbers 9266 7685 (tel) or 9266 3076 (fax) Website for Unit Materials http://elearn.cbs.curtin.edu.au Student Consultation Times Available from the school office IMPORTANT NOTICE The Unit Outline (this document) gives the student important information about the unit, aims, outcomes, syllabus, materials, timetable, program and assessment. Note that important general information including policies, expectations, examinations, copyright, referencing, academic misconduct, assistance for communication skills, guidelines for assessment and CV development is available in the CBS Student Handbook and can be downloaded at http://www.cbs.curtin.edu.au/business/student-resources/student-handbook-2005 February 2006 CRICOS provider code 00301J School of Information Systems Page 1 of 15
  • 2. 1. Aims.....................................................................................................................................................................3 2. Outcomes..............................................................................................................................................................3 3. Syllabus................................................................................................................................................................3 4. Materials...............................................................................................................................................................3 5. Timetable of Classes............................................................................................................................................4 6. Program................................................................................................................................................................5 7. Assessment...........................................................................................................................................................9 8. General Information...........................................................................................................................................14 9. Supplementary Instructions and Materials.........................................................................................................14 School of Information Systems Page 2 of 15
  • 3. UNIT INFORMATION 1. Aims The aim of this unit is to equip students with analytical and technical skills that will enable them to carry out the analysis phase of systems development. To achieve this, students will be given a fictional case study and apply the techniques and tools learned in the unit and to produce a Requirements Specification Report. 2. Outcomes 2.1 Learning Outcomes On successful completion of this unit you should be able to: 1. Use appropriate techniques and tools to: a. construct physical and logical process/task models for existing and new systems. b. construct conceptual and logical relational data models. 2. Demonstrate appropriate interviewing techniques with a variety of clients. 3. Demonstrate knowledge of a variety of legacy and contemporary systems development methodologies/techniques. (eg. SDLC, RAD, JAD, Prototyping). 4. Professionally present system development proposals to management. 5. Create a Requirement Specification Report which includes business objectives, an Information Systems specification, and a development plan. 2.2 Professional Skills Outcomes Employers worldwide want graduates who have developed effective work, life, and professional skills. The following skills are relevant to business graduates and are part of the CBS professional skills program. On successful completion of this unit you will have: 1. used your systems analysis skills to identify problem areas and limitations 2. completed a systems requirements report detailing the analysis that you have undertaken, and initiate solutions to overcome the problems 3. presented a summary of your report findings. 3. Syllabus Process modelling and data modelling, a variety of system development approaches tools and techniques using rapid application development, joint application development, and prototyping. 4. Materials 4.1 Texts 1. ESSENTIAL Satzinger, J.W., Jackson, R.B., and Burd, S. D. (2004), Systems Analysis and Design in a Changing World, 3rd Ed., Course Technology, Thomson Learning. 2. OPTIONAL Microsoft Visio Professional 2003, Student Edition 2004, Course Technology, Thomson Learning. 4.2 Software Microsoft Visio will be used in the computing laboratories. School of Information Systems Page 3 of 15
  • 4. 4.3 References In addition to the set textbook(s) the following references will be useful. Most of these references are available in the library. 1. Dennis, A. & Wixom, B. H. (2000). Systems Analysis and Design, John Wiley & Sons Inc. http://www.wiley.com/college/dennis/sad 2. Hawryszkiewycz, I. (1998). Introduction to Systems Analysis and Design, 4th ed. Prentice Hall. 3. Kendall, J.E. and Kendall, J.E., (2001), Introduction to Systems Analysis and Design, 5th ed., Prentice-Hall. 4. Lejk, M. & Deeks, D. (2002). An Introduction to Systems Analysis Techniques, Pearson Education Limited. 5. McConnell, S (1999). Rapid Development – Taming Wild Software Schedules, Microsoft Press. 6. Robinson, B. & Prior, M. (1995). Systems Analysis Techniques. International Thomson Computer Press. 7. Schwalbe K, (2002). Information Technology Project Management, 2nd Ed. Course Technology. 8. Shelly, G.B., Cashman, T.J., & Rosenblatt, H.J. (2003) Systems Analysis and Design, Fifth Edition, Thomson Course Technology, Boston, MA 9. Simsion, G. (2001). Data Modeling Essentials. Analysis, Design, and Innovation. The Coriolis Group. 10. Valacich S., George J. F., & Hoffer J. A. (2001), Essentials of Systems Analysis and Design, Prentice Hall. ISBN 0-13-018373-3, http://cw.prenhall.com/bookbind/pubbooks/valacich/ 4.4 Other Resources All assignments, team reports, and team progress notes are expected to be word-processed. You are also expected to use Powerpoint software or similar for all oral presentations. All lecture slides, tutorial exercises, assignment cover sheets, marking guides, and general announcements about the unit are available from the Analysis 200 Blackboard site. Please access the unit’s Blackboard regularly to check for updates about the unit. 5. Timetable of Classes Refer to website: http://www.cbs.curtin.edu.au for updates Type and Code Day Start Finish Room Lecture 01 Tuesday 11:30 1:00 402.220 Tutorial 01 Cancelled Monday 11:00 12:30 407.404 Lab 01 Cancelled Monday 10:00 11:00 402.231 Tutorial 02 Monday 12:30 14:00 407.404 Lab 02 Monday 14:00 15:00 402.231 Tutorial 03 Friday 11:00 12:30 402.347 Lab 03 Friday 10:00 11:00 402.231 Tutorial 04 Friday 12:30 14:00 402.347 Lab 04 Friday 14:00 15:00 402.231 Tutorial 05 Tuesday 14:00 15:30 402.314 Lab 05 Tuesday 13:00 14:00 402.231 Tutorial 06 Tuesday 15:30 17:00 402.314 Lab 06 Tuesday 17:00 18:00 402.211A School of Information Systems Page 4 of 15
  • 5. 6. Program WK BEGIN LECTURE (1.5hr) TUTORIAL (1.5hr) LAB (1hr) 0 Lecture Plan TE – Tutorial Exercise Case Study Discussion can be found in the textbook (Satzinger, Jackson & Burd) I: SYSTEMS ANALYST, REQUIREMENTS ANALYSIS, AND PROJECT MANAGEMENT 1 27 Feb  Unit Introduction  Tutorial Activity: MS-Project 2003  Skills and Activities of a Systems Analyst - Planning and Time Management Exercises Familiarisation READING: Chapter 1 (Gantt Chart); - Functional Decomposition 2 06 Mar  Managing the Information Systems Project  Tutorial Activity: MS-Project 2003 – GANTT  Systems Development Life Cycle – Overview - Tutorial Case Study Discussion, p32 & 72  Project Plan – Gantt Chart  Approaches to System Development (Reliable Pharmaceutical Service) READING: Appendix A - Traditional, Agile - Choosing a system development approach READING: Chapters 3, 17  TE1:Student Study Plan (Gantt Chart) 3 13 Mar  Determining System Requirements  Tutorial Activity:  Microsoft Visio 2003 - Requirements Determination Techniques - Requirements Determination Familiarisation - Joint Application Development  Tutorial Case Study Discussion, p 72 (continue)  Create Function Models - Prototyping (Reliable Pharmaceutical Service) using Visio 2003 – IDEFØ READING: Chapter 3 - Information gathering methods - Constructing FHD  Tutorial Exercise 1 Due School of Information Systems Page 5 of 15
  • 6. 4 20 Mar  INFORMAL FEEDBACK  Tutorial Activity: Create Function Models  Functional Hierarchy Diagram – FHD - Constructing FHD: using Visio 2003 – IDEFØ (Function/Process Model) Tutorial Case Study Discussion - Reliable  Requirements Gathering  Statement of Scope, Business Benefits, System Pharmaceutical Service, p150 Exercise (for Assignments) Capabilities - Statement of Scope, Business Benefits, READING: Chapter 4 System Capabilities  Assignment Activity: Requirements Gathering Exercise (for Assignments)  TE2: Business Benefits and System Capabilities School of Information Systems Page 6 of 15
  • 7. WK BEGIN LECTURE (1.5hr) TUTORIAL (1.5hr) LAB (1hr) II: MODELLING SYSTEMS REQUIREMENTS - ENTITY AND DATA MODELLING 5 27 Mar  Managing Data  Tutorial Activity: Create Data Models  Analysing System Requirements: Entity - Requirements Analysis / Structuring – using Visio 2003 Modelling Entity Modelling – ERD Exercises  Identifying Entities, Attributes, Relationships  Tutorial Exercise 2 Due READING: Chapter 5 6 03 Apr  Structuring System Requirements: Entity /  Tutorial Activity: Conceptual Data Model / Conceptual Data Modelling Requirements Structuring (Conceptual Data Model) Entity Relationship Diagram  Purpose of an Entity Model - Reliable Pharmaceutical Service, p196, q2 Exercises READING: Chapter 5  TE3: Conceptual Data Model / Entity Relationship Diagram Exercise 7 10 Apr  Structuring System Requirements:  Tutorial Activity: Conceptual Data Model / Conceptual and Logical Data Models - Conceptual & Logical Data Exercise Entity Relationship Diagram READING: Chapters 5, 13 - Work on Case Study Assignment Exercises  Tutorial Exercise 3 Due FORM GROUP FOR ASSIGNMENT 2 INDIVIDUAL - ASSIGNMENT 1 Due THURSDAY, 13th APRIL 2006 at 4pm 8 17 Apr Tuition Free Week 1 9 24 Apr Tuition Free Week 2 III: MODELLING SYSTEMS REQUIREMENTS - PROCESS MODELLING 10 01 May  Process Analysis and Process Model  Tutorial Activity: Creating Process Models  Purpose of a Process Model, Requirements Analysis: DFD Exercise Data Flow Diagrams using Context Diagram, Data Flow Diagrams  Group Activity: Work on Assignment Visio 2003 – Gane & Sarson READING: Chapter 6  TE4: Function Model / Analysis – FHD Exercise 11 08 May  Structuring System Requirements:  Tutorial Activity: Data Flow Diagrams Exercise Process Model using DFD Discuss TE5: Requirements Structuring – DFD Exercise & Function Hierarchy  Analysing and Defining Business Functions  Group Activity: Work on Assignment Diagrams using Visio 2003 READING: Chapter 6  Tutorial Exercise 4 Due School of Information Systems Page 7 of 15
  • 8. WK SESSION LECTURE (1.5hr) TUTORIAL (1.5hr) LAB (1hr) IV: SCOPE CREEP, IMPLEMENTATION AND SUPPORT 12 15 May  Handling Scope / Requirements Creep  Group Activity: Work on Assignment 2 Work on Major Assignment  Evaluating Alternatives for Requirements,  Tutorial Exercise 5 Due Environment, and Implementation  Analysing Screens and Reports  READING: Chapter 8 13 22 May  Implementation and Support  Presentations  Presentations  READING: Chapter 16 14 29 May  Systems Analysis - Recap  Presentations Work on Major Assignment  Unit Revision  SEEQ  READING: Chapter 8 GROUP - ASSIGNMENT 2 Due FRIDAY 2nd JUNE 2006 at 4pm 15 05 Jun Study Week 16 12 Jun Exams Week 1 17 19 Jun Exams Week 2 School of Information Systems Page 8 of 15
  • 9. 7. Assessment 7.1 Summary To pass this unit you must: a) Receive an overall grade of 5 or above and a mark greater than or equal to 50, b) Must attempt all assessable components, AND c) Pass the exam Submission Assessment Activity % Due Date Place or Method Assignment 1 (Individual) Submit to Tutor / – Preliminary Requirements Models 15 School of IS Due 4pm Thursday Assignment Box 13th April Assignment 2 (Group) – Requirements Specification Report 20 Submit to Tutor / Due End of Week 12 – Group Presentation 5 School of IS 4pm Friday – Weekly Progress Report Assignment Box – Peer Evaluation Form Tutorial & Lab Participation & Submit Tutorial Due in Tutorial Tutorial Exercises (5 TEs) 10 Exercises during tutorial You are Final Examination 50 REQUIRED to 3-hour Exam pass the exam to pass the unit TOTAL MARKS 100 7.2 Assessment Details ASSIGNMENT 1 (15%) PRELIMINARY REQUIREMENTS MODELS [INDIVIDUAL ASSIGNMENT] This assignment will be done individually. This assignment forms a part of the Major Assignment. You are required to submit a preliminary report which includes the following deliverables (maximum of 10 pages):  Gap Analysis – To analyse and determine the limitations of the current system using Functional Hierarchy Diagram and (possibly) SWOT  Statement of Scope with reference to the use of Context Diagram, Business Benefits and System Capabilities of the new system - A description of the functions and deliverables of the new system  Functional Hierarchy Diagram of the Current and New Systems (constructed using IDEFØ of Microsoft Visio Professional 2003)  Conceptual Data Model / Entity Relationship Diagram of the new system (constructed using Microsoft Visio Professional 2003) School of Information Systems Page 9 of 15
  • 10.  An overall Development / Project Plan Project (from Project Initiation to Implementation) using Gantt Chart (constructed using Microsoft Project 2003) Your tutor will play the user role(s) for a given case study. You should clarify any doubts (a list of assumptions accepted for this assignment but must be clarified in the final report) about the current system or new requirements with the user(s). You will be working on this case study during your tutorial sessions. Interviewing, JAD, and/or prototyping sessions will be held during your tutorial sessions. Each student MUST consult their tutor on a regular basis. Your progress will be monitored during the tutorials and you MUST provide a weekly progress report of your progress. The following headings may be used in the weekly progress report (max one A4 page):  Last Week’s Activities / Achievements  This week’s plan  Next Week’s plan You must sign off the weekly report. Be sure to list all the tasks that you have undertaken or will undertake. Marks will be allocated for your team’s progress. This assignment / report should include a table of contents and must be written to a professional standard. Assignments that do not meet these standards may be returned without mark for revision and resubmission with mark reductions. MAJOR ASSIGNMENT (20%) REQUIREMENTS SPECIFICATION FINAL REPORT [GROUP ASSIGNMENT] This assignment is a continuation of the previous assignment and this final assignment will be done in groups of 3 students. Once the group is formed, you are to consolidate your work from your previous assignment. You are required to submit a final requirements specification report and present the outcome of your work. The content of this report should include but not limited to: (additional requirements and clarification will be discussed in the lectures and tutorials)  Analysis of the Current System (revised from previous assignment),  Limitations of the Current System (revised from previous assignment),  Scope, Business Benefits and System Capabilities (revised from previous assignment),  Objectives and Requirements of the New System,  New Logical DFDs (Context, Level 0, Level 1) (using Gane & Sarson of Microsoft Visio)  Current and New Functional Hierarchy Diagram (revised from previous assignment - using Microsoft Visio)  Conceptual Data Model (revised from previous assignment – using Microsoft Visio)  Sample Screen Design (approx. 4 screens) and Report Design (max 8 reports)  A revised Development Plan – Gantt Chart for the entire Project (from Project Initiation to Implementation)  An extended and complete description of the new system must be included along with the functions and deliverables of the new system.  Handling of scope or requirements creep (if any) School of Information Systems Page 10 of 15
  • 11. Your team must clarify any doubts (a list of assumptions is not acceptable) about the current system and new requirements with the user(s). You will continue to work on this case study during your tutorial sessions. As per Assignment 1, each team MUST consult their tutor on a regular basis and MUST provide a weekly progress report of their teamwork and team’s progress. Team progress will be monitored during the tutorials and marks will be allocated for your team’s progress. By now, each team should have their own standard progress report template. This report should include a detailed table of contents and must be written to a professional standard. Assignments that do not meet these standards may be returned without mark for revision and resubmission with mark reductions. This report is intended for management and it is, therefore, vital that your written work is aimed at the correct audience. Each student MUST submit a Peer Evaluation Form after the completion of this assignment. As your final assignment will be assessed after the completion of formal classes, you need to provide a stamped self addressed A4 sized envelope to enable us to return your assignment to you through the post. If you do not attach a stamped self addressed A4 envelope your assignment will be destroyed after it is assessed. It will not be held for collection at some later date. Final assignments will NOT be available from the School Office. PRESENTATION (5%) Part of Assignment 2, your team will be presenting your new system to the Management. The presentation will be for 20 minutes with 5 minutes for discussion and questions. The structure of your presentation is up to your team and it must be presented to a high standard. Dress codes are considered important in professional presentations and marks will be allocated for the professionalism of your team. Computer projectors are booked and it is expected that Powerpoint slides or equivalent will be used in the presentation. Overhead projectors are also available in class. TUTORIAL/LAB EXERCISES & PARTICIPATION (10%) Tutorials and Labs play an integral part in your learning process. Much of the interaction and learning will take place during tutorials and labs. The sessions are designed for small group interactions where you will be able to meet with your tutor, fellow students, and be able to discuss the unit’s material and work together. In order for you to achieve satisfactory learning outcomes in Analysis 200, your attendance at Tutorials and Labs is VITAL. You may be severely disadvantaged if you fail to attend Tutorials and Labs. Do ensure that you maximise the use of these sessions. You are expected to actively participate during your tutorial sessions. Participation marks will be recorded in the following manner: 3 = Actively participated and contributed to tutorial discussions, no prompting required 2 = Some participation and contribution to tutorial discussions, some prompting required 1 = Participated and contributed when prompted 0 = Attended tutorial but no participation Five tutorial exercises are assigned during the semester. These exercises will be done individually and your work must be handed in to your tutor. The due date for each TE is detailed in the Program section of this unit outline. It is your responsibility to ensure that your work is handed in to your tutor. Failure to hand in all TEs will result in a DNC (Did School of Information Systems Page 11 of 15
  • 12. not Complete) grade at the end of the semester. Your tutor will keep an attendance list for Tutorials and Labs. FINAL EXAMINATION (50%) The final examination will be closed book and of THREE hours duration. Note that it is required that you pass the final exam to pass this unit. If you fail the final exam but still receive a mark of at least 50% in the overall assessment of this unit (which includes Assignments 1 and 2, Tutorial Participation, TEs, and the Final Exam), you will receive a Fail Grade and mark (eg, F-52, F-60). TEAM PROJECT PROGRESS WEEKLY NOTES & REPORT Group project has been chosen deliberately for the following reasons: a) The vast majority of the work of a professional in IS/IT field takes place as part of a team b) Systems development is still an ‘art or craft and not an exact science’ - you will learn more from group discussions than you can ever learn from lectures or books. When you have formed or been assigned to a team you must do the following: 1) Clearly specify roles of team members and vote on a team leader and notify your tutor of the choice 2) Keep detailed minutes of all team meetings at the time of the meeting 3) Division of labour - Assign and agree on tasks - clearly specifying the requirements and due dates to individuals or subgroups and record this in the minutes – this may form the Team’s Contract 4) Record the completion of tasks 5) All sign off each set of minutes as a true indication of the meetings 6) Write a Progress Report based on the following headings:  Last Week’s Activities and Achievements  This Week’s Activities and Plan  Next Week’s Plan  All team members sign off the weekly report 7) Self and Peer Evaluations - Students often complain of group members who do not “pull their weight” but gain the same mark as other students in the group. At the first sign of any such problem you should consult your tutor immediately (do not leave the problem until the week before the assignment is due) who will explain how to handle the problem. The Peer Evaluation Form has been designed to specifically handle potential problems in group projects. Please fill in the form for each assignment. The use of this form (or similar tools) may be a deterrent to those who do not “pull their weight”. School of Information Systems Page 12 of 15
  • 13. GUIDELINES FOR PRESENTATION Do: 1) Keep things simple – pitch it to an appropriate level for your audience. 2) Include a clear and motivating introduction – outline the structure of your talk. 3) Ensure your presentation has a logical sequence. 4) Ensure that your talk and visual resources are well organised. Ensure slides/ppt are brief and legible (min. font size 18pt). Check equipment. 5) Rehearse your talk at least 2 or 3 times. It will go much more smoothly if you do. Check your timing and be prepared to edit. Get feedback on distracting mannerisms and attempt to overcome these. 6) Engage your audience - make eye contact with everyone in the audience. 7) Speak clearly and not too quickly. 8) Ensure your conclusion is brief and outlines your main argument/case. Anticipate and prepare for likely questions. Do not: 1) Read long parts of your slides - this is boring for the audience. 2) Panic if you lose your place or go blank. Pause, regain your composure and then continue. 3) Look at your slides or notes instead of the audience. 4) Do not use jargon or acronyms without explanation – this alienates the audience. 7.3 Assessment Compliance Information Due dates will be strictly adhered to. Extensions will be granted only in cases of demonstrated urgent need. It is your responsibility to check the due date. The Final Exam will be held during the formal examination period. It is the student’s responsibility to check the date and time of the Final Exam on the Curtin website. Official release results for this unit are published on Oasis on the Curtin website: http://oasis.curtin.edu.au 7.4 Penalty for Late Submission of Assessments If assignments are not submitted by the due date, a penalty of 5% per day will be deducted from the assessment mark and after seven (7) days a zero mark will be recorded. It is the student’s responsibility to keep appropriate copies/backups of every assignment submitted. School of Information Systems Page 13 of 15
  • 14. 7.5 Relationship of Assessment Activities to Learning Outcomes and Professional Skills This table illustrates how the assessment activities relate to the assessment of the learning outcomes and professional skills. Outcomes Assessment Activity Major Learning Outcomes Assignment Assignment & TEs & Final 1 Presentation Participation Exam 1.Use appropriate techniques and tools to: a. construct physical and logical     process/task models for existing and new systems b. construct conceptual and logical relational data models.     2.Demonstrate appropriate interviewing techniques with a variety of clients.     3.Demonstrate knowledge of a variety of legacy and contemporary systems     development methodologies/techniques (eg. SDLC, RAD, JAD, Prototyping). 4.Professionally present system development proposals to management.  5.Create a Requirement Specification Report which includes business objectives, an Information Systems specification, a   development plan and financial justification. Professional Skills 1.Use systems analysis skills to identify problem areas and limitations.    2.Complete a systems requirements report detailing the undertaken analysis and initiate   solutions to overcome the problems. 3.Present a summary of the findings.  8. General Information Please see the CBS Student Handbook as described on Page 1 of this document for important general information. 9. Supplementary Instructions and Materials The Board of Examiners may grant supplementary examinations or assessments to a student whose SWA is greater than 50% and who fails the unit by a narrow margin. University policy allows for deferred examinations in some circumstances. 9.1 Undergraduate Supplementary and Deferred Examinations For more detailed information on Policies and Procedures relating to Examinations, students should refer to the web at: http://www.policies.curtin.edu.au/documents/examinations.doc or http://www.policies.curtin.edu.au/documents/deferment_final_exams_appeals.doc School of Information Systems Page 14 of 15
  • 15. Note - It is a student’s responsibility to obtain all relevant information regarding these examinations and to be present at the correct time and venue. A student who does not sit for a scheduled deferred examination in a unit has no claim to a further examination and therefore will receive a FAIL GRADE in this unit. For more details on Policies and Procedures relating to Examinations, students should refer to the http://policies.curtin.edu.au/documents/ assessment_policy.doc or http://www.policies.curtin.edu.au/documents/assessment_appeals. doc END OF UNIT INFORMATION School of Information Systems Page 15 of 15

×