Software Engineering › Key terms › Y12 Secure Software Architecture › Software development steps for secure code (order)
Software development steps for secure code (order)
Process Y12 Secure Software Architecture
Definition
Requirements definition, determining specifications, design, development, integration, testing and debugging, installation and maintenance, with security considered at each step.
Example: Security is considered in requirements, then design, then testing.
Found in: syllabus, sample exam and familiarisation guidelines, school notes.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Drag into order: Drag into order (familiarisation Q1)
- Multiple choice: Pick the option that matches the definition or example.
- Short answer: Define, outline or explain it and tie it to the scenario.
Where it has appeared in the paper
Secure Software Architecture (Part C); The Software Engineering Project (Part B). Part letters follow each paper’s own layout.
Related past questions
- Familiarisation Q1 (1 mark): Development steps Secure Software Architecture (Part C) · 1 mark
- Sample exam Q1 (1 mark): Software development steps The Software Engineering Project (Part B) · 1 mark
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Software development steps for secure code (order) in Secure Software Architecture (Year 12) · study that set
- Memorise: Describe the benefits of developing secure software
- Notes: Fundamental software development steps for secure code (Secure Software Architecture (Year 12))
How to use it in an answer
A model sentence
“Requirements definition, determining specifications, design, development, integration, testing and debugging, installation and maintenance, with security considered at each step.” Then apply it: Security is considered in requirements, then design, then testing.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Identify: Recognise and name. (Sample exam Q1 (1 mark): Software development steps)
Technique for the question types
- Drag into order: Put the steps in the correct order; know the SDLC order and the web request order.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
Know the order of the software development cycle: define and understand the problem (requirements) -> plan and design -> develop/construct -> test and evaluate -> deploy/implement -> maintain.
Worked answers from the marking guidelines
Sample exam Q1 (1 mark): Software development steps (1 mark): criteria and sample answer
Criteria
1: Identifies the correct answer.
Sample answer
Documenting the needs and constraints of the software
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: Benefits of collaboration (secure development) · Benefits to an enterprise of secure development · Social, ethical and legal issues · Employment (impact) · Copyright · Intellectual property · Digital disruption · Programmed backup · SQL injection · General Data Protection Regulation (GDPR)