Intranet Website Solution Based on Microsoft SharePoint Server Foundation 2010

Transcription

1 December 14, 2012 Authors: Wilmer Entena Supervisor: Henrik Kronborg Pedersen VIA University College, Horsens Denmark ICT Engineering Department

2 Table of Contents List of Figures and Tables... 3 Abstract Introduction SharePoint Architecture Intranet Solution Site System Specification Use Case Model Activity Diagram Site Planning Web Parts Departments Web Part Company News Web Part Announcements Web Part Discussion Board Web Part Information Web Part Quick Links Web Part Login Page and Authentication Main Site Masterpage Main Site Default Page Department Sub Sites Shared Documents Calendar Contact List Company Blog Testing Results Discussion Conclusion References

3 Appendices APPENDIX A APPENDIX B APPENDIX C List of Figures and Tables Figure 2.1 SharePoint Architecture Diagram... 7 Figure Use Case Diagram Figure Activity Diagram for User Login Figure Activity Diagram for Adding Discussion Figure 5.1 Rootsite and Subsites Figure Code location for Department s web part in Project Solution Figure Departments Web Part View Figure The code for Department s Web Part Figure Code location for Company News web part in Project Solution Figure Company News Web Part View Figure The code for Company s Web Part Figure Code location for Announcements web part in Project Solution Figure Announcements Web Part View Figure The code for Announcements Web Part Figure Code location for Discussion Board web part in Project Solution Figure Discussion Board Web Part View Figure The code for Discussion Board Web Part Figure Code location for Information web part in Project Solution Figure Information Web Part View Figure The code for Information Web Part Figure Code location for Quick Links web part in Project Solution Figure Quick Links Web Part View Figure The code Quick Links Web Part Figure 7.1 Login and Authentication Flow Diagram Figure 7.2 Token and Claims

4 Figure 8.1 Main Site Default Page View Figure Location of the Masterpage in Project Solution Figure Masterpage Layout Figure 8.1 Main Site Default Page WebPartZone with codes Figure 9.1 Department Site s Homepage Interface Figure 9.2 Department s Site Location in Project Solution Figure 10.1 Dialog box for Uploading Files and Documents Figure 11.1 Site s Calendar View Figure 12.1 Contact List View Figure 13.1 Company Blog Interface Table 8.1 Functional Area of SharePoint Main Site

5 Abstract Background: The objective of this study is to provide a company and organization an intranet solution site based on SharePoint 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 system based on SharePoint 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. 5

6 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. 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. 6

7 2. SharePoint 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 Architecture Diagram 7

8 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 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, 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. 8

9 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 Article posted by Abhijit Jana on 3/14/ Mike Flasko - Microsoft Corporation Published: August

10 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 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 10

11 4.2 Activity Diagram Figure Activity Diagram for User Login 11

12 Figure Activity Diagram for Adding Discussion 12

13 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. Figure 5.1 Rootsite and Subsites 13

14 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: Figure Code location for Department s web part in Project Solution 14

15 Figure Departments Web Part View Figure shows the actual layout and design of the department s web part. Consist of five different links to each department s home page. Figure The code for Department s Web Part Figure 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 CSS is also included in the code for the web parts format that point out to the url of the CSS file. 15

16 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: News/AllItems.aspx Figure Code location for Company News web part in Project Solution Figure Company News Web Part View Figure 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. 16

17 Figure The code for Company s Web Part Figure 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: 17

18 Figure Code location for Announcements web part in Project Solution Figure Announcements Web Part View Figure 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. 18

19 Figure The code for Announcements Web Part Figure 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: Board/AllItems.aspx 19

20 Figure Code location for Discussion Board web part in Project Solution Figure Discussion Board Web Part View Figure 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. 20

21 Figure The code for Discussion Board Web Part Figure 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. 21

22 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: Figure Code location for Information web part in Project Solution Figure Information Web Part View Figure 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. 22

23 Figure The code for Information Web Part Figure 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: Links/AllItems.aspx 23

24 Figure Code location for Quick Links web part in Project Solution Figure Quick Links Web Part View Figure 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. 24

25 Figure The code Quick Links Web Part Figure 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. Figure 7.1 Login and Authentication Flow Diagram 25

26 If we look at the figure, we can see that when a user is trying to log in, the application well 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) 26

27 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 Functions Description of Functionality Label 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. D Top Menu The horizontal navigation menu that links to sites other pages and functionalities. E Search Bar The user can search the page using this tool. 27

28 F Help Button Link to Microsoft SharePoint help site. 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: 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 Location of the Masterpage in Project Solution 28

29 Figure Masterpage Layout 8.2 Main Site Default Page 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. Figure 8.1 Main Site Default Page WebPartZone with codes 29

