Essential Terms — C10
Every term you need to recognise and use correctly across C10. Click a term to reveal its definition — if you cannot define it in your own words, you cannot use it in a class write.
flowchart TD
V["C10 vocabulary"] --> A["The judgement<br/>evaluation · evaluation criteria<br/>testing · beta testing"]
V --> B["What you judge against<br/>SRS · functional requirements<br/>non-functional requirements<br/>constraints · solution boundaries"]
V --> D["Quality factors defined here<br/>efficiency: functionality<br/>effectiveness: accuracy · usability<br/>accessibility · relevance · timeliness<br/>completeness · maintainability"]
V --> E["The plan<br/>project management · Gantt chart<br/>version control · PSM"]
V --> F["Why plans move<br/>scope creep · personnel changes<br/>technical issues"]
D -.-> G["Nearby, but NOT VCAA factors<br/>reliability · fit for purpose"]
The glossary is one long list; the clusters above are the five jobs those words do in C10. The full VCAA lists are 3 efficiency factors and 11 effectiveness factors — see Efficiency vs Effectiveness for the complete table. Only the factors this glossary defines are shown.
Topics:
- Evaluation of solution against SRS and criteria
- Reviewing the development process
- Assessing plan modifications
- Evaluating plan effectiveness
- Scope creep, personnel changes and technical issues
Evaluation
The final stage of the problem-solving methodology. It checks how well the solution is satisfying the needs of the user for which it was originally created.
Evaluation criteria
Performance criteria made from the expectations and specification.
Software requirements specification (SRS)
A single document that contains the outcomes of the analysis stage of the problem-solving methodology, including scope, constraints, functional requirements and non-functional requirements.
Functional requirements
The desired operations of a program that have specified inputs, behaviours and outputs.
Non-functional requirements
Qualitative requirements of a solution, often tied to solution constraints.
Completeness
The extent to which all necessary features and functionality are included in the software.
Functionality
The extent to which a solution is suited to its purpose.
Accuracy
The degree to which software correctly performs its intended functions without errors.
Usability
The extent to which a system is easy to learn and use.
Accessibility
Ensures that software can be used by people with a wide range of abilities and disabilities.
Relevance
The degree to which software meets the current needs and requirements of its users or market.
Timeliness
The ability of software to provide information or functionality when it is needed, without undue delay.
Scope creep
The tendency for a project's requirements to increase over time, often leading to delays and budget overruns.
Personnel changes
Modifications or transitions in the team composition that can impact the development process and timelines.
Technical issues
Challenges or problems related to the technology being used in software development, potentially impacting project progress.
Project management
A method of recording the progress of a project and managing resources to operate within time, resource and cost availability.
Gantt chart
A type of bar chart or graphic timeline that shows the progress of a project by placing tasks on a timeline, often with comments or annotations.
Problem-solving methodology (PSM)
An approach that develops the stages involved in solving a problem.
Constraints
Factors that may limit or restrict solution requirements.
Solution boundaries
The limits or edges of what a project or solution will encompass.
Fit for purpose
To be well suited for a role or purpose.
Maintainability
How easy a solution is to look after once it has been put in place.
Reliability
How much a solution can be depended upon to function as designed, and for how long.
Version control
The method that keeps track of the current, most up-to-date document through a drafting process.
Testing
Checks the accuracy of information outputs.
Beta testing
The phase of software testing where a sample of the intended audience tests the software in a real environment.