Skip to content

Content / Knowledge

Textbook focus

Software Development VCE Units 3&4, Chapter 4, textbook pages 135-157.

Software solution specifications

The textbook explains that the SRS provides the framework for your design work. Your design options should respond directly to the factors identified in the SRS.

For Unit 3 Outcome 2, you create two to three designs and then fully specify one preferred design.

Key Point

If a feature or function is not included in the specifications, it will not be in the design and it will not be an evaluated design criterion.

If changes are discovered after the SRS has been finalised, the textbook states that those changes should be recorded in the project management progress report and Gantt chart.

Thinking used to generate design ideas

Convergent thinking

Convergent thinking involves coming up with a single, well-established answer to a problem. The textbook links this to:

  • research
  • looking at other software with similar purposes
  • interviews
  • observations
  • using proven ideas as a basis for design ideas

Divergent thinking

Divergent thinking is more creative and explores many possible solutions. The textbook links it to spontaneous, free-flowing techniques such as:

  • mind mapping
  • brainstorming
  • meditation
  • role-playing

Combining both

The textbook argues that neither convergent thinking nor divergent thinking is enough on its own. The most effective approach is to combine both so that the design ideas are creative but still worth further exploration.

Techniques for design ideation

The textbook states that ideation techniques should aim to find the most effective and efficient software solution, while taking into account the functional and non-functional requirements of the solution.

Mood boards

A mood board is a visual tool used early in the UI design process to communicate the overall feeling or atmosphere of a project. It can include:

  • images
  • text
  • colours
  • patterns
  • other design elements

The textbook explains that mood boards help gather inspiration, explore different visual directions and create shared understanding between designers, clients and stakeholders.

Brainstorming

Brainstorming is described as a non-judgemental, spontaneous and unstructured process where no idea is criticised or rejected. The textbook stresses that:

  • every idea goes onto the list
  • no one should judge a contribution
  • one person should talk at a time
  • only one idea should be considered at a time

This helps generate a large number of possible ideas.

Mind mapping

Mind mapping involves quickly generating and linking ideas. The textbook describes it as a creative and flexible tool that allows you to:

  • add ideas
  • connect ideas
  • organise ideas
  • reorganise ideas

Electronic mind maps can be saved, edited, printed or transferred to another document.

Graphic organisers

Graphic organisers are visual methods of organising ideas. The textbook gives PMI as one example:

  • Plus
  • Minus
  • Interesting

It also mentions other organisers such as spider diagrams, concept webs, ranking ladders, stair steps, chain of events, sequence charts, pie charts, organising trees and Gantt charts.

Sketches and annotations

Sketches and annotations are used for:

  • brainstorming
  • communicating ideas
  • detailing software architecture

The textbook explains that sketches help designers visualise user interfaces, system architecture and data flow, while annotations add detail about:

  • functionality
  • behaviour
  • design rationale
  • technical requirements
  • constraints

Initial sketches can become the foundation for more detailed designs or prototypes.

Evaluating design ideas

The textbook is explicit that the first design idea will rarely be the best one. A different strategy may be:

  • cheaper
  • easier
  • faster
  • more effective
  • better suited to the client's needs

Providing a range of design ideas allows the client to choose the solution that best suits them.

When evaluating design ideas, the textbook says you should consider:

  • current functional requirements
  • current non-functional requirements
  • relevant constraints

Possible effectiveness criteria

The textbook lists effectiveness criteria such as:

  • accessibility
  • accuracy
  • attractiveness
  • clarity
  • communication of message
  • completeness
  • maintainability
  • readability
  • relevance
  • timeliness
  • usability

Possible efficiency criteria

The textbook lists efficiency criteria such as:

  • cost of data and file manipulation
  • functionality
  • speed of processing

Other useful considerations

The textbook also says it is helpful to consider:

  • ease of use
  • implementation time
  • scalability
  • future modification and enhancement
  • how well the design satisfies requirements
  • how well the design copes with constraints
  • ease of implementation
  • development cost
  • future running and maintenance costs
  • labour required
  • likely disruption
  • compatibility with existing hardware, software, data and procedures
  • training required for staff

Important

The textbook states that evaluation criteria must ask a question.

Examples given in the textbook include:

  • Is the software easy to use?
  • Can the software be implemented quickly?
  • Can the software be scaled for more users?
  • Can the software be simply modified?
  • Can the software be implemented easily?

Evaluation criteria should ideally be recorded in a table, and the outcome for each criterion should be documented as each design is evaluated.

Efficiency and effectiveness

The textbook explains that an evaluation strategy is normally created at the end of the design stage. This strategy specifies:

  • when evaluation will occur
  • what data will need to be collected
  • which methods and techniques will be used to collect that data
  • how the collected data relates to the criteria written in the design stage

Efficiency

Efficiency is concerned with how much time, cost and effort has been applied to achieve the intended results.

Effectiveness

Effectiveness is concerned with how well the solution achieves its intended results.

Textbook examples of effectiveness questions

Criterion Example evaluation questions from the textbook
Accessibility How well can the system be accessed by someone who is hearing impaired or vision impaired? Does the solution use a colourblind-safe palette? Do images have ALT tags? Will a screen reader work with the solution?
Accuracy Is stored data accurate in relation to how it was entered? Are calculations accurate 100% of the time? Are reports produced within correct date ranges, including boundary values?
Attractiveness Are the colours used throughout the software complementary? Are the colour choices appropriate to the context?
Clarity Is the language age-appropriate? Are headings, labels and buttons used consistently?
Communication of message Have appropriate and region-specific conventions been used for displayed data, such as currency conventions, date and time format, and alignment?
Completeness Were all required functional and non-functional requirements implemented?
Maintainability Are there clear processes for logging and tracking bugs? Is there a schedule for monitoring and evaluating system performance?
Readability Can every part of the software be read easily by users? Are fonts, contrast and text colour appropriate?
Relevance Is the information shown relevant to its intended use? Are there parts of the system that are rarely or never used?
Timeliness Does the software respond within an acceptable time frame?
Usability Are the elements of the software easy to use? Are there sections where users are more likely to make errors?