A typical WebApp contains a vast ar

A typical WebApp contains a vast array of content -text , graphics,applets, scripts, audio/vedio files, form active page element, tables, streaming data, and many others.
The challenge is to organize this sea of content into a rational set of configuration objects (section 22.1.4) and then establish appropriate configuration control mechanisms for these objects.
One approach is to model the WebApp content using conventional data modeling modeling techniques , attching a set of specialized properties to each object
the static/dynamic nature of each object and its projected longevity (e.g, temporary, fixed existence, or permanent object) are examples of properties that are required to establish an effective SCM approach
For example if a content item is changed hourly, it has temporary longevity
The control mechanisims for this item would be different (less formal) than those applied for a form component that is permanent object

ผลลัพธ์ (อังกฤษ) 2:

A Typical WebApp Contains a VAST array of content -Text, Graphics, applets, Scripts, audio / vedio Files, page Active Form Element, Tables, Streaming Data, and many others.
The Challenge is to Organize this content Into a Sea of Rational Set. Objects of configuration (Section 22.1.4) and then establish appropriate configuration Control Mechanisms for these Objects.
One is to Model Approach The WebApp content using conventional Modeling Data Modeling Techniques, attching a Set of specialized Properties to each object
The static / Dynamic Nature of. each object and ITS projected Longevity (eg, temporary, Fixed existence, or Permanent object) are examples of Properties that are Required to establish an Effective SCM Approach
For example IF a content Item is changed hourly, it has temporary Longevity
The Control mechanisims for this. item would be different (less formal) than those applied for a form component that is permanent object.