Agile Web Engineering
Process (AWE)
Abdul saboor
Kanza batool
Muhammad basim
INTRODUCTION
● Agile web engineering process is one of the processes in applying agile
principles that has been proposed specifically for web application
development.
● Agile web engineering is a light weight process which helps to tackle
the problems associated for the development of web based
applications.
● AWE helps in better maintaining, implementing and continuous
testing of applications.
● This AWE solution helps in getting the solutions that will get satisfied
by the end-users.
LIFE CYCLE OF AWE
BUSINESS ANALYSIS
● The purpose of the business analysis phase is to clearly understand the problems to be addressed by
the proposed web application.
● It is crucial that every developer be involved in this stage so that all challenged
with providing the proposed solution understand the problems that need to be
addressed. Often the business analysis phase is carried out by a different set of
stakeholders or developers.
REQUIREMENTS
• It is crucial that every member of the team agrees the problems to be solved
before the requirements activities begin.
• The Requirements phase is about defining what the proposed solution will do
(functional requirements), and what constraints are to be placed upon the
proposed solution (non-functional requirements).
DESIGN
● Design involves understanding, co-ordinating and communicating all the
major issues, before implementation, of building a complex web application.
● These issues should be independent of the lower-level implementation details.
IMPLEMENTATION
● Design and Implementation phases, both involve decisions that have a critical
impact on project success.
● The agile process encourages developers in teams, mostly comprising software
engineers, to communicate through the source code of the project deliverable.
This is achieved through pair programming and extensive testing.
● eAll developers should collaborate and focus their development efforts around
the Web interface, using collaborative sessions to discuss and review the browser
experience.
TESTING
● Testing is a crucial stage in any software activity.
● Testing objectives involve assessing whether or not what has been built has
satisfied the project's requirements.
● Testing requires input from the Requirements, Design and Implementation
phases
EVALUATION
● The Evaluation Plan should be derived from the issues or problems identified
in the Business Analysis phase.
● It is imperative that the team objectively evaluate what has been delivered
independent of design and implementation issues.
ITERATIVE AND INCREMENTAL DEVELOPMENT
● Iterative and incremental development cycles are crucial
to making the AWE process work.
● That is, framework activities will occur repeatedly as
each webapp increment is engineered and delivered.
● The agility principles should be applied.
● Each iteration should focus on solving a subset of the
problems that present the highest risk, ensuring that
previous iterations efforts are not compromised by the
incremental increase in development scope.
BENEFITS:
Though Agile web engineering process has certain
strengths like:
 Flexibility
 Collaboration
 Simplicity
 Iterative
 Incremental
 Strong focus on the end user,
 Usability
agile.pptx

agile.pptx

  • 1.
    Agile Web Engineering Process(AWE) Abdul saboor Kanza batool Muhammad basim
  • 2.
    INTRODUCTION ● Agile webengineering process is one of the processes in applying agile principles that has been proposed specifically for web application development. ● Agile web engineering is a light weight process which helps to tackle the problems associated for the development of web based applications. ● AWE helps in better maintaining, implementing and continuous testing of applications. ● This AWE solution helps in getting the solutions that will get satisfied by the end-users.
  • 3.
  • 4.
    BUSINESS ANALYSIS ● Thepurpose of the business analysis phase is to clearly understand the problems to be addressed by the proposed web application. ● It is crucial that every developer be involved in this stage so that all challenged with providing the proposed solution understand the problems that need to be addressed. Often the business analysis phase is carried out by a different set of stakeholders or developers. REQUIREMENTS • It is crucial that every member of the team agrees the problems to be solved before the requirements activities begin. • The Requirements phase is about defining what the proposed solution will do (functional requirements), and what constraints are to be placed upon the proposed solution (non-functional requirements).
  • 5.
    DESIGN ● Design involvesunderstanding, co-ordinating and communicating all the major issues, before implementation, of building a complex web application. ● These issues should be independent of the lower-level implementation details. IMPLEMENTATION ● Design and Implementation phases, both involve decisions that have a critical impact on project success. ● The agile process encourages developers in teams, mostly comprising software engineers, to communicate through the source code of the project deliverable. This is achieved through pair programming and extensive testing. ● eAll developers should collaborate and focus their development efforts around the Web interface, using collaborative sessions to discuss and review the browser experience.
  • 6.
    TESTING ● Testing isa crucial stage in any software activity. ● Testing objectives involve assessing whether or not what has been built has satisfied the project's requirements. ● Testing requires input from the Requirements, Design and Implementation phases EVALUATION ● The Evaluation Plan should be derived from the issues or problems identified in the Business Analysis phase. ● It is imperative that the team objectively evaluate what has been delivered independent of design and implementation issues.
  • 7.
    ITERATIVE AND INCREMENTALDEVELOPMENT ● Iterative and incremental development cycles are crucial to making the AWE process work. ● That is, framework activities will occur repeatedly as each webapp increment is engineered and delivered. ● The agility principles should be applied. ● Each iteration should focus on solving a subset of the problems that present the highest risk, ensuring that previous iterations efforts are not compromised by the incremental increase in development scope.
  • 8.
    BENEFITS: Though Agile webengineering process has certain strengths like:  Flexibility  Collaboration  Simplicity  Iterative  Incremental  Strong focus on the end user,  Usability