30 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 30

31 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. Figure 11.1 Site s Calendar View 31

32 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 32

33 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 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. 33

34 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 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. 34

35 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. 35

36 References [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] 36

37 [19] [20] [21] [22] SharePoint 2010 Development with Visual Studio 2010, Eric Carter, Boris Scholl, Peter Jausovec ISBN-13: , ISBN-10: [23] [24] IT Department, VIA University College, Aarhus Denmark [25] 37

38 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 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 for the User in the 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 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. 38

39 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 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 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 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 6. The Admin/User enters the Job Title in the job title field 7. The Admin/User clicks the Save Button and the announcement 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 39

40 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 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 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. 40

41 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. 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. 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. 1. The Admin/User choses one department a. New site appears 41

42 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. 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. 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. 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. 42

43 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. 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. 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. 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. 3. The Admin/User enters makes an edit in the news. 4. The User clicks save button. a. Dialog box disappear 43

44 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. 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. 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 44

45 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 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 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 45

46 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 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 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 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 46

47 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 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 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 47

48 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 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 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 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 48

49 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 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 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 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. 19. The User clicks the Save button and the contact is added. a. Dialog box disappear Alternative flows: A2.1: If the Last Name is not entered the You must specify a value for this required field is displayed 49

50 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 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 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 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. 50

51 9. The User checks Recurrence 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 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 51

52 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 New site will appear for the T departments in the main site chosen department. C4 Add Announcement Dialog box will appear; where T user can fell the fields and click save, dialog box disappear. C5 Edit Announcement Dialog box will appear; where T user can edit the fields and click save, dialog box disappear. C6 Delete Announcement Dialog box will appear; where T user can click Ok, dialog box disappear. C7 Add Company News Dialog box will appear; where T 52

53 user can fell the fields and 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. C9 Delete Company News Dialog box will appear; where user can click Ok, dialog box disappear. C10 Add Information Dialog box will appear; where user can fell the fields and click save, dialog box disappear. C11 Edit Information Dialog box will appear; where user can edit the fields and click save, dialog box disappear. C12 Delete Information Dialog box will appear; where user can click Ok, dialog box disappear. C13 Add Discussion Dialog box will appear; where user can fell the fields and click save, dialog box disappear. C14 Edit Discussion Dialog box will appear; where user can edit the fields and click save, dialog box disappear. C15 Delete Discussion Dialog box will appear; where user can click Ok, dialog box disappear. C16 View links New site will appear T C17 Add Post to the Company T Blog Dialog box will appear; where user can fell the fields and click publish, dialog box disappear. C18 Edit Post Dialog box will appear; where user can edit the fields and click save, dialog box disappear. C19 Delete Post Dialog box will appear; where user can click Ok, dialog box disappear. C20 Add Category Adds category to the company T Blog C21 Edit Category Dialog box will appear; where T 53 T T T T T T T T T T

54 user can edit the fields and click save, dialog box disappear. C22 Delete Category Dialog box will appear; where T user can click Ok, dialog box disappear. C23 Add Comment Adding comment to the T selected Post C24 Edit Comment Dialog box will appear; where T user can edit the fields and click save, dialog box disappear. C25 Delete Comment Dialog box will appear; where T user can click Ok, dialog box disappear. C26 Share a document Uploading a document to the T Shared document site C27 Delete Document Deletes the document T C28 Add Contact Dialog box will appear; where T user can fell the fields and click save, dialog box disappear. C29 Edit Contact Dialog box will appear; where T user can edit the fields and click save, dialog box disappear. C30 Delete Contact Dialog box will appear; where T user can click Ok, dialog box disappear. C31 Add Event to Calendar Dialog box will appear; where T user can fell the fields and click save, dialog box disappear. C32 Edit Event Dialog box will appear; where T user can edit the fields and click save, dialog box disappear. 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 54

55 APPENDIX C 4 Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008 Published: May 2010 When you create or customize SharePoint solutions, it is usually best to develop the solution on a local computer where Microsoft SharePoint Server 2010 or Microsoft SharePoint is installed. This article describes how to install a development environment with Microsoft SharePoint 2010 and Microsoft Visual Studio The development environment that you create by using these instructions will not support SharePoint farm installations, and you should not host active production sites with this configuration. These instructions enable you to get started with an environment that is specifically suited to developing SharePoint custom solutions. Step 1: Choose and Preconfigure the Operating System The requirements for a development environment are less stringent and costly than the requirements for a production environment, and the guidelines in this topic do not support a production environment installation. You have several options for preconfiguring the operating system of a local computer on which you will install SharePoint 2010 for development purposes. The choice that you make will be determined by factors specific to your organization and environment (such as budget, the size of your development team, and the operating systems that you and your organization are already using). In any development environment, you should use a computer with an x64-capable CPU, and at least 2 gigabytes (GB) of RAM to install and run SharePoint Foundation; 4 GB of RAM is preferable. You should use a computer with 4 GB of RAM to install and run SharePoint Server; 6 GB to 8 GB of RAM is preferable. Following are the options: Install SharePoint on Windows Server 2008 Service Pack 2 x64 (or Windows Server 2008 R2 x64)

