ITECH2309 - Software Engineering

Learning Outcomes Assessed
The following course learning outcomes are assessed by completing this assessment:
? S1. Apply software engineering principles to design and implement software applications.
? S2. Operate CASE software to develop appropriate models of software systems.
? S3. Develop comprehensive unit test suites.
? A1. Write integrated reports, using appropriate models, providing detailed analysis of given textual scenarios.
? A2. Implement software applications, using appropriate software engineering techniques, from a given textual scenario.


1. Step 1 – Identify who you will be working with and form your Pair.

2. Step 2 – Access the code

a) Complete the following to steps if necessary (you should already be familiar with these from Assignment 1) to setup your GitHub repository and download your starting code:

a. Enter the GitHub classroom https://classroom.github.com/g/V0GBzveX to create your individual repository in GitHub;

b. If you haven’t used GitHub before you will need to create an account using the link on the sign-in screen. Create a GitHub account by following the instructions in the handout (Registering for and using a GitHub repository and the GitHub Classroom) available in the Study Resources section of your Moodle shell.

c. Follow the separate handout (Using Eclipse IDE to interface with GitHub repository v2) available in the Study Resources section of your Moodle shell. Start at page 7 to page 11 to download and import the provided starter code from the GitHub classroom and load it into a new local repository in Eclipse.

d. Now you have imported the starter code in a project repository in Eclipse.

b) Run the system. You should see the main screen of the Federation Animal Clinic.

3. Step 3 – Begin Group Report

Open a new document in Word (or equivalent), This document will be your group submission. It will contain the pair response to each Refactor/Re-Design step of the assignment i.e. Refactoring/Design Name, Description, Steps taken, Design principles followed, Class Diagram, Test Information

4. Step 4 – Begin Individual Report

Open a new document in Word (or equivalent), This document will be your individual submission. It will contain an individual response to each re-design step of the assignment i.e. What went well, What could have been improved, Review/Description of the work done in Iteration, Measure of individual contribution (%),
School of Engineering and Information Technology

Measure of partner contribution (%) (These two measures should tally to 100%).

5. Step 5 – Iterate through the following tasks (until you’ve completed all tasks identified in the Iteration Tasks table below):

A. Understand requirements for task

Do you really understand what is required? Ask your lecturer for clarification about functional requirements. Consult the Satzinger, Jackson and Bird (2016) text for a general overview of OO analysis and design, UML and methodologies. Consult your lecture notes and sources such as Parsons (2012) and Sharan (2014) for Java; Freeman and others (2008), Hammer (2013), Holzner (2006), Johnson and others (1995), Metsker and Wake (2006), Martin (2003), Shalloway and Trott (2004) for principles and design patterns and Fowler (2000, 2019), Kerievsky (2005) and Suryanarayana, Samarthyam and Sharma (2015) for refactoring and the interrelationships with design patterns.

B. Iterate through (until satisfied):

i. Identify how you would change/refactor

Perhaps the most accessible books for this are Freeman and others (2008), Hammer (2013), Holzner (2006), Fowler (2000, 2019) and Kerievsky (2005).

ii. Identify and if necessary construct tests to perform

You need to be able to have some form of testing class/es using JUnit that allow you to test. Consult your lecture notes and tutorial seven for this. The books by Langr (2015) and Parsons (2012) would also be helpful.