Webmaailma ja tuotteenhallinta

1
Webmaailma ja tuotteenhallinta
2
Two Significant Differences forE-Development

• 1. Velocity of change
• 2. Tight synergism of business decisions and
  technical development

2
3
E-Development Is Like Software Development

• All best practices apply
• Traditional tools support it

3
4
Traditional Software Lifecycle
4
5
But ...

• Business rules have changed
• New challenges abound
• User expectations are different
• Blurring of code content
• Business/technical tight synergism
• Urgency dominates!
• Programming is different

5
6
Web Programming Is Different

• Higher volume of users and traffic
• Security needs access, data
• Distribution of services
• Internationalization
• Asynchronous programming
• Stateless programming
• Component reuse
• Browser, platform transparency

7
Why the Urgency?

• Competition drivers
• Success drivers
• Pain drivers
• Process drivers

8
Success Drivers

• Incredibly fast growth
• Too many new customers
• Technology evolution

9
Pain Drivers

• Cannot meet deadlines
• Cannot release multiple fixes
• Do not know what went into a release
• Missing features in products
• Developers fix same bug
• Do not know whats been tested
• Have no visibility into work status
• Cannot quantify quality
• Slow recovery from web site crashes

10
Process Drivers

• Capability Maturity Model Integration
• ISO 9000
• Audit failures
• Best practice for web?
• Automation for efficiency
• Web site mistakes

11
Typical Web Content Lifecycle
Create Web System
Outsource
Maintenance
Fix
Publish
Change
12
Publicly Visible Mistakes

• Inappropriate content
• Wrong timing
• Inaccurate content
• Top secret
• Corrupt

• Unauthorized
• Untested
• Stale
• Inconsistent

13
Companies Hit A Web Crisis Point

• Proliferation of quickly hacked together
  Web-based systems kept running via a continual
  stream of patches developed without any rigorous
  or systematic approach

14
Keys To Mastery of E-Development

• 1. CM as the core of development and maintenance
• 2. Process automation
• 3. Tools for efficiencies
• 4. Integration of tools

15
What is CM?

• A disciplined approach to managing the evolution
  of software development and maintenance practices
  and their products

16
CM Is a General Technique

• Can be used on any kind of artifact
• source source code
• graphics
• HTML text
• Java code
• documents
• packaged applications
• hardware

17
Standard Definition

• Identification
• Control
• Status accounting
• Audit and review

18
Operational Elements

• 1. Version configuration control
• 2. Configuration item structuring
• 3. Construction of items
• 4. Change management
• 5. Teamwork support
• 6. Process management
• 7. Status reporting
• 8. Auditing

19
Nine Web Challenges To Master

• 1. Speed of change
• 2. Variant explosion
• 3. Dynamic content
• 4. Process
• 5. Performance effect

• 6. Scalability
• 7. Outsourcing
• 8. Politics
• 9. Immaturity

20
Portals
Data Warehouse
Data Mart
Storage Area
Networks (SANs)
OLAP System
Internet Intranet Extranet Virtual
Private Network (VPN)
Mainframe
Document Imaging System
Web servers
Non-PC devices PDAs Smart Phones Pagers
Web accelerators
ERP Workflow System
FIREWALL
D-Commerce
Thin client
Fat Client
Users
Users
21
Speed of Change Challenge

• Problem
• Fast change
• Frequent change
• Types of changes
• Re-designs, spin-offs, mergers
• CM provides
• change management
• audit trail

22
Variant Explosion Challenge

• Problem
• Too many variants
• Sharing code
• Propagate changes
• CM provides
• Parallel development
• Concurrent baselines

23
Dynamic Active Content Challenge

• Dynamic Created on-the-fly
• Active executed
• HTML, ActiveX, Java, XML, VRML
• Component libraries
• CM provides
• snapshots
• configuration items
• build management

24
Various Objects

• Data objects
• Files
• Documents
• Images
• Streaming audio/video
• Component libraries
• Meta-data
• CM provides repository

25
Free-Form Process Challenge

• Change on-the-fly attitude
• Code and publish
• Lack of release cycle
• CM provides
• change cycles
• release cycles
• authorizations, notifications

26
Performance Effect Challenge

• Response time to users request
• Traffic monitoring
• Web accelerators caching
• CM provides
• legacy (hybrid) support
• parallel development

27
Scalability Challenge

• Millions of pages
• Thousands added per day
• Replication synchronization
• Terabytes of databases
• CM provides
• baselines
• repeatable builds
• repository

28
Outsourcing Challenge

• Corporate trend
• Web creation
• Distributed management
• CM provides
• process
• reports
• change propagation

29
Political Challenge

• Role of IT changing
• Business unit independence
• Who is the owner in control?
• Who can publish to live site?
• CM provides
• process
• audit trails

30
Immaturity Challenge

• First generation tools
• Non-software authors
• Evolving standards
• CM provides
• version everything
• query reports
• repeatable builds

31
Best Practices

• Separation of code, content, database
• Change types cycles
• Standards
• directory naming
• code design
• reuse
• CM Manager
• Separate servers staging areas

31
32
Web Coding Cycle
Development Server
Compile Server
Test Server
Production Server
33
Change Request Cycle
Requirements Design
Validate Request
Impact Analysis
Change review
Code Unit Test
Approval for Release
QA Test
Customer Test
Review
34
CM Is The Core
CRM Tools
Sales
Users
Help-desk Tools
CM
Distribution Tools
Release
Support
Dev
Test
Build
Requirements Management Tools
Change Managers
Test Tools
Design, Modeling Tools
35
CM Tools

• Serve as enterprise knowledge base
• Take the chore out of code content management
• Put safety, integrity repeatability into
  development
• Integrate with application tools to support full
  lifecycles
• Evolutionary or full-process tools

36
Evolutionary CM

• Pieces of CM solution
• Easy and quick start
• Example PVCS Tracker, PVCS Version Manager

37
Full-Process CM

• Process automation
• A comprehensive solution out-of-box
• Example PVCS Dimensions

38
Business value of CM

• Eliminate mistakes
• Recover from site crashes
• Quality automation
• Teamwork optimization
• Change complexity management
• Adaptability to process changes
• Enables survival and growth

39
Susan Darts New Book

• Configuration Management
• The Missing Link in Web Engineering
• Artech House, 2000
• www.artechhouse.com