41094 Software Engineering Studio 1B
Warning: The information on this page is indicative. The subject outline for a
particular session, location and mode of offering is the authoritative source
of all information about the subject for that offering. Required texts, recommended texts and references in particular are likely to change. Students will be provided with a subject outline once they enrol in the subject.
Subject handbook information prior to 2020 is available in the Archives.
Credit points: 6 cp
Subject level:
Undergraduate
Result type: Grade and marksRequisite(s): 41093 Software Engineering Studio 1A
Recommended studies:
48260 Engineering Project Management; 31257 Information System Development Methodologies; 31282 Software testing and quality management
Description
In this studio subject students extend a system using the professional practices established in 41093 Software Engineering Studio 1A by developing one or more additional features or resolving one or more software issues. Students learn to explore the problem efficiently, to develop solution designs that support rapid convergence to the best alternative.
It is challenging to develop a large program of a few thousand lines and even more challenging to develop a system of millions of lines of code, that cannot afford to fail. The early stages of development must balance problem exploration and design with convergence toward an implementable solution. Developing large, complex systems that must work perfectly requires a number of practices to ensure the development happens in a controlled manner. Developing the professional discipline to use and maintain all of the necessary practices is best done through experience, for little else convinces us of their need than our failings.
The focus of this subject is to experience and understand the longer-term consequences of selected and configured software development methods, tools and resources, then to consider, decide and implement improvements.
Subject learning objectives (SLOs)
Upon successful completion of this subject students should be able to:
| 1. | Apply established engineering methods to complex software engineering problem solving. |
|---|---|
| 2. | Apply software engineering techniques, tools and resources. |
| 3. | Apply systematic software engineering synthesis and design processes. |
| 4. | Apply systematic approaches to the conduct and management of software engineering projects. |
| 5. | Work efficiently in a team |
Course intended learning outcomes (CILOs)
This subject also contributes specifically to the development of the following Course Intended Learning Outcomes (CILOs):
- Socially Responsible: FEIT graduates identify, engage, interpret and analyse stakeholder needs and cultural perspectives, establish priorities and goals, and identify constraints, uncertainties and risks (social, ethical, cultural, legislative, environmental, economics etc.) to define the system requirements. (B.1)
- Design Oriented: FEIT graduates apply problem solving, design and decision-making methodologies to develop components, systems and processes to meet specified requirements. (C.1)
- Technically Proficient: FEIT graduates apply abstraction, mathematics and discipline fundamentals, software, tools and techniques to evaluate, implement and operate systems. (D.1)
- Collaborative and Communicative: FEIT graduates work as an effective member or leader of diverse teams, communicating effectively and operating within cross-disciplinary and cross-cultural contexts in the workplace. (E.1)
- Reflective: FEIT graduates critically self-review their performance to improve themselves, their teams, and the broader community and society. (F.1)
Teaching and learning strategies
This is a studio subject that duplicates commercial software development practices suited to small projects. In small self-managed teams, students are guided through the early stages of team formation and agile project planning before adopting greater autonomy for the remainder of the project. Teams are aided and guided by tutors knowledgeable about and experienced in software development.
To encourage peer learning all teams formally critique the work of another team at significant stages during the project life cycle. To encourage high technical standards, high achievement and peer learning, all teams develop a system from specified requirements but are free to decide how those requirements can be implemented to achieve greater customer satisfaction.
Tutors provide weekly feedback about progress, intended activities and achievements to date. Formal assessment of the project outcomes and deliverables occurs at mid-term and end of term. Early term team formation and skill development activities provide opportunities for feedback about essential team and technical skills. Students are also expected to participate in peer evaluations of teamwork via SparkPLUS.
Content (topics)
During the course of this subject students will cover the following topics:
1. Software engineering environments and tools
2. Software process
3. Software requirements elicitation and analysis
4. Software construction
5. Software development and testing
6. Project planning and management
7. Risk management
8. Team communication and collaboration
9. Reviewing the work of another team
Assessment
Assessment task 1: Pre-implementation Preparation
| Intent: | Assess how well the team has identified requirements and selected appropriate tools and resources for a suitable technology stack. |
|---|---|
| Objective(s): | This assessment task addresses the following subject learning objectives (SLOs): 1, 2, 3 and 4 This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs): B.1, C.1, D.1 and E.1 |
| Type: | Report |
| Groupwork: | Group, group assessed |
| Weight: | 20% |
| Length: | 1000-2000 words |
Assessment task 2: Process Reports
| Intent: | Assess how well the team member has worked on the project. |
|---|---|
| Objective(s): | This assessment task addresses the following subject learning objectives (SLOs): 1, 2, 3, 4 and 5 This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs): B.1, C.1, E.1 and F.1 |
| Type: | Report |
| Groupwork: | Individual |
| Weight: | 30% |
| Length: | > 500 words |
Assessment task 3: Product Demonstration
| Intent: | Evaluate how well the developed software has implemented the required functionality and achieved quality requirements |
|---|---|
| Objective(s): | This assessment task addresses the following subject learning objectives (SLOs): 1, 2 and 3 This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs): B.1, C.1, D.1 and E.1 |
| Type: | Presentation |
| Groupwork: | Group, individually assessed |
| Weight: | 20% |
| Length: | Approximately 20 to 40 minutes for presentation, critique and discussion. |
Assessment task 4: User Manual
| Intent: | The purpose of this task is for the team to prepare one user manual to the end users. |
|---|---|
| Objective(s): | This assessment task addresses the following subject learning objectives (SLOs): 3 and 5 This assessment task contributes to the development of the following Course Intended Learning Outcomes (CILOs): B.1, C.1, D.1 and E.1 |
| Type: | Report |
| Groupwork: | Group, individually assessed |
| Weight: | 30% |
| Length: | > 1500 words |
Minimum requirements
In order to pass the subject, a student must achieve an overall mark of 50% or more.
Recommended texts
Sommerville, I. (2011), Software Engineering: Ninth Edition, Addison-Wesley
Ambler, S. W. and Lines, M. (2012), Disciplined Agile Delivery, IBM Press
Beck, K. (2003), Test-driven development: By example, Addison-Wesley, Boston
References
https://github.com/
https://en.wikipedia.org/wiki/Agile_software_development
https://en.wikipedia.org/wiki/Scrum_(software_development)
Other resources
https://www.lynda.com/