查看原文
其他

[字幕文本和截图]UML+Enterprise Architect建模示范视频EA013期货交易仓单系统

潘加宇 UMLChina 2023-06-27
视频片段:

*********************
购买371分钟EA013期货交易仓单系统完整视频点下面:
全程字幕-23套UML+Enterprise Architect建模示范视频>>
*********************
00:11:58,100 --> 00:12:00,560

按照现在的实现,那些按钮嘛

 

00:12:00,560 --> 00:12:01,190

对吧

 

00:12:01,190 --> 00:12:05,260

按钮、指示灯就是了,按钮输入嘛

 

00:12:05,440 --> 00:12:06,520

指示灯输出嘛

 

00:12:06,520 --> 00:12:07,090

对吧

 

00:12:07,090 --> 00:12:07,810

还有声音了

 

00:12:07,810 --> 00:12:09,220

叮咚,我到啦

 

00:12:09,220 --> 00:12:09,740

对吧

 

00:12:09,920 --> 00:12:11,960

提醒你,到了,对吧

 

00:12:11,960 --> 00:12:13,560

叮咚都是的了

 

00:12:14,190 --> 00:12:15,540

声音输出

 

00:12:16,100 --> 00:12:17,590

乘客界面类

 

00:12:17,960 --> 00:12:20,040

要区分这两个东西的区别哦

 

00:12:21,420 --> 00:12:23,640

客户代表界面的这个映射过来了

 

00:12:24,050 --> 00:12:25,520

请求开始提交

 

00:12:25,520 --> 00:12:26,590

交割预报申请

 

00:12:26,770 --> 00:12:27,970

交割预报申请

 

00:12:27,970 --> 00:12:28,790

就是一个什么

 

00:12:30,730 --> 00:12:34,070

就是一个我们要维护的一个实体类了

 

00:12:36,220 --> 00:12:36,700

 

00:12:38,180 --> 00:12:41,520

反馈......就一个,预报申请

 

00:12:41,800 --> 00:12:42,760

......

 

00:12:44,170 --> 00:12:46,330

已保存并等待仓管处理

 

00:12:46,330 --> 00:12:47,530

提醒负责人仓管

 

00:12:47,530 --> 00:12:48,790

那在这里就有什么

 

00:12:49,980 --> 00:12:51,720

仓管我们要什么

 

00:12:52,340 --> 00:12:53,120

要维护了

 

00:12:53,120 --> 00:12:57,140

因为我们系统要是没有人的信息,我们怎么提醒他,对吧

 

00:12:57,140 --> 00:12:58,250

你要有的啊,仓管

 

00:12:58,250 --> 00:12:59,450

就是我们要维护的一个

 

00:12:59,690 --> 00:13:00,800

核心概念

 

00:13:00,980 --> 00:13:01,750

还有吗

 

00:13:02,070 --> 00:13:02,700

 

00:13:04,570 --> 00:13:06,040

还有负责联系的

 

00:13:06,220 --> 00:13:06,850

对不对

 

00:13:06,850 --> 00:13:08,590

这显然是仓管的一个什么

 

00:13:09,190 --> 00:13:10,090

特点,那说明什么

 

00:13:10,090 --> 00:13:10,920

我们先把它

 

00:13:11,550 --> 00:13:13,510

把这个形容词放到

 

00:13:13,920 --> 00:13:15,390

仓管这里来哦

 

00:13:18,150 --> 00:13:20,210

一会我们再慢慢调整

 

00:13:20,410 --> 00:13:22,630

先把信息作为仓管的属性

 


00:13:22,630 --> 00:13:23,900

他是不是负责联系

 

00:13:26,290 --> 00:13:26,910

对吧

 

00:13:34,860 --> 00:13:35,430

 

00:13:38,310 --> 00:13:38,850

下面还有吗

 

00:13:38,850 --> 00:13:39,240

没有了

 

00:13:39,240 --> 00:13:39,950

我删掉

 

00:13:40,160 --> 00:13:41,090

扩展路径

 

00:13:41,090 --> 00:13:42,160

也没什么东西

 

00:13:42,340 --> 00:13:43,660

你看上面就两个类

 

00:13:43,660 --> 00:13:44,160

对吧

 

00:13:44,720 --> 00:13:46,990

一个交割预报申请,一个仓管

 

00:13:47,170 --> 00:13:48,950

那细节在下面了

 

00:13:49,130 --> 00:13:49,940

可选仓库

 

00:13:49,940 --> 00:13:51,590

可选品种要有个仓库了

 

00:13:51,590 --> 00:13:52,130

对吧

 

00:13:53,090 --> 00:13:54,130

仓库的概念

 

00:13:55,980 --> 00:13:56,830

还有呢

 

00:13:57,210 --> 00:13:58,870

品种的概念对吧

 

00:14:03,510 --> 00:14:04,780

还有合适的

 

00:14:05,060 --> 00:14:05,810

对吧

 

00:14:06,680 --> 00:14:07,610

合适的

 

00:14:07,610 --> 00:14:07,760

那么

 

00:14:09,310 --> 00:14:10,930

把合适这个写在这里

 

00:14:12,290 --> 00:14:13,900

然后后面再调整啊

 

00:14:23,750 --> 00:14:25,040

好,客户名称

 

00:14:25,040 --> 00:14:26,810

会员名称,显然客户名称

 

00:14:26,990 --> 00:14:27,670

是什么

 

00:14:28,010 --> 00:14:29,240

客户的名称了

 

00:14:29,240 --> 00:14:30,080

对不对

 

00:14:30,290 --> 00:14:32,080

那我们这有个客户对吧

 

00:14:36,650 --> 00:14:38,320

名称是它的属性

 

00:14:53,300 --> 00:14:56,400

会员,名称那就会员

 

00:14:58,800 --> 00:15:00,080

名称也是属性

 

00:15:13,270 --> 00:15:15,330

仓库有了,预报数量

 

00:15:15,950 --> 00:15:17,570

那是预报 


00:15:17,570 --> 00:15:18,860

申请里面提到的哦

 

00:15:18,860 --> 00:15:19,040

 

00:15:19,530 --> 00:15:20,920

预报数量放这里

*********************
[2020.01加一套题]UMLChina建模竞赛题大全-题目全文+分卷自测(11套110题)

[幻灯]剔除“伪创新”和“无领域”的领域驱动设计-2月25日

猴子掰玉米?比较不同版《领域驱动设计》说“不变式”和“聚合”

《软件方法》书中自测题-题目全文+分卷自测(1-8章)16套111题

软件开发团队的脓包(3)废话迷

《非程序员》电子杂志下载(39-51期)

《非程序员》电子杂志下载(1-38期)

中文书籍中对《人月神话》的引用(完结,共110本):软件工程通史1930-2019、实用Common Lisp编程……

CTO也糊涂的常用术语:功能模块、业务架构、用户需求、文档……(2020年3月更新素材)

UMLChina服务介绍


您可能也对以下帖子感兴趣

文章有问题?点此查看未经处理的缓存