Applying Cross-Functional Evolutionary Methodologies to Web Development

  • Kenneth S. Norton
Part of the Lecture Notes in Computer Science book series (LNCS, volume 2016)


This paper presents reflections on the application of evolutionary delivery methodologies to a dynamic, fast-paced Web development environment. Conclusions and opinions in the paper are drawn from practical, industry-focused experience under the time-tomarket pressures of the Internet industry. The methodology described offers a mix of rapid application development, evolutionary delivery and joint application development adapted to the unique climate of the Web. Aspects of projects utilizing the methodology are compared to other projects for evidence of improvement. The paper reinforces the need to approach Web development with a pragmatic reverence for its inherent uniqueness, but without losing sight of the lessons learned focuses intently on the requirements definition and early stages of Web projects.


Web Engineering RAD JAD Cross-Functional Teams Evolutionary Delivery 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    T.A. Powell, Web Site Engineering, Prentice Hall, Upper Saddle River, N.J., 1998, pp. 13–17.Google Scholar
  2. 2.
    D. Lowe and W. Hall, Hypermedia and the Web: An Engineering Approach, John Wiley, West Sussex, England, 1999, pp. 212–213.Google Scholar
  3. 3.
    M. Paulk, B. Curtis, M. Chrissis and C. Webber, Capability Maturity Model for Software (Version 1.1), Software Engineering Institute, Carnegie Mellon University, Pittsburgh, 1993, p. 15.Google Scholar
  4. 4.
    R. Pressman, Can Internet-Based Applications Be Engineered?, IEEE Software, Sept./Oct. 1998, p. 105.Google Scholar
  5. 5.
    T. Gilb, Principles of Software Engineering Management, Addison-Wesley, Workingham, England, 1988, pp. 84–114.zbMATHGoogle Scholar
  6. 6.
    S. McConnell, Rapid Development, Microsoft Press, Redmond, Wash., 1996, pp. 425–432.Google Scholar
  7. 7.
    A. R. Dennis, Lessons from Three Years of Web Development, Communications of the ACM, Jul. 1998, p. 113.Google Scholar
  8. 8.
    P. H. Jones, Handbook of Team Design, McGraw-Hill, New York, 1998.Google Scholar
  9. 9.
    J. Wood and D. Silver, Joint Application Development, John Wiley & Sons, New York, 1995.Google Scholar
  10. 10.
    K. F. Chin, A JAD Experience, in (Ed) L. Olfman, Supporting Teams, Groups, and Learning Inside and Outside the IS Function, SIGCPR/ACM, Nashville, 1995, p. 235.CrossRefGoogle Scholar
  11. 11.
    D. C. Gause and G. M. Weinberg, Exploring Requirements: Quality Before Design, Dorset House, New York, 1989.zbMATHGoogle Scholar
  12. 12.
    K. Wiegers, Writing Quality Requirements, Software Development, May 1999, pp. 44–48.Google Scholar
  13. 13.
    P. G. Smith and D. G. Reinertsen, Developing Products in Half the Time, Van Nostrand Reinhold, New York, 1998, pp. 49–65.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2001

Authors and Affiliations

  • Kenneth S. Norton
    • 1
  1. 1.12 Entrepreneuring, Inc.12 Entrepreneuring, Inc.San FranciscoUSA

Personalised recommendations