Home > Articles > Programming > ASP .NET

  • Print
  • + Share This
This chapter is from the book

Site Framework for Content Management

A web site or portal needs a foundation, and content management allows the developer or architect to lay a site framework that will ensure a solid site in the future. This section describes the approach for laying this foundation.

Our methodology is based on the Microsoft Solutions Framework (MSF) and the Rational Unified Process. MSF is a spiral process model. Over the course of a project, all the steps are carried out several times. Figure 9.1 shows the key steps in the development methodology, showing only one trip around the spiral. For more information on the Microsoft Solutions Framework, go to www.microsoft.com/business/services/mcsmsf.asp.

09fig01.jpgFigure 9.1. MSF Methodology Overview


The MSF methodology consists of four broad phases:

  1. Inception

    • Major Activities

      - Formulate the scope of the project, that is, capture the context and the most important requirements and constraints to derive acceptance criteria.

      - Plan and prepare a business case and evaluate alternatives for risk management, staffing, project plan, and trade-offs between cost, schedule, and features.

      - Synthesize a candidate architecture, evaluate trade-offs in design, and assess make/buy/reuse decisions so that cost, schedule, and resources can be estimated.

    • Work Products

      - Vision document containing a general vision of the core project's requirements, key features, and main constraints.

      - Initial project glossary.

      - Initial business case that includes the business context and success criteria.

      - Initial risk assessment.

      - Project plan that shows the phases and iterations.

  2. Elaboration

    • Major Activities

      - Vision is elaborated, and a solid understanding is established of the most critical features that drive the architectural and planning issues.

      - The process, infrastructure, and the development environments are elaborated, and the process, tools, and automation support are put into place.

      - The architecture is elaborated and the components are put into place. Potential components are evaluated, and the make/buy/reuse decisions are sufficiently understood to determine the construction phase cost and schedule with confidence. The selected architectural components are integrated and assessed against the primary behavior scenarios.

    • Work Products

      - Requirements document that captures in detail functional, maintainability, extensibility, scalability, security, and usability requirements.

      - Software architecture description.

      - Revised business case.

      - Revised risk assessment.

      - A development plan for the overall project, including the coarse-grained project plan, which shows iterations and evaluation criteria for each criterion.

  3. Construction

    • Major Activities

      - Resource management, resource control, and process optimization.

      - Complete component development and testing against the defined evaluation criteria.

      - Assessment of product releases against acceptance criteria for the vision.

    • Work Products

      - The software product integrated on the adequate platforms.

      - The user manuals.

      - A description of the current release.

  4. Transition

    • Major Activities

      - Beta testing to validate the new system against user expectations.

      - Training of users and administrators.

      - Rollout of the product.

    • Work Products

      - Software acceptance and rollout.

All this methodology information may seem a bit much for a portal project, but it is quite important to manage a portal as you would manage any other significant development effort. Some customers have approached us to build portals without asking users about their requirements or verifying whether the capabilities the portal will provide will help users. This is a risky use of expensive resources.

Through the lens of our methodology, the MCMS portion of the portal project begins with review meetings and analysis to create a vision for the site in the inception phase. The elaboration or design phase calls for detailed functional specifications and design for elements including the templates and the navigation. The construction phase witnesses the implementation of channels, templates, and resources as well as supporting infrastructure implementation, including hardware and software installation. The transition phase involves putting the site into production, training, maintenance of the site, and preparation for the next round of development. The entire cycle may be iterated a number of times.

You may have your own methodology and want to map these activities accordingly. Having a solid methodology will reduce the risk of the project and improve the quality of the results. It also ensures continuity of a project when personnel change and safeguards against finger-pointing when schedule slips or scope changes.

