1. Sharepoint Solution
Presented by: Architecture
Rushikesh Ubgade (Global Practice Head Sharepoint )
Hosted by:
Vikram Rajkondawar
Architect Advisor
Ashvini Shahane (Head Strategic Service Unit - Synergetics)
Microsoft Corporation
2. 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
3. Indian IT Architect Needs
“Sharepoint - HTML Output is terrible
How do I get a different HTML Output.”
“Sharepoint Platform is complex to Build Solutions.
How do I know what solutions to build on Sharepoint
Platform”
How can we learn from some of the Best Practices
implemented /executed so far on Sharepoint.
4. 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
6. 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
7. ASAP - Agenda
Date Session Title Speaker Name Webinar Link
Introduction to ASAP for SharePoint and
Vikram Join Webinar
25th Jan Role of an Architect in Architecting Rushikesh 10:00 am. - 12:00 pm.
SharePoint 2010 Solutions
Ashvini
Architecting SharePoint 2010 Solutions Join Webinar
1st Feb that connect with Line-of-Business Ashvini
10:00 am. - 12:00 pm.
systems
Integrating SharePoint 2010 and Join Webinar
8th Feb Ashvini
Windows Azure 10:00 am. - 12:00 pm.
SharePoint 2010 Lessons Learned from Join Webinar
15th Feb Ashvini
Real World Implementations 10:00 am. - 12:00 pm.
Session Timing 10:00 a.m. – 12:00 p.m.
8.
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
9
10. Architecture is an
idea, a plan about
what the solution
that will be built.
Your job is to
create an
To collaborate effectively architecture that
you will need to will meet the need
communicate the
architecture to different
audiences using a variety
of tools, media and
means. 10
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? 11
12. Solve the right problem
Requirements are
the way we define
the problem we are
trying to solve.
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 “Houston, we’ve got a problem”
still be up there. The Apollo 13 Service Module after it was
- Commander Jim Lovell released from the Command Module and set
adrift in space
12
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
13
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
14
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
15
16. SharePoint Specialist Skills
SharePoint SharePoint Infrastructure
Business Analyst Specialist
Business Collaboration
Intelligence
Business Platform
Forms Services Portal
SharePoint
SharePoint
Creative Designer
Content
Developer(s)
Management Search
SharePoint SharePoint
Trainer Architect
17. 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
18. Role of a Sharepoint Solution Architect
• 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 ?
19. An Organizations Areas of IT Needs – Where Sharepoint Can play a
External Entities that IT should support Collaboration with
Role Integration
Supported through Customers Dealers/ Retailers Suppliers/ Partners
Customization
Currently these areas are mostly addressed through Email, Phone Calls & Faxes
Core IT – ERP Domain
Website – Business Extranet – Business Intranet/ Extranet –
Finance/Accounting Information Enquiry/Ordering Helpdesk/Service/Support
Functional Areas where solutions on WSS/Sharepoint can be offered
Analytic
Inventory Dashboards
Manufacturing CORE IT SYSTEMS
Organizational Pain Areas Data Warehouse
WSS/Sharepoint/S
How IT Can Help? SRS
Supply Chain Analytic
Dashboards
Sales – SFA & Purchase – Collaborate Service –Pre/Post-Sales, Admin – Document/
HR / Payroll Collaboration & Automate, RFP etc Maintenance/MRO Records Mgmnt, Audit
Functional Areas where solutions on WSS/Sharepoint can be offered
Transaction Based,
typically very little
customization. Internal Entities that IT should support Collaboration For
Corporate Wide Inter-Branch/Site Outstation/ Mobile
Integration Employees Collaboration Employees
Supported through
Customization Currently these areas are mostly addressed through Email, Phone Calls & Printouts
20. The Long Tail
Tail
The set of products that caters to
more specific user segments.
Popularity
Products
Head
The set of popular products that
caters to broad user segments.
21. IT Functions implemented on Sharepoint
Web Portals
(Structured content)
Tail
The set of applications and
Highly Structured Enterprise unstructured content (typically)
Repositories that caters to teams.
User Base
Departmental solutions
(Structured & Unstructured)
Collaboration Team Sites
(Unstructured content)
Empowerment
Head
The set of applications and structured
content (typically) that caters to large
audiences.
22. Typical IT Solutions addressed with Sharepoint
Regulatory
Extranet
Compliance Collaboration
Sales R&D Repository Site
Division Community
Portal Corporate
Web
Presence Knowledge
Management
Portal
Employee Office
Portal Web Apps
Business Site
Intelligence Project “X”
Dashboard Site
Custom
Team “ABC”
Site SAP
My “Facebook” Front-End
23. SharePoint Strategy and Roadmap
Corporate
Web
Presence
Single Business Productivity Platform leading
Employee
to common:
Portal - End-user Experience
- Rich Integrated Capabilities
Knowledge
Management
- Toolset and Development
Portal - Deployment and Management
Regulatory
Users
Compliance
Repository
Sales
Division
Portal Custom
SAP
Extranet R&D Geneva Business
Front-End
Collab Community Office Intelligence Team “ABC” Project “X” My
Site Site Dashboard Site Site “Facebook”
Corporate Departments Teams
Empowerment
24. Sharepoint Architect Strategy
Enterprise solutions (Head)
Corporate
Web
Presence • Which solutions do you want to move to your
SharePoint Platform?
Employee • What is your migration and/or co-existence
Portal strategy?
• Repeatable, configurable solutions or one-time
Knowledge deployments?
Management
Portal • What is your training and adoption strategy?
Regulatory
Users
Compliance
Repository
Sales
Division
Portal Custom
SAP
Extranet R&D Geneva Business
Front-End
Collab Community Office Intelligence Team “ABC” Project “X” My
Site Site Dashboard Site Site “Facebook”
Corporate Departments Teams
Empowerment
25. Sharepoint Architect Strategy
Corporate
Web
Self-service solutions/platform (Tail)
Presence
• Moderate with workflow?
Employee • What templates and features do you make
Portal available? Allow customizations via SharePoint
Designer?
Knowledge • What is your Service Level Agreement with users?
Management
Portal • What is your training and adoption strategy?
Regulatory
Users
Compliance
Repository
Sales
Division
Portal Custom
SAP
Extranet R&D Geneva Business
Front-End
Collab Community Office Intelligence Team “ABC” Project “X” My
Site Site Dashboard Site Site “Facebook”
Corporate Departments Teams
Empowerment
