FIT2001 Systems development - Semester 2, 2015

The unit introduces students to systems analysis and design as a problem solving activity, within the framework of a selected methodology. It will focus on contemporary industry practice; investigating understanding and documenting system requirements; a range of design and implementation activities; and professional skills required for systems development.

Mode of Delivery

Workload Requirements

Minimum total expected workload equals 12 hours per week comprising:

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

• Two hours of lectures
• One 2-hour laboratory
• One 1-hour meeting

(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 7 hours independent study per week for completing lab and project work, private study and revision.

See also Unit timetable information

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 5 smaller assignments to encourage every student in the team to collaborate on all parts 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

1. describe and analyse a range of system development methodologies and be able to assess when to use a particular approach;
2. describe key activities required for systems development;
3. apply problem solving techniques at different levels of abstraction;
4. select suitable techniques and methods to conduct analysis, design and implementation activities;
5. apply analysis and design techniques to a practical system development problem within a contemporary development methodology framework;
6. demonstrate an understanding of the professional skills required for effective systems development practice.

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): 50%; In-semester assessment: 50%

Assessment Requirements

Assessment Policy

Assessment Tasks

Participation

• Assessment task 1

  Title:

  Assignment 1: Requirements gathering and Peer Assessment 1

  Description:

  This group assignment involves demonstrating data gathering techniques, such as interviews and forms review to understand the system requirements.
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  6%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:  

  • Timeliness of interview planning;
  • Professionalism, completeness and accuracy of communication;
  • Logical interview structure, and professionalism of language and delivery;
  • Comprehensiveness and relevance of interview questions; 
  • Presentation and professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, tutor observation and discussion with the group.  All team members must complete the self and peer assessment for the assignment.  Failure to complete the peer assessment will result in a 0 for the assignment.

  Due date:

  Assignment 1 - Friday 21 August 2015, 5pm AND Peer Assessment 1 - Monday 24 August 2015, 5pm

• Assessment task 2

  Title:

  Assignment 2 - System Overview, User Stories, Use Case Diagrams, and Use Case Narratives AND Peer Assessment 2

  Description:

  This group assignment involves demonstrating an understanding of the overall system requirements, and showing a detailed understanding of specified functions using User stories, Use Case diagrams, and Use Case narratives. 
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  12%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:  

  • Clarity and comprehensiveness of System overview;
  • Clarity, completeness, accuracy and consistency of User Stories, Use Case diagrams and Use Case narratives;
  • Conformance to modelling standards, and correct use of technique for Use Case diagrams and Use Case narratives;
  • Presentation and professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, tutor observation and discussion with the group.  All team members must complete the self and peer assessment for the assignment.  Failure to complete the peer assessment will result in a 0 for the assignment.

  Due date:

  Assignment 2 - Friday 4 September 2015, 5pm AND Peer Assessment 2 - Due Monday 7 September 2015, 5pm

• Assessment task 3

  Title:

  Assignment 3 - Activity Diagrams, Prototyping & Interaction Design AND Peer Assessment 3

  Description:

  This group assignment involves demonstrating a detailed understanding of how business requirements of specified functions will be met, with the use of Activity Diagrams, Prototyping and Interaction Design. 
  
  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 Prototypes and Interaction Design and Activity Diagrams;
  • Conformance to modelling standards, and correct use of technique for Activity diagrams;
  • Presentation and professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, tutor observation and discussion with the group.  All team members must complete the self and peer assessment for the assignment.  Failure to complete the peer assessment will result in a 0 for the assignment.

  Due date:

  Assignment 3.1 - Friday 18 September 2015, 5pm AND Assignment 3.2 - During tutorials in week beginning 21 September 2015 AND Peer Assessment 3 - Friday 25 September 2015, 5pm

• Assessment task 4

  Title:

  Assignment 4 - Domain model class diagram AND Peer Assessment 4

  Description:

  This group assignment involves demonstrating a detailed understanding of the data requirements of the overall system, and the business processes of specified functions using a Domain model class diagram. 
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  6%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:  

  • Clarity, completeness, accuracy and consistency of Domain Class models;
  • Conformance to modelling standards, and correct use of technique for Domain Class models;
  • Presentation and professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, tutor observation and discussion with the group.  All team members must complete the self and peer assessment for the assignment.  Failure to complete the peer assessment will result in a 0 for the assignment.

   

  Due date:

  Assignment 4 - Friday 25 September 2015, 5pm AND Peer Assessment 4 - Sunday 27 September 2015, 11:50pm