MCMS lends itself to an iterative team development process much more than a typical page-at-a-time web site. You can approach the channels and templates in a modular fashion. While one team is fielding the templates and testing the workflow for the marketing department, another can be independently developing the human resources channel and integrating job application web pages with an existing PeopleSoft installation. When channels and templates pass user acceptance testing, the real work of cranking out or converting content begins, but developers have already been freed to focus on other development tasks.

Site Vision

The first step in planning the site is to hold a design review session to map the content and organization of the site with the stakeholders of the portal. Most portals start from existing web sites rather than from scratch, so it is essential to identify the pages in the web sites that will be converted to the CMS. Some dynamic content such as online stores or interfaces to databases and other applications will not be converted to MCMS; instead, this content will be integrated into the larger .NET Framework for the portal. A good place to start is with the static pages of the site, which typically constitute the vast majority by page count.

You can use the current site homepage as the baseline for a master template. Use it as the basis for suggestions during the design review meetings when graphic design and navigation decisions are made based on user input. During those meetings, participants provide graphic design and graphic elements for use in MCMS templates. The client freezes the graphic design at the conclusion of this phase. A storyboard, or static mockup of web pages, is a useful tool to capture this design.

Next, audit the existing web site to determine which components will run without modification in the new architecture, which will be migrated, and which will have to be rewritten entirely. At this time, measure the performance of the current site or sites as a benchmark for the new site. Include measures such as average response time for various operations.

Microsoft Visio provides an excellent tool for this stage of designing your portal. Use the Conceptual Web Site Shapes under the Web Diagram provided with Visio to sketch out the general plan for the site.

The deliverable from this phase is a site migration plan that enumerates the pages to be migrated, the target navigation, and the high-level template design. The site migration plan shows which pages will be migrated and how they map to sections in the new site. It also lists the templates to be created and describes the graphics and other elements to be used in the templates.

Taxonomy and Container Hierarchies

Once the overall vision for the site is set, you implement the site taxonomy using MCMS channels. A taxonomy is a hierarchy of categories under which content is organized. It helps users navigate and search in a portal. Chapter 10 provides guidance on how to create a taxonomy and some sample taxonomies. For the examples in this chapter, I use simple site taxonomies.

Microsoft recommends that you create channels before building and populating the other containers in MCMS because the channels are the vertebrae of your content management system. Later in this chapter I describe the steps in defining the channels. At this point you develop the template and resource galleries.

Security Implementation

This stage is a good time to choose the security implementation for the portal. Start by creating a simple login page to grant developers access to MCMS, and then add content creators and others as the site progresses.

Template Creation

You need to develop a base or skeleton template that includes shared page elements and navigation. It can be the basis of other templates for the site. Develop custom placeholders as required at this stage. You want to create the base templates as quickly as possible to allow the content creation and migration process to begin. Subsequent template development may be carried out in parallel to the content creation process.

Content Creation and Migration

The next step is to create content based on the templates and migrate existing content to the site. This is also the time to clean up the site by removing dated content, and editing and refreshing content as identified in the vision phase of the project. In the case of SharePoint Portal Server, this means migration of documents such as Office documents as well as the creation of HTML pages.

Site Testing

Site testing for functionality and performance is a continuous process that can be initiated once the framework is complete and content is being added to the site. Use whatever testing methodologies and automated tools you choose for the testing process.

Some vendors offer site-testing products integrated with MCMS. For instance, Coast (www.coast.com) provides testing and quality assurance tools for web sites during development and postdeployment. Their product becomes part of the MCMS routing and approval process, checking for errors such as broken links, inappropriate content, and compliance with accessibility guidelines such as Section 508 (http://www.section508.gov/). Section 508 is a U.S. government regulation which amended the Rehabilitation Act in 1998. It calls for Federal government agencies to make electronic and information technologies available to people with disabilities. HiSoftware (www.hisoftware.com) also integrates its solution with MCMS. This package, called Solution for Online Accessibility, includes Content Management Server and HiSoftware products to help customers achieve Section 508 compliance (http://www.hisoftware.com/soa/).

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020