> For the complete documentation index, see [llms.txt](https://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/27.-software-engineering-i.md).

# 27. Software Engineering I

By Aniruth Narayanan

Prior to the Fall 2023 semester, Professor Hug had a lecture about software code complexity.

For the Fall 2023 semester, this lecture was adjusted to have a similar form of content with different examples and real-world experiences that I (Aniruth) have been through on my gap year from Berkeley.

The content in this GitBook has been adjusted to the newest information. Both video recordings are linked below.

{% embed url="<https://www.youtube.com/watch?ab_channel=UCBerkeleyCS61B&v=JfATr-BBPY0>" %}
Full Lecture on Software Engineering I by Aniruth Narayanan, Fall 2023
{% endembed %}

{% embed url="<https://docs.google.com/presentation/d/1ZQ35zGrbnMCIk2kr37bKyxc4RMvRBFrvZd1me2Av2hQ/edit#slide=id.g28d08577524_0_0>" %}
Lecture Slides for Software Engineering I, Fall 2023
{% endembed %}

{% embed url="<https://youtu.be/WT-sBbm6rsw>" %}
Full Lecture on Software Engineering I by Professor Hug, Fall 2022
{% endembed %}


---

# 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://cs61b-2.gitbook.io/cs61b-textbook-spring-2026/27.-software-engineering-i.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.