The Bachelor of Software Engineering (BSE) was introduced in 1998 and took its first students in 1999 as a joint program between the Faculties of Engineering and Information Technology. Since then, the program has been transferred entirely to the Faculty of Information Technology, although there will continue to be some teaching input by the Faculty of Engineering.

One of the first year subjects offered by the Faculty of Engineering into the original degree structure was ENG1601 Engineering Context, intended as a general introduction to the broad discipline of engineering, and taken by all students in that faculty, particularly those in the first year of the Bachelor of Engineering (BE).

It is no longer appropriate to use this subject as an introduction for students in the Bachelor of Software Engineering, for several reasons:

1. The BE is based upon a four credit point per subject structure, and IT degrees all use a six credit point per subject structure,
2. Part of ENG1601 addressed the needs of students to develop presentational skills, a topic addressed in more detail by other IT subjects to be introduced into the BSE, and
3. There is a need to introduce BSE students to some of the fundamentals of software engineering early in the course, a need not met by the original BSE structure due to Engineering degree constraints.

CSE1401 Introduction to Software Engineering will provide a more comprehensive and specific introduction to issues in Software Engineering, as well as covering some of the general engineering background, for which Faculty of Engineering teaching expertise will be sought.

The subject will be a core subject for the Bachelor of Software Engineering (course code TBA). It will be available as an elective to students in the? Bachelor of Digital Systems? (0356) and Bachelor of Computer Science (1606).

4. have an understanding of the breadth and nature of the discipline of Software Engineering;
5. have an understanding of the effect and implications of complexity in large software systems;
6. understand the issues in constructing large software systems from its components, and the nature and design of those components.

4. be aware of the responsibilities placed upon a software engineer;

5. be able to use basic modelling techniques to define and describe the behaviour of software systems;
6. be able to apply some basic measurement techniques to software systems;

The subject provides an introduction to the discipline of Software Engineering. The emphasis is upon a broad coverage of the areas, since students will at this early stage not have adequate programming skills to tackle many of the topics in greater depth. The notion of a software system as a model or approximation of a desired system is introduced, and used as a way of describing such things as the software life cycle and its various models, programming by contract, design and testing issues, maintenance, reuse, complexity, divide and conquer strategies, metrics and measurement, project management and software legacy.

Stephen R. Schach: Object-Oriented and Classical Software Engineering, McGraw-Hill (Required Textbook).

Pressman: Software Engineering - A practitioner\'s approach, McGraw-Hill.

Sommerville, Software Engineering, Addison-Wesley.

Langford: Practical Computer Ethics, McGraw-Hill.

Lectures, Tutorials, Computer Teaching Laboratory classes.

Lectures will be used to address the required level of knowledge (all objectives). Tutorials will pursue those objectives with an attitudinal component (1,4) through class room discussion, as well as those requiring some abstract conceptualization skills (2,5). Computer Teaching Laboratory classes will provide the skills necessary to meet the practical skills and understanding objectives (3,6).

• laboratory classes 10%
• tutorials 10%
• Two assignments worth 10% each, based on a short written report of no more than 5 A4 pages each
• 60% written exam of 2 hours duration

Each laboratory class will be assessed on a "satisfactory/unsatisfactory" basis to ensure that students meet the practical skills objectives (3,6) for a total weight of 10%. Tutors will also be required to assess the contributions and understandings evidenced by students in tutorials in order to assess objectives 1,2,4,5 for a total of 10%. Two assignments worth 10% each, based on a short written report of no more than 5 A4 pages each, will address objectives 2,3,5,6, and a 60% written exam of 2 hours duration will assess students overall achievement in all objectives.

Lecture theatre for 3 hours per week

Tutorial rooms for 1 hour per week

Computer Teaching Laboratories for 3 hours per fortnight.

A 0.4 full-time lecturer and 0.005n tutors are required to teach the subject (n is number of students enrolled: for 100 students, this is 0.5 fraction of a full-time tutor). Subject coordinator TBA.

• Software Title:
• Vendor:
• Version:
• OS: MS Windows XP ( ) and/or LINUX ( )
• License Details: (A valid software license certificate/s or Vendor permission must be available upon request if the software is to be installed for teaching)
• Are we currently licensed: Yes ( ) or No ( ) (If unsure, please check with your local IT support )
• If (Yes), who is the contact person for this software?:
• If (No), will the software license be arranged by: Staff member requesting the software ( ) or Technical Services* ( ) ? *If the latter is selected, please discuss your requirement/s with myself ASAP, prior to finalising your request, as there could be financial or resourcing implications.
• Is the software to be installed and accessed from a: Client/Workstation ( ), or Server ( ) ?
• Type of license: Site License ( ), Freeware ( ), FOSS (Free and Open Source Software) ( ), Shareware ( ), Lab based ( ) # of Licenses needed ____
• In what week will you commence using the software in class? Semester 1 (Week ___ ) and/or Semester 2 (Week ___ ):
• Nominated Staff For Acceptance Testing Software: (Name) (Phone) (Email)
• Additional Information: Special Requirements, Software Configuration/Installation Requirements, etc:

None

The library impact statement is attached to the course proposal document.

Originals of signed library impact statements are held by the Faculty of Information Technology Secretariat and copies are available on request (Tel. 9903 2726/2983, Fax 99032745, email jillian.oldfield@infotech.monash.edu.au).

100% from the School of Computer Science and Software Engineering.

None. The Faculty of Engineering has been consulted, but states that it is unable to resource this subject at this stage.

None.

None