CASL Technology
Surrey Downs
South Australia
SA 5127
Tel (+61) 8 8288 7528
(+61) 466 390 197

Software Development

CASL internally is working to ISO accreditation, developing it's software processes around the ISO 12207 standard.

This means that each development follows the process of:

  • Concept document
    • This is a high level document intended to provide the broad aims and goals of the project. Spanning from a side of A4 to many pages this provides focus and limitations on what will be produced.
  • User Requirements
    • This is a document outlines key functions, demonstrated via
      • Use cases - simple descriptions with diagrams and flowcharts where needed of small pieces of functionality
      • UI Mock ups where relevant
    • We also capture any non-functional requirements here, such as operating environment, time constraints intended loading etc.
  • System Requirements
    • This covers the system as a whole and includes the hardware and software. Interfaces between hardware and software will be identified at this stage.
  • Architecture
    • Providing viewpoints from many areas such as:
      • Users
      • Sponsor
      • Developer
      • Maintainer
      • Hardware
      • Software
    • This document starts to ascribe functionality from the system requirements to elements of the hardware and software.
  • Hardware Requirements
    • If hardware is involved this document outlines the needed functionality.
  • Software Requirements
    • This documents the software requirements calling on all the previous documents.
  • Hardware/Software architecture
    • A high to medium level document of the hardware and software designs as a whole. This will identify in detail interfaces between HW and SW, and between any significant modules of HW or SW.
  • Detailed design documents
    • Each element has a design stage, followed by implementation and documenting of the implementation.
  • Testing
    • A set of testing documentation will be drawn up testing against the requirements.

CASL uses an automated package to track requirements through the levels and also has a specified tailoring processes based on project size, user and intended function that allows some or most of these stages to be omitted.

The tailoring process is in itself a key part, since it highlights the down track issues if parts are skipped and the resultant issues in cases of high integrity or high volume products.

Related resources