Kategorier: Alla - security

av Pascal Rode för 16 årar sedan

346

WebEngineering WS 08

WebEngineering WS 08

WebEngineering WS 08/09

Part 6 - Developement

Preserving State

Jackie fragt

Request/Response
hint nur bei XForms
HTML Forms
ENCTYPE
XSL-Transformations
XHTML
DTD
&
Conflicts Resolving
Cascading the style sheets
Positioning
Inheritance
Applying Styles
Other Media Types
Media Type Image I

Poster

Bewerbung Karibik

SVG

Differences?

Advantages?

PNG

JPEG

GIF

Domain Specific standards
Standard XML Schemas
There is no "the standard"
Data Technologies
Testing & Evolution in Context
test & coding

Part 5 - Planning

Federation Technologies
Security Concerns
Cookie
HTTP
CGI
SSI
Webserver
AJAX
Combine different technologies for creating web pages that“behave” like desktop applications
XSS
Cross Site Scripting
DHTML
Dhtml just for laught's
Client-Side Code
XForms
HTML-Forms
XSL
Learing XSLT
CSS
Why you should use CSS
XPath
Zur Extraktion beliebiger Teile eines wohl-geformten XML-Dokuments verabschiedete das W3C 1999 die Sprache XPath.
XLink

Das zugrundeliegende Problem, nämlich der Wunsch durch einen Link mehrere Ressourcen gebündelt referenzieren zu können, tritt in praktischen Anwendungen häufig auf. Beispielsweise beim Verweis auf mehrere Versionen eines Dokuments, alternativen Downloadservern oder Bildern verschiedener Auflösung.

Zu Realisierung erlaubt XLink die Bündelung von verschiedenen Verweisen zu einem einzigen erweiterten XLink. Nachfolgend ein Codeausschnitt, der dies für die Projektverwaltung zeigt.

http://www.jeckle.de/vorlesung/xml/script.html#XLink
some other formats
image/jpg
image/gif
Media Type Image 1
Standard XML-Schemas
Just Enough XML to Survive
Testing and Evolution in Context
Building releases
Tech-Map
Presentation
Dialogue
DSA
Process
Data

Part 4 - Pre-Planning

Simple Change control
Managing Change
A Web-based system must be treated like a garden
Managing requirements and change
RE & Project Lifecycle

Specification and ValidationPhases

Beyond SRS

Manage Scope

Prepare for planning

Work breakdown structure

Tree structure

Specification

Priority

Description

Name

Documenting and SRS

Assess Phase

Requirements Prioritization

by risk

by readiness

by value

Quality Attributes

Business Rules

Features

Must-solution

Product Dimensions

Assessing Requirements

Mockup

Prototype

Elicit Phase

Update Vision and Scope

Technology

Operations

UIX-Experience

RNA's Taxonomy

Navigation

Accessibility

UI-Experience

Categories of information

Mind-Maps

Techniques for Gathering

Use-Case Diagram

Example: E-Concierge

Refining Scope

Goal: Better understanding

Requires finding stakeholder representatives

Gather more information

Performing Elicitation

change control

Identify stakeholder

how

what

why

Initiate Phase

Blackboard Approach

Ein Blackboard-Modell basiert auf der Vorstellung einer Gruppe von Experten, die durch Zusammenarbeit ein Problem lösen, das sich aufgrund seiner Komplexität der Lösung durch einen einzelnen Experten entzieht

Project initiation

Memorandum of agreement

Finalisation

Preparation

Vision and Scope

Drafting the vision

Market Requirement Document

Use Case

Alistair Cockburn Classification

fully dressed

is a formal document based on a detailed template with fields for various sections

Casual

onsists of a few paragraphs of text, summarizing the use case.

Brief

consists of a few sentences summarizing the use case. It can be easily inserted in a spreadsheet cell, and allows the other columns in the spreadsheet to record priority, technical complexity, release number, and so on.

Use Case Realization

Use Case Scenario

Developing Solution Concept

Business requirements

Objective

links project in business environment

Description Documentation of Project for authorization purpose

Prepare a glossary

Prepare for RE activities

Levels of requirements

Environmental

Operational

User

Business

Goal of requirements engineering
performing RE
Requirements engineering
Types of requirements
What is a requirement ?
Stakeholder analysis
Stakeholders
Dealing with requirements
Requirements and the Web
Understanding the problem

Part 3 - Aspects of the lifecycle

Part 2 - Technology: Basic & Principles

XML
XML Language Family
HTML
Markup
MIME
Content-Type
URN vs. URL
URL

Example: http-URL

URN
Reserved characters
URI
Adressing ressources
retrieving information
process/render data of resource
handle response
server side

send resource

process

handle request

request resource
prepare request

Unter-Topic

adress?

find resolver

adress resource

round robin
Multi-homed hosts
DNS host name resolution
Protocol Layers Overview
OSI

Open Systems Interconnection Reference Model

TCP/IP
Standards and Organisations
SOA

Service Oriented Architecture

SOAP

Simple Object Access Protocol

Standards

How

w3c - iterative establishing process

workshops

Why

reusability

interoperability

understand requirements

understand processes

Part 1 - Introduction and Overview

The Need for Process
webengineering

Web Engineering – is the application of systematic, disciplined,and quantifiable approaches to the design, production,deployment, operation, maintenance and evolution of Webbasedsoftware products. [Gaedke, 2000]

Engineering is about the systematic application of scientific knowledgein creating and building cost-effective solutions to practical problems

different definitions

history

4 disciplines

Network Engineering

Information systems

storage devices

Hypermedia

Softwareengineering

aesthetic and cognitive aspects
quality requirements

reliable

low cost
high qualitiy
Different requirements views
Web Application Production
influence factors
the change of technology
A look at resources
World Wide Web and the early beginning
W3C

6 Document types

World Wide Web

Consequences

Concept

WWW is...

Uniform Access

Uniform Adressing

Idea

Tim Berners-Lee at CERN

History

Hypertext History

Atkinson

Nelson

Englebart

Bush

Hypermedia?
Hypertext-Documents

Anchor

Link

Node

What is Hypertext

Non-linear nodes of information

Navigate through Information Space

How to Feed your Head
Ted Nelson

"hyptertext = non-sequential writing"

Memex
Vannevar Bush