COMP SCI 2006 - Introduction to Software Engineering

North Terrace Campus - Semester 1 - 2014

Design: software design, UML notation, static models - identifying classes and associations, dynamic models - identifying states, events, transitions, use cases, mapping designs into code. Specification: the scope, role and styles of software specification. Testing: modes of testing, organising test suites. Human issues: managing object-oriented projects, ethics, professional practice.

  • General Course Information
    Course Details
    Course Code COMP SCI 2006
    Course Introduction to Software Engineering
    Coordinating Unit School of Computer Science
    Term Semester 1
    Level Undergraduate
    Location/s North Terrace Campus
    Units 3
    Contact Up to 2.5 hours per week
    Prerequisites one of COMP SCI 1009, COMP SCI 1007, COMP SCI 1102, COMP SCI 1202, or COMP SCI 2202
    Assumed Knowledge MATHS 1012 or MATHS 1008
    Course Description Design: software design, UML notation, static models - identifying classes and associations, dynamic models - identifying states, events, transitions, use cases, mapping designs into code. Specification: the scope, role and styles of software specification. Testing: modes of testing, organising test suites. Human issues: managing object-oriented projects, ethics, professional practice.
    Course Staff

    Course Coordinator: Dr Amali Weerasinghe

    Course Timetable

    The full timetable of all activities for this course can be accessed from Course Planner.

  • Learning Outcomes
    Course Learning Outcomes
    At the end of this course, you should be able to 

    1.  understand the issues of producing quality software
    2.  design an object-oriented design using UML notation
    3.  prepare a design in Rational Software Architect (RSA), an industrial strength tool;
    4.  be able to design test suites
    5.  be aware of human issues in the software engineering professions: ethics and professional      
         practice
    6.  understand the different aspects of project management in producing quality software
    7.  work in small groups
    University Graduate Attributes

    This course will provide students with an opportunity to develop the Graduate Attribute(s) specified below:

    University Graduate Attribute Course Learning Outcome(s)
    Knowledge and understanding of the content and techniques of a chosen discipline at advanced levels that are internationally recognised. 2,3,4,6
    The ability to locate, analyse, evaluate and synthesise information from a wide variety of sources in a planned and timely manner. 2,3,4,6
    An ability to apply effective, creative and innovative solutions, both independently and cooperatively, to current and future problems. 2,3,4,5,6,7
    Skills of a high order in interpersonal understanding, teamwork and communication. 6,7
    A proficiency in the appropriate use of contemporary technologies. 2,3,4
    A commitment to continuous learning and the capacity to maintain intellectual curiosity throughout life. 1,5
    A commitment to the highest standards of professional endeavour and the ability to take a leadership role in the community. 1,5
    An awareness of ethical, social and cultural issues within a global context and their importance in the exercise of professional skills and responsibilities. 1,5
  • Learning Resources
    Required Resources
    Software Engineering, 9th Edition  Ian Sommerville, 2009.
    ISBN 13: 9780137053469.
    Available from Unibooks, with limited copies also available from the library
    Online Learning
    All information about this course will be available via the ISE Moodle page. 
    It is accessible from http://forums.cs.adelaide.edu.au

    The Moodle page will include:
    – A discussion forum for asking questions
    – Links to online resources
    – Lecture schedule, notes, recordings
    – Assignment specifications and tutorial questions
    – Other important announcements

    *   It is important that you check these forums regularly.
    *  All students participating in the course MUST join this forum. It is your responsibility to regularly           check this forum for notices, and to participate in online activities.




  • Learning & Teaching Activities
    Learning & Teaching Modes
    In this course you will receive two one hour lectures per week. You are expected to attend all of the lectures. In the lectures, we will discuss new concepts and discuss worked examples.

    Starting from week 2,  tutorials will be held fortnightly. Some of the tutorials will be held within computer labs as they are focussed on developing practical skills needed for the assignments. Even though your answers to tutorials are not assessed, we strongly encourage you to attempt the questions prior to each tutorial to receive maximum benefit. Your attendance will be recorded.

    Details of the assignments will be outlined in the Assessment section.
    Workload

    The information below is provided as a guide to assist students in engaging appropriately with the course requirements.

    Students are expected to spend 10-12 hours per three unit course. This includes approximately 2.5 hours of contact time per week. Remaining hours should be spent on independent study.

    Learning Activities Summary
    This course consists of the following key topics:

    Topic  Description 
    Introduction The first lecture for this course introduces you to the course requirements and to the laboratory environment that you will be using throughout the course.
    Software Testing Testing Principles, Development Testing, Software Inspections, Unit Testing, Component Testing, System Testing, Test Driven Development, Release Testing, Acceptance Testing
    Analysis and Design Principles of Design, Design Approaches, Object-Oriented Analysis and Design, Unified Modelling Language, Design Patterns
    Software Project Management Software pricing, Plan-driven development, Project scheduling, Agile planning, Estimation techniques
    Ethics Bases for Ethics – Objectivist vs Relativist, Theories for Ethical behaviour – Teleological vs Deontological
  • Assessment

    The University's policy on Assessment for Coursework Programs is based on the following four principles:

    1. Assessment must encourage and reinforce learning.
    2. Assessment must enable robust and fair judgements about student performance.
    3. Assessment practices must be fair and equitable to students and give them the opportunity to demonstrate what they have learned.
    4. Assessment must maintain academic standards.

    Assessment Summary
    This course has TWO components:
    1. Final written exam: 65%
    2. Coursework: 35%
    • Assignment 1 (Individual assignment focused on developing software testing skills): 10%
    • Assignment 2 (Group assignment on object-oriented analysis and design): 15%
    • Assignment 3 (Individual assignment on software project management): 10%
    Assessment Related Requirements
    Students must obtain at least 40% in each of the assessment components (exam and course work), and 50% overall, to pass the course.
    Assessment Detail
    Written exam: this will be a closed-book exam. Questions will test the students’ understanding of concepts presented throughout the course, and their ability to put them to use to solve problems.

    Tutorial and class participation: intended to assess the student’s knowledge in practical application of the concepts taught in lectures.

    Assignments: are used to help assess whether the required graduate attributes are being developed. Written feedback will be provided for some of the assessment work.
    Submission
    Tutorial answers will not be assessed. However, we strongly encourage you to attempt the questions prior to each tutorial to receive maximum benefit. Your attendance will be recorded.

    Assignments will be submitted online. Please refer to each assignment description for details.
    Course Grading

    Grades for your performance in this course will be awarded in accordance with the following scheme:

    M10 (Coursework Mark Scheme)
    Grade Mark Description
    FNS   Fail No Submission
    F 1-49 Fail
    P 50-64 Pass
    C 65-74 Credit
    D 75-84 Distinction
    HD 85-100 High Distinction
    CN   Continuing
    NFE   No Formal Examination
    RP   Result Pending

    Further details of the grades/results can be obtained from Examinations.

    Grade Descriptors are available which provide a general guide to the standard of work that is expected at each grade level. More information at Assessment for Coursework Programs.

    Final results for this course will be made available through Access Adelaide.

  • Student Feedback

    The University places a high priority on approaches to learning and teaching that enhance the student experience. Feedback is sought from students in a variety of ways including on-going engagement with staff, the use of online discussion boards and the use of Student Experience of Learning and Teaching (SELT) surveys as well as GOS surveys and Program reviews.

    SELTs are an important source of information to inform individual teaching practice, decisions about teaching duties, and course and program curriculum design. They enable the University to assess how effectively its learning environments and teaching practices facilitate student engagement and learning outcomes. Under the current SELT Policy (http://www.adelaide.edu.au/policies/101/) course SELTs are mandated and must be conducted at the conclusion of each term/semester/trimester for every course offering. Feedback on issues raised through course SELT surveys is made available to enrolled students through various resources (e.g. MyUni). In addition aggregated course SELT data is available.

  • Student Support
  • Policies & Guidelines
  • Fraud Awareness

    Students are reminded that in order to maintain the academic integrity of all programs and courses, the university has a zero-tolerance approach to students offering money or significant value goods or services to any staff member who is involved in their teaching or assessment. Students offering lecturers or tutors or professional staff anything more than a small token of appreciation is totally unacceptable, in any circumstances. Staff members are obliged to report all such incidents to their supervisor/manager, who will refer them for action under the university's student’s disciplinary procedures.

The University of Adelaide is committed to regular reviews of the courses and programs it offers to students. The University of Adelaide therefore reserves the right to discontinue or vary programs and courses without notice. Please read the important information contained in the disclaimer.