Przejdź do treści

VCE Applied Computing: Software Development

VCE · VCAAComputer Science554 fiszki

554 fiszki dla VCAA VCE Computer Science, przygotowane przez cookie, w 58 podzestawach z tematami zgodnymi z kursem.

Ucz się z tych kart

Wybrane dla tego samego kursu na podstawie tego, z czego ludzie najczęściej korzystają. Wszystko można przeczytać bez konta.

Wszystko dla Computer Science

Szukasz pomocy z Computer Science?

Cookie Tutoring, nasza własna usługa korepetycji, może mieć korepetytorów z przedmiotu Computer Science. Lekcje odbywają się na żywo i indywidualnie, a pierwsze 15 minut z każdym korepetytorem jest bezpłatne.

Znajdź korepetytora

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).

Dodając zestaw, otrzymasz własną kopię wraz ze wszystkimi podzestawami. Każda fiszka będzie wracać tuż przed tym, jak miałbyś(-abyś) ją zapomnieć, a każda odpowiedź dobra lub zła wpłynie na poziom opanowania danego tematu. Gdy zestaw będzie już twój, możesz usunąć lub zawiesić te części, których się nie uczysz.

Co zawiera (58 podzestawów)

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

Niektóre fiszki z tego zestawu

  • Recognising aspects of a problem that can be worked out by computation, and thinking logically, algorithmically and inferentially, typically through decomposition, pattern recognition, abstraction, modelling and algorithms
    Computational thinking
  • 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
  • User-centred design
    Designing a solution around the needs, abilities and preferences of the people who will use it
  • An approach to identifying and solving problems that looks at the whole system, by analysing how its parts interact and affect each other
    Systems thinking
  • Breaking a complex problem down into smaller, more manageable parts
    Decomposition
  • Design stage (problem-solving methodology)
    The stage that determines how a solution will function and appear, using design tools and design principles
  • What makes code 'clear and concise' as a characteristic of an effective solution?
    It is easy to read and does not contain unnecessary or repeated instructions
  • Give one goal a medium or large organisation might have that relates to secure software development.
    Protecting its data and systems from being compromised
  • Identifying similarities or trends within a problem, or between it and a problem already solved
    Pattern recognition (computational thinking)
  • Which problem-solving methodology stage produces the document that sets out a solution's requirements, constraints and scope?
    The analysis stage

I jeszcze 544, gdy dodasz talię.