Infrastructure Level/Operational
1. Capacity Planning (Scalability)
2. Physical Architecture (Farm Setup, Network, OS, Licensing)
Application level (Functional and Non-Functional)
1. Knowledge of 3rd party webparts
2. Requirement and Feasibility Analysis (Custom Vs OOTB Development/Implementation)
3. Techno-functional Mapping of requirements
4. Information Architecture
5. Logical Architecture
6. Conceptual Architecture
7. Detailed Design
8. Database design (not in terms of traditional Database design), this is with respect to Number of content Databases for Site collections/web apps.
9. Experiences with SharePoint Integration - this comes in two equally important flavours - both from SharePoint accessing existing systems (business catalogs, webparts, etc), as well as other systems accessing SharePoint content via webservice or API.
10. Read SharePoint code using reflector
Deployment
1. Best way to go for deployment, first time and incremental
Migration
2. SharePoint upgrade from v2 (MOSS 2003) to v3 (MOSS 2007).
Others
1. collaboratively work is the Project Manager in Planning, Estimation, Execution/Implementation, Risk Management (assessment, mitigation).
2. Apart from his daily tasks of working with technical teams, testers, User Interface professionals, Vendors, Clients (Business and IT teams).
3. Interacting with Enterprise Architect groups if any.
4. Have at least 5 SharePoint blogs
5. Attend local SharePoint usergroups
Reference:
1. http://blog.furuknap.net/the-role-of-a-sharepoint-architect
2. http://blogs.msdn.com/b/joelo/archive/2007/07/23/depth-and-breadth-in-a-sharepoint-architect-skills.aspx
1. Capacity Planning (Scalability)
2. Physical Architecture (Farm Setup, Network, OS, Licensing)
Application level (Functional and Non-Functional)
1. Knowledge of 3rd party webparts
2. Requirement and Feasibility Analysis (Custom Vs OOTB Development/Implementation)
3. Techno-functional Mapping of requirements
4. Information Architecture
5. Logical Architecture
6. Conceptual Architecture
7. Detailed Design
8. Database design (not in terms of traditional Database design), this is with respect to Number of content Databases for Site collections/web apps.
9. Experiences with SharePoint Integration - this comes in two equally important flavours - both from SharePoint accessing existing systems (business catalogs, webparts, etc), as well as other systems accessing SharePoint content via webservice or API.
10. Read SharePoint code using reflector
Deployment
1. Best way to go for deployment, first time and incremental
Migration
2. SharePoint upgrade from v2 (MOSS 2003) to v3 (MOSS 2007).
Others
1. collaboratively work is the Project Manager in Planning, Estimation, Execution/Implementation, Risk Management (assessment, mitigation).
2. Apart from his daily tasks of working with technical teams, testers, User Interface professionals, Vendors, Clients (Business and IT teams).
3. Interacting with Enterprise Architect groups if any.
4. Have at least 5 SharePoint blogs
5. Attend local SharePoint usergroups
Reference:
1. http://blog.furuknap.net/the-role-of-a-sharepoint-architect
2. http://blogs.msdn.com/b/joelo/archive/2007/07/23/depth-and-breadth-in-a-sharepoint-architect-skills.aspx
No comments:
Post a Comment