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.

This is a core third year unit in the Bachelor of Software Engineering and Bachelor of Computer Science.

Update of teaching hours to add a 2-hour tutorial/lab session. This session has been run for the past 5 years in this unit, however the monatar and handbook entries do not reflect this.

This unit will be taught for the final time in S1 2007. In 2008 the new FIT unit will be offered instead.

This is a core third year unit in the Bachelor of Software Engineering and Bachelor of Computer Science.

This subject covers the analysis, design and specification of large software systems through to system implementation. On successful completion of this unit, the student should have:

• Knowledge of the difficulties of specifying and producing large software products, leading to
  • an appreciation of the need for software engineering methodologies and models (waterfalls, prototyping, iterative development, unified process, extreme programming)
  • understanding of the distinction between software engineering and programming, and thus the distinction between a software configuration and a program
• An understanding of, and ability to apply, the methods of analysis and design, including:
  • structured analysis and design using Yourdon notation
    • Context Diagram, Event Lists, Data-Flow Diagrams, Entity-Relationship Diagram, State Transition Diagrams, Process Specifications, Data Dictionary, Structure Chart
  • object-oriented analysis and design using UML
    • Use Cases, Class Diagrams, Interaction Diagrams, State Diagrams, Package Diagrams, Activity Diagrams
• Knowledge of the problems of managing large software development projects, and the techniques used to address them, including
  • Configuration management
  • Software metrics
  • Software reliability issues such as safety, responsibility, and risk assessment
  • Validation and verification techniques (walkthroughs, and testing (test plan generation, acceptance testing, unit testing, integration testing, regression testing))
  • Quality management
• Knowledge of, and the ability to apply, principles of user interface design such as affordances, awareness of mental models, visibility, mapping and feedback.

Prescribed Text:

There is no prescribed text for this unit

Recommended Text:

Pressman R Software engineering: a practitioner's approach 5th edn, McGraw-Hill 2001

Yourdon E Modern Structured AnalysisPrentice Hall, 1989

Page-Jones, M The Practical Guide to Structured Systems Design 2nd edn, McGraw-Hill, 2000

Booch G, Rumbaugh J, and Jacobson I The Unified Modeling Language User Guide 4th edn, Addison-Wesley Professional, 1998

Page-Jones, M Fundamentals of Object-Oriented Design in UML Addison-Wesley Professional, 2000

Norman, D The Design of Everyday ThingsBasic Books, 2002

Gamma E, Helm R, Johnson R, and Vlissides J Design Patterns Addison-Wesley Professional, 1995

On campus

One 2 hour lecture and one 2 hour tutorial/lab session per week for 13 weeks.

Examination (3 hours): 40% - Two exercises: 60%

Knowledge and understanding objectives: achieved mainly through the examination. Attitudes, values and belief objectives: achieved mainly through both the exam and assignment work. Practical skills objectives: achieved mainly through assignment work. Realtionships, communication and team work objectives: achieved mainly through assignment work.

12 hours per week including 2 hour lecture and 2 hour prac class.

Hi tech lecture theatre for 2 hours per week.

This unit will require a tutorial/laboratory room for the conduct of tutorials/workshops.

Clayton 1 EFT lecturer for 13 weeks for each semester.

1 tutor per 16 students for 13 weeks.

• 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:

Existing unit

Faculty of IT

None

None