56 Use Microsoft Hyper-V and install SharePoint on a virtual machine running a Windows Server 2008 Service Pack 2 x64 (or Windows Server 2008 R2 x64) guest operating system. Install SharePoint on Windows 7 x64, Windows Vista Service Pack 1 x64, or Windows Vista Service Pack 2 x64. Use Microsoft Hyper-V and install SharePoint on a virtual machine running a Windows 7 x64, Windows Vista Service Pack 1 x64, or Windows Vista Service Pack 2 x64 guest operating system. You must install the WCF Hotfix for Microsoft Windows. The hotfix is available for Windows Server 2008 Service Pack 2, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 and for Windows Server 2008 R2 and Windows 7. If you are using Windows Vista Service Pack 1 or Windows Vista Service Pack 2, install the hotfix for ASP.NET on IIS 7.0 (KB967535). This hotfix, which has already been installed on Windows 7, Windows Server 2008 Service Pack 2, and Windows Server 2008 R2, updates the ASP.NET common language runtime (CLR) to recognize a new option of optimizing compilations. To take advantage of this option, set the optimizecompilations property of the <compilation> tag in your web.config file to true: XML <compilation optimizecompilations="true"> This change significantly improves the initial page load time after you have installed a solution to the bin directory. You must install the ADO.NET Data Services Update for.net Framework 3.5 SP1 to enable REST-based data services. This update is available for Windows Server 2008 Service Pack 2, Windows Vista Service Pack 1, and Windows Vista Service Pack 2 and for Windows Server 2008 R2 and Windows 7. Windows 7 and Windows Vista cannot be used for production deployments of SharePoint If you use Windows 7 or Windows Vista for your development environment, you should have access to a test environment that has the same operating system installed as your production environment. Windows 7 and Windows Vista are recommended only for developer workstations and should be used only for stand-alone installations. You can use a separate Microsoft SQL Server instance, but you should not configure your installation as a SharePoint farm and you should not host active sites on this configuration. 56

57 Step 2: Install the Prerequisites for SharePoint 2010 SharePoint requires your operating system to have certain prerequisites installed before installation begins. For this reason, SharePoint includes a PrerequisiteInstalle.exe tool that installs all of these prerequisites for you. If your developer workstation is set up with the Windows Server 2008 Service Pack 2 or Windows Server 2008 R2 operating system, you can install SharePoint 2010 by running the PrerequisiteInstaller.exe tool (which is included with SharePoint 2010) to install the prerequisites that SharePoint needs, and then run Setup.exe. However, you cannot use PrerequisiteInstaller.exe on Windows 7 or Windows Vista. For those operating systems, you must follow the additional instructions in this section. Because the default installation works only for Windows Server 2008, you must edit one configuration file and install many of the prerequisites manually. You must perform each of the following steps while logged on with an account that has administrator access on the local computer. These steps assume that you received the SharePoint 2010 distribution as a single compressed executable file namedsharepointfoundation.exe for SharePoint and setup.exe for SharePoint Server To set up a developer workstation 1. Copy the SharePointFoundation.exe (or setup.exe) installation file to a folder on the computer where you are installing SharePoint and doing your development, such as in the following path: c:\sharepointfiles 2. Extract the installation files by opening a Command Prompt window, and then typing the following command at the directory location of the folder where you copied the installation files in the previous step. For SharePoint : c:\sharepointfiles\sharepoint /extract:c:\sharepointfiles For SharePoint Server 2010: c:\sharepointfiles\officeserver /extract:c:\sharepointfiles 3. Using a text editor such as Notepad, open the installation configuration file, config.xml, located in the following 57

58 path:c:\sharepointfiles\files\setup\config.xml Add this line inside the <configuration> tag: XML <Setting Id="AllowWindowsClientInstall" Value="True"/> 4. Save the configuration file. 5. Review the complete configuration file. It now looks similar to the following for SharePoint. The complete configuration file will be longer for SharePoint Server 2010 (and therefore the text below cannot replace the contents of that file), but should use the same setting for the AllowWindowsClientInstall attribute. XML <Configuration> <Package Id="sts"> <Setting Id="SETUPTYPE" Value="CLEAN_INSTALL" /> </Package> <DATADIR Value="%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\Data" /> <Logging Type="verbose" Path="%temp%" Template="Microsoft Windows SharePoint Services 4.0 Setup *.log" /> <PIDKEY Value="PIDKey Value" /> <Setting Id="UsingUIInstallMode" Value="1" /> <Setting Id="SETUP_REBOOT" Value="Never" /> <Setting Id="AllowWindowsClientInstall" Value="True"/> </Configuration> All of the text in this configuration file is case-sensitive. If you do not edit the configuration file as described in the previous step or if you do not save the configuration file, when you try to run the installation you see the error message shown in Figure 1. 58

