Web Engineering
Webe

               Prepared By-
           Vibhanshu Chaturvedi
•


•



•
Web App Attributes
      Network intensive


       Content-driven


     Continuous evolution


         Immediacy
Web App Attributes

        Availability

     Unpredictable load

       Performance

        Concurrency
Web App Attributes

              Security

           Aesthetics

     Content sensitivity

          Data Driven
     ©2011ecs-42-45-48
Contain read only content with simple navigation and
       links



Down   Allows visitor to download
load
                             ©2011ecs-42-45-48
                                                        Continued…
Implement forms based input so that every request for
           quote is organized in a predictable manner



Database That lets the user to extract the information from a
         database.
 access
                                 ©2011ecs-42-45-48
                                                                Continued…
Tailor the content presented at the website to the
         specific needs of each user



Intera   Place where people can chat, ask and answer questions,
         provide product testimonials and the like
 ctive
                                ©2011ecs-42-45-48
The user makes a request that is full-filled by the web
           app



Service    The application provides service to the user.
oriented
                                  ©2011ecs-42-45-48
                                                               Continued…
The user queries a collection of large databases
         and extracts info.


         The application channels the user to other web content
Portal   or services outside the domain of the portal
         application.
                                ©2011ecs-42-45-48
1.Formulation of the problem
2.Planning
3.WebApp requirements analysis
4.Architectural, navigational, and interface design

5.System implementation using specialized languages and tools
associated with the Web

6.Configuration management, quality control, and maintenance
mechanisms are established early
                                 ©2011ecs-42-45-48
 Component-based
  development
 Security
  (encryption,firewalls,etc.)
 Internet standards
 Web programming tools
                        ©2011ecs-42-45-48
©2011ecs-42-45-48
Continued……
©2011ecs-42-45-48
Content design and production
tasks are one thread

Architectural design,
navigation design, interface are
the other thread


          ©2011ecs-42-45-48
Content and technical designs are merged to
        produce executable web pages



Testing exercises WebApp navigation, attempts to uncover errors in
applets/scripts/forms, and checks for environment
incompatibilities

                         ©2011ecs-42-45-48
Each increment of the WebApp
is reviewed


Changes required by customer
are applied to next increment



            ©2011ecs-42-45-48
WebE Best Practices

Take time to understand the business needs and product objectives,
even if WebApp details are vague.

Describe how users will interact with the WebApp using a scenario-
based approach.

Develop a brief project plan.


Spend time modeling what you are going to build.

                                ©2011ecs-42-45-48                    Continued…
WebE Best Practices


Review models for consistency and quality.

Use tools and technology that enable you to construct the system with
as many reusable components as possible.

Don’t rely on users to debug the WebApp, design comprehensive tests
and execute them before releasing the system.

                                 ©2011ecs-42-45-48
Thank you!
                 References:

             Software Engineering-
               Roger S Pressman

Web engineering (2)

  • 1.
    Web Engineering Webe Prepared By- Vibhanshu Chaturvedi
  • 2.
  • 3.
    Web App Attributes Network intensive Content-driven Continuous evolution Immediacy
  • 4.
    Web App Attributes Availability Unpredictable load Performance Concurrency
  • 5.
    Web App Attributes Security Aesthetics Content sensitivity Data Driven ©2011ecs-42-45-48
  • 6.
    Contain read onlycontent with simple navigation and links Down Allows visitor to download load ©2011ecs-42-45-48 Continued…
  • 7.
    Implement forms basedinput so that every request for quote is organized in a predictable manner Database That lets the user to extract the information from a database. access ©2011ecs-42-45-48 Continued…
  • 8.
    Tailor the contentpresented at the website to the specific needs of each user Intera Place where people can chat, ask and answer questions, provide product testimonials and the like ctive ©2011ecs-42-45-48
  • 9.
    The user makesa request that is full-filled by the web app Service The application provides service to the user. oriented ©2011ecs-42-45-48 Continued…
  • 10.
    The user queriesa collection of large databases and extracts info. The application channels the user to other web content Portal or services outside the domain of the portal application. ©2011ecs-42-45-48
  • 11.
    1.Formulation of theproblem 2.Planning 3.WebApp requirements analysis 4.Architectural, navigational, and interface design 5.System implementation using specialized languages and tools associated with the Web 6.Configuration management, quality control, and maintenance mechanisms are established early ©2011ecs-42-45-48
  • 12.
     Component-based development  Security (encryption,firewalls,etc.)  Internet standards  Web programming tools ©2011ecs-42-45-48
  • 13.
  • 15.
  • 16.
  • 17.
    Content design andproduction tasks are one thread Architectural design, navigation design, interface are the other thread ©2011ecs-42-45-48
  • 18.
    Content and technicaldesigns are merged to produce executable web pages Testing exercises WebApp navigation, attempts to uncover errors in applets/scripts/forms, and checks for environment incompatibilities ©2011ecs-42-45-48
  • 19.
    Each increment ofthe WebApp is reviewed Changes required by customer are applied to next increment ©2011ecs-42-45-48
  • 20.
    WebE Best Practices Taketime to understand the business needs and product objectives, even if WebApp details are vague. Describe how users will interact with the WebApp using a scenario- based approach. Develop a brief project plan. Spend time modeling what you are going to build. ©2011ecs-42-45-48 Continued…
  • 21.
    WebE Best Practices Reviewmodels for consistency and quality. Use tools and technology that enable you to construct the system with as many reusable components as possible. Don’t rely on users to debug the WebApp, design comprehensive tests and execute them before releasing the system. ©2011ecs-42-45-48
  • 22.
    Thank you! References: Software Engineering- Roger S Pressman