Skip to Content

Software Development Practices

Unit code: HIT2308

Credit points12.5 Credit Points
Duration1 Semester or equivalent
Contact hours48 hours
CampusHawthorn, Sarawak
Prerequisites
CorequisitesNil

Aims and objectives

This unit of study aims to introduce knowledge and techniques for techniques for modelling problem and solution domains for software systems.
 
Learning Outcomes
 
After successfully completing this unit, you should be able to: 
  • Identify the stakeholders and their needs from a given scenario
  • Formulates a problem statement that identifies the issues that need resolution by analysing a scenario
  • Formulate a vision statement and a set of goals for a system that will address the identified problems given a scenario and a problem statement
  • Identify and describe the main reasons why the software is to be developed 
  • Design and generate a conceptual solution which includes paper prototypes, domain models, and user stories, given a scenario, problem statement and vision statement 
  • Describe the attributes and activities involved in contemporary software development process models
  • Describe problems and solutions using contemporary documentation techniques 
  • Propose possible testing strategies for a solution 
Swinburne Engineering Competencies for this Unit of Study
 
This Unit of Study will contribute to you attaining the following Swinburne Engineering Competencies:
  • Maths and IT as Tools: Proficiently uses relevant mathematics and computer and information science concepts as tools. 
  • Practice Context: Discerns and appreciates the contextual factors affecting professional engineering practice. 
  • Engineering Methods: Applies engineering methods in practical applications. 
  • Problem Solving: Systematically uses engineering methods in solving complex problems. 
  • Design: Systematically uses engineering methods in design. 
  • Communication: Demonstrates effective communication to professional and wider audiences. 
  • Management of Self: Demonstrates self-management processes.

Teaching methods

Lecture (24 hrs), Tutorial (24 hrs)

Assessment

Examination and Assignments (individual and group)

Content

Process Models:
  • How software is built
  • Iterative, non-linear development processes
  • Models of the software development lifecycle

Problems and solutions:
  • Why software is developed
  • Problem and vision statements
  • Goals and objectives
Stakeholders and goals:
  • Users and usability
  • Sponsors and functionality


Understanding the problem domain:

  • Conceptual solutions
  • User stories
  • Domain modelling
  • Prototyping
Validation and verification:
  • Build the right product, correctly