Skip to content
cookie
Shared flashcard decks

NSW HSC Software Engineering

HSC · NESAComputer Science571 cards

More for NESA HSC 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 the NSW HSC Software Engineering course (NESA, Software Engineering 11-12 Syllabus 2022, first examined 2025), split into the four Year 12 focus areas and then by heading in the syllabus's own order: secure software architecture, programming for the web, software automation and the software engineering project. Preliminary (Year 11) content is not examined and is left out. This course replaced Software Design and Development, last examined in 2024.

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 (16 subdecks)

  • 1. Secure software architecture154 cards
    • 1.1 Designing software24 cards
    • 1.2 Developing secure code106 cards
    • 1.3 Impact of safe and secure software development24 cards
  • 2. Programming for the web141 cards
    • 2.1 Data transmission using the web65 cards
    • 2.2 Designing web applications76 cards
  • 3. Software automation102 cards
    • 3.1 Algorithms in machine learning57 cards
    • 3.2 Programming for automation19 cards
    • 3.3 Significance and impact of ML and AI26 cards
  • 4. Software engineering project174 cards
    • 4.1 Identifying and defining72 cards
    • 4.2 Research and planning48 cards
    • 4.3 Producing and implementing23 cards
    • 4.4 Testing and evaluating31 cards

Some of its cards

  • The international organisation that sets the standards used for developing for the web
    World Wide Web Consortium (W3C)
  • Why does a team apply a testing methodology systematically, rather than just trying the software and seeing what happens?
    A systematic methodology is more likely to find faults in cases nobody thought to try casually, including rare or extreme inputs
  • A development approach where each stage of the life cycle is completed in order before the next one begins
    Waterfall (development approach)
  • Artificial intelligence (AI)
    Intelligence shown by a machine, especially when it does something that would need intelligence if a person did it
  • Why might a team choose a Waterfall approach for one part of a solution but an Agile approach for another part of the same project?
    Because different parts of a solution can have different levels of certainty in their requirements, so the approach that suits each part best can be chosen for it
  • Keeping data accessible only to the people or systems that are authorised to see it
    Confidentiality (software security)
  • Give one reason collaboration helps produce more secure software.
    Different team members bring different points of view, so a weakness one person misses another may catch
  • Before a software engineering project starts, what has to be demonstrated about the problem it will solve?
    That there is a real need for the software, or a genuine opportunity it can take advantage of
  • Polynomial regression
    A regression method that fits a curved line, rather than a straight one, to predict a continuous numeric value
  • Give one benefit of developing software securely from the start, rather than adding security later.
    Better protection of the data the software handles

And 561 more once you add the deck.