CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Chapter 16 Change/Content Management Change management procedures and a content management system work in conjunction with one another to help ensure that all requested changes to WebApp content and functionality are managed in a way that does not disrupt the Web engineering process or corrupt the quality of the WebApp itself, and all WebApp content is properly collected, structured, and presented to the end user who requests it. Change management: ensures that changes are made correctly, recorded for future reference, and do not conflict with other changes that have already been made. Content management: collects, manages, and publishes all content that is seen by each end-user category, including content (and functions) that have undergone change.

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Changes A description that explains the nature of the change from the point of view of the stakeholder(s) affected by the change An impact that describes how the change will manifest itself externally (what end users will see) and how it will affect the internal content and functionality of the WebApp A target that defines the specific WebApp objects (both content and functionality) that will be changed An implementation pathway that describes the technical aspects of how the change will be made A history that records when the change was requested, assessed, and implemented and what WebApp content and functionality was affected

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Change Control Class 1. A content or function change that corrects an error or enhances local content or functionality Class 2. A content or function change that has an impact on other content objects or functional components within the increment Class 3. A content or function change that has a broad impact across a WebApp (e.g., major extension of functionality, significant enhancement or reduction in content, major required changes in navigation) Class 4. A major design change (e.g., a change in interface design or navigation approach) that will be immediately noticeable to one or more categories of end users

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Managing Changes

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Managing Changes How do we ensure a change has been properly implemented? (1) conduct pair walkthroughs (focuses on technical correctness), and: (2) perform a change management audit. Ask the following questions: 1.Have any extra modifications been incorporated in addition to those alterations that relate to the requested change? 2.Has a pair walkthrough been conducted to assess technical correctness? 3.Has the WebE process been followed, and have local Web engineering standards been properly applied? 4.Has the change been “highlighted” in the source code? Have the change date and change author been specified? Do the attributes of the content object reflect the change? 5.Have change management procedures for noting the change, recording it, and reporting it been followed? 6.Have all related objects been properly updated?

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Content Management

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright CMS Repository

CMPS 435 F08 These slides are designed to accompany Web Engineering: A Practitioner’s Approach (McGraw-Hill 2008) by Roger Pressman and David Lowe, copyright Content Management System Do you need a CMS? It will depend upon: Content volume. The number of categories (classes) of content objects and the approximate number of content objects within each class Contributor population. The number of content contributors who will create content that will be used by the WebApp, and the complexity of the permissions structures controlling their access to content modification Change volume. The frequency and amount of change that is likely for each class of content and for content objects themselves Publication volume. The number of “publications” that will be produced from the content that is managed within the WebApp