SharePoint - Alternate Address

The following is a SharePoint dictionary word of the day:

Alternate address

While using Microsoft/Office 365, any email address associated with the account that is not one’s primary e-mail address.

4 Critical Design Review (CDR) Criteria for a SharePoint Project

The following are four key critical design review for a SharePoint project.

Cost Estimate - Production cost model is known and kept updated, needed aspects are allocated and tracked against targets.  

Technical Baseline Documentation + Digital Artifacts - Detailed design is modeled which includes an interface description and mockup if desired.

Risk Assessment - All risk assessments and risk mitigation plans are documented, formally addressed and implemented. 

Technical Plans - The preliminary design review (PDR) is successfully completed. This includes all needed documentation, set-up and hand-off as needed. 

SharePoint - Alternate account

The following is a SharePoint dictionary word of the day:

Alternate account

An additional user account that is in a different domain, but within the same forest as the primary account.

SharePoint - Alert subscription

The following is a SharePoint dictionary word of the day:

Alert subscription

A request to receive an Internet message automatically when user-defined criteria are met. Such messages are generated automatically when items such as documents, Web pages, list items, sites, or other resources on a server are changed.

SharePoint - After event

The following is a SharePoint dictionary word of the day:

After event

An asynchronous event that runs only after the action that raised the event is finished.

SharePoint - Application Identifier

The following is a SharePoint dictionary word of the day:

Application identifier

A unique integer which classifies a protocol client application. A string that is utilized to look up data in a single sign-on (SSO) database.

4 Document Aspects to Account for in a SharePoint Project

The following are four key documentation aspects to account for in a SharePoint project:

• Reason for the Requirement: What is the reason for the SharePoint requirement, which sometimes it not obvious and needs documented.

• Document Assumptions: If a SharePoint requirement was written assuming the completion of a technology aspect, the assumption should be documented.

• Document Relationships: The SharePoint relationships with the ecosystems expected operations should be documented.

• Document Design Constraints: SharePoint constraints imposed by the results from decisions made as the project evolves should be documented.