Proceedings of the 4 th National Conference; INDIACom-2010 Computing For Nation Development, February 25 – 26, 2010 Bharati Vidyapeeth’s Institute of Computer Applications and Management, New Delhi Applying Agile And Web Engineering Technique For Successful Web Management B.V.Ramana Murthy Salman Abdul Moiz Mohammed Sharfuddin Professor, GNEC, RR District Research Scientist, C-DAC Assistant Professor,GNEC, RR District drbvrm@gmail.com salman.abdul.moiz@ieee.org sharfuddin_se@yahoo.com ABSTRACT A new generation of software development lifecycle models has emerged lately called "Agile" and they embrace change, reduce development cycle time, and attempt a useful compromise between no process and too much process. Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames typically last from one to four weeks. Each iteration involves a team working through a full software development cycle, when a working product is demonstrated to stakeholders. This helps minimize overall risk, and lets the project adapt to changes quickly[2]. Agile methods emphasize face-to-face communication over written documents when the team is all in the same location. When a team works in different locations, they maintain daily contact through videoconferencing, voice, e-mail; etc the web engineering process begins with the formulation of a problem to be solved by the web application. KEYWORDS Agile, Web Process, Web Engineering. 1.0 MOTIVATION AND BACKGROUND Web-based systems [1] and applications deliver a complex array of content and functionality, to a broad population of end- users. Web engineering is the process that is used to create high-quality web applications. Web engineering is not a perfect clone of a software engineering, but it borrows many of software engineering fundamental concepts and principles. In addition, the web engineering process emphasizes similar technical and management activities are conducted, but the overriding Philosophy dictates a disciplined approach to the development of a computer-based system. Web engineers and non-technical content developers [2] create the web applications. As web becomes increasingly integrated in business strategies, for small and large companies, the need to build reliable, usable, and adaptable systems grows in importance. 2.0 OBJECTIVE To enable the Project Manager/Web developers to understand Web Engineering better Scope: The research work is helpful for Web Management 3.0 INTRODUCTION Contrary to popular belief, architecture is an important aspect of agile software development efforts, just like traditional efforts, and is a critical part of scaling agile approaches to meet the real-world needs of modern organizations. But, agile approach architecture a bit differently than traditionalists do architecture provides the foundation from which systems are built and an architectural model defines the vision on which your architecture is based. The scope of architecture can be that of a single application, of a family of applications, for an organization, or for an infrastructure such as the Internet that is shared by many organizations. Regardless of the scope, my experience is that you can take an agile approach to the modeling, development, and evolution of architecture. An agile approach: Focus on people, not technology or techniques [3] Keep it simple Work iteratively and incrementally Roll up your sleeves Build it before you talk about it An Agile Approach First and foremost, the values, principles, and practices of Agile Modeling (AM) should help to guide your enterprise architecture modeling and documentation efforts. This is just a good start though these issues are: Focus on people, not technology or techniques 1. Keep it simple 2. Work iteratively and incrementally 3. Roll up your sleeves 4. Look at the whole picture 5. Make enterprise architecture attractive to your customers 6. Potential Problems With The Agile Approach No approach is perfect, including this one. We would like to address the issues: It does not include an explicit way to ensure compliancy (although having enterprise architects embedded on the teams goes a long way towards this). It depends on people being responsible. It requires you to actively strive to keep things simple. It requires you to accept an agile approach to modeling and documentation[8]. 4.0 Web Engineering The World Wide Web and the Internet that empowers it are arguably the most important developments in the history of computing. The technologies have drawn us all into the information age. They have become integral to daily life in the first decade of the twenty-first century. For those who can remember a world without the web, the chaotic growth of the technology hackers backs to another era- the early days of software.