在各种不同的软件需求中，功能需求描述了用户使用产品必须要完成的任务，可以在用例模型或方案脚本中予以说明，(59)是从各个角度对系统的约束和限制，反映了应用对软件系统质量和特性的额外要求。

(86)

(88)

(87)

(85)

Because　Web　servers　axe　platform.　and　application(71),　they　can　send　or　request　data　from　legacy　or　external　applications　including　databases.　All　replies,　once　converted　into(72).　mark-up　language,　can　then　be　transmitted　to　a(73).Used　in　this　way,　Intranets　can(74)lower　desktop　support　costs,　easy　links　with　legacy　applications　and　databases　and,(75)all,　ease　of　use.

(82)

(83)

Prior　to　the　UML,　there　was　no　clearleading(66)Ianguage.　Users　had　to　choose　from　among　many　similar　modeling　languages　with　minor　differences　in　overall(67)power.　Most　of　the　modeling　languages　shared　a　set　of　commonly　accepted　concepts　that　are　expressed　slightly　differently　in　various　languages.　This　lack　of(68)discouraged　new　users　from　entering　the　OO　market　and　from　doing　OO　modeling,　without　greatly　expanding　the　power　of　modeling.　Users　longed　for　the　industry　to　adopt　one,　or　a　very　few,　broadly　supported　modeling　languages　suitable　for(69)usage.

Some　Vendors　were　discouraged　from　entering　the　OO　modeling　area　because　of　the　need　to　support　many　similar,　but　slightly　different,　modeling　languages.　In　particular,　the　supply　of　add-on　tools　has　been　depressed　because　small　vendors　cannot　afford　to　support　many　different　formats　from　many　differem(70)modeling　tools.　It　is　important　to　the　entire　OO　industry　to　encourage　broadly　based　tools　and　vendors,　as　well　as　niche　products　that　cater　to　the　needs　of　specialized　groups.

(80)

(81)