1 to 3 of 3
Sort by

Blog Entry
Understanding On-Premises, Cloud, & Hybrid Environments in SharePoint 2013 & Office 365

The storage design and requirements will continue to be clearer to you and the team as some additional questions are asked and the technical architecture design process that’s next described begins. EPC Group's Technical Architecture Design Process - High Level Overview As you consider the questions asked in the previous sections, also consider the following list of technical architecture design process points. This is a proven check list from EPC Group of items that should be followed and you should begin with one or more of the following: • Business requirements of the organization • Functional requirements of the organization • User experience and devices from which SharePoint 2013 / Office 365 will be accessed • Logical design • Boundaries of SharePoint 2013 / Office 365 • Information architecture design • Technical architecture • Define, iterate, and revise • Outcome • Server counts • Database design • Server roles • Storage requirements • Sites / Portal / etc. design Ensure That Your Design Starts with What You Currently Know Ensure that this process first takes into consideration the items that have already been uncovered and are known to the project team

Errin O'Connor's profile image

Blog Entry
3 Keys to Develop a Collaboration Strategy around SharePoint

Future State and Roadmap - Design the future state both at a high level functional/conceptual perspective and technical architecture level around SharePoint

Rich Blank's profile image