South Bay Streets (SBS) – Team Guide

Guide Ver 0.7 – 2025-06-03 – For South Bay Streets Ver 0.8 – R. McQuillin

1. NOTE: ROUGH DRAFT – PARTIALLY COMPLETED – WORK IN PROGRESS

2. NOTE: This document is COMPANY CONFIDENTIAL with limited distribution. It has been provided to you for early review. Please do not forward, copy, or otherwise distribute it without prior authorization.

3. WARNING: This guide may be updated often. Avoid using outdated copies. Please note the version number above. A version history is shown at the end of this guide.

Contents

Version History. 2

1 Introduction. 2

2 Other Documents. 2

2.1 Documentation Plan. 3

3 What This Project Can Do for You. 3

4 Terms and Abbreviations (Application-Specific). 3

5 The Overall Plan. 3

5.1 Create an Account. 4

6 Adopt a Style of Thinking. 4

6.1 Motivations. 4

6.2 Community Participation. 4

6.3 Elevated Purchasing / Rational Purchasing / Automatic Buying. 4

7 General Task Areas for Volunteers. 5

8 Tasks: Data Creation. 5

8.1 Maps. 5

8.2 Goals, Profiles, Projects, and Needs. 5

8.3 Categories & Classifications. 5

9 Tasks: Testing. 5

9.1 Types of Testing. 5

9.1.1 User Simulation / Actual Use (Eating the Dog Food). 5

9.1.2 Unit Testing. 5

9.1.3 Integration Testing. 5

9.1.4 Regression Testing. 5

9.1.5 Smoke Testing. 5

9.1.6 Operation Testing. 5

9.2 Ways of Testing. 5

9.2.1 Manual 5

9.2.2 Automated. 5

9.2.3 AI-Assisted. 5

10 Tasks: Creative. 6

10.1 Web Styling. 6

11 Tasks: Technical - AI 6

11.1 R.A.G. Chatbot. 6

11.2 Seller Agent. 6

12 Tasks: Technical 6

13 Tasks: Strategy. 6

14 Tasks: Infrastructure. 6

15 Tasks: Outreach/Communications/Sales. 6

16 FAQs. 6

17 Using Requests / Bug Reporting / App Tasks. 7

Version History

Version	Date	Primary Author	Change Summary
0.8	2025-03-14	R.McQuillin	Original

1 Meeting Agenda 6/5/2025

Intros

Look at the App

App Tasks

Status Reports

2 Introduction

This guide is for team members who will help develop and grow the South Bay Streets (“Streets”) project, application, and services.

3 Other Documents

There are several other documents available in this suite: User Guides, etc. Please refer to those when necessary:

1. (never complete) Streets Incoming Content (the input queue for other content)

2. (~30% complete) Streets Team Guide

3. (~70% complete) Streets Intro

4. (~50% complete) Streets User Guide

5. (~80% complete) Streets Maps Intro

6. (~30% complete) Streets Maps User Guide

7. (~70% complete) Streets Import Locations Guide

8. (~80% complete) Streets Styling Guide

3.1 Documentation Plan

Documentation

4 What This Project Can Do for You

TO BE COMPLETED.

I WANT TO HELP IF YOU WANT TO DO SOMETHING LIKE THISL

Rocha awarded Multiple Major Scholarships – La Vista (https://www.lavistamchs.com/rocha-awarded-prestigious-edition-scholarship/)

5 Terms and Abbreviations (Application-Specific)

NOTE: See also Terms and Abbreviations (General) in the Streets Introduction document. Those terms are also needed to understand this document. This is a list of additional terms specifically for the team.

Term	Meaning
Actor
Use Case	A Use Case is a “How To”: It is a task performed by an actor (a user in a role) using the application to complete an operation.
Page

CDL (Cdl)	A comma-delimited list, for example: “1,123,88” or “Lorem,ipsum,dolor,sit,amet”.
CdlWec
NvpCdl