Fubangbang Requirements Analysis Project Blog

Assignment 3 — Group 2

Project: Fubangbang — Campus Resource Sharing Platform

Table of Contents

• 1. Team Division of Labor
  • 1.1 Team Structure and Responsibilities
  • 1.2 Requirements Documentation and Class Diagram
  • 1.3 Member Workload and Contribution
• 2. Software Requirements Specification
  • 2.1 Project Overview
  • 2.2 Technical and Implementation Baseline
  • 2.3 SRS Content and Scope Control
  • 2.4 SRS Checklist
• 3. Team Organization and Schedule
  • 3.1 Project Schedule and Milestones
  • 3.2 Progress Tracking
• 4. Team Collaboration
• 5. Key Challenges and Countermeasures
  • 5.1 Key Challenges
  • 5.2 Project Risks and Countermeasures
  • 5.3 Risk Management Strategy
• 6. Deliverables and Links

1. Team Division of Labor

Group 2 consists of 14 members organized into four teams: the Backend Team, Frontend Team, UI and Presentation Team, and Execution Support Team. A cross-team documentation role coordinates the project blog, Software Requirements Specification (SRS), and domain class diagram with the development work.

1.1 Team Structure and Responsibilities

1.2 Requirements Documentation and Class Diagram

Chen Jiayuan is primarily responsible for the main project blog, the Software Requirements Specification (SRS), and the domain class diagram. This role includes organizing the requirements analysis, documenting system functions and constraints, preparing the class diagram, and integrating the project documentation.

Coordination with the backend, frontend, and UI teams helps keep the documents consistent with the intended system design and current development status. The documentation role also checks that the SRS, class diagram, interface prototype, and implementation describe the same system scope.

1.3 Member Workload and Contribution

The following contribution percentages apply specifically to this requirements analysis assignment, rather than to the overall software project. They reflect the team's allocation of work for this assignment.

The contribution percentages shown above sum to 100%. They describe the workload for this assignment only and should not be interpreted as the members' contributions to the entire software project.

2. Software Requirements Specification

2.1 Project Overview

Fubangbang is a campus-oriented web application designed for second-hand resource exchange and campus information sharing among students of Fuzhou University.

The project focuses on two main areas: campus second-hand trading and campus information sharing. Students can browse and publish second-hand items and access useful campus information through the platform. The interface prototype also presents campus forum and related information-sharing interactions.

The goal is to provide students with a convenient platform for finding campus resources, sharing useful information, and improving everyday campus life.

2.2 Technical and Implementation Baseline

The project uses a separated frontend and backend architecture.

Frontend: Vue 3, TypeScript, Vue Router, and Vite.

Backend: FastAPI, SQLAlchemy 2, and Pydantic.

The current backend provides a foundation for user authentication, profile management, product management, favorites, and transaction requests. The initial frontend and backend frameworks have been prepared, but frontend-backend integration has not yet been completed.

2.3 SRS Content and Scope Control

The SRS organizes the project requirements through an introduction, overall system description, user scenarios, domain class diagram, interface prototypes, functional descriptions, and acceptance and verification criteria.

The document focuses on the actual requirements of Fubangbang and distinguishes intended functionality from features that have not yet been fully implemented or integrated. This prevents prototype interactions from being presented as completed backend functionality.

The SRS, class diagram, interface prototype, and source code must remain consistent as development continues. Important changes to requirements or implementation should be reviewed and reflected in the relevant documents.

The complete SRS document is linked in Section 6.

2.4 SRS Checklist

Before submitting the SRS, the team checks whether the required sections are present and consistent with the project design and implementation. The checklist below records the current document scope and the final checks that should be performed.

This checklist is intended to support the final review rather than to replace the SRS itself. Any incomplete item should be corrected or clearly identified before submission.

3. Team Organization and Schedule

3.1 Project Schedule and Milestones

The project is planned to run from September 30 to December 14, 2026. The following milestones describe the team's roadmap and are subject to adjustment according to actual development progress.

3.2 Progress Tracking

The team tracks progress against the project milestones and monitors the completion of expected deliverables. The current priority is to align the frontend with the supported backend APIs and verify the main workflows.

Prototype-only functions will remain separate from functions that have been implemented and tested. Unresolved issues will be recorded, and task priorities will be adjusted when necessary.

The team aims to complete and verify the core workflows before expanding optional features, while preparing the final deliverables before December 14, 2026.

4. Team Collaboration

The team uses a four-team structure to allocate responsibilities while coordinating requirements, design, implementation, and presentation materials across different roles.

This collaboration structure helps reduce misunderstandings between teams and supports consistency between the requirements, interface design, class diagram, and implementation.

5. Key Challenges and Countermeasures

5.1 Key Challenges

5.1.1 Frontend and Backend Integration

The frontend and backend are maintained in separate repositories. API requests, data formats, and authentication mechanisms must work together correctly. Although the initial frameworks have been prepared, integration has not yet been completed.

5.1.2 Consistency Between Requirements and Implementation

The SRS, class diagram, interface prototype, and source code must remain consistent. Some interactions visible in the prototype are not yet supported by completed backend services. The team must distinguish planned functionality from functionality that has been implemented and tested.

5.1.3 Data Management and Access Control

Product management, favorites, and transaction requests connect users and products. Data must remain consistent, and users must be limited to authorized operations. These relationships need to be reflected correctly in the data model and verified during implementation and testing.

5.1.4 Limited Development Time

The project must progress from initial frameworks to integration, testing, and final delivery within the course schedule. Essential workflows therefore take priority over optional features.

5.2 Project Risks and Countermeasures

5.3 Risk Management Strategy

The team plans to manage these risks through regular progress reviews, clear task ownership, incremental integration, and functional testing.

Priority will be given to backend-supported workflows for user authentication, product management, favorites, and transaction requests. Each integrated workflow will be tested before it is considered complete.

By tracking unresolved issues and adjusting priorities according to actual progress, Group 2 aims to reduce integration risks and deliver a stable version of Fubangbang by December 14, 2026.

6. Deliverables and Links

6.1 Software Requirements Specification (SRS)

The Software Requirements Specification describes the objectives, scope, system requirements, domain class diagram, interface prototype, functional descriptions, and acceptance and verification criteria of Fubangbang.

• SRS Word Version (.docx): Download the SRS Word document

• SRS PDF Version: Fubangbang_SRS_Group2_Assignment3.pdf

• Direct SRS Link:
  

  Fubangbang_SRS_Group2_Assignment3.docx 3.80M

• Class Diagram:
  

  类图.png 1.02M

The Word version is the required electronic document for this assignment. The PDF version is provided for convenient online reading.

6.2 Requirements Analysis Presentation

The presentation summarizes the project's background, objectives, requirements analysis, domain class diagram, interface prototype, team organization, division of labor, and workload distribution.

• Presentation PDF: 福帮帮_课堂汇报_最终版.pdf

• Editable PowerPoint (.pptx): Download the final presentation PPTX

• Direct PPT Link:
  

  福帮帮_课堂汇报_最终版.pptx 4.10M

6.3 Assignment References

• Previous Group 2 Blog: Open the previous group blog

• Third Assignment Requirements: Open the assignment requirements

• Backend Repository: Aurowisp/Backend

• Frontend Repository: Aurowisp/Frontend

These deliverables document the current requirements analysis and provide a reference for subsequent development, integration, testing, and final demonstration.