59 Figure 1. Setup is unable to proceed error message 6. If you are using Windows Vista Service Pack 1 or Windows Vista Service Pack 2, you must install the following prerequisites:.net Framework 3.5 SP1 Windows PowerShell 2.0 Windows Installer 4.5 Redistributable 7. If you are using Windows Vista Service Pack 1, Windows Vista Service Pack 2, or Windows 7, install the following additional prerequisites: Microsoft FilterPack 2.0. At a command prompt, type the following: c:\sharepointfiles\prerequisiteinstallerfiles\filterpack\filte rpack.msi Microsoft Sync Framework SQL Server Native Client Windows Identity Foundation (Windows6.1-KB x64.msu) Chart Controls (this is not required if you are going to install SharePoint Foundation 2010). SQL Server Analysis Services - ADOMD.Net (this is not required if you are going to install SharePoint ). 8. Manually enable each of the required Windows Features. You can do this quickly by copying and running the following command in a Command Prompt window. 59

60 9. start /w pkgmgr /iu:iis-webserverrole;iis-webserver;iis- CommonHttpFeatures;^ 10. IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS- HttpErrors;^ 11. IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;^ 12. IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-HealthAndDiagnostics;^ 13. IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS- HttpTracing;IIS-CustomLogging;IIS-ManagementScriptingTools;^ 14. IIS-Security;IIS-BasicAuthentication;IIS- WindowsAuthentication;IIS-DigestAuthentication;^ 15. IIS-RequestFiltering;IIS-Performance;IIS- HttpCompressionStatic;IIS-HttpCompressionDynamic;^ 16. IIS-WebServerManagementTools;IIS-ManagementConsole;IIS- IIS6ManagementCompatibility;^ 17. IIS-Metabase;IIS-WMICompatibility;WAS- WindowsActivationService;WAS-ProcessModel;^ 18. WAS-NetFxEnvironment;WAS-ConfigurationAPI;WCF-HTTP-Activation;^ 19. WCF-NonHTTP-Activation 20. Verify that the required Windows Features are enabled. The command in the previous step enables all of the required features in the Internet Information Services section of the Windows Features dialog box (which you can access through the Programssection in Control Panel). Use Figure 2 and Figure 3 to check that you have enabled all of the required Windows Features. If any features are missing in your operating system, return to the Internet Information Services section of the Windows Featuresdialog box and enable them. 60

61 21. Figure 2. First part of Windows Features list from Windows 7 61

62 22. Figure 3. Second part of Windows Features list from Windows Restart your computer to complete the changes that you made to Windows Features. Step 3: Install SharePoint To install SharePoint Server 2010 or SharePoint, open a Command Prompt window, and then type the following at the command prompt: 2. c:\sharepointfiles\setup.exe 3. Accept the Microsoft Software License Terms. 4. On the Choose the installation you want page, click Standalone to install everything on one developer workstation. 62

63 Figure 4. Installation type choice 5. If any errors occur in the installation, review the log file. To find the log file, open a Command Prompt window, and then type the following commands at the command prompt. The log file is displayed at the end of the directory listing. 6. cd %temp% 7. dir /od *.log 63

64 8. After the installation is complete, you are prompted to start the SharePoint Products and Technologies Configuration Wizard. If you are using a local instance of Microsoft SQL Server 2008, install the Microsoft SQL Server 2008 KB x64 before starting the wizard. If your development environment uses a remote instance of Microsoft SQL Server 2008 or if it has a pre-existing installation of Microsoft SQL Server 2008 on which KB x64 has already been applied, this step is not necessary. With the wizard open, do the following: a. Install SQL Server 2008 KB x64. b. After the Microsoft SQL Server 2008 KB x64 installation is finished, complete the wizard. 9. Alternatively, you can choose not to run the wizard by clearing the SharePoint Products and Technologies Configuration Wizard check box and closing the completed installation dialog box. Install SQL Server 2008 KB x64, and then manually start the SharePoint Products and Technologies Configuration Wizard by opening a Command Prompt window and executing the following command: 10. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN\psconfigui.exe After the configuration wizard is complete, you see the new SharePoint site. Figure 5. New SharePoint site 64