Request Document for Micro-Project

Request Document for Micro-Project

---

The following sections follow the typical structure of the “RSE Request Document” at University of Manchester used as part of the departmental Project Demand and Monitoring Process. It is used to record initial discussions with the customer and outlines the broad scope and gist of the project. Where possible, it also suggests fundamental requirements to help define the potential solution enough such that project effort and duration may be estimated. This information is then used for funding applications and/or scheduling and resourcing.

Callout

In your teams, you may also receive an initial request from your academic customers in a similar form, depending on your organisation’s existing workflow, which will form the basis for the work you do for them.

For this training course, the Request Document below represents the scope of the development work to allow population of the backlog.

Project Background

A local community group want to create a Collaborative Multicultural Recipe Book to celebrate the diverse range of cuisines represented in their neighborhood. The project’s goal is to collect, organize, and present recipes from various cultural backgrounds, showcasing the traditions, flavors, and cooking techniques that make each cuisine unique.

The recipe book will be compiled from contributions by community members, resulting in a well-structured, high-quality collection that can be shared as both a professionally printed book and a downloadable digital PDF.

The collection will be organized by cuisine type (e.g., Italian, Indian, Mexican, Japanese) and will follow a consistent structure and style, ensuring that every recipe is easy to read, follow, and reproduce. Contributors will be asked to provide their recipes in Markdown format to ensure uniformity and ease of editing.

The project will focus exclusively on:

• Content gathering (recipes, introductions, and images)
• Organization and categorization (correct classification by cuisine)
• Editing and proofreading for accuracy and clarity
• Quality control to maintain consistent formatting and style

No software development or custom application building will be required; the end product will be the recipe collection itself, ready for printing and digital distribution.

Requirements

All recipes must be stored in the following folder structure to ensure easy organisation:

recipes/
│
├── italian/
│   └── spaghetti_carbonara.md
│
├── indian/
│   └── chicken_tikka.md
│
├── mexican/
│   └── tacos_al_pastor.md
│
└── japanese/
    └── sushi_rolls.md

Content Guidelines for Each Recipe File

Each recipe file should contain:

• Recipe Title
• Cuisine
• Preparation Time
• Cooking Time
• Serving Size
• Ingredients (clear list with quantities)
• Method (step-by-step instructions)
• Serving Suggestions
• Photo (optional)

Primary Goals of the Project

Gather at least three recipes for each cuisine category.

1. Ensure all recipes follow the agreed structure and are placed in the correct folder.
2. Provide high-quality photographs for at least half of the recipes.
3. Include a short cultural introduction for each cuisine section.
4. Proofread and edit all recipes to ensure clarity.