arudhra

Web site life cycle plan   A plan should be prepared for managing appropriate life cycle processes for the Web site—acquisition, sup- ply, development, operation, and maintenance. The plan for the Web site should define when, how, and by whom specific activities are to be performed, including options and alternatives, as appropriate. The plan should include, at least, the following generic items: a) Date of issue and status b) Scope c) Issuing organization d) References e) Approval authority f) Planned activities and tasks g) Macro references (policies or laws that give rise to the need for this plan) h) Micro references (other plans or task descriptions that elaborate details of this plan) i) Schedules j) Estimates k) Resources and their allocation l) Responsibilities and authority m) Risks n) Quality control measures o) Cost p) Interfaces among parties involved q) Environment/infrastructure (including safety needs) r) Training s) Glossary t)

A Managerial Community of Web Services Nowadays, Web services are considered as new and attracting distributed approach of application/services integration over the Internet. As the number of Web Services is exponentially growing and expected to do so for the next decade, the need for categorizing and/or classifying Web Services is very crucial for their success and the success of the underlying SOA. Categorization aims at systematizing Web Services according to their functionalities and their Quality of Service attributes. Communities of Web Services have been used to gather Web Services based on their functionalities. In fact, Web Services in a community usually offer similar and/or complementary services. In this paper, we augment Web Services communities’ classification by adding a new support layer for Quality of Service classification. This is d