FIT2001 Systems development - Semester 2, 2014

This unit will provide students with an introduction to systems development using an agile development approach. The unit will focus on the application of UML models to the analysis and design of a system. The unit will introduce students to the nature of systems analysis and design as a problem-solving activity, describe the key elements of analysis and design, and explain the place of the analysis and design phases within the an agile development life cycle. The unit will introduce students to the nature of modelling as an analytical and a communicative process.

Major topics include: Agile development and the role of prototyping in systems development, user interface design, domain modelling with UML class diagrams, process modelling with use-case diagrams, use-case driven development and testing, use-case realisation with sequence diagrams, requirements gathering and the implementation and support phases of systems development.

Mode of Delivery

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

(a.) Contact hours for on-campus students:

• One 2-hour lecture
• One 2-hour laboratory

(b.) Study schedule for off-campus students:

• Off-campus students generally do not attend lecture and tutorial sessions, however should plan to spend equivalent time working through the relevant resources and participating in discussion groups each week.

(c.) Additional requirements (all students):

• A minimum of 8 hours independent study per week for completing lab and project work, private study and revision.

Unit Relationships

Prohibitions

BUS2021, CPE2003, CSE1204, CSE1205, GCO1813, GCO2601, GCO2852, GCO2826, IMS1001, IMS1002, IMS1805, IMS2071, IMS9001

Co-requisites

FIT1004 or FIT2010

Chief Examiner

Campus Lecturer

Tutors

Your feedback to Us

Previous Student Evaluations of this Unit

In response to student feedback for this unit, the following changes have been made:

• the order of the lectures has been revised.
• the 2 assignments have been changed to 6 smaller assignments to encourage every student in the team to collaborate on all part of the assignment rather than use the 'divide and conquer' method.  

Student feedback has highlighted the following strength(s) in this unit:

• the tutorial participation in groups in the unit, which gives students the opportunity to collaborate, develop their teamwork skills, and benefit from learning from their peers.
• the case based approach used in tutorials which helps students contextualise the subject content.

Academic Overview

Learning Outcomes

• the roles of systems analysts and designers in agile system development;
• the criteria that can be used to evaluate the quality of a model of a system;
• the purpose of different types of models in the UML;
• the role and application of automated tools in systems modelling.

• appreciate that a range of valid solutions exist for any given problem.

• interpret and evaluate systems analysis and systems design models created using UML;
• create analysis and design models using the main elements of UML; namely class, use-case, sequence and robustness diagrams;
• create system test plans and test cases, and conduct system testing;
• create and evaluate models and prototypes of a user interface using storyboards and wireframes;
• apply problem solving techniques at different levels of abstraction and understand the effect this may have on a system specification.

• explain the interdependence and relationships between all stake-holders in the systems development process;
• create and understand RFP documents.

Unit Schedule

*Unit Schedule details will be maintained and communicated to you via your learning system.

Teaching Approach

• Lecture and tutorials or problem classes
  This teaching and learning approach provides facilitated learning, practical exploration and peer learning.
• Studio teaching
  This approach is hands-on learning where you interact with fellow students in a studio environment.

Assessment Summary

Examination (3 hours): 60%; In-semester assessment: 40%

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

• Assessment task 1

  Title:

  Assignment 1: Analysing Requirements

  Description:

  This group assignment involves creating a requirements specification using requirements gathering techniques, and documenting the requirements using prototyping and relevant modelling tools.  
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  20%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:

  • Quality, accuracy and completeness of the requirements specification and models;
  • Quality of the prototypes;
  • Consistency of the models;
  • Professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, contribution assessment and tutor observation and discussion with group.  All team members must complete the self and peer assessment for each component of the assignment.   

  Due date:

  Weeks 4, 6, 7 and 8 for different assignment components. Refer to Unit Schedule and Assignment Specification for details.

• Assessment task 2

  Title:

  Assignment 2: Designing the System and Preparing for Implementation

  Description:

  This group assignment involves a creating system design models and test cases, and detailing Implementation considerations for the system.  
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  10%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:  

  • Clarity, completeness, accuracy and consistency of the design specification and models;
  • Completeness and comprehensiveness of the test cases;
  • Comprehensive consideration of implementation issues;
  • Presentation and professionalism of the submission and supporting documentation

  Marks for individual group members may vary based on peer assessment, contribution assessment and tutor observation and discussion with group.  All team members must complete the self and peer assessment for each component of the assignment.  

  Due date:

  Weeks 10 and 11 for different assignment components. Refer to Unit Schedule and Assignment Specification for details.

• Assessment task 3

  Title:

  Tutorial participation

  Description:

  Assessment will be based on both tutor observations and peer assessment. This assessment task will encourage you to demonstrate your understanding and knowledge of systems development practice by actively engaging in the tutorial activities. 

  Weighting:

  10%

  Criteria for assessment:

  You are expected to have completed any pre-tutorial activities, and bring any required documentation to the tutorial.   You must be prepared to discuss your findings in a tutorial review group, and use the knowledge to analyse and design a case study system during the tutorials.  

  The assessment for this item is based on the peer evaluation and tutor observation of your performance in the review tutorials, including preparation, participation and contribution, the ability to allow and encourage others to contribute, and the ability to share your understanding of systems development practice with other students.

  Due date:

  Every week in tutorials, starting Week 1

Examinations

• Examination 1

  Weighting:

  60%

  Length:

  3 hours

  Type (open/closed book):

  Closed book

  Electronic devices allowed in the exam:

  None

Learning resources

Reading list

Booch, G., Rumbaugh, J. and I. Jacobson (1999) The Unified Modeling Language User Guide Addison Wesley Professional. 

Dennis, A., Wixom, B.H. and D. Tegarden (2008) Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach, 3rd Edition, Wiley.

Hoffer, J.A., George, J.F. and J.S. Valacich (2001) Modern Systems Analysis and Design 3rd Edition, Prentice Hall.

George, J.F., Batra, D., Valacich J.S. and J.A. Hoffer, (2004) Object-Oriented System Analysis and Design Prentice-Hall.

Lee, R. and W. Tepfenhart (2002) Practical Object-Oriented Development with UML and Java, 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.

Shelley, G.B. and H.J. Rosenblatt (2010) Systems Analysis and Design, 8th Edition, Thomson Course Technology.

Feedback to you

• Informal feedback on progress in labs/tutes
• Graded assignments with comments

Extensions and penalties

Returning assignments

Assignment submission

Online submission

If Electronic Submission has been approved for your unit, please submit your work via the learning system for this unit, which you can access via links in the my.monash portal.

Required Resources

Students will also require access to standard personal productivity tools (word processing , graphics and presentation).

Recommended text(s)

John W Satzinger, Robert B Jackson, Stephen D Burd. (2012). Systems Analysis And Design In A Changing World. (6th Edition) Course Technology Cengage Learning.

Other Information

Policies

Graduate Attributes Policy

Student Charter

Student services

Monash University Library

Disability Liaison Unit