The WebE Team
29.7.1 The WebE Team
The creation of a successful Web application demands a broad array of skills. Tilley and Huang [TIL99] address this issue when they state: “There are so many different aspects to [Web] application software that there is a (re)emergence of the renais-
“In today’s net-centric sance person, one who is comfortable operating in several disciplines . . .” While the and Web-enabled
world, one now authors are absolutely correct, “renaissance” people are in relatively short supply; needs to know a lot
and given the demands associated with major WebApp development projects, the about a lot.”
diverse skill set required might be better distributed over a WebE team.
Scott Tilly and
WebE teams can be organized in much the same way as the software teams dis-
Shihoug Huang
cussed in Chapter 3. However, the players and their roles are often quite different. Among the many skills that must be distributed across WebE team members are com- ponent-based software engineering, networking, architectural and navigational design, Internet standards/languages, human interface design, graphic design, content lay-
out, and WebApp testing. The following roles 8 should be distributed among the mem- bers of the WebE team:
? Content developer and providers. Because WebApps are inherently con-
What roles
do people
tent driven, one WebE team member role must focus on the generation or
play on a WebE
collection of content. Recalling that content spans a broad array of data
team?
objects, content developers and providers may come from diverse (non-soft- ware) backgrounds. For example, marketing or sales staff may provide prod- uct information and graphical images, media producers may provide video and audio, graphic designers may provide layout design and aesthetic con- tent, copywriters may provide text-based content. In addition, research staff may be required to find and format external content for placement or refer- ence within the WebApp.
Web publisher. The diverse content generated by content developers and providers must be organized for inclusion within the WebApp. In addition, someone must act as liaison between technical staff that engineers the WebApp and nontechnical content developers and providers. This role is filled by the Web publisher, who must understand both content and WebApp technology including HTML (or its next generation extensions, such as XML), database functionality, scripts, and general Web-site navigation.
Web engineer. A Web engineer becomes involved in a wide range of activi- ties during the development of a WebApp including requirements elicitation; analysis modeling; architectural, navigational, and interface design; WebApp implementation; and testing. The Web engineer should also have a solid understanding of component technologies, client/server architectures, HTML/XML, and database technologies as well as a working knowledge of
8 These roles have been adapted from Hansen, Deshpande, and Murgusan [HAN99].
CHAPTER 29 WEB ENGINEERING
multi-media concepts, hardware/software platforms, network security, and Web-site support issues.
Support specialist. This role is assigned to the person (people) who has responsibility for continuing WebApp support. Because WebApps continu- ously evolve, the support specialist is responsible for corrections, adapta- tions, and enhancements to the site, including updates to content, implementation of new procedures and forms, and changes to the navigation pattern.
Administrator. Often called the Web master, this person has responsibility for the day-to-day operation of the WebApp, including
• Development and implementation of policies for the operation of the
WebApp. • Establishment of support and feedback procedures. • Implementation of security procedures and access rights. • Measurement and analysis of Web-site traffic. • Coordination of change control procedures (Section 29.7.3). • Coordination with support specialists.
The administrator may also be involved in the technical activities performed by Web engineers and support specialists.
Parts
» The Concurrent Development Model
» SUMMARY Software engineering is a discipline that integrates process, methods, and tools for
» PEOPLE In a study published by the IEEE [CUR88], the engineering vice presidents of three
» THE PROCESS The generic phases that characterize the software process—definition, development,
» THE PROJECT In order to manage a successful software project, we must understand what can go
» METRICS IN THE PROCESS AND PROJECT DOMAINS
» Extended Function Point Metrics
» METRICS FOR SOFTWARE QUALITY
» INTEGRATING METRICS WITHIN THE SOFTWARE PROCESS
» METRICS FOR SMALL ORGANIZATIONS
» ESTABLISHING A SOFTWARE METRICS PROGRAM
» Obtaining Information Necessary for Scope
» An Example of LOC-Based Estimation
» QUALITY CONCEPTS 1 It has been said that no two snowflakes are alike. Certainly when we watch snow
» SUMMARY Software quality assurance is an umbrella activity that is applied at each step in the
» R diagram 1.4 <part-of> data model; data model <part-of> design specification;
» SYSTEM MODELING Every computer-based system can be modeled as an information transform using an
» Facilitated Application Specification Techniques
» Data Objects, Attributes, and Relationships
» Entity/Relationship Diagrams
» Hatley and Pirbhai Extensions
» Creating an Entity/Relationship Diagram
» SUMMARY Design is the technical kernel of software engineering. During design, progressive
» Data Modeling, Data Structures, Databases, and the Data Warehouse
» Data Design at the Component Level
» A Brief Taxonomy of Styles and Patterns
» Quantitative Guidance for Architectural Design
» Isolate the transform center by specifying incoming and outgoing
» SUMMARY Software architecture provides a holistic view of the system to be built. It depicts the
» The User Interface Design Process
» Defining Interface Objects and Actions
» D E S I G N E VA L U AT I O N
» Testing for Real-Time Systems
» Organizing for Software Testing
» Criteria for Completion of Testing
» The Transition to a Quantitative View
» The Attributes of Effective Software Metrics
» Architectural Design Metrics
» Component-Level Design Metrics
» SUMMARY Software metrics provide a quantitative way to assess the quality of internal product
» Encapsulation, Inheritance, and Polymorphism
» Identifying Classes and Objects
» The Common Process Framework for OO
» OO Project Metrics and Estimation
» Event Identification with Use-Cases
» SUMMARY Object-oriented analysis methods enable a software engineer to model a problem by
» Partitioning the Analysis Model
» Designing Algorithms and Data Structures
» Program Components and Interfaces
» SUMMARY Object-oriented design translates the OOA model of the real world into an
» Testing Surface Structure and Deep Structure
» Deficiencies of Less Formal Approaches 1
» What Makes Cleanroom Different?
» Design Refinement and Verification
» SUMMARY Cleanroom software engineering is a formal approach to software development that
» Structural Modeling and Structure Points
» Describing Reusable Components
» SUMMARY Component-based software engineering offers inherent benefits in software quality,
» Guidelines for Distributing Application Subsystems
» Middleware and Object Request Broker Architectures
» An Overview of a Design Approach
» Consider expert Web developer will create a complete design, but time and cost can be appropriate
» A Software Reengineering Process Model
» Reverse Engineering to Understand Data
» Forward Engineering for Client/Server Architectures
» SUMMARY Reengineering occurs at two different levels of abstraction. At the business level,
Show more