Sharepoint Solution Architecture

Hosted by:

Vikram Rajkondawar

Architect Advisor

Microsoft Corporation

Presented by:

Rushikesh Ubgade (Global Practice Head Sharepoint )

Ashvini Shahane (Head Strategic Service Unit - Synergetics)

Agenda

• Introduction to ASAP

• Role of an Architect

• What is SharePoint – Conceptual View

• Functional Components of SharePoint

• SharePoint as a Application Development Platform

• Functional Features of SharePoint 2010

Indian IT Architect Needs

“Sharepoint - HTML Output is terrible

How do I get a different HTML Output.”

How can we learn from some of the Best Practices implemented /executed so far on Sharepoint.

“Sharepoint Platform is complex to Build Solutions. How do I know what solutions to build on Sharepoint Platform”

Purpose of this Program

The purpose is to develop architecture and design skills

required by individuals to design solutions, on Microsoft

Office Sharepoint Platform and get the “abc” of

architecture thinking for Sharepoint based Solutions.

This program is designed to take the senior Developers

with 3-5 years of experience on .net to the Next Level of

what it takes to become an Application Architect

Junior Developer (1-3 yrs)

Senior Developer (3-5 yrs)

Application Architect (5-9 yrs)

Solution Architect (9-15 yrs)

Enterprise Architect (15/20 + yrs)

Architect Maturity Path and Target Audience

Solution Architect

Application /Infrastructure

Architect

Enterprise Architect

Key Take Aways

• What it takes to be a Application Architect on Sharepoint Platform

• Understanding and using the right set of tools/ technologies/ design patterns/ architecture decisions to implement a successful Sharepoint project

• 4 sessions demonstrating some complex scenarios

• Understanding undocumented Best Practices/References and Lessons Learnt for Sharepoint Implementations

ASAP - Agenda

Date Session Title Speaker Name Webinar Link

Vikram Join Webinar

Rushikesh 10:00 am. - 12:00 pm.

Ashvini

Join Webinar

10:00 am. - 12:00 pm.

Join Webinar

10:00 am. - 12:00 pm.

Join Webinar

10:00 am. - 12:00 pm.

Ashvini

15th FebSharePoint 2010 Lessons Learned from 

Real World ImplementationsAshvini

Session Timing 10:00 a.m. – 12:00 p.m.

25th Jan Introduction to ASAP for SharePoint and

Role of an Architect in Architecting

SharePoint 2010 Solutions

1st Feb Architecting SharePoint 2010 Solutions

that connect with Line-of-Business

systems

Ashvini

8th FebIntegrating SharePoint 2010 and

Windows Azure

9

Architecture as a profession

New York City – 1857 Thirteen powerful men—friends of presidents, capitalists, intellectuals, and architects—emerged from horse-drawn carriages to gather together with a singular purpose: to elevate the practice of architecture to a profession in its own right.

The Software Architect’s Profession Marc & Laura Sewell

10

Architecture is an idea, a plan about what the solution that will be built.

To collaborate effectively you will need to communicate the architecture to different audiences using a variety of tools, media and means.

Your job is to create an architecture that will meet the need

11

What problem are we solving?

What are the practical limits of the solution?

How good does the solution need to be?

What resources do we have to build the solution?

12

Solve the right problem

Requirements are the way we define the problem we are trying to solve.

“Houston, we’ve got a problem” The Apollo 13 Service Module after it was released from the Command Module and set adrift in space

To get Apollo 13 home would require a lot of innovation… I certainly agree that without the splendid people in Mission Control, and their backups, we'd still be up there. - Commander Jim Lovell

13

Practical limits

Constraints limit the solution in some practical ways. These limits include time, money, technology, legacy systems etc.

“The Lunar Module was designed to support two men for two days. Now it was being asked to care for three men nearly four days.” - Commander Jim Lovell

14

How good is the solution? The solution must perform well, be secure, be robust and easily managed these characteristics are considered non-functional requirements

“We cut down to six ounces each per day, a fifth of normal intake, and used fruit juices; we ate hot dogs and other wet-pack foods when we ate at all” - Commander Jim Lovell

15

Available resources

Resources include people, technology, legacy systems, technical know-how etc.

“They had thought up a way to attach a CM canister to the LM system by using plastic bags, cardboard, and tape- all materials we had on board. Jack and I put it together: just like building a model airplane” - Commander Jack Lovell

Business Intelligence

Business Forms

Search Content

Management

Collaboration

Portal Platform Services

SharePoint Infrastructure Specialist

SharePoint Architect

SharePoint Creative Designer

SharePoint Business Analyst

SharePoint Developer(s)

SharePoint Specialist Skills

SharePoint Trainer

Role of a Sharepoint Solution Architect

• Analyze the Business Requirement and break it down into functional modules and solution phases as envisioned

• Map the Business Requirement to a logical solution utilizing ‘Out of the Box’ Sharepoint

functional modules and list the missing functional areas • Analyze the points of Sharepoint Customization required within the solution for addressing

