Intranet Website Solution
Based on Microsoft SharePoint Server Foundation 2010
December 14, 2012 Authors:
Wilmer Entena – 128809 Rimon Nassori – 131311
Supervisor: Henrik Kronborg Pedersen
VIA University College, Horsens Denmark
List of Figures and Tables ... 3
Abstract ... 5
1. Introduction ... 6
2. SharePoint Foundation 2010 Architecture ... 7
3. Intranet Solution Site ... 8
4. System Specification ... 10
4.1 Use Case Model ... 10
4.2 Activity Diagram... 11
5. Site Planning ... 13
6. Web Parts ... 14
6.1 Departments Web Part ... 14
6.2 Company News Web Part ... 16
6.3 Announcements Web Part ... 17
6.4 Discussion Board Web Part ... 19
6.5 Information Web Part... 22
6.6 Quick Links Web Part ... 23
7. Login Page and Authentication ... 25
8. Main Site ... 27
8.1 Masterpage ... 28
8.2 Main Site Default Page ... 29
9. Department Sub Sites ... 30
10. Shared Documents ... 31
11. Calendar ... 31
12. Contact List ... 32
13. Company Blog ... 32
15. Testing ... 33
16. Results ... 33
17. Discussion ... 34
18. Conclusion ... 35
References ... 36
APPENDIX A ... 38
APPENDIX B ... 52
APPENDIX C ... 55
List of Figures and Tables Figure 2.1 – SharePoint Foundation 2010 Architecture Diagram ... 7
Figure 4.1.1 Use Case Diagram ... 10
Figure 4.1.2 Activity Diagram for User Login ... 11
Figure 4.1.3 Activity Diagram for Adding Discussion ... 12
Figure 5.1 Rootsite and Subsites ... 13
Figure 6.1.1– Code location for Department’s web part in Project Solution... 14
Figure 6.1.2 – Departments Web Part View ... 15
Figure 6.1.3 – The code for Department’s Web Part ... 15
Figure 6.2.1 – Code location for Company News web part in Project Solution ... 16
Figure 6.2.2 – Company News Web Part View ... 16
Figure 6.2.3 – The code for Company’s Web Part ... 17
Figure 6.3.1 – Code location for Announcements web part in Project Solution ... 18
Figure 6.3.2 – Announcements Web Part View ... 18
Figure 6.3.3 – The code for Announcements Web Part ... 19
Figure 6.4.1 – Code location for Discussion Board web part in Project Solution ... 20
Figure 6.4.2 – Discussion Board Web Part View ... 20
Figure 6.4.3 – The code for Discussion Board Web Part ... 21
Figure 6.5.1 – Code location for Information web part in Project Solution ... 22
Figure 6.5.2 – Information Web Part View ... 22
Figure 6.5.3 – The code for Information Web Part ... 23
Figure 6.6.1 – Code location for Quick Links web part in Project Solution ... 24
Figure 6.6.2 – Quick Links Web Part View ... 24
Figure 6.6.3 – The code Quick Links Web Part ... 25
Figure 7.1 Login and Authentication Flow Diagram ... 25
Figure 7.2 Token and Claims ... 26
Figure 8.1 – Main Site Default Page View ... 27
Figure 8.1.1 – Location of the Masterpage in Project Solution ... 28
Figure 8.1.2 Masterpage Layout ... 29
Figure 8.1 Main Site Default Page WebPartZone with codes ... 29
Figure 9.1 Department Site’s Homepage Interface ... 30
Figure 9.2 Department’s Site Location in Project Solution ... 30
Figure 10.1 Dialog box for Uploading Files and Documents ... 31
Figure 11.1 Site’s Calendar View ... 31
Figure 12.1 Contact List View ... 32
Figure 13.1 Company Blog Interface ... 32
Table 8.1 – Functional Area of SharePoint Main Site ... 27
Abstract
Background: The objective of this study is to provide a company and organization an intranet solution site based on SharePoint Foundation 2010 that will help their team members to work together efficiently. The study was done in close consultation with companies and organization that requires challenging ideas on how to meet their requirements on information sharing and by investigating and learning on how Microsoft SharePoint technology can achieve these goals.
Results: SharePoint site can deliver a solution for business collaboration with its features and applications. We have created an effective Intranet Website Solution system based on SharePoint Foundation 2010 Server.
Significance: The significance of the study gave us the opportunity to demonstrate and provide the
company a solution for their intranet site and gave their team members a useful tool for working
together.
1. Introduction
Companies and organizations are finding ways and great solution for their team members to be able to share significant and vital information throughout the company or organization, and the goal of this project is to deliver the solution that they needed.
LN Pro ApS is a small IT company in Århus Denmark specializing in development of Commerce Express an IBM Lotus Notes based CRM system for its clients. The company is in need of an intranet collaboration website to be presented to its perspective clients. The intranet website will be based on Microsoft’s SharePoint Foundation Server 2010 technology. The company asked us to create an intranet website based on the client’s requirement and will run on a Microsoft SharePoint Foundation Server 2010 system. The client’s intranet site is requiring us to program all the functionalities of a SharePoint website.
The aim of this project was to create an Intranet Solution Site based on SharePoint Server Foundation 2010. The system will create an environment for the employees and team members of the organization where they can share information quickly and efficiently.
The intranet system that we created will be the basis for the company to take advantage of the SharePoint technology and the significant role it will provide to their business. The system was carefully planned and executed through thorough investigation, learning process, and teamwork.
The following chapters of this report will provide the reader a deep understanding about the Intranet
SharePoint Site system that we created and the methodologies that we used. Thus this project will
not only open a new and challenging idea but can also achieve the company’s goal of an effective
channel of communication in information technology.
2. SharePoint Foundation 2010 Architecture
The main part of the report discussed about the detailed information of the planning, designing and programming the intranet website. In this section includes the structure and architecture of the site.
A brief description of the SharePoint technology that was used as the core basis for this project was also introduced. The main components and functionalities of the site are also covered in this section. The diagram below illustrates the architectural structure our SharePoint site project.
*Please see Appendix C for setting up and configuration of SharePoint 2010 Foundation sever.
Figure 2.1 – SharePoint Foundation 2010 Architecture Diagram
3. Intranet Solution Site
This is a brief overview of the SharePoint architecture implemented in this project. The development environment was done on Windows 7 Professional (64 bit) operating system as part of the SharePoint Foundation 2010 server requirements. Internet browser, Visual Studio 2010, SharePoint Designer 2010 are the user’s interface for the use and development of the SharePoint site.
SharePoint Foundation Server 2010 is the core foundation in building the intranet website that includes the following features and applications:
1. List, Libraries, Content Types, Field Types – this service allows the users to store, manage, and share all types of files and data that the team members need for collaboration within the company or organization.
2. Web Parts – this is the structure of a SharePoint site within the page where the different data and applications are easily accessible by the user.
3. Web Pages – consists of a Master page and other web pages built on top of ASP.NET, these pages is the user’s interface to access data and applications that runs in the SharePoint site.
4. Site Definition – is the definition of what a site is in SharePoint, it consists of .aspx pages and xml files with Collaborative Application Mark-up Language (CAML).
5. Service Application – the application services available to SharePoint site that includes web content management, search service, email integration, Business Connectivity services, that can be shared across the site and can be access by the user through a hosting web application.
6. Security and Authentication – the permission and roles assigned to the groups and team
members that restrict different users to control the access specific SharePoint site and
pages.
1
Microsoft SQL Server is a relational database management system developed by Microsoft. As a database, it is a software product whose primary function is to store and retrieve data as requested by other software applications, be it those on the same computer or those running on another computer across a network (including the Internet). There are at least a dozen different editions of Microsoft SQL Server aimed at different audiences and for different workloads (ranging from small applications that store and retrieve data on the same computer, to millions of users and computers that access huge amounts of data from the Internet at the same time).
2
IIS (Internet Information Server) is one of the most powerful web servers from Microsoft that is used to host your ASP.NET Web application. IIS has its own ASP.NET Process Engine to handle the ASP.NET request. So, when a request comes from client to server, IIS takes that request and process it and send response back to clients.
3
The ADO.NET Data Services framework is Microsoft’s technology for creating and consuming
data services. These data services use the Entity Data Model (EDM) to model data in terms of
entities. These entities are exposed as URI-addressable resources that can be accessed using
standard HTTP requests. ADO.NET Data Services also establishes uniform patterns that UI widget
frameworks and libraries can leverage to provide additional services on top of the data services.
4. System Specification 4.1 Use Case Model
Use case model is a tool used for defining system specifications. It describes the goals of the users, the interaction between the users and the system.
Figure 4.1.1 Use Case Diagram
The use case diagram shows the functionalities for the system. There are to actors “Admin” and
“User”. The association between user/admin and use cases, shows the functionalities which the user/admin can use. The inheritance between the admin and the user means, that the admin have the same functionalities as the user has.
*Please see Use Case Specification on Appendix A
4.2 Activity Diagram
Figure 4.1.2 Activity Diagram for User Login
Figure 4.1.3 Activity Diagram for Adding Discussion
5. Site Planning
The requirements of the intranet site were carefully planned and various consultation and references was made before the beginning of the project. The intranet website project is composed of a top level site and below is the sub site collection that includes the following departments:
1. Human Resources 2. Marketing
3. Sales 4. Finance 5. I.T.
The applications and features of the site include the following:
1. Department’s Link – Members can go to home page of their designated department 2. Shared Documents – members can share files and documents
3. Calendar – members are able to view events and schedules within the company 4. Contact List – a useful tool to find contacts in the organization
5. Company News – members are able to view, read, and post latest news of the company 6. Announcements – members are able to view, read, and post announcements
7. Information – members are able to view, read, and post related information 8. Discussion Board – members can participate in teams discussions
9. Quick Links – link to related websites
10. Company Blog – members are able to view, read, and post blogs
11. Social Media – a useful tool for integrating social media to the SharePoint site
Each sub site will also implement the required functionalities. Each users and members will be
assigned a specific authorization and permissions within the site.
6. Web Parts
Web parts provide the users the access to different applications and data on the same page. This is a useful tool for a dynamic and collaboration site such as SharePoint. Web part is a list in SharePoint site and a reusable item that can be implemented in different sites in the site collection. This section will explain the functional description of the web parts and code.
6.1 Departments Web Part
The Department Web Part includes five different links. The links are the sub sites, Human Resources, Marketing, Finance, Sales, IT Department. The link will send the user to the designated home page of the department. The department’s web part is a list designed and created in Visual Studio 2010 and uploaded on the server.
File Name: DepartmentsUserControl.ascx
Location: http://rootsite/Lists/Departments/AllItems.aspx
Figure 6.1.1– Code location for Department’s web part in Project Solution
Figure 6.1.2 – Departments Web Part View
Figure 6.1.2 shows the actual layout and design of the department’s web part. Consist of five different links to each department’s home page.
Figure 6.1.3 – The code for Department’s Web Part
Figure 6.1.3 shows the code for the department’s link web part. Each department is enclosed on a
hyperlink markup that will eventually send the user to the department’s homepage. The link for the
6.2 Company News Web Part
The company news web part is a where a member or user can post a news on the company’s web part area. The user can view, add, edit, and delete items on the web part. The company news web part is a list designed and created in xml code using Visual Studio 2010 and uploaded on the server.
File Name: Schema.xml
Location: http://rootsite/Lists/Company News/AllItems.aspx
Figure 6.2.1 – Code location for Company News web part in Project Solution
Figure 6.2.2 – Company News Web Part View
Figure 6.2.2 shows the actual layout and design of the company news web part. The heading,
the content part, the add new item button can be use by the member to add a new item on the
news area. The user can view recent posted news, add a new item to the news, delete or edit
the news that the member posted.
Figure 6.2.3 – The code for Company’s Web Part
Figure 6.2.3 shows the partial xml code of company news web part which creates the fields’
title and body forms. The view of the forms is also coded in xml that will display the company news items of the web part. The data of the company web part list are stored on the SharePoint’s SQL database server.
6.3 Announcements Web Part
The Announcement Web Part has a add button, if you click on the add button it will show you a new window where you can create an announcement. It includes a “Title” it’s a required field, so you have to write something inside it. A “Description” describing what you are about to announce. Then we have “Department” just to tell what kind of department you from. A
“Date Expire” so you can choose when you want your announcement to expire, it’s also a required field. And last “My Job Title” so they others can see if you are a manager, member etc. After done that click on save and we can see the new announcement under the Web Part Announcements. The announcements web part is a list designed and created in xml codes using Visual Studio 2010 and uploaded on the server.
File Name: Schema.xml
Location: http://rootsite/Lists/Announcements/AllItems.aspx
Figure 6.3.1 – Code location for Announcements web part in Project Solution
Figure 6.3.2 – Announcements Web Part View
Figure 6.3.2 shows the actual layout and design of the Announcement web part. The heading,
the content part, the add new announcement button can be use by the member to add a new
item on the announcement area. The user can view recent posted announcement, add a new
item to the announcement, delete or edit the announcement that the member posted.
Figure 6.3.3 – The code for Announcements Web Part
Figure 6.3.3 shows the partial xml code which creates the fields’ title, body, and expiry date.
The view of the forms is also coded in xml that will display the announcements items of the web part. The data of the announcement web part list are stored on the SharePoint’s SQL database server.
6.4 Discussion Board Web Part
The discussion board web part is a tool for members and user within the company where the user can post a topic and be able to reply to the topics that was posted by the member. The subject is being displayed together with the user who created the subject or topic. The user can add an item by clicking on the add item button on the web part. The discussion board web part is a list designed and created in xml codes using Visual Studio 2010 and uploaded on the server.
File Name: Schema.xml
Location: http://rootsite/Lists/Discussion Board/AllItems.aspx
Figure 6.4.1 – Code location for Discussion Board web part in Project Solution
Figure 6.4.2 – Discussion Board Web Part View
Figure 6.4.2 shows the actual layout and design of the Discussion Board web part. The
heading, the content part, the add new discussion button can be use by the member to add a
new subject on the discussion area. The user can view recent posted discussion, add a new
item to the discussion, delete or edit the discussion that the member posted.
Figure 6.4.3 – The code for Discussion Board Web Part
Figure 6.4.3 shows the partial xml code which creates the fields’ subject and body. The view
of the forms is also coded in xml that will display the discussions subject, author, replies, and
the date when the subject was last updated from the web part. The data of the discussion
board web part list are stored on the SharePoint’s SQL database server.
6.5 Information Web Part
The information web part is the area on the page where a member or user can post useful information on the company’s information area. The user can view, add, edit, and delete items on the web part. The information web part is a list designed and created in xml code using Visual Studio 2010 and uploaded on the server.
File Name: Schema.xml
Location: http://rootsite/Lists/Information/AllItems.aspx
Figure 6.5.1 – Code location for Information web part in Project Solution
Figure 6.5.2 – Information Web Part View
Figure 6.5.2 shows the actual layout and design of the Information web part. The heading, the
content part, the add new item button can be use by the member to add a new information on
the information area. The user can view recent posted information, add a new item to the
information, delete or edit the information that the member posted.
Figure 6.5.3 – The code for Information Web Part
Figure 6.5.3 shows the partial xml code for the information web part which creates the fields’
title and body. The view of the forms is also coded in xml that will display the title and the body of the web part. The data of the information web part list are stored on the SharePoint’s SQL database server.
6.6 Quick Links Web Part
The Quick Links Web Part is a link to other related website that a member can use. A separate window will appear on the screen when the user clicks on the link. The information web part is a list. The quick links web part is a list designed and created in Visual Studio 2010 and uploaded on the server.
File Name: Quick LinksUserControl.ascx
Location: http://rootsite/Lists/Quick Links/AllItems.aspx
Figure 6.6.1 – Code location for Quick Links web part in Project Solution
Figure 6.6.2 – Quick Links Web Part View
Figure 6.6.2 shows the actual layout and design of the quick links web part. The links will
send the user to another window that points to the sites url.
Figure 6.6.3 – The code Quick Links Web Part
Figure 6.6.3 shows the code for the quick link web part. Each link is enclosed on a hyperlink markup that will eventually send the user to the external site s homepage that will opens to a new window.
7. Login Page and Authentication
In our web site we have one user credentials, with username and password. By using claim
based authentication that’s actually enough to access the web site. When a user is logging in
an Identity is assigned to that session, and that Identity is maintained until the user logs out or
it expires.
check if the users is authenticated, and if the user is authenticated, then it gives an Identity and the user gets the right to access the application. If the user is not authenticated, then the user is denied access.
The Claim based Authentication lets us set whether Windows authentication is enabled and whether Forms Based Authentication via ASP.NET. By using Forms Based Authentication it lets us use either a default Sign in page provided by SharePoint or our own customized Sign in page.
In the above figure there are some basic things involved. There are Identity, Tokens, Claims, etc.
Identity can identify anything it’s like a group of information that identifies a user. When Identity is passed as a stream of bytes, then it’s called Token. Token contains information about the user in the Claim format, and the token contains specific information.
Figure 7.2 Token and Claims
Token can be XML based Security Assertion Makeup Language (SAML) format. But an application can also use a simpler token called Simple web Token (SWT). Benefit is that we do not pass user credential but, but other information about the user to the application.
Identity provider authenticates the user and creates the token with claims, and also known as
Security token services (STS)
8. Main Site
This is the first page that will be displayed to the user after logging in to his/her account. The main site consists of a masterpage, a default page, the links, and the web part features and functionality.
The area is divided into four parts, 1. the header part where the company logo, login menu, 2. the top menu links, 3. quick launch menu area where the other site menus are located, and the 4.
content area of the main page where the content and web parts of the site and pages will be placed.
Figure 8.1 – Main Site Default Page View
*Please refer to Table 8.1 for the detailed description of the Main Site default page.
Table 8.1 – Functional Area of SharePoint Main Site
Figure Label
Functions Description of Functionality
A Logo Display the company logo, can also be use as a link to return to sites home page.
B Site Title Display the specific title of the page that will guide the users when exploring the site.
C Account’s Menu This is where the user can Login or Logout from their account.
G Launch Menu The vertical navigation menu that links to the sites other pages and functionalities.
H All Site Content The user can view all the site content.
I Content Area This is the area where the content, web parts and functionalities are displayed.
8.1 Masterpage
File Name: mycustom.master
Location:http://rootsite/_catalogs/masterpage/mycustom.master
The master page was implemented and will serve as the template for all the sites and pages within the site collections, the layout will be inherited by all the pages. The main parts of the master page consist of header part where the company logo, site title, account’s menu, top menu bar, search bar, and help menu button is placed. The quick launch menu and all site content is at the left side part of the page. The body of the page is located in the content area of the page.
*Please refer to Figure 8.1 for the visual representation.Figure 8.1.1 – Location of the Masterpage in Project Solution
Figure 8.1.2 Masterpage Layout
8.2 Main Site Default Page http://rootsite/default.aspx
The default page of the website will inherit the default masterpage. When the user
successfully login he/she will then be directed to the default page of the site. The page is
designed with a table inside with three columns and three webpart zones where all the web
parts that we created can be inserted in each webpart zone. Each WebPartZone has a unique id
and a title for each.
9. Department Sub Sites
The SharePoint site has five different sub sites for each department namely: Human Resources, Marketing, Finance, Sales, IT Department. Each members of the site can utilize the features and functionality of the SharePoint site. The page will implement the following web parts:
Company News
Announcements
Information
Discussion Board
Quick Links
Every department’s site will inherit the default masterpage that we created. Every department also have individual default page, these default pages will have the container for the web parts. All the pages, features, and functionality were deployed on the SharePoint server. Each member or groups within the department has their own permission level which let them perform tasks.
Figure 9.1 Department Site’s Homepage Interface
Figure 9.2 Department’s Site Location in Project Solution
10. Shared Documents
Sharing documents is a great feature of SharePoint site. We utilize this feature for the groups and members of the site to be able to share files and important and download documents across the organization. People can easily access the file using the browser and save it to their local computer.
Figure 10.1 Dialog box for Uploading Files and Documents
11. Calendar
Calendar is another feature of SharePoint where a group or member can create and share their
schedule to the team members. You can add event to the calendar so that team members can view
that specific event when they log in.
12. Contact List
The contact list is a great way to find members contact details and information across the organization. The members can add their information and members can use this as a directory if they want to contact the person in their organization.
Figure 12.1 Contact List View
13. Company Blog
Blog site is a useful tool for the company where all the members of the group can post their ideas and share it throughout the organization.
Figure 13.1 Company Blog Interface
15. Testing
Testing is an important part of the system, to keep errors and to make our system stable. There are many kinds of testing. There are two testing parts “White Box Testing” and “Black Box Testing”.
In our case we are only using Black box testing. White box testing includes Unit-Test and integration test, and these 2 are not part of our system, but what we are doing is Black box testing, where we use Performance testing and System testing.
With System testing we are making sure that everything in our system is working as we expected it to work. With performance testing, we are testing if the site and the URL and links acting without any errors.
* Please see Appendix B for all result for the System Test and Performance Test
16. Results
The outcome of this project is a working intranet system site that is running on SharePoint Foundation 2010 server. Information sharing and collaboration with team members are just amongst the benefits of the system. The usefulness, applications, and features of SharePoint site makes it easier for the user to get engaged and get easy access to any important information they needed. We are able to create a site for the company and for each department that needs the same functionality that an intranet has to offer.
The member can participate and contribute to the content of the site which will be a valuable asset
to the company. Sharing files and documents makes it possible with the SharePoint sites
application. The project was able to achieve its goals and company requirements by implementing
all the necessary tools for an intranet site.
17. Discussion
This focus of this project is to deliver an intranet system based on SharePoint technology using SharePoint Foundation server 2010 and its functionalities. How to build the system base on the company’s requirements and what tools and methodologies we need to implement such.
It is critical in every business and its members to have easy access to important information, thus our system accomplished these objectives in a way that the site performs the necessary tools needed. Team members can contribute by means of posting news, announcements, information that others may need. Sharing files and documents can be done and manage easily.
There are two available servers for the SharePoint one is the Foundation Server and the other is the SharePoint Server. This maybe out of our scope but plays a significant role in creating SharePoint site. The difficulties we encounter occurs by doing this project is the limitations of what a SharePoint Foundation 2010 server can do, but without any further discussion about this subject we recommend the use of SharePoint server for its advance features and functionality both for the user and the developer.
The system is done in a way, so they don’t need to navigate a lot in the system, but where they have everything in front of them, and by one click the member can submit the valuable content to the site. The best thing we have on our system is, members in the company can share information, so when a member logs into the system they can see the information shared right away.
In future developments of the system we would take advantage of the integration of the social
media in SharePoint site, we want create a social environment for the members. And that also send
a clear message to the members that it’s about communication and collaboration with each other.
18. Conclusion
The intranet system site has the functionality that meets the company’s requirements. The tools and
methodologies that we used to create a working system were made possible by research,
consultation, learning, creating, and implementing SharePoint tools and technology. Based on the
discussion presented, there are more features and applications can be implemented in the project
and can be done with the continuous development of the intranet site. With this system the team
members of the company can now utilize and take advantage of its features and application to be
able to work together more efficiently and effectively. Information Technology on its own words is
the core of our system.
References
[1] http://shermanstechnicalblog.blogspot.dk/2012/10/adding-custom-css-file-to-your-visual.html [2] http://www.codeproject.com/Articles/268236/Claim-based-Authentication-and-WIF
[3] http://fabiangwilliams.wordpress.com/2010/07/03/how-to-create-content-types-with-site- columns-in-code-visual-studio-2010-for-sharepoint-2010/
[4] http://rickhilferink.wordpress.com/2011/01/25/creating-a-sharepoint-2010-foundation- masterpage-solution-and-automatically-activate-it-for-all-sites-and-newly-created-subsites/
[5] http://pooyakhamooshi.blogspot.dk/2011/01/how-to-add-custom-css-and-js-files-to.html [6] http://sharepointgeorge.com/2009/creating-web-application-site-collection-sharepoint-2010/
[7] http://blogs.msdn.com/b/kaevans/archive/2010/07/09/creating-a-custom-login-page-for- sharepoint-2010.aspx
[8] http://msdn.microsoft.com/en-
us/library/hh537935.aspx#CustomizingSP2010WebPartUI_AdditionalResources
[9] http://www.sharepointbriefing.com/spcode/develop-sharepoint-2010-content-type-using-visual- studio-2010.html
[10] http://blogs.technet.com/b/mahesm/archive/2010/04/07/configure-forms-based-authentication- fba-with-sharepoint-2010.aspx
[11] http://aarebrot.net/blog/2010/06/frodes-awesome-list-of-sharepoint-column-field-ids-for- sharepoint-2010/
[12] http://www.c-sharpcorner.com/Forums/Thread/182458/how-to-create-page-layout-in- sharepoint-2010-using-visual-st.aspx
[13] http://www.mssharepointtips.com/tip.asp?id=1093&page=2 [14] http://www.youtube.com/watch?v=mFHQYQIMVPk
[15] http://dotnet.dzone.com/articles/introduction-unit-testing-net [16] http://www.youtube.com/watch?v=_2O5u9ZDzuM
[17] http://www.heathersolomon.com/blog/articles/controlling-single-web-parts-with-css.aspx
[18] http://social.technet.microsoft.com/wiki/contents/articles/8871.sharepoint-2010-how-to-set-up-
a-development-environment-en-us.aspx
[19] http://blogs.msdn.com/b/kaevans/archive/2010/07/09/sql-server-provider-for-claims-based- authentication-in-sharepoint-2010.aspx
[20] http://blogs.msdn.com/b/bethmassi/archive/2011/02/18/step-by-step-installing-sql-server- management-studio-2008-express-after-visual-studio-2010.aspx
[21] http://msdn.microsoft.com/en-us/library/ff769953.aspx
[22] SharePoint 2010 Development with Visual Studio 2010, Eric Carter, Boris Scholl, Peter Jausovec ISBN-13: 978-0-321-71831-0, ISBN-10: 0-321-71831-3
[23] http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx [24] IT Department, VIA University College, Aarhus Denmark
[25] https://studienet.viauc.dk/
Appendices APPENDIX A
Name: Create user Account
Intro: Creating an account for the new user Actor: Admin
Pre-condition: The administrator has .NET administration tool running
Post-condition: The admin has created a new user account and assigned a new role for the user Basic Flow:
1. The Admin logins into the .NET Administration Tool.
2. The Admin clicks the “Security” Tab.
3. The Admin clicks “Create user”.
4. The Admin assigns a username for the User in the username field.
5. The Admin assigns a password for the User in the password field.
6. The Admin re-enters the previously typed password in the confirm password field.
7. The Admin assigns an email for the User in the email field.
8. The Admin assigns a role for the User.
9. The Admin clicks on the “Create User” button.
Alternative flows:
A6.1: If the password typed the second time does not match the one entered first time, the confirm password field displays error, when clicking on the Create button.
Name: Delete user account
Intro: Deletes an account from the system Actor: Admin
Pre-condition: The administrator has .NET administration tool running Post-condition: The user’s account is deleted from the system
Basic Flow:
1. The Admin logins into the .NET Administration Tool.
2. The Admin clicks the “Security” Tab.
3. The Admin clicks “Manage user”.
4. The Admin clicks on “Delete user”.
5. The Admin chooses “Yes” to delete the User.
Alternative flows:
A4.1: If the user clicks on the “No” button when asked if the Owner is sure about deleting the
account (step 4 of the basic flow), the account is not deleted.
Name: Log in on an account
Intro: Log the Admin/User on his account Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in Basic Flow:
1. The Admin/User enters his username in the username field 2. The Admin/User enters his password in the password field 3. The Admin/User clicks on the “Log in” button
4. The Admin/User is logged in onto his account and the default site is displayed
Alternative flows: A4.1: If the password inserted is incorrect, the “Wrong credentials” message is displayed
Name: Log out of an account
Intro: Log the User out of the account Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an logged in Post-condition: Admin/User is logged out of the account
Basic Flow:
1. The Admin/User clicks “Log out” field in the menu 2. The Admin/User is logged out of his account
Name: Add announcement
Intro: The Admin/User adds an announcement Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system
Post-condition: Admin/User is logged in Basic Flow:
1. The Admin/User clicks “Add new Item” button a. A dialog box appears
2. The Admin/User enters the “Title” in the title field
3. The Admin/User enters the “Description” in the description field
4. The Admin/User enters the “Expire Date” in the expire date field
5. The Admin/User choses the “Department” in the department box
Name: Add Company News Intro: The Admin/User adds news Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in Basic Flow:
1. The Admin/User clicks “Add new Item” button a. A dialog box appears.
2. The Admin/User enters the “Tile” in the title field 3. The Admin/User enters the “Body” in the body field
4. The Admin/User clicks the “Save Button” and the news is added.
a. Dialog box disappear
Alternative flows: A2.1: If the “Title” is not entered the “You must specify a value for this required field” is displayed
Name: Add Information
Intro: The Admin/User adds information Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system
Post-condition: Admin/User is logged in Basic Flow:
1. The Admin/User clicks “Add new Item” button a. A dialog box appears
2. The Admin/User enters the “Tile” in the title field 3. The Admin/User enters the “Body” in the body field
4. The Admin/User clicks the “Save Button” and the news is added.
a. Dialog box disappear
Alternative flows: A2.1: If the “Title” is not entered the “You must specify a value for this
required field” is displayed.
Name: Add Discussion
Intro: The Admin/User adds discussion Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User clicks “Add new Item” button.
a. A dialog box appears.
2. The Admin/User enters the “Subject” in the title field 3. The Admin/User enters the “Body” in the body field
4. The Admin/User clicks the “Save Button” and the news is added.
a. Dialog box disappear
Alternative flows: A2.1: If the “Subject” is not entered the “You must specify a value for this required field” is displayed.
Name: View Quick Links
Intro: The Admin/User View the link Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User clicks “Quick Link” link a. New Window appears
Name: View Department
Intro: The Admin/User enters a new department Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User choses one department
a. New site appears
Name: Delete Announcement
Intro: The Admin/User deletes announcement Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses an announcement in the check box.
2. The Admin/User selects from the drop down menu “delete”.
3. The announcement is deleted.
Name: Delete Company News Intro: The Admin/User deletes a news Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses news in the check box.
2. The Admin/User selects from the drop down box menu “delete”.
3. The news is deleted.
Name: Delete Information
Intro: The Admin/User deletes information Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses information in the check box.
2. The Admin/User selects from the drop box down menu “delete”.
3. The information is deleted.
Name: Delete Discussion
Intro: The Admin/User deletes discussion Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses discussion in the check box.
2. The Admin/User selects from the drop down box menu “delete”.
3. The discussion is deleted.
Name: Edit Announcement
Intro: The Admin/User Edits announcement Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses discussion in the check box.
2. The Admin/User clicks selects from the drop down box “edit”.
a. A dialog box appears.
3. The Admin/User enters makes an edit in the announcement.
4. The User clicks save button.
a. Dialog box disappear
Name: Edit Company News Intro: The Admin/User Edit news Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses news in the check box.
2. The Admin/User clicks selects from the drop down box “edit”.
a. A dialog box appears.
Name: Edit Information
Intro: The Admin/User Edit information Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses information in the check box.
2. The Admin/User clicks selects from the drop down box “edit”.
a. A dialog box appears.
3. The Admin/User enters makes an edit in the information.
4. The User clicks save button.
a. Dialog box disappear
Name: Edit Discussion
Intro: The Admin/User Edit discussion Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the Admin/User has an account registered on the system.
Post-condition: Admin/User is logged in.
Basic Flow:
1. The Admin/User chooses discussion in the check box.
2. The Admin/User clicks selects from the drop down box “edit”.
a. A dialog box appears.
3. The Admin/User enters makes an edit in the discussion.
4. The User clicks save button.
a. Dialog box disappear
Name: Add Post
Intro: The user adds post Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks “Add new Item” button a. A dialog box appears
2. The User enters the “Title” in the text field 3. The User enters the “Body” in the text field 4. The User adds “Category”
5. The User choses when published
6. The User clicks the “Publish” and the post is added.
a. Dialog box disappear Alternative flows:
A2.1: If the “Title” is not entered the “You must specify a value for this required field” is displayed
A5.1: If the “Published” is not entered the “You must specify a value for this required field” is displayed
Name: Edit Post
Intro: The user edit post Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a post
2. The user choses from the drop down menu “Edit”
a. A dialog box appears 3. The User edit the post
4. The User clicks the “Publish” and the post is edited.
a. Dialog box disappear
Name: Delete Post
Intro: The user deletes post Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a post
2. The user choses from the drop down menu “Delete”
a. A dialog box appears
3. The User clicks the “Ok” button and the post is deleted.
a. Dialog box disappear
Name: Add Category
Intro: The user adds category Actor: Admin/User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks “Add new Item” button a. A dialog box appears
2. The User enters the “Title” in the text field
3. The User clicks the “Save” button and the category is added.
a. Dialog box disappear
Name: Edit Category
Intro: The user edit category Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a Category
2. The user choses from the drop down menu “Edit”
a. A dialog box appears 3. The User edit the category
4. The User clicks the “Save” button and the category is edited.
a. Dialog box disappear
Name: Delete Category
Intro: The user deletes category Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a category
2. The user choses from the drop down menu “Delete”
a. A dialog box appears
3. The User clicks the “Ok” button and the category is deleted.
a. Dialog box disappear
Name: Add Comment
Intro: The user adds a comment to the a blog Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks “Comment” button a. A new page appears
2. The User enters the “Title” in the text field 3. The User enters the “Body” in the text field
4. The User clicks the “Submit Comment” button and the comment is submitted.
Alternative flows:
A3.1: If the “Body” is not entered the “You must specify a value for this required field” is
displayed
Name: Edit Comment
Intro: The user edit comment Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a comment
2. The user choses from the drop down menu “Edit”
a. A dialog box appears 3. The User edits the comment
4. The User clicks the “Submit Comment” button and the comment is edited.
a. Dialog box disappear
Name: Delete Comment
Intro: The user deletes comment Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a comment
2. The user choses from the drop down menu “Delete”
a. A dialog box appears
3. The User clicks the “Ok” button and the comment is deleted.
a. Dialog box disappear
Name: Add Document
Intro: The user adds document Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks the “Add new item”.
a. A dialog box appears
2. The User clicks “Browse” to browse for a document.
3. The User clicks the “Ok” and the document is added.
a. Dialog box disappear
Name: Delete Document
Intro: The user deletes document Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a document
2. The user choses from the drop down menu “Delete”
a. A dialog box appears
3. The User clicks “Ok” and document deleted a. Dialog box disappear
Name: Add Contact
Intro: The user adds contact Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks the “Add new item”.
a. A dialog box appears
2. The User enters “Last Name” in the text field.
3. The User enters “First Name” in the text field.
4. The User enters “Full Name” in the text field.
5. The User enters “E-mail Address” in the text field.
6. The User enters “Company” in the text field.
7. The User enters “Job Title” in the text field.
8. The User enters “Business Phone” in the text field.
9. The User enters “Home Phone” in the text field.
10. The User enters “Mobile Number” in the text field.
11. The User enters “Fax Number” in the text field.
12. The User enters “Address” in the text field.
13. The User enters “City” in the text field.
14. The User enters “State/Province” in the text field.
15. The User enters “ZIP/Postal Code” in the text field.
16. The User enters “Country/Region” in the text field.
17. The User enters “Web Page” in the text field.
18. The User enters “Notes” in the text field.
Name: Edit Contact
Intro: The user edit contact Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a contact
2. The user choses from the drop down menu “Edit”
a. A dialog box appears 3. The User edits the contact
4. The User clicks the “Save” button and the contact is edited.
a. Dialog box disappear
Name: Delete Contact
Intro: The user deletes contact Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses a contact
2. The user choses from the drop down menu “Delete”
a. A dialog box appears
3. The User clicks “Ok” and contact is deleted a. Dialog box disappear
Name: Add Event to Calendar Intro: The user adds an event Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User clicks the “Add” button.
a. A dialog box appears
2. The User enters “Title” in the text field.
3. The User enters “Location” in the text field.
4. The User choses “Start Time”.
5. The User choses “End Time”.
6. The User enters “Description” in the text field.
7. The User choses “Category”.
8. The User checks the “All Day Event” box if needed.
10. The User checks “Workspace” box if needed.
11. The User clicks the “Save” button and the event is added.
a. Dialog box disappear Alternative flows:
A2.1: If the “Title” is not entered the “You must specify a value for this required field” is displayed
A4.1: If the “Start Time” is not entered the “You must specify a value for this required field” is displayed
A5.1: If the “End Time” is not entered the “You must specify a value for this required field” is displayed
Name: Edit Event
Intro: The user edit the event Actor: User
Pre-condition: The SharePoint Site has been started and the user has an account registered on the system
Post-condition: User is logged in Basic Flow:
1. The User choses an event
2. The user double clicks the event”
a. A dialog box appears 3. The User clicks the “Edit” button 4. The user edit the event
5. The User clicks the “Save” button and the event is edited.
a. Dialog box disappear
APPENDIX B
Web performance test of the Main Site.
This is the result of our Performance test in URL of the Main Site.
System testing
Case Description Expected result T/F
C1 Log in to the system Main site will appear. T
C2 Sign out from the system Log in page will appear T C3 Clicking one of the
departments in the main site
New site will appear for the chosen department.
T C4 Add Announcement Dialog box will appear; where
user can fell the fields and click save, dialog box disappear.
T
C5 Edit Announcement Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C6 Delete Announcement Dialog box will appear; where user can click Ok, dialog box disappear.
T
click save, dialog box disappear.
C8 Edit Company News Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C9 Delete Company News Dialog box will appear; where user can click Ok, dialog box disappear.
T
C10 Add Information Dialog box will appear; where user can fell the fields and click save, dialog box disappear.
T
C11 Edit Information Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C12 Delete Information Dialog box will appear; where user can click Ok, dialog box disappear.
T
C13 Add Discussion Dialog box will appear; where user can fell the fields and click save, dialog box disappear.
T
C14 Edit Discussion Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C15 Delete Discussion Dialog box will appear; where user can click Ok, dialog box disappear.
T
C16 View links New site will appear T
C17 Add Post to the Company Blog
Dialog box will appear; where user can fell the fields and click publish, dialog box disappear.
T
C18 Edit Post Dialog box will appear; where
user can edit the fields and click save, dialog box disappear.
T
C19 Delete Post Dialog box will appear; where T
click save, dialog box disappear.
C22 Delete Category Dialog box will appear; where user can click Ok, dialog box disappear.
T
C23 Add Comment Adding comment to the
selected Post
T C24 Edit Comment Dialog box will appear; where
user can edit the fields and click save, dialog box disappear.
T
C25 Delete Comment Dialog box will appear; where user can click Ok, dialog box disappear.
T
C26 Share a document Uploading a document to the Shared document site
T
C27 Delete Document Deletes the document T
C28 Add Contact Dialog box will appear; where user can fell the fields and click save, dialog box disappear.
T
C29 Edit Contact Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C30 Delete Contact Dialog box will appear; where user can click Ok, dialog box disappear.
T
C31 Add Event to Calendar Dialog box will appear; where user can fell the fields and click save, dialog box disappear.
T
C32 Edit Event Dialog box will appear; where user can edit the fields and click save, dialog box disappear.
T
C33 Human Resources Link Site will appear T
C34 Sales Link Site will appear T
C35 Finance Link Site will appear T
C36 Marketing Link Site will appear T
C37 I.T Department Link Site will appear T
APPENDIX C
4
