An Introduction to Web Engineering Engineering (Glushko and McGrath 2002), Content Engineering (Reich and G untner 2005), and Internet Software Engineering (Balasubramaniam et al. 2002). In comparison, Web Engineering is a concise term, although strictly speaking not completely accurate it is not the Web that is engineered, but rather Web applications. But Web Applications Engineering does not quite have the same ring to it. From the point of view of Software Engineering, the development of Web applications is a new application domain (Glass 2003, Kautz and N rbjerg 2003). Despite some similarities to traditional applications, the special characteristics of Web applications require an adaptation of many Software Engineering approaches or even the development of completely new approaches (Deshpande et al. 1999, Murugesan et al. 1999). The basic principles of Web Engineering can, however, be described similarly to those of Software Engineering (cf. e.g. Lowe 1999, Selmi 2005): Clearly defined goals and requirements Systematic development of a Web application in phases Careful planning of these phases Continuous audit of the entire development process. Web Engineering makes it possible to plan and iterate development processes and thus also facilitates the continuous evolution of Web applications. This permits not only cost reduction and risk minimization during development and maintenance, but also an increase in quality, as well as measurement of the quality of the results of each phase (Ginige and Murugesan 2001b, Mendes and Mosley 2006). The structure of this book is based on that of the Guide to the Software Engineering Body of Knowledge (SWEBOK, Bourque and Dupuis 2005), i.e. the individual chapters follow the structuring of traditional Software Engineering. Each of the contributions focuses on the special characteristics of the relevant topic in relation to the Web. The following section defines the categories of Web applications. Section 1.3 expands on this by describing the special characteristics of Web applications. Finally, section 1.4 presents an overview of the structure of the book. 1.2 Categories of Web Applications Web applications have varying degrees of complexity. They may be purely informational or handle full-size/full-fledged 24/7 e-commerce applications. Fig. 1-1 identifies different categories of Web applications depending on their development history and their degree of complexity and gives examples (cf. Murugesan 2000).2 We must bear in mind that there is a correlation between the chronology of development and complexity. Workflow-based applications, for example, are transaction-based, i.e. the higher level of development requires the previous development of a less complex category. However, there may be exceptions to that rule in that some of the categories (e.g. the portal-oriented applications) are historically rather recent while having a lower degree of complexity. 2 Similar categorizations of Web applications can be found e.g. in (Conallen 2000, Kappel et al. 2003, Powell et al. 1998, Pressman 2005, Weitz 2002).
Note: If you are looking for good and high quality web space to host and run your java application check Lunarwebhost java web hosting services