Second assignment——GOAT_666’s Team up and Topic selection
| Which course does this assignment belong to | MIEC EE308FZ |
|---|---|
| What are the requirements for this assignment? | Second assignment-- Team up and Topic selection(https://bbs.csdn.net/topics/620544586) |
| Team Name | GOAT_666 |
| The objective of this assignment | We finish team‑building of 13‑member group, select Online Travel Platform as our semester project topic. This blog introduces team members, clarifies team vision, gives project timeline & milestone plan, completes task division and workload contribution statistics, formulates team member performance assessment rules, and prepares NABCD‑based PPT for 8‑min presentation. The Requirements Specification Document is attached. |
| Other Reference Documents | 《The Art of Construction》 |
2.2 Performance Assessment Plan:
1. Team Introduction
1.1 Team name: GOAT_666
Team scale: 13 people;Team Leader:Zihan Zhao
1.2 Team slogan
Team slogan: We don't intend to take a simplistic approach cause we're all of the same age.
1.3 Team member introduction
Below are templates for 13 members, fill real information afterwards.
| Name: | Zihan Zhao | ID: | 832401129(FZU) 24125750(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 832401129赵子涵 | ||||
| Personality | Has a strong sense of collective honor and the ability to think strategically. | ||||
| Technical Expertise: | Strong practical skills and proficient in the application of AI. | Hobbies: | badminton | ||
| Desired Software Engineering Role: | Overall planning, mainly responsible for web design | ||||
| Slogan: | Calm as still water | ||||
| Name: | Liucheng Wang | ID: | 832401218(FZU) 24125164(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | qq_46998935 | ||||
| Personality | Maintain a positive and optimistic attitude, with strong ability to execute plans. | ||||
| Technical Expertise: | good at frontend rendering & teamwork | Hobbies: | photography, fitness, motorcycling | ||
| Desired Software Engineering Role: | Build frontend pages, integrate backend APIs. | ||||
| Slogan: | Stay optimistic, act decisively, keep exploring. | ||||
| Name: | Ruizhi Liu | ID: | 832401114(FZU) 24125091(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 零落之雨 | ||||
| Personality | easy-going curiosity and energetic | ||||
| Technical Expertise: | coding | Hobbies: | badminton | ||
| Desired Software Engineering Role: | backend developer | ||||
| Slogan: | Will win | ||||
| Name: | Qihang Peng | ID: | 832401217(FZU) 24125504(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | makawaka | ||||
| Personality | Quietly engineer, constantly refine. | ||||
| Technical Expertise: | Back-end dev: Java/Node, MySQL, Redis, Docker. | Hobbies: | table tennis | ||
| Desired Software Engineering Role: | Backend / low-level software developer. | ||||
| Slogan: | Stay curious. Keep growing. | ||||
| Name: | Haomin Lin | ID: | 832401116(FZU) 24125512(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 832401116_林昊旻 | ||||
| Personality | Meticulous, logical thinking and good at team communication | ||||
| Technical Expertise: | PPT documentation, backend design and scheme selection | Hobbies: | basketball | ||
| Desired Software Engineering Role: | Project Analyst & Backend Designer | ||||
| Slogan: | That which does not kill us makes us stronger | ||||
| Name: | Minghao Zhang | ID: | 832401125 (FZU) 24125113 (MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | zmh_832401125 | ||||
| Personality | Conscientious, curious,and cooperative | ||||
| Technical Expertise: | Basic knowledge of Python programming | Hobbies: | Tennis, traveling, and basketball | ||
| Desired Software Engineering Role: | Software Tester / Project Coordinator | ||||
| Slogan: | Learn by doing, growthrough challenges. | ||||
| Name: | Zexin Zhang | ID: | 832401127(FZU) 24125121(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 832401127 张泽新 | ||||
| Personality | Eager to learn and conscientious | ||||
| Technical Expertise: | Basic front-end development | Hobbies: | basketball | ||
| Desired Software Engineering Role: | Frontend Developer | ||||
| Slogan: | Where there is a will, there is a way. | ||||
| Name: | Hongfu Zhao | ID: | 832401128(FZU) 24126772(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 832401128 赵泓夫 | ||||
| Personality | patient and passionate | ||||
| Technical Expertise: | basic knowledge of C++and python | Hobbies: | basketball | ||
| Desired Software Engineering Role: | front end design | ||||
| frSlogoan: | Good good study day day up | ||||
| Name: | Longzhe Lin | ID: | 832401118(FZU) 24126624(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | longzhe356‑max | ||||
| Personality | Proficient in both front‑end and back‑end development | ||||
| Technical Expertise: | Proficient in both front‑end and back‑end development | Hobbies: | Reading tech articles and playing badminton | ||
| Desired Software Engineering Role: | Back‑end Developer | ||||
| Slogan: | Stay curious, keep learning, and strive for perfection | ||||
| Name: | Wenjie Yan | ID: | 832401123(FZU) 24127116(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 2401_89483661 | ||||
| Personality | Adaptable and Strong Willingness to Learn | ||||
| Technical Expertise: | UI design | Hobbies: | badminton | ||
| Desired Software Engineering Role: | Frontend Developer | ||||
| Slogan: | There are some things money can't buy. | ||||
| Name: | Zhihua He | ID: | 832401111(FZU) 24124907(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | 何事为序 | ||||
| Personality | Passionate about learning in areas of interest | ||||
| Technical Expertise: | typing | Hobbies: | reading | ||
| Desired Software Engineering Role: | server configuration | ||||
| Slogan: | If it runs,it’s real | ||||
| Name: | Zerui Xie | ID: | 832401121(FZU) 24126683(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | Dusk_Maple | ||||
| Personality | Adaptable, thoughtful and patient | ||||
| Technical Expertise: | Solid technical expertise in Java full-stack | Hobbies: | Tennis | ||
| Desired Software Engineering Role: | Backend Software Enginee | ||||
| Slogan: | Pursue excellence in every practice | ||||
| Name: | Xinyang Zhang | ID: | 832401126(FZU) 24124991(MZU) | ||
|---|---|---|---|---|---|
| CSDN Profile: | Tribulati0n | ||||
| Personality | Enthusiastic and proactive | ||||
| Technical Expertise: | Backend programming | Hobbies: | Listening to Sivon music | ||
| Desired Software Engineering Role: | Backend Developer | ||||
| Slogan: | Never gonna give you up | ||||
1.4 Team vision:
Our goal is to build an easy‑to‑use, practical Online Travel Platform, which helps ordinary users solve troubles during travel planning. We want to integrate travel strategy sharing, attraction recommendation, hotel‑ticket reservation, travel note publishing and user comment management together to optimize the whole travel preparation experience for travelers.
We envision this platform can simplify travel planning workflows, help users quickly collect travel information, compare accommodation and ticket resources, and record personal travel memories via travel notes. For casual tourists who lack travel experience, our platform can provide reliable reference information and reduce decision‑making cost.
In the long run, we hope our product can serve young travel lovers, continuously iterate functions based on real user feedback. We focus on team collaboration, requirement analysis and user experience, and keep polishing the platform according to the idea from The Art of Construction.
1.5 Team's Group Photo:
2. Team Project
2.1 Team Project Description
- Brief Description: Our project is an Online Travel Platform, a web‑oriented travel service platform for travel enthusiasts. It combines information browsing, resource booking and content‑sharing capability, aiming to offer one‑stop travel‑planning service for users.
- major function:
- Travel strategy & attraction recommendation: Push popular scenic spots, collect and display travel guides.
- Hotel & ticket booking module: View commodity information, submit order, simulate reservation process.
- Travel note publishing: Users can post travel diaries, upload pictures, edit text content.
- Comment & rating: Users rate scenic spots / hotels and view other people’s reviews.
- Personal center: Manage personal orders, published notes, favorite travel content.
- Implementation method: We will adopt front‑end‑back‑end separated architecture. Front‑end completes page rendering and user interaction; back‑end implements business logic, user authority management and interface service; database stores user data, travel notes, commodity and comment data. We will complete requirement analysis, prototype design, iterative development, system testing step‑by‑step, pay attention to usability, stability and data security of the whole platform.
2.2 Performance Assessment Plan:
2.2.1 Project Timeline Plan
Phase 1: Requirement Analysis & Prototype Design (Week 1‑2) Team Leader: Project management, organize requirement discussion, track milestone progress, hold regular team meetings. Product & UI group: Sort out user stories, draw product prototype and UI draft. Backend group: Complete preliminary database table design. Document group: Compile Requirements Specification Document.
Phase 2: Framework Construction & Preliminary Development (Week3‑5) Frontend group: Build front‑end project framework, develop basic page components, implement login‑register, personal‑center page. Backend group: Build backend project framework, design RESTful API interface, implement user authorization module. Database group: Complete formal database creation, optimize basic table structure.
Phase3: Core‑Function Iterative Development (Week6‑8) Frontend group: Develop strategy display, booking page, travel‑note publish‑edit page. Backend group: Realize recommendation module, order simulation module, travel‑note CRUD interface, comment service. Test group: Write test cases for each module, submit bug records.
Phase4: Integration Test & Bug Repair (Week9‑10) All groups: Joint debugging of front‑end and back‑end interfaces; fix bugs found in testing. Test group: Execute system integration test, output test report. Document group: Update project‑related documents synchronously.
Phase5: Demo Polishing & Project Acceptance Preparation (Week11+) Team Leader: Overall progress review, organize demo rehearsal. DevOps member: Complete project deployment for demo display. Every member: Finish self‑check of assigned tasks, sort out project summary materials.
2.2.2 Group composition and division of labor
| Name | Role | Work Distribution | Contribution |
|---|---|---|---|
| Zihan Zhao | Team Leader | Overall project management, meeting organization, progress tracking, external communication | 15% |
| Liucheng Wang | Front‑end Developer | Front‑end framework building, basic page component development | 10% |
| Zexin Zhang | Front‑end Developer | Travel strategy & booking page development, page interaction realization | 10% |
| Ruizhi Liu | Front‑end Developer | Travel‑note publish module, UI adjustment & page optimization | 10% |
| Wenjie Yan | UI / UX Designer | Product prototype drawing, page UI design, interactive scheme design | 10% |
| Haomin Lin | Backend Developer | Backend framework building, user login & permission related API | 10% |
| Xinyang Zhang | Backend Developer | Booking & order business logic, scenic‑spot data interface development | 10% |
| Zerui Xie | Backend Developer | Travel‑note & comment module back‑end interface implementation | 10% |
| Longzhe Lin | Database Engineer | Database table design, data model adjustment, query optimization | 10% |
| Minghao Zhang | Test Engineer | Write test cases, functional test, record and track bugs | 10% |
| Zhihua He | Test Engineer | Integration test, compatibility test, test report output | 10% |
| Haomin Lin | Document Engineer | Write and update Requirements Specification Document, sort out blog materials | 10% |
| Qihang Peng | DevOps & Auxiliary | Demo deployment, environment configuration, assist cross‑group debugging | 10% |
2.2.3 Assessment Rules
Total assessment score = Objective Work(70%) + Subjective Attitude(30%)
Objective Work (70%)
- Quality of Work (30%)
- Assessment Criteria: Evaluate task completion, code / document quality, whether functions conform to requirement description, bug density.
- Project Relevance: For Online Travel Platform, ensure each core module meets requirement specification, guarantee normal operation of booking, note‑publishing, recommendation function. Reduce obvious defects in iteration.
- Work Efficiency (15%)
- Assessment Criteria: Whether finish assigned tasks according to milestone time node; response speed for requirement change & bug feedback.
- Project Relevance: Guarantee each phase output delivered on schedule; avoid blocking other teammates’ work progress.
- Technical Competence (15%)
- Assessment Criteria: Mastery of development / design / testing / document‑writing skill; rationality of technical solution.
- Project Relevance: Give play to each member’s technical advantage in front‑end, back‑end, database, UI and testing work.
- Risk awareness (10%)
- Assessment Criteria: Discover potential problems in advance, put forward solutions; pay attention to data security and user‑information protection.
- Project Relevance: Travel platform involves user personal information and order data; members need to pay attention to data security risk in development process.
Subjective Attitude (30%)
- Teamwork performance (10%)
- Assessment Criteria: Actively participate in group discussion, communicate problems timely, give help to teammates.
- Project Relevance: Our project is developed by 13‑person large‑size team; cross‑module communication and mutual assistance are essential for progress.
- Working Attitude & Meeting attendance (10%)
- Assessment Criteria: Task initiative, meeting attendance, sense of responsibility for assigned work.
- Project Relevance: Regular meetings keep the whole team aligned; positive working attitude guarantees stable advance of long‑term semester project.
- Intra‑team mutual evaluation (10%)
- Assessment Criteria: Other team members score for actual contribution, cooperation performance of the individual.
- Project Relevance: Peer evaluation reflects real‑world performance in daily collaboration, complements objective task‑based evaluation.
Reference
- CSDN assignment requirement from 2601_FZU‑MU‑SE community
- 《The Art of Construction》
相关推荐
51单片机矩阵键盘——LCD1602显示
矩阵键盘扫描(输入扫描) 原理:读取第1行(列)→读取第2行(列) →读取第3行(列) → ……,然后快速循环这个过程,最终实现所有按键同时检测的效果 在键盘中按键数量较多时,为了减少I/O口的占用,通常将按键排列成矩阵形式采用逐行或逐列的“扫描”,就可以读出任何位置按键的状态。
5款高性价比LDO芯片实测对比:从TPS7A4501到LM2940,哪款更适合你的项目?
本文通过实测对比了TPS7A4501、TPS72301、LM2937、LM2940等五款高性价比LDO芯片的核心性能。文章详细分析了跌落电压、输出噪声、静态电流及热性能等关键指标,并结合电池供电物联网节点、高精度数据采集等典型应用场景,提供了清晰的选型指南,帮助工程师根据项目需求选择最合适的LDO芯片。
RC4加密算法详解
RC4(也称为 Rivest Cipher 4)是流密码的一种形式,流密码逐字节操作数据流。RC4 流密码是使用最广泛的流密码之一,它通过算法一次一个字节地加密消息,简单并且操作速度快。RC4是一种在电子信息领域加密的技术手段,用于无线通信网络,是一种电子密码,只有经过授权的用户才能享受该服务,使用 64 位或 128 位密钥大小。它通常用于安全套接层 (SSL)、传输层安全 (TLS) 等应用,也用于 IEEE 802.11 无线 LAN 标准。在存储大量的信息时,RC4展现出它的实用性,面对大量的数据,
HEVC/VVC中R-Lambda码率控制算法原理
文章目录1. 比特分配1.1 GOP级比特分配1.2 帧级比特分配1.3 LCU级比特分配2. 码率控制2.1 λ的计算和更新2.2 参数QP的确定 VVC中码率控制算法沿用了HEVC中经典的R-λ码率控制模型,R-λ由中科大的李斌博士提出(详情参考JCTVC-K0103)。R-λ模型的基础为视频编码中 R(比特 bpp)和 D(失真 MSE)之间的双曲线模型,即 D(R)=CR−KD(R) = ...
从Applied Intelligence被拒到The Visual Computer录用:我的计算机视觉论文投稿时间线全记录(含详细修改意见)
本文详细记录了作者从Applied Intelligence被拒到The Visual Computer成功发表计算机视觉论文的全过程,重点分享了如何将模糊的拒稿理由转化为具体改进方案。文章包含技术改进细节、写作调整策略以及期刊选择经验,为计算机视觉领域的研究者提供了实用的投稿指南。


