Nexus Book: The Systems Team Process

Welcome to the Systems Team Handbook! This book serves as a comprehensive guide for the Systems Team, detailing our processes, tools, and best practices. It is designed to help both new and existing team members understand our workflows and contribute effectively to our mission of delivering high-quality systems solutions.

This book is intended for all members of the Systems Team, including:

• Fresher to Systems Team: New team members who are just starting their journey with us.

• Existing Team Members: Current team members looking to refresh their knowledge or understand new processes.

• Stakeholders: Individuals interested in understanding how the Systems Team operates and collaborates with other teams.

Getting Started:

• Introduction
  • SB- Systems Architecture Overview
• L2 to Dev Team Process Guide
  • Issue/Cases Identification & Categorization
  • Issue/Cases Analysis Guide Docs:
  • Issue/Case Routing & Documentation
• Dev Team Perspective: Execution & Responsibility
  • Task Assignment & Planning
  • Developer’s Responsibilities
  • Collaboration & Escalation
• Release Management & Deployment
  • Bugs Lifecycle & Continuous Improvement
• Development Process:
  • 1. Handling Bugs Efficiently
  • 2. Handling Features
  • 3. Handling Issues

• DI Development Process
  • 1. Motivation
  • 2. Setup
    • 2.1 Installation Tools & Libraries
    • Tech stack
    • 2.2 Required Permissions
    • 2.3 Cloning Procedure
    • 2.4 Repositories to Clone
    • 2.5 Installations
  • 3. Useful tools to have in place before starting
    • 3.1 Aliases
    • 3.2 CLI highlighting
    • 3.3 Dev containers
      • 3.3.1 Concept of building a container
      • 3.3.2 Setting up your own dev container
  • 4. Development process
    • 4.0 RCA
    • 4.1 Bugs
      • 4.1.1 Get the Ticket (Bugs)
      • 4.1.2 Reproduce the Bug (Bugs)
      • 4.1.3 Repository Setup (Bugs)
      • 4.1.4 Implementation (Bugs)
      • 4.1.5 Testing (Bugs)
      • 4.1.6 Raising a Pull Request (PR) (Bugs)
      • 4.1.7 Code Review & Revisions (Bugs)
      • 4.1.8 QA Testing (Bugs)
      • 4.1.9 Merging & Backporting (Bugs)
    • 4.2 Features
      • 4.2.1 Prepare a Design Document
      • 4.2.2 Put Down a Boilerplate of Objects and Data Structures Needed
      • 4.2.3 Repository Setup (Features)
      • 4.2.4 Implement the Methods in Each Object or Modify Existing Ones Based on the Requirements Defined in the Design Doc
      • 4.2.5 Write Unit Tests in Sync with QA for the Feature
      • 4.2.6 Write Documentation
      • 4.2.7 Add Ample Logs and Traces Without Introducing Too Much Log Spam
      • 4.2.8 Raising a Pull Request (PR) (Features)
      • 4.2.9 Code Review & Revisions (Features)
      • 4.2.10 QA Testing (Features)
      • 4.2.11 Merging & Backporting (Features)
  • Revision History
• UI Development Process (Frontend)
  • 1. Requirements for Setup
    • 1.1 Installation Tools & Libraries
    • 1.2. Required Permissions
    • 1.3. Cloning Procedure
    • 1.4. Repositories to Clone
  • 2. Workflow
    • 2.1. Get the Ticket
    • 2.2. Feature Documentation
    • 2.3. Design Review
    • 2.4. Repository Setup
    • 2.5. Implementation
    • 2.6. Unit Testing
    • 2.7. Raising a Pull Request (PR)
    • 2.8. Code Review & Revisions
    • 2.9. QA Testing
    • 2.10. Merging & Backporting
  • 3. UI - Bug Fix Workflow
    • 3.1. Get the Ticket
    • 3.2. Reproduce the Bug
    • 3.3. Repository Setup
    • 3.4. Implementation
    • 3.5. Testing
    • Next

• RTE Process: Managing Release Flow & Coordination

• QA Process: Feature & Bug Validation
  • Work Assignment & Ticket Creation

• Development & Release Process: Ensuring a Smooth Deployment

• Revision History

Revision History

Rev.	Date of revision	Description	Author	Reviewers
	03-Mar-2025	First draft	Dinesh Kumar V	Pierre Buechler
	02-Jun-2025	ReadTheDocs	Rajkumar S	Dinesh Kumar V