-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
aae5c10
commit 3b72bae
Showing
5 changed files
with
22 additions
and
4 deletions.
There are no files selected for viewing
Binary file added
BIN
+179 KB
...ress/public/images/article/project/group-buy-market/group-buy-market-1-3-01.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+119 KB
...ress/public/images/article/project/group-buy-market/group-buy-market-1-3-02.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+237 KB
...ress/public/images/article/project/group-buy-market/group-buy-market-1-3-03.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+310 KB
...ress/public/images/article/project/group-buy-market/group-buy-market-1-3-04.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,33 @@ | ||
--- | ||
title: 第1-3节:研发系统设计 | ||
lock: no | ||
pay: https://t.zsxq.com/ESHMx | ||
--- | ||
|
||
# 第1-3节:研发系统设计 | ||
# 《拼团交易平台系统》第1-3节:研发系统设计 | ||
|
||
作者:小傅哥 | ||
<br/>博客:[https://bugstack.cn](https://bugstack.cn) | ||
|
||
> 沉淀、分享、成长,让自己和他人都能有所收获!😄 | ||
## 一、前言 | ||
大家好,我是技术UP主小傅哥。 | ||
|
||
... 新章节,编写中 | ||
对于程序员👨🏻💻来说,虽然写代码是最直接的工作体现,但工作可不是就只写代码。就一个产品功能需求而言,研发在参与评审后,还需要对需求进行功能的研发系统设计。 | ||
|
||
这个过程是比较消耗时间的,一般在2-3天完成,或者大型项目与外部对接的较多的情况,会需要3-5天以上。一般初级的开发在不具有系统的把控能力的时候,会考虑在工程中写伪代码的过程,来梳理系统设计。包括;涉及模块、功能流程、外部对接、接口字段等,全新的系统还要做架构的设计、分层的设计、模块的设计等。 | ||
|
||
那么对于小伙伴们学习的本节来说,就是一个全新的系统,我们可以全部的了解到系统设计所需的内容。 | ||
|
||
## 一、本章诉求 | ||
|
||
通过对拼团需求的理解,进行研发系统设计。包括;用例图、系统建模、工程模型、功能流程、UML时序图。另外像是库表设计已经在前面完成了,它也属于研发系统设计的一部分,提前做了这部分是为了让大家更好的理解系统需求。 | ||
|
||
## 二、设计目的 | ||
|
||
为什么,不上来就写代码? | ||
|
||
在15年刚加入互联网大厂的时候,基本上是一上来就写代码。产品聊完需求,研发简单记录,之后就是打开工程直接编码了。需求是上午写的,代码是下午干的。这样对于刚起步阶段是比较合适的,可以快速迭代。 | ||
|
||
但随着公司的体系化越来越完整,一个小项目也变成一个个独立业务线的大项目,一个人开发也变成了一个团队开发。所有的系统功能的实现,一点点小问题,都可能是一个个大问题。甚至一个bug,一会时间就会被传到微博,之后就是一片的舆情和客诉。 | ||
|
||
所以,到了目前这个阶段,研发不能只是为了功能而直接开发。还要遵守一些列的流程,确保开发迭代的需求,都能平稳的交付。所以要有研发设计、要有评审、要有测试、要有预发、要有黑白名单验证和功能切量。 |