The unit is a 12-point leve-4 core unit in the new Bachelor of Software Engineering (Honours) degree to be introduced in 2016.

16/02/2021: Admin - updating scheduled activities (workload) as advised by the CE.

23/09/2020 Admin: Update to include new assessment and teaching approach fields as per Handbook requirements.

24/04/2020: Update to corequisites to add Engineering CPD unit ENG0001 (already in callista).

5/10/2018: Update to prerequisites for 2770 teachout. Effective 2019.

14/03/2018 - Admin: clarifying ULO 2 on behalf of the CE.

4/9/2015 - updated for course architecture programs. Effective semester 1, 2016

September 2014: Change in unit name to clarify that the project is an industry project. As discussed with ADE.

May 2014 - change objectives to learning outcomes for AQF compliance.

Nov 2013: remove CSE/BUS units from prerequisites. There are no students remaining in this version of the BSE.

Nov 2013: FIT4004 added as a co-req. It was always intended that this unit be done in the final year, when students would also be doing FIT4002. Not having it has a co-req seems to have been an oversight.

Nov 2013: The change to the teaching hours has 2 parts.

Since the MUSE lab is already available for BSE final year group projects, it does not add any extra facility resources. The unit coordinator and the supervisors will be around for at least some of the 2 hrs, but on an as-needs basis, and they would be meeting with students anyway, so it should not add to their workload in any substantial way.

---------------------------------

This unit has been updated as part of a 2009 review and comparison of data with current Handbook, Syllabus + and Callista data.

This is a full year Capstone project in the final year Bachelor of Software Engineering (Honours). It provides an opportunity for students to apply the knowledge and skills gained in other units as they synthesise a solution to a significant, realistic and practical problem (Software Engineering in the medium/large depending on the size of the project and the group).

Students also have an opportunity to learn leading edge technologies and apply it in practice as per the client?s project requirement. One of the important aspects of the unit is also to get the students to reflect on the SE body of knowledge that has been covered in the program and how they apply it in practice in this unit.

It is conducted in a simulated real life working environment in a control setting in the lab under the supervision of the unit leader. Student teams learn to integrate much of the material they have learnt through the earlier years of study in SE for an external client?s project. The whole SE life cycle includes from requirements, design, HCI, professionalism, confidentiality issues, and project management.

The unit provides a valuable industry relevant project experience and is valuable for student?s transition to professional work in IT industry in general and in SE in particular.

At the completion of this unit students should be able to:

1. design and implement a software system of a quality acceptable to an external client;
2. select and use appropriate tools, techniques and strategies to manage project resources, including time and personnel;
3. identify potential sources of risk, including ethical risk, and devise and adopt appropriate strategies to monitor and mitigate these risks;
4. choose and follow a software development methodology that is appropriate to the team, project and client, and justify this methodology;
5. elicit requirements from client representatives and ensure that these are communicated to team members and other stakeholders in an appropriate form;
6. produce internal documentation of a sufficient quality to support project development activities (including specification, analysis, design, testing);
7. communicate effectively with other project stakeholders, including clients, end users, and supervisors;
8. verify systematically that internal and external project deliverables meet agreed quality standards;
9. produce external documentation of a sufficient quality to meet the needs of clients, end users, and client-site technical staff.

029999

Students will undertake a large project and work in groups on a software project for a client. The client may be internal to Monash or from the industry or research organisation. In general, projects involve all aspects of the system development lifecycle. Groups are responsible for their own project management, with guidance from a supervisor. Some projects will warrant students working in pairs or individually.

Recommended resources

Reading list

• Relevant Journal Articles and Conference Proceedings depending on the project chosen.
• Gilb T and Graham D, Software inspection, Addison-Wesley, 1993
• Stiller, Project-based Software Engineering, Prentice-Hall, 2001
• Humphrey W, Managing the software process, Addison-Wesley,1989
• Pfleeger S.L., Software Engineering Theory and Practice, Prentice Hall 2001
• Somerville I.S., Software Engineering Addison Wesley 2001
• Sallis P, Tate G and MacDonell S, Software Engineering: Practice, Management, Improvement, Addison-Wesley, 1995
• Humphrey W, Introduction to the Personal Software Process, Addison Wesley 2000
• Pressman R.S., Software Engineering, A Practitioner's approach, Fifth Ed., McGraw Hill, 2001
• Maciaszek, Requirements Analysis and System Design: Developing Information Systems with UML 2001, Prentice-Hall, 2001

Technological requirements

On-campus

• Laboratory teaching Laboratory teaching is a facilitated active, participatory, peer learning approach.
• Seminars Students will listen to presentations from the unit-coordinator, guest speakers and fellow students on topics relevant to the studio project

In-semester assessment: 100%

1. Scrum of scrums: 5% - ULO 3, 4, 5, 6, 7
2. Process and project status interviews: 20% - ULO: 1, 2, 3, 4, 5, 6, 7, 8, 9
3. Design walkthrough: 10% - ULO: 1, 6, 7, 8
4. Group presentations - 20% - ULO: 1, 2, 3, 4, 5, 6, 7, 8, 9
5. Software walkthrough: 5% - ULO: 1, 6, 7, 8
6. Capstone interview: 10% - ULO: 1, 2, 3, 4, 5, 6, 7, 8, 9
7. Software product: 30% - ULO: 1, 2, 3, 4, 5, 6, 7, 8, 9

12

Minimum total expected workload equals 12 hours per week comprising:

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

(b.) Additional requirements (all students):

For Software Engineering Studio unit, the workload commitments are for 2 semesters of study

For Software Engineering Studio unit, the workload commitments are for 2 semesters of study

(FIT3170 and FIT3171) or (FIT2002 and FIT3077)