the missing functional areas • Apply the 80/20 rule to make a feasibility assessment on the appropriateness of Sharepoint

as the solution platform • Engage with a Sharepoint Technical Architect to create the Sharepoint Logical Design

Document and estimate effort and costs for the Solution Implementation • Present the solution options based on Sharepoint for review and approval, by also

addressing the impact of Sharepoint to future enhancements required as per any envisioned solution roadmap

• Contribute to the Training and Operational Support required to maintain the solution in production

• What is the market potential on Sharepoint Technologies ?

• What's the career growth path on Sharepoint technologies ?

• What’s the demand for Sharepoint certification from Customers – like MCMs ?

• What are the customer asks on Sharepoint ?

• What do you envisage as the Role of an Sharepoint Architect ?

Role of a Sharepoint Solution Architect

An Organizations Areas of IT Needs – Where Sharepoint Can play a Role

Internal Entities that IT should support Collaboration For

External Entities that IT should support Collaboration with

Finance/Accounting

Inventory

Manufacturing

Supply Chain

HR / Payroll

Core IT – ERP Domain

Transaction Based, typically very little

customization.

Customers Dealers/ Retailers Suppliers/ Partners

Currently these areas are mostly addressed through Email, Phone Calls & Faxes

Organizational Pain Areas How IT Can Help?

Corporate Wide Employees

Inter-Branch/Site Collaboration

Outstation/ Mobile Employees

Currently these areas are mostly addressed through Email, Phone Calls & Printouts

Sales – SFA & Collaboration

Purchase – Collaborate & Automate, RFP etc

Service –Pre/Post-Sales, Maintenance/MRO

Admin – Document/ Records Mgmnt, Audit

Website – Business Information

Extranet – Business Enquiry/Ordering

Intranet/ Extranet – Helpdesk/Service/Support

Functional Areas where solutions on WSS/Sharepoint can be offered

Functional Areas where solutions on WSS/Sharepoint can be offered

Data Warehouse

WSS/Sharepoint/SSRS

Analytic Dashboards

Analytic Dashboards

CORE IT SYSTEMS

Integration Supported through

Customization

Integration Supported through

Customization

The Long Tail

Products

Pop

ula

rity

Head The set of popular products that caters to broad user segments.

Tail The set of products that caters to more specific user segments.

IT Functions implemented on Sharepoint

Empowerment

Use

r B

ase

Collaboration Team Sites (Unstructured content)

Web Portals (Structured content) Highly Structured Enterprise Repositories

Departmental solutions (Structured & Unstructured)

Tail The set of applications and unstructured content (typically) that caters to teams.

Head The set of applications and structured content (typically) that caters to large audiences.

Typical IT Solutions addressed with Sharepoint

Employee

Portal

Project “X”

Site

Business

Intelligence

Dashboard

Extranet

Collaboration

Site

Custom

SAP

Front-End

Office

Web Apps

Site

Knowledge

Management

Portal

R&D

Community

Regulatory

Compliance

Repository

Corporate

Web

Presence

Team “ABC”

Site

Sales

Division

Portal

My “Facebook”

SharePoint Strategy and Roadmap U

sers

Knowledge

Management

Portal

Regulatory

Compliance

Repository

Corporate

Web

Presence

Sales

Division

Portal Custom

SAP

Front-End Team “ABC”

Site Project “X”

Site

My

“Facebook”

Business

Intelligence

Dashboard

R&D

Community

Geneva

Office

Site

Employee

Portal

Extranet

Collab

Site

Single Business Productivity Platform leading to common: - End-user Experience - Rich Integrated Capabilities - Toolset and Development - Deployment and Management

Teams Corporate Departments

Empowerment

Sharepoint Architect Strategy U

sers

Knowledge

Management

Portal

Regulatory

Compliance

Repository

Corporate

Web

Presence

Sales

Division

Portal Custom

SAP

Front-End Team “ABC”

Site Project “X”

Site

My

“Facebook”

Business

Intelligence

Dashboard

R&D

Community

Geneva

Office

Site

Employee

Portal

Extranet

Collab

Site

Teams Corporate Departments

Empowerment

Enterprise solutions (Head)

• Which solutions do you want to move to your SharePoint Platform?

• What is your migration and/or co-existence strategy?

• Repeatable, configurable solutions or one-time deployments?

• What is your training and adoption strategy?

Sharepoint Architect Strategy U

sers

Knowledge

Management

Portal

Regulatory

Compliance

Repository

Corporate

Web

Presence

Sales

Division

Portal Custom

SAP

Front-End Team “ABC”

Site Project “X”

Site

My

“Facebook”

Business

Intelligence

Dashboard

R&D

Community

Geneva

Office

Site

Employee

Portal

Extranet

Collab

Site

Teams Corporate Departments

Empowerment

Self-service solutions/platform (Tail)

• Moderate with workflow?

• What templates and features do you make available? Allow customizations via SharePoint Designer?

• What is your Service Level Agreement with users?

• What is your training and adoption strategy?