软件静态架构 软件组件图_软件组件分类| 软件工程

软件静态架构 软件组件图

Software Components should be appropriately characterized to build up a viable ordering and capacity conspire. However, when dealing with software, hardware should also be dealt with side by side as they both are complementary to each other. Hardware reuse has been fruitful. Hardware components are characterized by utilizing a staggered progression. At the least level, the components are portrayed in a few structures: natural language description, logic schema, timing information, and so on. The higher the level at which a component is portrayed, the more is the vagueness. This has persuaded the Prieto-Diaz's order plot.

应该适当地对软件组件进行特征化，以建立可行的订购和容量合谋。 但是，在处理软件时，硬件也应同时处理，因为它们彼此互补。 硬件重用取得了丰硕的成果。 硬件组件的特征是利用交错的进度。 至少，这些组件以几种结构描绘：自然语言描述，逻辑架构，时序信息等等。 组件描绘的级别越高，模糊性越大。 这说服了Prieto-Diaz的订单情节。

Prieto-Diaz的分类方案 (Prieto-Diaz's classification scheme)

Each component is best described according to its characteristics and facets. Objects can be classified as follows,

每个组件最好根据其特征和方面进行描述。 对象可以分类如下：

• actions they embody

  他们体现的行动

• objects which they manipulate or are manipulated by

  他们操纵或被操纵的物体

• data structures that are used

  使用的数据结构

• systems that they are part of, etc

  他们所属的系统等

Prieto-Diaz's faceted classification conspire requires picking an n-tuple that best fits a component. The faceted classification has favorable circumstances over enumerative order. Carefully enumerative plans utilize a predefined chain of command. Accordingly, these powers to look for a thing that best fit the component to be classified. This makes it hard to look through a necessary software component. In spite of the fact that cross-referencing different things can be incorporated, the subsequent system gets confounded.

Prieto-Diaz的多面分类密谋需要选择一个最适合组件的n元组。 分面分类具有优于枚举顺序的条件。 仔细的枚举计划利用预定义的命令链。 因此，这些权力寻找最适合要分类的组件的事物。 这使得很难查看必要的软件组件。 尽管可以合并交叉引用不同的事物，但随后的系统却感到困惑。

正在搜寻 (Searching)

The area vault may contain a huge number of reusable things. A prominent inquiry procedure that has demonstrated to be successful is one that gives a web interface to the storehouse. Utilizing such a web interface, one would look through a thing utilizing a rough computerized hunt utilizing watchwords, and afterward from these outcomes do browsing utilizing the connections gave to look into related things. The approximate automated search finds items that seem to satisfy a portion of the predefined necessities. The things situated through the inexact inquiry fill in as a beginning stage for perusing the vault. These fill in as the beginning stage for perusing the store. The developer may follow links to different items until an adequately decent match is found. Browsing is finished utilizing the keyword-to-keyword, keyword-to-product, and product-to-product links.

区域文件库可能包含大量可重复使用的内容。 已经证明是成功的一种突出的查询程序是给仓库提供Web界面的程序。 利用这样的Web界面，人们将使用粗略的计算机搜索(使用关键词)浏览事物，然后从这些结果中进行浏览，并利用给出的连接来研究相关事物。 近似自动搜索将查找似乎满足一部分预定义必需品的项目。 通过不精确的查询定位的事物填充为细读金库的开始阶段。 这些作为细读商店的开始阶段。 开发人员可以跟踪到不同项目的链接，直到找到足够合适的匹配为止。 使用关键字到关键字，关键字到产品和产品到产品的链接完成浏览。

仓库维护 (Repository Maintenance)

Repository maintenance includes entering new things, resigning those things which are not any more important, and adjusting the inquiry ascribes of things to improve the adequacy of search. The software industry is continually attempting to actualize something that has not been very done previously. As examples prerequisites rise, new reusable parts are recognized, which may, at last, become pretty much the measures. Notwithstanding, as innovation propels, a few components which are as yet reusable, don't completely address the present prerequisites. Then again, limiting reuse to profoundly develop components, penances one of the makes potential reuse opportunities. Making a product accessible before it has been completely evaluated can be counterproductive. Negative encounters will in general break down the trust in the whole reuse system.

存储库维护包括输入新内容，辞退那些不再重要的内容，以及调整事物的查询归因以提高搜索的充分性。 软件行业一直在努力实现以前未曾做过的事情。 随着示例先决条件的提高，人们认识到了新的可重复使用的部分，这些部分最终可能会成为措施。 尽管如此，随着创新的推进，仍有一些可重用的组件无法完全满足当前的先决条件。 再一次，限制重用以深刻地开发组件，这便成为潜在的重用机会之一。 在对产品进行完全评估之前使其可访问可能会适得其反。 负面接触通常会破坏对整个重用系统的信任。

翻译自: https://www.includehelp.com/basics/software-component-classification-software-engineering.aspx

软件静态架构 软件组件图