what is the common term for the newest stage of web development?
398628
Are you referring to Web 2.0 based upon AJAX technology? And using the WEB as a platform.. O'Reilly defined it and is the best source of information on this.
245740
Id go with UML also - especially if its a detailed dynamic site.\n\nMy process is:\n1. Concept (UML)\n2. Pen & Paper wireframes (or wireframes in Photoshop/Fireworks)\n3. Basic colors in wireframes.\n4. Design\n5. Code your CSS\n6. HTML Shell for all pages\n7. Build Database\n8. Tweak HTML, Design and CSS\n9. Add Dynamic code\n10. Tweak\n11. Tweak
137108
DEFINITION: System Development Life Cycle (SDLC) is the overall process of developing information systems through a multistep process from investigation of initial requirements through analysis, design, implementation and maintenance. There are many different models and methodologies, but each generally consists of a series of defined steps or stages. \n\n\nMAY 14, 2002 (COMPUTERWORLD) - Once upon a time, software development consisted of a programmer writing code to solve a problem or automate a procedure. Nowadays, systems are so big and complex that teams of architects, analysts, programmers, testers and users must work together to create the millions of lines of custom-written code that drive our enterprises. \nTo manage this, a number of system development life cycle (SDLC) models have been created: waterfall, fountain, spiral, build and fix, rapid prototyping, incremental, and synchronize and stabilize. \n\nThe oldest of these, and the best known, is the waterfall: a sequence of stages in which the output of each stage becomes the input for the next. These stages can be characterized and divided up in different ways, including the following: \n\n\n\nProject planning, feasibility study: Establishes a high-level view of the intended project and determines its goals. \n\nSystems analysis, requirements definition: Refines project goals into defined functions and operation of the intended application. Analyzes end-user information needs. \n\nSystems design: Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation. \n\nImplementation: The real code is written here. \n\nIntegration and testing: Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability. \n\nAcceptance, installation, deployment: The final stage of initial development, where the software is put into production and runs actual business. \n\nMaintenance: What happens during the rest of the software's life: changes, correction, additions, moves to a different computing platform and more. This, the least glamorous and perhaps most important step of all, goes on seemingly forever.\n\nBut It Doesn't Work! \n\nThe waterfall model is well understood, but it's not as useful as it once was. In a 1991 Information Center Quarterly article, Larry Runge says that SDLC "works very well when we are automating the activities of clerks and accountants. It doesn't work nearly as well, if at all, when building systems for knowledge workers -- people at help desks, experts trying to solve problems, or executives trying to lead their company into the Fortune 100."  \nAnother problem is that the waterfall model assumes that the only role for users is in specifying requirements, and that all requirements can be specified in advance. Unfortunately, requirements grow and change throughout the process and beyond, calling for considerable feedback and iterative consultation. Thus many other SDLC models have been developed. \n\nThe fountain model recognizes that although some activities can't start before others -- such as you need a design before you can start coding -- there's a considerable overlap of activities throughout the development cycle. \n\nThe spiral model emphasizes the need to go back and reiterate earlier stages a number of times as the project progresses. It's actually a series of short waterfall cycles, each producing an early prototype representing a part of the entire project. This approach helps demonstrate a proof of concept early in the cycle, and it more accurately reflects the disorderly, even chaotic evolution of technology. \n\nBuild and fix is the crudest of the methods. Write some code, then keep modifying it until the customer is happy. Without planning, this is very open-ended and can by risky. \n\nIn the rapid prototyping (sometimes called rapid application development) model,
553810
Probably the term you are thinking of is "Web-Based Technology", or "Web Application."  This is not the same as a "web page."  It's more like a complete application that uses a web browser as a user interface.  \n\nMy company writes "Web Applications" often, because then it can be run on any device that runs a web browser, and we don't have to worry about installing software on individual workstations.
248779
Yup I am a web application developer mostly working with .net application. I love this job but it can become stressful at times and you usually have to keep up to date with the current technology. Also knowing one programming language is not enough but you'll have to know a couple in order to work in this field.
633705
Here is a complete definition with details...Too much info to type it all in here...\nhttp://en.wikipedia.org/wiki/Software_development
909026
Present trrend in IT appears to be web oriented with interactive features.
659465
front end  is the toll which is used to make your program as easy and to more convinience to use it\n\n\nit is also userfriendly\n\nexample:\n    VB\n    developer 2000\n\nback end:\n  this is the area where the real process is going to take place i.e in database
1178339
Frontpage has been out there for a good while but to much HTML scripting. Dreamweaver is good and makes the creation of web pages easier.
53139
Web engineering deals with design, development and implementation of large-scale Web applications. In particular, it focuses on the methodologies, techniques and tools that are the foundation of complex Web application development and which support their design, development, evolution, and evaluation. It is a relatively a new discipline.\n\nWeb application development has certain characteristics that make it different from traditional software, information system, or computer application development.\n\nWeb engineering is multidisciplinary and encompasses contributions from diverse areas: systems analysis and design, software engineering, hypermedia/hypertext engineering, requirements engineering, human-computer interaction, user interface, information engineering, information indexing and retrieval, testing, modelling and simulation, project management, and graphic design and presentation.\n\nWeb engineering is not a clone or not a subset of software engineering, although both involve programming and software development. While Web Engineering uses software engineering principles, it encompasses new approaches, methodologies, tools, techniques, and guidelines to meet the unique requirements of Web-based.\n\nMain topics of Web engineering include, but are not limited to, the following areas:\n\n    * Business Processes for Applications on the Web\n    * CASE Tools for Web Applications\n    * Code Generation for Web Applications\n    * Collaborative Web Development\n    * Conceptual Modelling of Web Applications (aka. Web modeling)\n    * Data Models for Web Information Systems\n    * Development Process and Process Improvement of Web Applications\n    * Empirical Web Engineering\n    * Integrated Web Application Development Environments\n    * Multimedia Authoring Tools and Software\n    * Performance of Web-based Applications\n    * Personalisation and Adaptation of Web Applications\n    * Process Modelling of Web Applications\n    * Prototyping Methods and Tools\n    * Quality Control and Testing\n    * Requirements Engineering for Web Applications\n    * Semantic Web Applications\n    * Software Factories for/on the Web\n    * Testing Automation, Methods and Tools for Web Applications\n    * Ubiquitous and Mobile Web Applications\n    * UML and the Web\n    * Usability of Web Applications\n    * Web Accessibility\n    * Web Design Methods\n    * Web Engineering Education\n    * Web Interface Design\n    * Web Metrics, Cost Estimation, and Measurement\n    * Web Project Management and Risk Management\n    * Web Services Development and Deployment
508246
They mostly upgraded their website.\n\nDB
1026045
For client side application programs the hot stuff is anything .NET, preferably c# and even vc++.net is doing well. Java is really taking off too.\n\nFor server side web programming... PHP hands down is hot. Paired up with MySQL, that technology is really dominating. Perl is there, but slowly dying by the wayside.\n\nFor web development, AJAX and straight XML with a sprinkle of DHTML. Its the foundation of the Web 2.0 movement.\n\nBelieve me, I have my hands in all three of these categories and I often can't keep up with all the work people want to throw at me. I pretty much can command my own perks and salary because of it.\n\nHope I helped you out with this.
354365
To use for a website mostly it depends on what your most comfortable with. HTML is the standard web development language along with a bunch of other add ons like php, javascript, vbscript that allow you to make more dynamic web sites. In the end it just depends on what exactly you are trying to do and what you are comfortable with.
293326
use activexcontrol if it is a snippet program\n\nalso you can go for visual interdev (VS6)\n\nin case of vs.net then they have option for web development\n\nhope this helps you a little
554158
There is No such standard solution structure or standard architecture for web project or windows application..\n\nBut I could say is Microsoft PetShop 3.0 architecture is now considered to be advantageous and also standard which competes with many other standard solution is java
1017279
That's HTML (hyper text markup language). It is the coding language used to create web pages viewed on the world wide web.
23788
New text: There are really too many things to cover in a Q/A, I'll add a couple high level things but you really need a pro consultant to set you up. There are also some good books on the subject but really you have to believe in what you are doing so you want to pick a successfull project/architect lead first that will set up the processes.  Code repositories (you need one), defect feature process (you need one), driver sequencing to get the satelite sites working earlier vs later, or they can use the contract to develop test components.  \n\nThe keys here are to set up processes at the IT level that enforce:\n\nProduct/Development Management \n==============================\n1) Proper Componentization, design by contract etc. will go along way to smooth the combined build\n2) Select a Lead Architect and / or Lead Developer carefully, someone has to override the regional issues\n3) Set up Wikis early and assign people to maintain\n4) One Region can develop another test another support etc., but you need to be able to reproduce errors locally to the team that will fix\n5) Multi-Release wars... optionally set up a research or r.next release development team who focuses on the next release to replace parts of the current or in development release.\n\n\nInternationalization <ok i18n is not a issue thx for adding the detail>\n====================\n1) Separation of translatable text into translation packages, separating code from visuals such that you can translate / update translations on demand\n2) Unicode...  HTML/XML/Java/File Systems all support NLS chars via UTF8 on the wire/disk and UTF16 in memory.  Stick with Unicode in that stack/programs and you can support all NLS chars, use a specific code page in your runtime applications such as any latin code page and you're busted.\n3)Convert data at the edge.. use edge point mediations to convert code page specific data to unicode to enable NLS in the apps. Convert to Browser specific code pages at the last possible moment to orient to the user.