> For the complete documentation index, see [llms.txt](https://qatesting.gitbook.io/qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qatesting.gitbook.io/qa/manual-testing/sdlc/phase-3-design.md).

# Phase 3: Design

The design phase of the Software Development Life Cycle (SDLC) is where a <mark style="background-color:yellow;">detailed plan for the software development process is created</mark>, based on the requirements gathered in the previous phase.&#x20;

## Design Phase Activities

* System design: This involves creating a high-level design for the software system, including its architecture, components, and interfaces. The system design is intended to provide a blueprint for the software development process and is typically documented in a system design document.
* Software design: This involves designing the software components and modules required to implement the system design. The software design is intended to provide a detailed plan for the development of the software and is typically documented in a software design document.
* Database design: This involves designing the database schema and data structures required to support the software system. The database design is intended to ensure that the software system can efficiently store, retrieve, and process data, and is typically documented in a database design document.
* User interface design: This involves designing the user interface for the software system, including the layout, navigation, and visual design. The user interface design is intended to ensure that the software system is intuitive and easy to use, and is typically documented in a user interface design document.

{% hint style="success" %}
The **output** of the design phase is a **set of documents** that provide a detailed plan for the software development process. These documents typically include the system design document, the software design document, and the database design document.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://qatesting.gitbook.io/qa/manual-testing/sdlc/phase-3-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.