Ȩ > Ç¥ÁØÈ °³¿ä > TTAÀÇ Ç¥ÁØÇöȲ
Ç¥ÁعøÈ£ | TTAE.OT-01.0002 | ±¸Ç¥ÁعøÈ£ | |
---|---|---|---|
Á¦°³Á¤ÀÏ | 2005-12-21 | ÃÑÆäÀÌÁö | 66 |
ÇѱÛÇ¥Áظí | ¾îÇø®ÄÉÀÌ¼Ç °ü¸® ¸ðµ¨ | ||
¿µ¹®Ç¥Áظí | Understanding the Application Management Model | ||
Çѱ۳»¿ë¿ä¾à | Åë½Å¿î¿ëȯ°æÇÏÀÇ Ç¥ÁØÈµÈ ¿î¿ë °ü¸® ÇÁ·Î¼¼½º Á¤¸³À» À§ÇÏ¿© º» Ç¥ÁØ¿¡¼´Â CIM Application Management Model À» Á¤ÀÇÇÏ¿© °ü¸® ¼ÒÇÁÆ®¿þ¾î¿Í ¾îÇø®ÄÉÀ̼ǿ¡¼ °øÅëÀûÀ¸·Î ÇÊ¿ä·Î ÇÏ´Â Á¤º¸ ¸ðµ¨À» ±â¼úÇÑ´Ù. | ||
¿µ¹®³»¿ë¿ä¾à | In most cases, developers start with application/software providers, producing instances of the classes in the model to describe the manageable aspects of their
product. The manageable aspects include details such as installable or deployable units, the files these units are composed of, the memory required to properly execute the software, etc. These providers can either become familiar with the details of the information model, so they can produce the details by hand, or application development tool vendors can enhance their tools to produce the information based on this open standard. |
||
±¹Á¦Ç¥ÁØ | |||
°ü·ÃÆÄÀÏ | TTAE_OT-01_0002.pdf |