• Assessment task 5

  Title:

  Assignment 5 - Sequence Diagrams & Design Class Diagrams & Peer Assessment 5

  Description:

  This group assignment involves demonstrating an understanding of what is required for the detailed design of specified functions in the system.
  
  Full details of the assignment will be available on the unit web site.

  Weighting:

  6%

  Criteria for assessment:

  The assignment will be assessed using the following main criteria:  

  • Clarity, completeness, accuracy and consistency of the Sequence Diagrams and Design Class Diagrams;
  • Conformance to modelling standards, and correct use of technique for Sequence Diagrams and Design Class Diagrams;
  • Presentation and professionalism of the submission and supporting documentation.

  Marks for individual group members may vary based on peer assessment, tutor observation and discussion with the group.  All team members must complete the self and peer assessment for the assignment.  Failure to complete the peer assessment will result in a 0 for the assignment.

  Due date:

  Assignment 5 - Friday 16 October 2015, 5pm AND Peer Assessment 5 - Monday 19 October 2015, 5pm

• Assessment task 6

  Title:

  Tutorial participation

  Description:

  Assessment will be based on both peer assessment and tutor observation. 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 must complete 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, and will include assessment of your preparation, participation and contribution, and your ability to allow and encourage others to contribute, and your ability to share your understanding of systems development practice with other students.

  Due date:

  In most tutorials during the semester

  Remarks:

  Tutorial participation mark calculation
  
  If you have attended, you get the tutorial participation mark given to you based on your participation. 
  
  If you have not attended for a valid reason and have provided suitable evidence, the week is not counted in the Tutorial participation mark calculation. 
  
  If you have not attended, and have not provided any reason or suitable evidence as to why you have not attended, you receive a 0 for the week, and the week is counted, in the calculation.
  
  So for example, if a student's participation is as follows:
  
  Week 1    Participation assessment not done in the subject this week
  
  Week 2    4
  
  Week 3    3.5
  
  Week 4    2
  
  Week 5    Not applicable - Sick - evidence provided
  
  Week 6    4
  
  Week 7    3.5
  
  Week 8    4
  
  Week 9    Participation not done in the subject this week - Public holiday 
  
  Week 10  0 - Did not attend - no evidence provided 
  
  Week 11  0 - Did not attend - no evidence provided
  
  Week 12  4    
  
  
  For the student above, the mark is calculated in the following way:
  
  There are 10 out of the 12 weeks where participation was conducted in the subject. As the student did not attend for 1 week due to illness and evidence was provided, they have 9 weeks where participation will be counted.  The student did not attend for another 2 weeks, but these weeks will be counted as they did not provide a reason or evidence.  So for this student, their mark for tutorial participation will be calculated as follows:
  
  Addition of all assessments = 4 + 3.5 + 2 + 4 + 3.5 + 4 + 0 + 0 + 4 = 25
  
  This is divided by 9 weeks = 25/9 = 2.77
  
  This equals  2.77 out of 5  which equals 55.5 out of 100  which is a grade of P  
  
  NOTE:  While the student has generally done well when then have attended, their non-attendance for 2 weeks has had a bit impact on their grade.

Examinations

• Examination 1

  Weighting:

  50%

  Length:

  3 hours

  Type (open/closed book):

  Closed book

  Electronic devices allowed in the exam:

  None

Learning resources

Reading list

 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.

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. (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).  These are available in the Labs.

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

Other

Engineers Australia Stage 1 competencies

This unit is a core unit in the Bachelor of Software Engineering accredited by Engineers Australia. Engineers Australia Accreditation Policy of Professional Engineering Programs requires that programs demonstrate how engineering graduates are prepared for entry to the profession and achieve Stage 1 competencies. The following information describes how this unit contributes to the development of these competencies for the Bachelor of Software Engineering. (Note: not all competencies may be emphasised in this unit).

Relationship between Unit Learning Outcomes and BSE Course Outcomes

Relationship between Unit Learning Outcomes and Assessments