Skip to content
cookie
Shared flashcard decks

VCE Applied Computing: Software Development

VCE · VCAAComputer Science554 cards

More for VCAA VCE Computer Science

Picked for the same course from what people use most, and all of it can be read without an account.

Everything for Computer Science

Looking for help with Computer Science?

Cookie Tutoring, our own tutoring service, may have tutors for Computer Science. Lessons are live and one to one, and the first 15 minutes with any tutor is free.

Find a tutor

Flashcards for VCE Applied Computing: Software Development Units 3 and 4, split by area of study and then by key knowledge topic, following the study design accredited from 2025. Pseudocode uses the study design's own conventions (BEGIN/END, IF/ELSEIF/ELSE, REPEAT/UNTIL, WHILE/DO, FOR/NEXT).

Adding it gives you your own copy, with every subdeck below. Each card then comes back just before you would forget it, and every one you get right or wrong counts towards your mastery of its topic. You can delete or suspend the parts you are not studying once it is yours.

What is inside (58 subdecks)

  • Unit 3 Area of Study 1: Software development, programming215 cards
    • 0. Computational thinking6 cards
    • 1. Emerging trends: AI in programming7 cards
    • 2. Design tools for representing modules17 cards
    • 3. Data types11 cards
    • 4. Data structures13 cards
    • 5. Data sources7 cards
    • 6. Principles of OOP12 cards
    • 7. Features of a programming language34 cards
    • 8. Naming conventions11 cards
    • 9. Validation techniques11 cards
    • 10. Internal documentation6 cards
    • 11. Algorithms: searching and sorting23 cards
    • 12. Types of errors21 cards
    • 13. Debugging and testing techniques18 cards
    • 14. Problem-solving methodology: development7 cards
    • 15. Tracing pseudocode8 cards
    • 16. Tracing class methods3 cards
  • Unit 3 Area of Study 2: Software development, analysis and design179 cards
    • 1. Problem-solving methodology: analysis and design9 cards
    • 2. Reasons for software development projects4 cards
    • 3. Features of a brief10 cards
    • 4. Project management with Gantt charts15 cards
    • 5. Methods for collecting data11 cards
    • 6. Functional and non-functional requirements9 cards
    • 7. Solution constraints15 cards
    • 8. Solution scope5 cards
    • 9. Analytical tools22 cards
    • 10. Software requirements specification6 cards
    • 11. Legal requirements22 cards
    • 12. File management techniques11 cards
    • 13. Ideation techniques and tools10 cards
    • 14. Evaluation criteria5 cards
    • 15. Design tools for generating designs5 cards
    • 16. User experience (UX)8 cards
    • 17. Design principles12 cards
  • Unit 4 Area of Study 1: Software development, development and evaluation77 cards
    • 1. Characteristics of efficient and effective solutions9 cards
    • 2. Choosing data types, structures and sources7 cards
    • 3. Access modifiers9 cards
    • 4. Established and innovative development approaches10 cards
    • 5. Debugging and alpha testing10 cards
    • 6. Beta testing9 cards
    • 7. Evaluation strategies7 cards
    • 8. Factors affecting project plan effectiveness7 cards
    • 9. Recording project progress5 cards
    • 10. Assessing a project plan's effectiveness4 cards
  • Unit 4 Area of Study 2: Cyber security, secure software development practices83 cards
    • 1. Organisational context12 cards
    • 2. Vulnerabilities and risks in insecure environments14 cards
    • 3. Security controls8 cards
    • 4. Threat modelling principles5 cards
    • 5. Legislation and industry frameworks9 cards
    • 6. Ethical issues in software development6 cards
    • 7. Mitigation and improvement strategies9 cards
    • 8. Evaluating security practices4 cards
    • 9. Applying security controls to scenarios8 cards
    • 10. Categories of security threats8 cards

Some of its cards

  • Analysis stage (problem-solving methodology)
    The stage that determines what is required to solve a problem, by acquiring and analysing data and identifying requirements, constraints and scope
  • New features or requirements being added to a project after it has started, without adjusting its time frame or resources
    Scope creep
  • What does comparing actual versus expected durations on a project plan show?
    Whether tasks are taking more or less time than planned
  • Measures used to judge how well design ideas, and later the whole solution, meet requirements
    Evaluation criteria
  • Hiding the complex detail of how an object works and exposing only what a user of the object needs
    Abstraction (OOP)
  • User-centred design
    Designing a solution around the needs, abilities and preferences of the people who will use it
  • Beta testing
    A testing phase in a production-like environment that checks a solution is stable, usable and meets requirements for its intended users
  • A data structure that stores a list of values of the same data type, each accessed by a single index
    One-dimensional array
  • Essential Eight
    An Australian Government framework of eight strategies organisations can follow to mitigate cyber security incidents
  • What is an interview, as a method of collecting data for a software project?
    Asking a person questions directly, in person or remotely, to gather their needs and requirements

And 544 more once you add the deck.