> 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-4-development.md).

# Phase 4: Development

The development phase of the Software Development Life Cycle (SDLC) is where the software system is actually built, based on the design plans created in the previous phase. This is the phase <mark style="background-color:purple;">where the</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">**code is written, tested, and integrated**</mark> <mark style="background-color:purple;"></mark><mark style="background-color:purple;">into the final product.</mark>

## Development Phase Activities

* Implementation: This involves writing the code for the software system, based on the design plans created in the previous phase. This is the actual coding of the system and includes developing the software components and modules, database structures, and user interface.
* Testing: This involves testing the software system and identifying any defects or issues that need to be addressed. Testing is carried out at various levels, including unit testing, integration testing, and system testing.
* Integration: This involves integrating the various software components and modules into a cohesive system. This is typically done using a build management system, which automates the process of building and testing the software system.
* Deployment: This involves deploying the software system to the production environment, where it can be used by end-users. This typically involves installing the software system on the production servers and configuring it for use.

{% hint style="success" %}
The output of the development phase is a <mark style="background-color:purple;">**fully functional software system**</mark> that has yet to be tested. This system includes all the software components and modules, database structures, and user interface, and has been integrated into a cohesive system.
{% 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-4-development.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.