web engineering?

56
Demonstrators: Mudasir Nazir(08-CS-41) Web Engineering?

Upload: anoki

Post on 10-Jan-2016

26 views

Category:

Documents


3 download

DESCRIPTION

Web Engineering?. Demonstrators: Mudasir Nazir (08-CS-41). Why This Topic?. 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 - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Web Engineering?

Demonstrators:

Mudasir Nazir(08-CS-41)

Web Engineering?

Page 2: Web Engineering?

Why This Topic?

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

Page 3: Web Engineering?

WEB –Designing & WEB-DevelopmentThe 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.

WEB-Designing?

WEB-Development?

Front-end

Back-end

Page 4: Web Engineering?

What is WebApp?

Client?

Client-server Environment?

Page 5: Web Engineering?

Web E?

Web Systems?

Page 6: Web Engineering?

Attributes of web based systems

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

LOUIS MONIER

Page 7: Web Engineering?

Attributes of web based systemsNetwork intensiveness

Concurrency

Unpredictable load

Performance

Availability

Data driven

Content sensitive

Continuous evolution

Immediacy

Security

Aesthetic

Page 8: Web Engineering?

Categories of WebApp in WebE

Informational

Download

Interaction

User input forms

User transaction

Portals

Data base access

Page 9: Web Engineering?

WebE Layers:

Process:

• Embrace change

• Strong interaction

• builds systems using small teams

• Increment development using small development

teams

Page 10: Web Engineering?

Methods:It encompasses a set of technical tasksUnderstand ,characterize and build high quality webapp

Communication methods:

Requirement analysis method:

Design method:

Testing method:

Page 11: Web Engineering?

Tools and technology:

Page 12: Web Engineering?

PlanningModelingConstructionDeployment

WebE Process:

Page 13: Web Engineering?

WebE process:

Page 14: Web Engineering?

I am Scrolling

Page 15: Web Engineering?

Initiating A WebApp project

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.

Page 16: Web Engineering?

They laughed at the notion that careful formulation and planning should occur before construction commenced…??

Why is it important…??????? ? ? ?What are the steps…????????? ? ? ?

Page 17: Web Engineering?

Formulating Web Based systemsFormulation 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.

Page 18: Web Engineering?

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.

Page 19: Web Engineering?

Defining user categories.Communication with stakeholders and end

users.Analyzing information gathered.

Page 20: Web Engineering?

The web engineering teamWeb 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.

Page 21: Web Engineering?

The following roles should be distributed in web team.

Contents developerWeb publisherWeb engineerBusiness domain expertsSupport specialist

Page 22: Web Engineering?

Content developer

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

Page 23: Web Engineering?

Web publisherThe contents generated by content

developersMust 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.

Page 24: Web Engineering?

Web engineerA 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.

Page 25: Web Engineering?

Business domain expertsA business domain expert should be able to

answer all questions related to business goals, objectives and requirements associated to the webApp.

Page 26: Web Engineering?

Support specialistThis 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.

Page 27: Web Engineering?

AdministratorOften 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.

Page 28: Web Engineering?

Application-Design Mistakes 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.

Page 29: Web Engineering?

There are some violations that are often seen In a wide variety of applications.

Tiny Click TargetsNo Perceived AffordanceOut to Lunch Without a Progress Indicator

Page 30: Web Engineering?

Why the fuzzy faces?

Page 31: Web Engineering?

Analysis for WebAppsIt 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?

Page 32: Web Engineering?

Requirment analysis for WebApps:

It actually encompasses three major tasks:

Formulation

Requirements Gathering

Analysis modeling

Page 33: Web Engineering?

Requirment analysis for WebApps:

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

Page 34: Web Engineering?

The User Hirerachy

Page 35: Web Engineering?

Developing Use Cases

Page 36: Web Engineering?

The Analysis Model for WebApps

Content Analysis:

Interaction Analysis:

Functional Analysis:

Configuration Analysis:

Page 37: Web Engineering?

Content Model:

Defining Content Objects:o A paragraph general DescriptionoA photographoTechnical DescriptionoThumbnail Video

Page 38: Web Engineering?

Content RelationShip &Hierarchy

Page 39: Web Engineering?

Analysis Class for USE CASE

Page 40: Web Engineering?

The Interaction Model:

The Functional Model:

The Configuration Model:

Page 41: Web Engineering?

Relationship Navigation analysis:

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

Page 42: Web Engineering?

Scroll

Page 43: Web Engineering?

Design for webApp

Page 44: Web Engineering?

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???

Page 45: Web Engineering?

Design issue for web engineering

Design and web quality Security Availability Scalability

Page 46: Web Engineering?

Offutt extends the five major quality attributes by adding the following attributes.

o Securityo Availabilityo Scalability

Page 47: Web Engineering?

Design goals Jean Kaiser suggests the following design

goals that are applicable to virtually every web application regardless of application domain ,size, or complex.

SimplicityConsistency IdentityNavigabilityRobustnessCompatibility

Page 48: Web Engineering?

The web design activities Interface design Aestheic design Content design Navigation design Architecture design Component design

Page 49: Web Engineering?

Interface designEvery 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.

Page 50: Web Engineering?

Interface design principles and guidelinesCommunicationConsistencyEfficiencyFlexibilityReadability

Page 51: Web Engineering?

Interface design workflow

Page 52: Web Engineering?

Wind UP section!!

Page 53: Web Engineering?

Aesthetic Design:Layout Issues:

Graphic Design Issues:

Content Design Issues:

Page 54: Web Engineering?

REFERENCES:

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

Page 55: Web Engineering?
Page 56: Web Engineering?

THANK

YOU