Nat 5 Computing SDD - Review

• Computing
• Upper Secondary (Key Stage 4)
• GCSE

Nat 5 Masterclass:

 The Software Design Process

Learning Objective

At the end of the lesson, you will be able to understand the steps involved in the software design process and create a basic design document for a software application.

Introduce the topic and explain what students will learn in the lesson.

What do you already know about designing software applications?

Identify the problem in terms of Input-Process-Output

Identify the datatypes and structures required for implementation

Describe, exemplify, and implement appropriately:

• Data types and structures
• Algorithm specification
• Computational constructs

Describe, identify, exemplify, and implement normal, extreme, and

exceptional test data for a specific problem, using a test table. 

Explain the difference between syntax, execution and logic errors;

User guide - how to use the program

Technical guide: minimum requirements installation guide and other requirements

Describe, identify, and exemplify the evaluation of a solution in terms of:

• fitness for purpose
• efficient use of coding constructs
• robustness
• readability

Identify instances were maintenance would be required

The Software Design Process is an iterative process. Explain why it may be required to return to the design stage (2022-Q9) 1 mark

Possible answers:

The program is not fit for purpose

New functionality is requested

Logic errors are found at a later stage

Design Document Components

A design document typically includes an introduction, requirements, analysis, design, implementation, testing, deployment, and maintenance sections.

Describe the components of a design document and provide examples.

Introduction Section

The introduction section of the design document provides an overview of the software application and its purpose. It should also include information about the intended audience and any constraints or limitations.

Explain the purpose of the introduction section and provide examples.

Requirements Section

The requirements section of the design document should outline the needs of the user and the problem that the software application will solve. It should also include any functional and non-functional requirements.

Explain the purpose of the requirements section and provide examples.

Analysis Section

The analysis section of the design document should break down the requirements into smaller, more manageable parts and identify any potential challenges or roadblocks. It should also include information about the project scope and timelines.

Explain the purpose of the analysis section and provide examples.

Design Section

The design section of the design document should include diagrams, flowcharts, and other visual aids to help explain how the software will work. It should also include information about the software architecture and any design patterns used.

Explain the purpose of the design section and provide examples.

Implementation Section

The implementation section of the design document should include information about the programming language, tools, and frameworks used to build the software application. It should also include information about the coding standards and conventions used.

Explain the purpose of the implementation section and provide examples.

Testing Section

The testing section of the design document should include information about the testing strategy and any testing tools used. It should also include information about the types of testing performed, such as unit testing and integration testing.

Explain the purpose of the testing section and provide examples.

Deployment Section

The deployment section of the design document should include information about how the software application will be released to the intended users. It should also include information about any installation requirements and support documentation.

Explain the purpose of the deployment section and provide examples.

Maintenance Section

The maintenance section of the design document should include information about how ongoing support for the software application will be provided. It should also include information about any future updates or changes that may be necessary.

Explain the purpose of the maintenance section and provide examples.

Conclusion

In conclusion, the software design process is an important step in creating a successful software application. By following the steps outlined in this lesson, you can create a basic design document for your own software projects.

Summarize the key points of the lesson and encourage students to apply what they have learned.

Write down 3 things you learned in this lesson.

Have students enter three things they learned in this lesson. With this they can indicate their own learning efficiency of this lesson.

Write down 2 things you want to know more about.

Here, students enter two things they would like to know more about. This not only increases involvement, but also gives them more ownership.

Ask 1 question about something you haven't quite understood yet.

The students indicate here (in question form) with which part of the material they still have difficulty. For the teacher, this not only provides insight into the extent to which the students understand/master the material, but also a good starting point for the next lesson.