Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Web engineering
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== As a discipline == Proponents of Web engineering supported the establishment of Web engineering as a discipline at an early stage of Web. Major arguments for Web engineering as a new discipline are: * Web-based Information Systems (WIS) development process is different and unique.<ref>Gerti Kappel, Birgit Proll, Seiegfried, and Werner Retschitzegger, "An Introduction to Web Engineering," in Web Engineering, Gerti Kappel, et al. (eds.) John Wiley and Sons, Heidelberg, Germany, 2003</ref> * Web engineering is multi-disciplinary; no single discipline (such as software engineering) can provide a complete theory basis, body of knowledge and practices to guide WIS development.<ref>{{cite journal | last1 = Deshpande | first1 = Yogesh | last2 = Hansen | first2 = Steve | year = 2001 | title = Web Engineering: Creating Discipline among Disciplines | journal = IEEE MultiMedia | volume = 8 | issue = 1| pages = 81β86 | doi = 10.1109/93.917974 }}</ref> * Issues of evolution and lifecycle management when compared to more 'traditional' applications. * Web-based information systems and applications are pervasive and non-trivial. The prospect of Web as a platform will continue to grow and it is worth being treated specifically. However, it has been controversial, especially for people in other traditional disciplines such as software engineering, to recognize Web engineering as a new field. The issue is how different and independent Web engineering is, compared with other disciplines. Main topics of Web engineering include, but are not limited to, the following areas: === Modeling disciplines === * Business Processes for Applications on the Web * Process Modelling of Web applications * Requirements Engineering for Web applications * B2B applications === Design disciplines, tools, and methods === * [[Unified Modeling Language|UML]] and the Web * Conceptual Modeling of Web Applications (aka. [[Web modeling]]) * Prototyping Methods and Tools * [[Web design]] methods * CASE Tools for Web Applications * Web Interface Design * Data Models for Web Information Systems === Implementation disciplines === * Integrated Web Application Development Environments * Code Generation for Web Applications * Software Factories for/on the Web * Web 2.0, AJAX, E4X, ASP.NET, PHP and Other New Developments * [[Web Service]]s Development and Deployment === Testing disciplines === * Testing and Evaluation of Web systems and Applications. * Testing Automation, Methods, and Tools. === Applications categories disciplines === * [[Semantic Web]] applications * Document centric Web sites * Transactional Web applications * Interactive Web applications * Workflow-based Web applications * Collaborative Web applications * Portal-oriented Web applications * Ubiquitous and Mobile Web Applications * Device Independent Web Delivery * [[Internationalization and localization|Localization and Internationalization]] of Web Applications * [[Personalization]] of Web Applications
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)