glm 07/05/2002 a. kosmicki, e.sánchez-corral, f. skaar 1 st web re-engineering progress report...

10
GLM 07/05/2002 A. Kosmicki, E.Sánchez- Corral, F. Skaar 1 ST Web Re-engineering Progress Report • Organization • Strategy. Objectives • Status: design, development • Roles/Responsibilities • Planning

Upload: angela-anthony

Post on 20-Jan-2016

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1

ST Web Re-engineeringProgress Report

• Organization

• Strategy. Objectives

• Status: design, development

• Roles/Responsibilities

• Planning

Page 2: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 2

Organization• ST Webmasters working group

• Regular meetings since start of project:• 15/3, 22/3, 19/4, 3/5

Divisional Web Masters E. Sanchez-Corral, F. SkaarDivisional Web Secretary E. Cochet, C. BieriGroups' WebmastersDI K. Foraz, I. Bejar AlonsoCE T. Watson, A. KosmickiCV L. AnnilaEL G. BurdetHM S. ProdonMA F. Skaar, N. Dos Santos (TCR)TFM J. Garcin

Page 3: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 3

Strategy. Objectives • Easy to build, use and maintain • “Attractive and interesting” but simple• Common look and feel

– Homogeneity in the form and information architecture

• Concentrate in the contents, consistency• Assure confidentiality and security issues

Page 4: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 4

Progress Status • Set-up development environment

– Test site in IT/Central Web servers– Common tool: FrontPage

• Design– Simplicity

• Light images and effects, no scripting if not needed

– Platform and Browser independent• Native html + FrontPage generated code without using specific

features (being tested)

– Site architecture• Simple and clear, common structure for ST groups• Rules, recommendations

Page 5: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 5

Progress Status (2) • Design

– Common look and feel, homogeneity• Common images• Common styles, fonts, colours by using Cascade Styles Sheet• Pages templates: basic, frame pages, projects, …

– CSS included in all the templates– Standard header, footer– Recommendation for contents– Guidelines for users

– Confidentiality and security issues• Technically possible with FrontPage and IT Web servers• User Requirements being prepared

Page 6: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 6

Progress Status (3) • Development

– Site common configuration settings defined– Prototype for ST-MA and ST-DI

• Common layout and main topics (except ST-DI)• Direct entry points to Services and Projects• Easy to maintain (granted templates and guidelines are

followed!)• Reviewed and “Approved” by ST Web masters and DI & MA

– ST Home page• Clear overview of information provided • Direct entry points to Services, Projects and Divisional

Procedures

Page 7: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 7

Responsibilities • Div Web masters

– Site configuration and administration, operation, maintenance (monthly)

– Site structure. Common default for groups– Provide templates (purpose, explanation), guidelines– Create common default group pages– Provide support to group web masters– Divisional pages creation & maintenance

• Group web masters– Customization and contents of group pages– Create new pages if required using divisional

templates/following guidelines

Page 8: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 8

Planning) • Confidentiality requirements

– Requirements, rules to be defined by GLs and DL

• Preparation divisional (projects, services, procedures) and groups pages:– Pages templates, structure and default group pages +

Divisional pages provided by Divisional Web masters: end April

– Group pages to be provided by Group Web masters once approved within group (GL) by middle June

• Review and Approval of new pages (ST, Groups) by ST Management – June

Page 9: GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 1 ST Web Re-engineering Progress Report Organization Strategy. Objectives Status: design, development

GLM 07/05/2002 A. Kosmicki, E.Sánchez-Corral, F. Skaar 9

Planning (2)

• Put in production new pages, possible planning if approval by ST management– 3rd week June

• ST home page + Divisional pages (Projects, Services, Procedures)

• Groups MA, DI, CV

– 4th week June • Group EL, CE

– July• Group HM