Well, as many people there are as many answers and opinions you will probably get but here are my $0.02.
In my practice high-level design has been identifying major goals of the application, splitting them to separate global modules, sections of your website, global functionality blocks addressing particular customer/user needs. Also here I would identify the global business logic of the application. Global database design can also be a part of it, but not down to the tables or databases, but rather which data will be stored and which not, how long, etcetera.
Low-level design will in turn take each building block that came out of high-level design and break it up to even smaller parts, where you'd be thinking about your data strictures, PHP classes, database tables, data exchange and so on.
发布评论
评论（1）
好吧，有多少人就有多少答案和意见，但这是我的 0.02 美元。
在我的实践中，高层设计一直在确定应用程序的主要目标，将它们拆分为单独的全局模块、网站的部分、满足特定客户/用户需求的全局功能块。另外，在这里我将确定应用程序的全局业务逻辑。全局数据库设计也可以是其中的一部分，但不是具体到表或数据库，而是存储哪些数据、不存储哪些数据、存储多长时间等等。
底层设计将依次采用高层设计中的每个构建块，并将其分解为更小的部分，您将在其中考虑数据结构、PHP 类、数据库表、数据交换等。
Well, as many people there are as many answers and opinions you will probably get but here are my $0.02.
In my practice high-level design has been identifying major goals of the application, splitting them to separate global modules, sections of your website, global functionality blocks addressing particular customer/user needs. Also here I would identify the global business logic of the application. Global database design can also be a part of it, but not down to the tables or databases, but rather which data will be stored and which not, how long, etcetera.
Low-level design will in turn take each building block that came out of high-level design and break it up to even smaller parts, where you'd be thinking about your data strictures, PHP classes, database tables, data exchange and so on.