Redefining Data Engineering with AI

Chapter 4. Designing with Context

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 4th chapter of the final book. There is an active GitHub repository for this book.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

Returning to the friend’s reunion analogy from the previous chapter, the group decided on the reunion, the activities they wanted to do, and the things they would need. The next planning involves inventorying what they already have, identifying what must be procured, and informing everyone who will attend. These post steps are the focus of this chapter. After requirements are solidified, every company has constraints on architectural components, optimization choices, and logging decisions. With AI as a new teammate, decision logging takes on an additional dimension.

In the previous chapter, we covered the first part of planning: creating the DRD (see “Introduction to Planning with AI” in Chapter 3). The business analyst agent has turned a vague business request into a structured document for Patient 360. Let’s look at the next roles in the planning workflow, that helps is designing the artifacts needed with the context we have from DRD.

The Data Architect

In many organizations, ...