FIT3037 Software Engineering , Unit Information Guide (Semester 1, 2006)

Chief Examiner Dr Raymond Smith
Gippsland : Raymond Smith

ASCED Field of Education: 020199 Computer Science, Not Elsewhere Classified

Software engineering is much more than the ability to analyse, design and develop program code to solve particular information system problems. Software engineering includes project management, team and personnel management, quality assurance, configuration management and many other aspects.

In this unit students will learn about many aspects of working with a large team on large projects to produce quality software products on time and within budget. The student will gain an appreciation of the tools and techniques used to develop software systems within a group context.

Topics to be studied include:


  • software development lifecycle models.
  • sizing, estimation, planning and control of projects.
  • functional specification and design of real-time systems.
  • formal specification and design using Z.
  • integration and testing strategies.
  • configuration management.
  • reuse and re-engineering.

    Objectives Knowledge and Understanding

    At the completion of this unit, students will have:

    Knowledge of:

    • the continuing software crisis, problems encountered in the development of large software systems: poor quality, late delivery and budget overruns
    • techniques used in software engineering to counter these problems


    Understanding of:

    • the role of software lifecycle models in project control and planning
    • different categories of software metrics
    • software estimation methods
    • methods for specifying real-time systems
    • techniques and tools to support configuration management
    • strategies for testing software
    • the roles and responsibilites of project team members


    Skills in:

    • applying techniques for scheduling and control of large projects
    • constructing and validating a software specification
    • formal methods specification of software systems
    • functional design of software systems
    • describing large software systems using appropriate language and technical sprecification techniques to suit the intended audience



    • that quality software is not a luxury but essential in solving the software crisis



    Before attempting this unit you must have satisfactorily completed FIT2005, or equivalent.

    You should have knowledge of

  • Ability to analyse an information system specification and develop detailed and appropriate models.
  • Familiarity with the commonly used software analysis and design methodologies, including structured analysis and design and the object oriented techniques.
  • Basic programming skills and general familiarity with the processes involved in the development of software using languages like Java and C .
  • ]


    Unit relationships

    FIT3037 is a core unit in the Application Development and Networks major of the BITS degree.

    You may not study this unit and GCO3811 in your degree.

    Texts and software

    Required text(s)

    Pressman R.S., Software Engineering: A Practitioners Approach, Sixth Edition, McGraw-Hill, 2005. ISBN 0-07-123840-9

    Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.

    Hardware requirements:

    Students studying off-campus are required to have the minimum system configuration specified by the faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to n hours per week for use of a computer, including time for newsgroups/discussion groups.

    Recommended reading

    Sommerville, Ian. Software Engineering, Sixth Edition, Addison-Wesley, 2000. ISBN 0-201-39815-X

    Van Vliet Hans, Software Engineering: Principles and Practice, Second Edition, John Wiley and Sons, 2000. ISBN 0-497-97508-7

    Pfleeger Shari Lawrence, Software Engineering Theory and Practice, Prentice-Hall, 1998. ISBN 0-13-081272-2

    Library access You may need to access the Monash library either personally to be able to satisfactorily complete the subject.  Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.
    Study resources

    Study resources for FIT3037 are:

    Study resources for FIT3037 are:

    • A printed Unit Book containing 7 Study Guides (52 pages), sent from CeLTS
    • This Unit Information outlining the administrative information for the unit on the unit website
    • The FIT3037 web site, where lecture slides, weekly tutorial requirements, assignment specifications and sample solutions will be posted
    • Newsgroups that can be linked to from the Unit Homepage

    Structure and organisation



    Study Guide


    Key Dates

    1 Introduction, Software process models, Software metrics 1 Pressman Chapters 1, 3, 14.4, 15, 22
    2 Project management - feasibility, Risk management, Scheduling 2 Pressman Chapters 21, 24, 25
    3 Project management - software estimation 2 Pressman Chapter 23
    4 Requirements specification, Real-time specification 3 Pressman Chapters 7.1-7.4, 8.2-8.7 Ass 1 due 22/3/06
    5 Formal methods introduction 3 Pressman Chapter 28
    6 Formal specification - Z 3 Pressman Chapter 28 & reading from Diller
    7 System and software design 4 Pressman Chapters 9.1-9.3, 10, 11
    8 Component-based SE, Distributed architectures 5 Pressman Chapters 27, 30 Ass 2 due 26/4/06
    9 Software testing and strategies 6 Pressman Chapters 13, 14
    10 Configuration management and tools 7 Pressman Chapter 27
    11 Software re-use and re-engineering 7 Pressman Chapter 31
    12 Ass 3 due 24/5/06

    The timetable for on-campus classes for this unit can be viewed in Allocate+


    Assessment for the unit consists of 3 assignments with a weighting of 45% and an examination with a weighting of 55%. Read this section VERY carefully.

    Assessment Policy

    To pass this unit you must:

    • attempt all assignments and the examination
    • score at least 50% of the possible marks for the unit
    • achieve no less than 40% of the total available marks for the assignments overall, and the examination

    Your score for the unit will be calculated by:

    Final Mark Calculation If both the examination mark and the assignment mark is at least 40%, then the final mark is obtained by:

    final mark = ( R * A * E ) / ( ( (R-1) * A ) + E )

    where :

    • A = assignment mark as a percentage
    • E = examination mark as a percentage
    • Aw = Assignment Nominal Weighting (45%)
    • Ew = Examination Nominal Weighting (55%)
    • R = (Aw + Ew ) / Aw
      Therefore for this unit R = ( 45 + 55 ) / 45 = 100/45

    If either the examination mark or the assignment mark is less than 40%, then the final mark is obtained by:

    final mark = Minimum (M1, M2, M3)


    • M1 = E*Ew+A*Aw
    • M2 = A+E*Ew*(40-A)/100
    • M3 = E+A*Aw*(40-E)/100

    The intention of these formulas is to weight your marks in such a way as to encourage a consistent effort in both components of the assessment, namely the assignments and examination.

    A table is given below to show the final marks that may be obtained in this unit, calculated applying the above formula, for some representative examination and assignment marks.


    Assessment Requirements


    Due Date


    Assignment 1: Software Requirement Specification 22 March 2006 15 %
    Assignment 2: Formal Methods Specification 26 April 2006 15 %
    Assignment 3: Real-time analysis 24 May 2006 15 %
    Examination 3 hour(s), closed book Exam period starts 5th June. 55 %

    Assignment specifications will be made available on the FIT3037/GCO3811 web site assignment page. Information about assignments will be published on the Unit's Notices Newsgroup.

    Assignment Submission Methods

    Assignments will be submitted through the WebFace Assignment Submission System.

    Extensions and late submissions

    Late submission of assignments

    Assignments received after the due date will be unit to a penalty of 5% per day or part thereof up to one week late. Assignments received later than one week after the due date will not normally be accepted.

    This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment. 


    It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting extensions. 

    Requests for extensions must be made by email at least two days before the due date. You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary.

    Contact the Unit Adviser by email to request extensions.

    Grading of assessment

    Assignments, and the unit, will be marked and allocated a grade according to the following scale:

    HD High Distinction - very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
    In the 80+% range of marks for the assignment.
    D Distinction - high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
    In the 70-79% range.
    C Credit - sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
    In the 60-69% range.
    P Pass - acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
    In the 50-59% range.
    N Not satisfactory -  failure to meet the basic requirements of the assessment.
    Below 50%.

    We will aim to have assignment results made available to you within two/three weeks after assignment receipt.

    Feedback Feedback to you

    You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.

    Feedback from you

    You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.

    And if you are having problems

    It is essential that you take action immediately if you realise that you have a problem with your study. The semester is short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.

    Plagiarism and cheating

    Plagiarism and cheating are regarded as very serious offences. In cases where cheating  has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.

    In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work. 

    When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer. 

    Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.

    Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.

    Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.


    Questions of a personal nature may be emailed directly to the lecturer.

    More general queries and comments should be directed to the appropriate newsgroup.


    Notices related to the unit during the semester will be placed on the Notices Newsgroup in the Unit Website. Check this regularly. Failure to read the Notices newsgroup is not regarded as grounds for special consideration.

    Consultation Times

    If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:

    All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.

    Last updated: Feb 27, 2006