Identify user and/or audience personalization requirements for a portal solution

Define types and sources of content, and search implementation for a portal solution. Considerations include Web content, file shares, Microsoft Exchange Server folders, and the ability to process metadata and maintain access control settings

Identify the search implementation for identified content sources. Considerations include the type of content source (for example: Web content, file shares, and Microsoft Exchange Server folders), and the ability to process metadata and maintain access control settings

Define the workflow methods and publishing capabilities to be included in a portal solution

Select Microsoft Integrated Portal Technologies to use as part of a team/inter-departmental collaboration solution. Considerations may include placement/integration of Microsoft Project Server, Microsoft Windows SharePoint Services, Microsoft Office SharePoint Portal Server 2003, and Microsoft Live Communication Server

Select Microsoft Integrated Portal Technologies to use as part of a company-wide employee portal solution (for example: self-service portals for human resources systems or a virtual program management platform).

Select Microsoft Integrated Portal Technologies to use as part of a business process (automation) portal solution. Considerations include business-to-business (B2B) and/or enterprise application integration (EAI) solutions

Select Microsoft Integrated Portal Technologies to use as part of a business-to-business (B2B) portal solution that enables partners to interact with each other

Select Microsoft Integrated Portal Technologies to use as part of a business-to-consumer (B2C)/Internet-facing portal solution

Identify the appropriate site structure for a Microsoft Office SharePoint Portal Server site, a Microsoft Windows SharePoint Services site, and a Microsoft Content Management Server site. Considerations include site collections, top-level sites, and child sites

Decide which data sources and storage architecture to include in a portal solution. Considerations include digital assets, catalog information, and hardware resources

Identify methods to improve the scalability of a portal solution

Identify methods to improve availability for a portal solution. Considerations include Network Load Balancing, Microsoft Cluster Service, and redundant array of independent disks (RAID)

Decide which desktop/client environment to include in a portal solution. Considerations include integration with Microsoft Office System applications and connectors

Identify methods to secure search functions and access to sites, data, and content sources

Define the appropriate authentication architecture based on customer requirements. Considerations include Microsoft Active Directory, Secure Sockets Layer (SSL), Windows NT LAN Manager (NTLM), Lightweight Directory Access Protocol (LDAP), directory and authentication operability, and Single Sign-on integration

Apply the appropriate methods to secure the physical architecture, perimeter network, and infrastructure of a portal solution

Integrate non-Microsoft applications (for example: SAP, PeopleSoft, and Siebel) into a portal solution

Decide whether to implement non-Microsoft solutions or custom software development to extend out-of-the-box functionality

Specify development and deployment environment requirements and configuration. Considerations include version control; development tools; components included on a development client computer; whether to implement a shared database; and the approach, strategy, and size of teams and resources

Identify methods or technologies to integrate Microsoft SharePoint Portal Server and Microsoft Content Management Server into a portal solution

Decide which reporting and analysis tools to use in a portal solution