需要 ERD 帮助 错误跟踪系统 图片已附

发布于 2024-09-14 05:19:13 字数 386 浏览 1 评论 0原文

您能看到简单的错误跟踪系统可能遗漏的任何内容吗?

ERD http://img694.imageshack.us/img694/8166/captureqpe.jpg

这是包含新更改的更新版本

Erd2 http://img691.imageshack.us/ img691/2825/capturekh.jpg

Can you see anything that might have been left out for a simple bug tracking system?

ERD http://img694.imageshack.us/img694/8166/captureqpe.jpg

Here's an updated version with new changes

Erd2 http://img691.imageshack.us/img691/2825/capturekh.jpg

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

人│生佛魔见 2024-09-21 05:19:13

这取决于你对“简单”的定义。您没有附加文档的机制(例如屏幕截图),但简单的错误跟踪系统可能没有这些机制。

“产品”并不是很细粒度。版本号或修订版将很有用,子系统(对于更大的系统)和组件(对于更复杂的体系结构)也是如此。

此外,Bugs 表应该具有环境(开发、测试、生产等)、预计完成日期和删除截止日期的属性。能够区分谁报告了该问题以及谁正在处理该问题也很有帮助,更不用说谁最终负责确保该问题完成。

可以肯定的是,您的文本字段太短了。我的错误需要超过 255 个字符来描述!


对术语争论不休。除开发人员之外的其他人(特别是测试人员)也会对错误进行报告、进展和评论。因此 Developer 表需要一个更通用的名称。同样,并非所有内容都是错误,因此错误表应该有一个加载较少的名称,例如问题。

It depends on your definition of "simple". You don't have a mechanism for attaching documents (e.g. screen shots) but perhaps a simple bug tracking system wouldn't have those.

"Product" is not very fine-grained. Release No or Revision would be useful, as would SubSystem (for bigger systems) and Component (for more complex architectures).

Also, the Bugs table ought to have attributes for Environment (Dev, Test, Production, etc), Projected Completion Date and Drop Dead Date. It is also helpful to be able to distinguish who reported it from who is currently working on it, not to mention who is ultimately responsible for seeing it gets finished.

For certain sure your text fields are too short. My bugs require way more than 255 characters to describe!


Quibble over terminology. People other than Developers will report, progress and comment on Bugs, notably Testers. So the Developer table needs a more general name. Likewise not everything is a bug, so the Bug table should have a less loaded name e.g. Issue.

箹锭⒈辈孓 2024-09-21 05:19:13

也许是一个 Teams 表,其中包含从开发人员到代表开发人员团队的 FK。 (QA 团队、开发团队、分类团队)。

Maybe a Teams table with a FK from Developers to that representing teams of developers. (QA team, dev team, triage team).

稚然 2024-09-21 05:19:13

BUg和开发者应该是多对多的关系。会有多个开发人员被分配处理的错误。为此,您需要一个连接表。

BUg and developer should be a many to many relationship. There will be bugs that multiple developers are assigned to. You need a join table for that.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文