Alignment with Project Requirements
The requirements for the first week of the Solution Architect project are to define the customer, detail the requirements, and perform capacity estimation. The PBL6 logbook has already completed a significant portion of this work.
1. Customer and Business Definition
- Customer Identified: The project’s objective statement clearly defines the customer as a Government-type entity focused on Smart Cities/Utilities.
- Business Problem: The logbook details the business problem through an extensive Problem Deep-dive section. This includes analysis of the passenger experience, driver feedback, and the operational inefficiencies of the current bus system in major Vietnamese cities. It establishes a clear business case for improving the public transport network’s efficiency and reliability.
2. Functional and Non-Functional Requirements
We are required to define the functional, non-functional, and out-of-scope requirements. The PBL6 logbook contains a detailed Specification Development section that covers this:
- Functional Requirements: These define what a system is supposed to do. They describe the specific behaviors, features, and functions of the system. Think of them as the “verbs” of the system—the actions it must perform. For example, “the system must authenticate a user” or “the system must process a transaction. These are captured under Customer Needs and Customer Requirements, which detail functions like real-time journey information for passengers and in-cabin decision support for drivers.
- Non-Functional Requirements: These define how the system should perform its functions. They are the quality attributes, constraints, and operational criteria the system must meet. NFRs are often quantitative and measurable. They are the “adverbs” that qualify the system’s actions. These are extensively documented under Engineering Requirements. They cover critical aspects such as ETA Accuracy, Data Reliability, Connectivity, and Compliance & Safety, complete with a weighted ranking to establish priorities.
- Out of Scope: The Existing Solutions Gaps analysis implicitly defines the project’s scope by identifying what problems current applications like BusMap and BusEye do not solve, which is the core focus of your project.
3. Capacity Estimation
The PBL6 logbook focuses on the system’s conceptual design, features, and requirements but does not include capacity estimations (e.g., number of concurrent users, data storage needs, requests per second, network bandwidth).
For our Solution Architect project, we will need to build on the logbook’s foundation by estimating these figures. This aligns perfectly with the goal of a solution architect, which is to design a system that is scalable, resilient, and performant. We can use the detailed functional decomposition in the logbook as a starting point to estimate the load on each component.