173
社区成员
发帖
与我相关
我的任务
分享| Course for This Assignment | 2401_MU_SE_EE308 |
|---|---|
| First member | Liu Danni (MU: FZU:832202208) |
| Second member | Wu Yansghun (MU: FZU:832202213) |
| Assignment requirements | Contact management system |
| Github Address | https://github.com/lnd2014/ExtremeProgramming |
| Other References | 2021最新阿里代码规范 |


Objective: Allow users to mark certain contacts as favorites for quick access.
Implementation Ideas:
star boolean field to the contacts table in your database to track whether a contact is bookmarked.Objective: Enable users to store multiple contact methods for a single contact.
Implementation Ideas:
contact_methods table, each linked to the main contacts table via a foreign key.Objective: Enable users to import and export their contacts to and from an Excel spreadsheet.
Implementation Ideas:
(1)Export:
(2) Import:
You can mark a contact as a favorite. Contacts marked as favorites can be unfavorites. Contacts that are marked as favorites will appear on the Favorites page. Make it easy to find and modify favorites
A contact can add multiple categories of information, such as phone, address, email, and so on. You can add multiple contact information to each category, associating a single contact with multiple contact information.
| Liu Danni | Wu Yangshun |
|---|---|
| Front-end frame | Front-end page function implementation |
| Implementation of front and back end interaction | Front-end page optimization |
| Back-end frame | Blog writing |
| Back-end function implementation | |
| Database implementation |
Description of the problem: The format of the data returned by the back-end is inconsistent with the format expected by the front-end, causing the front-end to fail to parse correctly.
Solution:
(1)Unified Data Format: Ensure that the data format returned by the back end is consistent with the front-end expectations.
(2)API Documentation: Provides detailed API documentation that specifies data structures and types that both front and back end developers should follow.
Description of the problem: Application status management is chaotic, resulting in data inconsistency or difficulty to maintain.
Solution:
Unified status management: ensures unified status management and operations, avoiding multiple decentralized management.
| Modules | Estimated Time(hour) | Actual Time(hour) |
|---|---|---|
| Planning | 0.5 | 1 |
| Analysis and design | 2 | 2 |
| Front-end | 8 | 10 |
| Back-end | 8 | 10 |
| Test | 2 | 4 |
| Debug | 2 | 4 |
| Blog | 1 | 2 |
| Total | 23.5 | 33 |