1. Demonstrators: Mudasir Nazir(08-CS-41)

2.  I am highly addicted to this field.  Working with W3C in research program(building CSS for creating web site for Blind Users)  Developing web projects with some consortiums For more details visit me at engrmudasir.wordpress.com

3. The terms sound very similar, but there is great difference between these two. When you are looking for some one to build website for you its important to differentiate between these. Front-end Back-end

6. “By the time passes, we see any sort of stabilization, the web will turned into something completely different ” LOUIS MONIER

7.  Network intensiveness  Concurrency  Unpredictable load  Performance  Availability  Data driven  Content sensitive  Continuous evolution  Immediacy  Security  Aesthetic

8.  Informational  Download  Interaction  User input forms  User transaction  Portals  Data base access

9.  Process: Embrace change Strong interaction builds systems using small teams Increment development using small development teams

10. It encompasses a set of technical tasks Understand,characterize and build high quality webapp Communication methods: Requirement analysis method: Design method: Testing method:

12. Planning Modeling Construction Deployment

15.  During 1990 the internet boom generated arrogance than any other event in computer history.  Web app developers argued that a new concept of software development had arisen,that old rules are no longer applicable.

16.  They laughed at the notion that careful formulation and planning should occur before construction commenced…??  Why is it important…??????? ? ? ? What are the steps…????????? ? ? ?

17.  Formulation allows web engineering team and stakeholders to establish a common set of goals and objectives for the construction of a webApp.  It also specify the scope of the development effort and provides a mean for successful outcome.

18.  The following are some steps for requirements gathering.  Ask stakeholders to define user categories and develop descriptions for each user.  Communicate with stakeholders to define basic webApp requirements.  Analyze information gathered and use information to follow up with stake holders.  Define use cases that describe interaction scenarios for each user class.

19.  Defining user categories.  Communication with stakeholders and end users.  Analyzing information gathered.

20.  Web engineering team can be organized in much the same way as traditional software team. Among many skills that must be distributed among the web engineering team are component based software engineering,networking, architectural and navigational design, internet standards, human interface design, graphic design etc.

21.  The following roles should be distributed in web team.  Contents developer  Web publisher  Web engineer  Business domain experts  Support specialist

22.  Because webApp are inherently contents driven so one role of the web team must focus on collection of contents.

23.  The contents generated by content developers Must be organized for inclusion with in the webAPP technology.  This role is filled by the web developers who must understand both contents and webApp technology.

24.  A web engineer becomes invoved in wide range of activities during the development of WebApp including requirement elicitation, analysis modeling, architectural, navigational and interface design, webApp implementation and testing.  Web engineer should also have a solid understanding of component technologies.

25.  A business domain expert should be able to answer all questions related to business goals, objectives and requirements associated to the webApp.

26.  This role is assigned to the person who is responsible for continuing webApp support because webApp continously evolve the support specialist is responsible for corrections including updates of contents.

27.  Often called the “web master” this person is responsible for day-to-day operation including development and implementation of policies.  The administrator may also be involved in the technical activities performed by web engineers and support specialist.

28.  Its hard to write an article on application mistakes because the very worst mistakes are domain- specific.Usually, applications fail because they (a) solve the wrong problem, (b) have the wrong features for the right problem, or (c) make the right features too complicated for users to understand.

29.  There are some violations that are often seen In a wide variety of applications.  Tiny Click Targets  No Perceived Affordance  Out to Lunch Without a Progress Indicator

31. It actually focuses on three things:  What information to be presented?  What functions to be performed?  What behaviors will it exhibit as it presents information and functions?

32. It actually encompasses three major tasks:  Formulation  Requirements Gathering  Analysis modeling

33. Note: The main is to establish basic understanding of the WebApp is to build, who will use it and which problems it will solve

36.  Content Analysis:  Interaction Analysis:  Functional Analysis:  Configuration Analysis:

37. Defining Content Objects: o A paragraph general Description o A photograph o Technical Description o Thumbnail Video

41. Navigation is not only the action of jumping from page to page, but the idea of moving through information space.

43.  Design for webApp

44.  First of all we discuss what is webApp design in actual by giving answers of some questions  The first question is what is it????  Who does it?????  Why is it important???  What are the steps????  What is the work product???

45.  Design and web quality  Security  Availability  Scalability

46.  Offutt extends the five major quality attributes by adding the following attributes. o Security o Availability o Scalability

47.  Jean Kaiser suggests the following design goals that are applicable to virtually every web application regardless of application domain,size, or complex.  Simplicity  Consistency  Identity  Navigability  Robustness  Compatibility

48.  Interface design  Aestheic design  Content design  Navigation design  Architecture design  Component design

49.  Every user interface whether it is designed for a webApp,a traditional software app, a consumer product, or an industrial device should follow the following characteristics, easy to use, easy to learn, easy to navigate, error free and functional.

50.  Communication  Consistency  Efficiency  Flexibility  Readability

53. Layout Issues: Graphic Design Issues: Content Design Issues:

54. REFERENCES: http://www.w3.org/standards/ http://engrmudasir.wordpress.com/ Software Engineering(a practitioner approach) By: Roger S.Pressman