MAIN full

7/31/2019 MAIN full

1/81

Hochschule Rosenheim,

University of Applied Sciences

MASTER THESIS

Web Enabled ASEC PMO Support System

Author : Mr. Suneer Subhashchandra Dubal

Registration Number : 719220

First Supervisor : Prof. Dr.-Ing. Reiner Schell

Second supervisor : Prof. Werner Braatz

7/31/2019 MAIN full

2/81

ASEC PMO Support System

2 | P a g e

DECLARATION

I hereby declare that this thesis is my own work and

effort and that it has not been submitted anywhere for any

award. Where other sources of information have been used,

they have been acknowledged.

Name: Suneer Subhashchandra Dubal

Date: 25th July, 2012

7/31/2019 MAIN full

3/81


3 | P a g e

7/31/2019 MAIN full

4/81


4 | P a g e

ABSTRACT

SharePoint Server 2010 is an information portal from Microsoft. It helps

employees, clients and developers communicate and collaborate within the

company. SharePoint lets people share documents and files by storing them in

a central site making cooperation within the company trouble-free.

The focus of the thesis is to implement an Institution wide web based ASEC

Project Management Office (PMO) Support System which provides a

comprehensive solution to manage different activities, tasks handled by

different departments to fulfil their customer needs and Knowledge base and

training requirements. Moreover it provides easy to use interface for external

and internal users based on different permissions and roles with respect to

their departments.

The Site will be used internally and by various groups of users like Head of the

Department, Developers, Support Staff and System Administrators of the

company (ASEC). Each department will have functionality based on their daily

working and will be assign permissions from site to item level as and when

required byASEC PMO Support System itself. Anonymous users will also get

some browsing rights on the Site to view and register themselves as customers

of ASEC and can also browse and demand for different courses.

7/31/2019 MAIN full

5/81


5 | P a g e

ACKNOWLEDGEMENT

I would like to thank my supervisors, Prof. Dr.-Ing. Reiner Schell and Prof.

Werner Braatz, for his support and dedication for reviewing my master thesis.

I would also like to thank my father Dr. Subhash C. Dubal, for his support

during all the time I have been writing this thesis. Also to my mother Niruben

S. Dubal for the personalised recommendation and the encouragement given.

Finally, I would also like to thank to Ms. Minaxi Vasinav, for her patience. Her

invaluable advices have meant a lot to me. Without her support and

encouragement this thesis would probably not be what it is.

7/31/2019 MAIN full

6/81


6 | P a g e

Table of Contents1 Introduction ...................................................................................................................... 14

1.1 Scope ......................................................................................................................... 14

1.1.1 Scope includes ................................................................................................... 15

1.1.2 Scopes excludes ................................................................................................. 16

1.2 Ratified Stakeholders ................................................................................................ 16

1.3 Summary of Key Stakeholder or User Needs ............................................................ 16

1.4 Dependencies ............................................................................................................ 17

1.5 Assumption................................................................................................................ 17

2 Requirement Analysis ....................................................................................................... 19

2.1 General Business Requirement ................................................................................. 19

2.1.1 Product Perspective ........................................................................................... 19

2.1.2 Access Group ...................................................................................................... 20

2.1.3 Access Approval ................................................................................................. 21

2.1.4 Usability ............................................................................................................. 21

2.2 Business Requirement ............................................................................................... 22

2.2.1 Home page ......................................................................................................... 22

2.2.2 Common links on quick launch .......................................................................... 22

2.2.3 FAQ ..................................................................................................................... 23

2.2.4 Trainings ............................................................................................................. 23

2.2.5 Training Materials .............................................................................................. 23

2.2.6 Internal Wiki ....................................................................................................... 24

2.2.7 Various Proposals ............................................................................................... 24

2.3 Non-Functional Requirement.................................................................................... 25

2.3.1 Availability .......................................................................................................... 25

2.3.2 Capability ........................................................................................................... 25

2.3.3 Environment/System Requirements ................................................................. 25

2.3.4 Data Retention ................................................................................................... 25

2.3.5 Performance ...................................................................................................... 26

2.3.6 Scalability ........................................................................................................... 26

7/31/2019 MAIN full

7/81


7 | P a g e

2.3.7 Security Requirements ....................................................................................... 26

3 Technical Details ............................................................................................................... 28

3.1 Technical introduction: ............................................................................................. 28

3.2 Hardware Specification: ............................................................................................ 283.3 Software Specification............................................................................................... 28

3.3.1 OS Components ................................................................................................. 29

3.3.2 Database Components ....................................................................................... 29

3.3.3 SharePoint Specification .................................................................................... 30

3.3.4 Visual Studio Specification ................................................................................. 30

3.3.5 SharePoint Designer Specification ..................................................................... 30

4 Web Application Development ........................................................................................ 32

4.1 Web Application Creation ......................................................................................... 32

4.2 Site Collection ............................................................................................................ 34

4.2.1 Site Collection Creation ..................................................................................... 34

4.3 Lists and Libraries ...................................................................................................... 36

4.3.1 Site Pages ........................................................................................................... 36

4.3.2 Department ........................................................................................................ 36

4.3.3 FAQ ..................................................................................................................... 37

4.3.4 FAQ View ............................................................................................................ 37

4.3.5 Training .............................................................................................................. 38

4.3.6 Training Transactions ......................................................................................... 38

4.3.7 Customer Details ................................................................................................ 39

4.3.8 Customer Queries .............................................................................................. 40

4.3.9 Training Materials .............................................................................................. 40

4.3.10 Wiki Documents ................................................................................................. 41

4.3.11 Wiki Library ........................................................................................................ 41

4.3.12 Proposals ............................................................................................................ 42

4.4 Permissions ............................................................................................................... 43

4.4.1 Site Permissions ................................................................................................. 43

4.4.2 Department Permissions ................................................................................... 43

4.4.3 FAQ Permissions ................................................................................................ 44

4.4.4 Training Permissions .......................................................................................... 44

7/31/2019 MAIN full

8/81


8 | P a g e

4.4.5 Training Transaction Permissions ...................................................................... 44

4.4.6 Customer Details Permissions ........................................................................... 45

4.4.7 Customer Queries Permission ........................................................................... 45

4.4.8 Site Pages Permission ........................................................................................ 464.4.9 Training Material Permission ............................................................................. 46

5 Web parts and Workflows ................................................................................................ 48

5.1 CheckCustomerTrainigForFAQ Web part .................................................................. 48

5.2 Manage FAQ Web page and web part ...................................................................... 50

5.3 Training Trans Permissions Workflow ....................................................................... 51

5.4 FAQ Workflow ........................................................................................................... 52

5.5 Customer query and notification SharePoint Designer workflow ............................ 53

6 Configuring Site to another Computer ............................................................................. 55

6.1 Creating a back-up .................................................................................................... 55

6.2 Restoring a database to other computer .................................................................. 56

6.3 Managing Site Content Database .............................................................................. 58

6.4 Adding a Solution to Web Application ...................................................................... 59

6.5 Configuring Security Settings .................................................................................... 60

6.6 Refresh the Web application ..................................................................................... 61

7 Testing the Site ................................................................................................................. 63

7.1 Anonymous Access: ................................................................................................... 63

7.2 Customer Access: ...................................................................................................... 65

7.3 Support Staff Access: ................................................................................................. 67

7.4 Developer Access: ..................................................................................................... 68

7.5 HOD Access: .............................................................................................................. 70

7.6 Administrator Access: ............................................................................................... 73

8 Conclusion ........................................................................................................................ 75

9 Bibliography ...................................................................................................................... 78

7/31/2019 MAIN full

9/81


9 | P a g e

LIST OFABBREVIATIONS

AdministratorAsean Softech Engineering Centre

Business Resource Development

Central Administration

Enterprise Resource Planning

Frequently Asked Questions

Head Of the Department

Project Management OfficeSystem Development Life Cycle

SharePoint

Sequel Query Language

7/31/2019 MAIN full

10/81


10 | P a g e

LIST OFFIGURES

Figure 1: Manage Web Application ................................................................................. 32

Figure 2: New Button for Creating Web Application ................................................ 33

Figure 3: Create New Web Application Pop-up Window ........................................ 33

Figure 4: Create Site Collection Pop-up Window ....................................................... 34

Figure 5: Blank SharePoint Site .......................................................................................... 35

Figure 6: Check Customer Training For FAQ Web Part ............................................ 48

Figure 7: Check Customer Training For FAQ site view ............................................. 49

Figure 8: Manage FAQ Web page and Web Part ......................................................... 50

Figure 9: Training transaction Permission Workflow Design ................................ 51

Figure 10: Training transaction Permission Workflow Coding ............................. 51

Figure 11: FAQ Workflow Design .................................................................................... 52

Figure 12: FAQ Workflow Coding .................................................................................... 52

Figure 13: Customer Query and Notification ............................................................... 53

Figure 14: Taking backup of SharePoint Database ..................................................... 55

Figure 15: Restoring database to another computer .................................................. 56

Figure 16: Filling General information of the Database Restore ............................ 56

Figure 17: Setting Restore Database Properties ............................................................ 57

Figure 18: add a content database to a Web Application (SharePoint Site) ....... 58

Figure 19: Deploy.bat file code .......................................................................................... 59

Figure 20: Successful Deploy of the ***.WSP files........................................................ 59

7/31/2019 MAIN full

11/81


11 | P a g e

Figure 21: using web application as a System Account ............................................ 60

Figure 22: ASEC PMO Support System--> Home Page ........................................... 61

Figure 23: Home Page for anonymous user .................................................................. 63

Figure 24: Customer Registration for Anonymous Users ......................................... 64

Figure 25: Various Training Programs offered ............................................................ 64

Figure 26: FAQs for Customer1 ......................................................................................... 65

Figure 27: Customer Query Window .............................................................................. 66

Figure 28: Training Material for Customer1 ................................................................ 66

Figure 29: Support Staff Members read only rights to the Proposals ................... 67

Figure 30: Developers read only access to Manage FAQs ........................................ 68

Figure 31: Developers Contribute access to all training material ......................... 68

Figure 32: Developers access to upload new training Materials ........................... 69

Figure 33: HODs access to add New FAQ Pop-up Window .................................... 70

Figure 34: HODs access to add New Proposal .............................................................. 70

Figure 35: Proposal List view by hodpmo ...................................................................... 71

Figure 36: Proposal View Format ...................................................................................... 71

Figure 37: Adding new training transactions by hodpmo ....................................... 72

Figure 38: HODs access all Training Transactions ..................................................... 72

Figure 39: Administrator User Permissions ................................................................... 73

Figure 40: Administrator Wiki Documents ................................................................... 73

Figure 41: hodpmo Wiki Documents .............................................................................. 73

7/31/2019 MAIN full

12/81


12 | P a g e

LIST OFTABLES

Table 1 : Ratified Stake Holders ......................................................................................... 16

Table 2: Access Group ........................................................................................................... 20

Table 3: Hardware Specification ....................................................................................... 28

Table 4: OS Components ...................................................................................................... 29

Table 5: Database Components .......................................................................................... 29

Table 6: SharePoint Specification ...................................................................................... 30

Table 7: Visual Studio Specification ................................................................................. 30

Table 8: SharePoint Designer Specification ................................................................... 30

7/31/2019 MAIN full

13/81


13 | P a g e

INTRODUCTION

7/31/2019 MAIN full

14/81


14 | P a g e

1 IntroductionThe purpose of this document is to collect, analyze, and define high-level needs and

features of the ASEC PMO Support System. It focuses on the capabilities needed by the

stakeholders and the target users, and why these needs exist. The details of how the

Application ASEC PMO Support System fulfills these needs are detailed in the use-case and

supplementary specifications.

1.1 ScopeThe purpose of this thesis is to implement an Institution wide web based ASEC PMO Support

System which provides a comprehensive solution to manage different activities, tasks

handled by different departments to fulfil their customer needs and Knowledge base and

training requirements. Moreover it provides easy to use interface for external and internal

users based on different permissions and roles with respect to their departments.

The ASEC PMO Support System will be used internally and by various groups of users likeHODs, Developers, Support Staff and System Administrators of ASEC. Each department will

have functionality based on their daily working and will be assign permissions from site to

item level as and when required by PMO system itself. Anonymous users will also get some

browsing rights on PMO system to view and register themselves as customers of ASEC and

browse and demand for different courses.

7/31/2019 MAIN full

15/81


15 | P a g e

The application and process will provide several key business benefits:

Provide better and more accurate way of managing different projects, trainingsand customers.

Set the stage for introducing a more structured training and FAQ process. Provide a centralized application for all level of users. Provide a basis for management decision regarding application development,

Proposals, trainings & FAQs

Due to project timeframe constraints the proposed system will be developed in single

phases, this BRD will document the business requirement/features of phase 1 only of the

project.

1.1.1 Scope includes Ability to manage FAQs with role based access. Ability to logically and interactively capture the customer queries and

feedbacks and manage contents/FAQs accordingly.

Ability to view and register trainings for customer. Real time Update & notification ability to update HODs for customer

queries and alert if not attained in 24 hours.

Integrate & present Online Help

The above highlights the main requirements for Phase 1 of the PMO Support Management

system development project. Section 2 of this document details these requirements,

organizing them as much as possible into functional or logical sub sections.

7/31/2019 MAIN full

16/81


16 | P a g e

1.1.2 Scopes excludesThe following are out of scope for the Phase 1 implementation.

Other Reporting needs and printing needs. Custom Branding and Navigation of SharePoint Site. Data Migration/Mining/Trending capacity Additional Attributes & related Workflows - e.g. Access control attributes,

Course fees payment and external email notifications to customers.

ERPs management for ASEC

1.2 Ratified StakeholdersTable 1 : Ratified Stake Holders

Project/Business Sponsor Asean Softech Engineering Centre,

Vadodara

Project Lead Ms. Minaxi Vaisnav

Business Analysis Suneer Dubal

Developer Suneer Dubal

1.3 Summary of Key Stakeholder or User NeedsThere are currently several existing manual process involved in managing FAQs, queries,

Help, a complex access rights management etc. moreover customers queries and demandsare not maintained properly and replied irregularly or missed. A system which helps

different users to search and manage respected data according to their roles and

registration.

7/31/2019 MAIN full

17/81


17 | P a g e

1.4 Dependencies The system is dependent on users updating /completing any incorrect content after

rollout.

1.5 Assumption Groups and Lists/Libraries/Columns and their types are static names and will not

be changed later.

7/31/2019 MAIN full

18/81


18 | P a g e

Requirement Analysis

7/31/2019 MAIN full

19/81


19 | P a g e

2 Requirement Analysis2.1 General Business RequirementThe general business requirement is to develop an internet and intranet based web solution

that will be ASECs PMO Support system used to add, track and maintain customers,

trainings and documentation online, replacing the manual process currently in use.

Other requirements for this solution other than those explicitly concerning its functionality,

e.g. those relating to security, scalability, performance, archiving, extensibility, etc. are not

documented in this document.

2.1.1 Product PerspectiveThis product is a new application/system to be developed. It is not a component of a larger

system(s) and does not, at this present time interface with other application(s). This productis independent and totally self-contained. However it is intended to replace the current

manual system and it is important that the system is designed to allow future enhancements

and also to integrate smoothly with new interfaces.

7/31/2019 MAIN full

20/81

7/31/2019 MAIN full

21/81


21 | P a g e

demand of HOD a system administrator can give access rights on particular data. While

support staff will have read right majority content and will give proper information to

HODs/other users as and when required. Each customer will have some anonymous access

on site to brose few forms/data to get enquiry or registration, once attended a course he/shecan view/download content for that course/training only.

2.1.3 Access ApprovalAccess to the application PMO Support system shall by departments; each business

department shall have an HOD. All requests to access a Department shall be approved by

System Admin / Owner only on HOD approval.

2.1.4 UsabilityThe proposed system is a web based application, it shall be designed in a user friendly way,

this means that it must be implemented in a user oriented context providing easy to use

inter terms of:

Ease and effectiveness of navigation. Effectiveness of presentation, i.e., the process of adding an item does not take

too long. The add new interface should be interactive and not a long list of

questions in a form, fields should be displayed or not displayed depending on

the questioning logic.

Where possible questions that represent users selections should be displayed

in a way that is does not clutter the page/screen and it is understandable to

user what is needed to be done is completed the question.

Ease of learning, appropriate error messages to inform user of what they aredoing wrong.

Visual hierarchy - all the mandatory fields are identifiable as mandatory.

7/31/2019 MAIN full

22/81


22 | P a g e

2.2 Business RequirementThis section details the business solution for the proposed system at a more granular level. It

also uses use cases where necessary to describe the sequence of interactions between the

user/actor and the system necessary to deliver the solution that satisfies the goal/scope of the

project.

2.2.1 Home pageHome page link Site Pages/Home.aspx is anonymously accessible. Any registered or non-

registered user can access this page.

2.2.2 Common links on quick launch1. FAQ Link:- A link redirecting to listing page of all available FAQs should be shown.

However only registered users should allowed going on page. Anonymous users

should be re-directed back to the home page.

2. Trainings Link:- Training links should also be visible to all users but only should beaccessible to users who are registered and have attended at least one training.

3. Customer Queries:- Customer queries should also be accessible to registered usersfor queries, questions, help etc.

4. Customer Registration:- A link accessible to all users for a new registration form.Where a user can fill details and submit for new customer registration.

7/31/2019 MAIN full

23/81


23 | P a g e

2.2.3 FAQFAQs would be accessible to all registered users.

Customers: Customers who are registered and have attended at least one training. The

department for which customer has attended the training; he/she can view FAQs from that

respective department only. However if a user has attended training of multiple

departments he/she can view FAQs for all those departments.

2.2.4 TrainingsAll trainings should be visible to all users so that registered customers can browse and viewall trainings of all departments.

If he/she is interested to attend any training, they can put a query to the system and based

on available training schedules HOD can put that customer as attendee in to the training

transaction list.

Once added as trainee to any training transaction a customer should then browse the FAQs

and training materials of the department under which he / she has attended the training.

2.2.5 Training MaterialsTraining material should be a common document repository where all departments can

store their training related documents, spreadsheets, presentations, diagrams, snapshots etc.

This repository should also keep track of training for which it has been created and used.

There might be case when a single training scheduled at different years might contain

different course material i.e. MS Office 2000 and MS Office 2010 will have different

course materials and structure.

Training based security should be maintained here also, if a user has attended any training

then only he/she can view respected trainings course material.

Entire document library will be managed by HODs and all documents should be keeping

multiple file versions.

7/31/2019 MAIN full

24/81


24 | P a g e

2.2.6 Internal WikiThis module will be only accessible to HODs. HOD will use this module to manage FAQs

and Trainings.

Here also department wise edit permission should be given to respected HODs, however

they can see other departments FAQs and trainings but they cannot update them.

2.2.7 Various ProposalsASEC maintains different forms layout to keep track of various proposals comes and

demanded to ASEC for any project or training. An HOD of a department verifies the

proposal and can take further action on that proposal. In proposal forms few attributes are

common like company, proposal makers designation etc. but though a proposal maker can

write proposal in enhanced rich text format to include diagrams, figures and tables.

7/31/2019 MAIN full

25/81


25 | P a g e

2.3 Non-Functional Requirement2.3.1 AvailabilityThis subsection specifies the following requirements associated with the time that the

system must available for use. At the moment there are not users accessing the system from

SQL or claims authentication only anonymous or AD users are allowed.

The system shall be available for use 24 hours per day and 7 days per week expect during

maintenance when the downtime period will be communicated users.

2.3.2 Capability

The system shall be able to cater for simultaneous users within the periods

2.3.3 Environment/System Requirements

The system shall be developed on ASECs existing application development

environment/platform and shall comply with existing system & environment requirements.

2.3.4Data Retention

This subsection specifies the following requirements associated with the length of time data

must be retained and requirements for its archival and destruction.

The system shall comply with ASECs data archiving process and policy

7/31/2019 MAIN full

26/81


26 | P a g e

2.3.5 PerformanceThis subsection specifies the following requirements associated with the performance.

Maximum response time of 5 seconds or less for all pages. Is to view page 5s at most for

search

The system shall be an on-line system, which can be viewed using Internet Explorer 7 and

above

The system shall be accessible from any computer connected on ASECs Network

2.3.6 Scalability

The system shall be scalable to accommodate unrestricted growth in the number of users;

attachment size should be limited to 50 MB; however no limit for document size uploaded in

document repository.

2.3.7 Security RequirementsThis subsection documents the security requirements that specify the extent to which the

system shall protect itself against unauthorized access.

The system must comply to ASECs Access Control Policy and Standard

If not in the SDLC process, secure coding techniques must be employed to project the system

against web application vulnerabilities such as SQL injections.

7/31/2019 MAIN full

27/81


27 | P a g e

Technical Details

7/31/2019 MAIN full

28/81


28 | P a g e

3 Technical Details3.1 Technical introduction:

ASEC PMO support system is web based SharePoint site which can be hosted on

any intranet or internet LAN/WAN network which hosts SharePoint Server.

However the site is fundamentally designed to work only with windows

authentication.

3.2 Hardware Specification:This section describes only the specification on which this site was developed and

hosted. However any server supporting SharePoint version also may host this site.

Table 3: Hardware Specification

Processor Intel Core i3 & i52100 3.10 GHz

HDD 500GB

RAM 8 GB

3.3 Software SpecificationThis section also describes different software / programs used to develop this

solution. However any supported software / program with this solution and

compatible version may also support.

7/31/2019 MAIN full

29/81


29 | P a g e

3.3.1 OS ComponentsTable 4: OS Components

Operating System Windows Server 2008 R2 or Windows 7 Ultimate

Operating System Type 64 bit

Operating System Version 6.1.7601 Service Pack 1 build 7601

3.3.2 Database ComponentsTable 5: Database Components

Microsoft SQL Server 2008 R2 Microsoft SQL Server 2008 (SP1) -

10.0.2531.0 (X64) Express Edition

(64-bit) on Windows NT 6.1

(Build 7601: Service Pack 1)

Microsoft SQL Server Management Studio 10.50.1617.0

Microsoft Analysis Services Client Tools 10.50.1617.0

Microsoft Data Access Components(MDAC)

6.1.7601.17514

Microsoft MSXML 3.0 6.0

Microsoft Internet Explorer 9.0.8112.16421

Microsoft .NET Framework 2.0.50727.5456

7/31/2019 MAIN full

30/81


30 | P a g e

3.3.3 SharePoint SpecificationTable 6: SharePoint Specification

Microsoft SharePoint Foundation 2010 14.0.6029.1000

Security Update for Microsoft SharePoint Foundation

2010 (KB2553365) 64-Bit Edition

14.0.6120.5005

Microsoft SharePoint 2010 Service Pack 1 (SP1) 14.0.6029.1000

Microsoft SharePoint Foundation 2010 1033 Lang

Pack

14.0.6029.1000

Update for Microsoft SharePoint Foundation 2010

(KB2553014)

14.0.6106.5000

Microsoft SharePoint Foundation 2010 Core 14.0.6029.1000


2010 (KB2553365) 64-Bit Edition

14.0.6120.5005


2010 (KB2553413) 64-Bit Edition

14.0.6114.5002 Superseded

3.3.4 Visual Studio SpecificationTable 7: Visual Studio Specification

Component Specification

Microsoft Visual Studio 2010 Professional ENU Version 10.0.40219.1 SP1 Rel

Microsoft .Net Framework Version 4.0.30319 SP1 Rel

Microsoft Visual C# 2010 Require .Net 2.0

Microsoft Visual Web Developer 2010 Require .Net 2.0

Microsoft Visual Studio 2010 Team Explorer Require .Net 2.0

Microsoft Visual Studio 2010 SharePoint Developer

Tools

Require .Net 2.0

3.3.5 SharePoint Designer SpecificationTable 8: SharePoint Designer Specification

Microsoft SharePoint Designer 2010 Version 14.0.6112.5000 (64 bit)

7/31/2019 MAIN full

31/81


31 | P a g e

Web Application

Development

7/31/2019 MAIN full

32/81


32 | P a g e

4 Web Application Development4.1 Web Application Creation

In your Central Administration, go to application management (CA Application

Management), under Web Application heading a link named Manage Web Applications

click on it.

Figure 1: Manage Web Application

This will open manage page for web applications. In top left corner there is option for new

web application. Click on, it will open new web application page with options.

7/31/2019 MAIN full

33/81


33 | P a g e

Figure 2: New Button for Creating Web Application

Figure 3: Create New Web Application Pop-up Window

Choose authentication Classic mode, New IIS website, Port, Authentication Provider =

NTLM, Allow anonymous access = no, SSL = no, new application pool, with a predefined

Network Service and DB name with windows authentication. This will create a new web

application and a new Database in your SharePoint database instance.

7/31/2019 MAIN full

34/81


34 | P a g e

4.2 Site Collection4.2.1 Site Collection Creation

Go to Central Administrator Application Management Under Site Collections

Click on Create Site Collections.

Figure 4: Create Site Collection Pop-up Window

Choose Blank Site template and give title as ASEC PMO Support System.

7/31/2019 MAIN full

35/81


35 | P a g e

Figure 5: Blank SharePoint Site

7/31/2019 MAIN full

36/81


36 | P a g e

4.3 Lists and LibrariesCreated following lists and libraries as specified in tables

4.3.1 Site Pages

Multiple lines of text

Person or Group

Person or Group

Person or Group

4.3.2 Department

Single line of text

Single line of text

Person or Group

Person or Group

Person or Group

7/31/2019 MAIN full

37/81


37 | P a g e

4.3.3 FAQ

Single line of text

Number



Lookup

Person or Group

Person or Group

4.3.4 FAQ ViewCreate FAQ view as below and delete default view created by list.

Question Number 1

Question 2

Answer3

7/31/2019 MAIN full

38/81


38 | P a g e

4.3.5 Training

Single line of text


Lookup

Person or Group

Person or Group

4.3.6 Training Transactions

Single line of text

Lookup

Date and Time

Date and Time

Person or Group

Person or Group

Person or Group

Person or Group

7/31/2019 MAIN full

39/81


39 | P a g e

4.3.7 Customer Details

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text

Single line of text


Single line of text

Single line of text

Single line of text

Single line of text

Hyperlink or Picture


Person or Group

7/31/2019 MAIN full

40/81


40 | P a g e

Person or Group

4.3.8 Customer Queries

Single line of text

Choice



Person or Group

Person or Group

4.3.9 Training Materials

Single line of text


Number

Person or Group

Person or Group

Person or Group

7/31/2019 MAIN full

41/81


41 | P a g e

4.3.10 Wiki Documents

Single line of text

Lookup

Person or Group

Person or Group

Person or Group

4.3.11 Wiki Library

Single line of text

Person or Group

Person or Group

Person or Group

7/31/2019 MAIN full

42/81


42 | P a g e

4.3.12 Proposals

Single line of text

Single line of text

Date and Time

Hyperlink or Picture

Single line of text

Single line of text


Person or Group

Person or Group

7/31/2019 MAIN full

43/81


43 | P a g e

4.4 PermissionsFollowing section shows what permissions are set for site, lists and libraries.

4.4.1 Site Permissions

4.4.2 DepartmentPermissions

7/31/2019 MAIN full

44/81


44 | P a g e

4.4.3 FAQ Permissions

4.4.4 Training Permissions

4.4.5 Training Transaction Permissions

7/31/2019 MAIN full

45/81


45 | P a g e

4.4.6 Customer Details Permissions

4.4.7 Customer Queries Permission

7/31/2019 MAIN full

46/81


46 | P a g e

4.4.8 Site Pages Permission

4.4.9 Training Material Permission

7/31/2019 MAIN full

47/81


47 | P a g e

Web Parts and

Workflows

7/31/2019 MAIN full

48/81


48 | P a g e

5 Web parts and Workflows5.1 CheckCustomerTrainigForFAQ Web partThis web part is created to check if the current user has registered for any training and is a

customer? Or member of any other user group then customer. Based on it web part will

redirect response. This is hidden web part placed on FAQs list view page.

Figure 6: Check Customer Training For FAQ Web Part

7/31/2019 MAIN full

49/81


49 | P a g e

Figure 7: Check Customer Training For FAQ site view

7/31/2019 MAIN full

50/81


50 | P a g e

5.2 Manage FAQ Web page and web partCreate an .aspx page in SharePoint designer into Wiki Library and insert FAQ list view web

part to it and allow inline editing on that web part.

Figure 8: Manage FAQ Web page and Web Part

7/31/2019 MAIN full

51/81


51 | P a g e

5.3 Training Trans Permissions WorkflowThis workflow will assign customers and other users individual item level permission on

training transactions and training materials.

Figure 9: Training transaction Permission Workflow Design

Figure 10: Training transaction Permission Workflow Coding

7/31/2019 MAIN full

52/81


52 | P a g e

5.4 FAQ WorkflowThis workflow will check trainings attended and will assign rights based on it to FAQs to

customers as well as HODs for respective departments. All other users will get read rights.

Figure 11: FAQ Workflow Design

Figure 12: FAQ Workflow Coding

7/31/2019 MAIN full

53/81


53 | P a g e

5.5 Customer query and notification SharePoint Designerworkflow

This workflow will check new customer query and will also check has HOD replied to

query or not. If no reply given it will send two notifications before 2 and 1 hours of 24

hours after new query.

Figure 13: Customer Query and Notification

7/31/2019 MAIN full

54/81


54 | P a g e

Configuring SharePoint

Site to other Computer

7/31/2019 MAIN full

55/81


55 | P a g e

6 Configuring Site to anotherComputer

Assumption: SharePoint Server 2010, SQL Server 2008 R2, Windows Server 2008 R2 data

centre is installed. This configuration is used for developer members and also for the

intranet users of the company.

6.1 Creating a back-upCreate Back-up of SharePoint Site database using SQL Server Management Studio 2008 R2 and save

the file as ASEC_Date_Month_Year.bak. (Done by the Administrator only)

Figure 14: Taking backup of SharePoint Database

7/31/2019 MAIN full

56/81


56 | P a g e

6.2 Restoring a database to other computerRestore the Database in another computer where it has to be configured and give the database

name.

Figure 15: Restoring database to another computer

Figure 16: Filling General information of the Database Restore

7/31/2019 MAIN full

57/81


57 | P a g e

Figure 17: Setting Restore Database Properties

7/31/2019 MAIN full

58/81


58 | P a g e

6.3 Managing Site Content DatabaseNow open the Central Administration as System Account.

Click on Application ManagementOn Database Section Click Manage Content

Databases. Remove the current database (e.g. WSS_Content_1234) of the web application.

Click on add a content database.

Figure 18: add a content database to a Web Application (SharePoint Site)

7/31/2019 MAIN full

59/81


59 | P a g e

6.4 Adding a Solution to Web ApplicationNow add a solution to the Web Application. For this run Command Prompt (as an administrator)

launch file Deploy.bat. After successfully completing click on Central AdministratorSystem

SettingsManage Farm Solutions to check the ***.wsp is successfully deployed or not.

Figure 19: Deploy.bat file code

Figure 20: Successful Deploy of the ***.WSP files

7/31/2019 MAIN full

60/81


60 | P a g e

6.5 Configuring Security SettingsFor that Click on CA Security Users Specify web application user policy.

Click

add users

Select web application and click Next

add users, give permission tofull control, and set account as system account Click Finish.

Figure 21: using web application as a System Account

7/31/2019 MAIN full

61/81


61 | P a g e

6.6 Refresh the Web applicationRefresh web application (e.g. asec:1234/Site Pages/Home.aspx)

Figure 22: ASEC PMO Support System--> Home Page

7/31/2019 MAIN full

62/81


62 | P a g e

Testing the Site

7/31/2019 MAIN full

63/81


63 | P a g e

7 Testing the SiteThe testing is based on the user access rights. From 7.1 to 7.6 the access to the Site increases.

7.1 Anonymous Access:Home page link Site Pages/Home.aspx (here http://asec:1234/Site Pages/Home.aspx) is

anonymously accessible. Any registered or non-registered user can access this page.

Figure 23: Home Page for anonymous user

Anonymous User can also have an access to Customer Registration and Various Training

Details.
http://asec:1234/Sitehttp://asec:1234/Site

7/31/2019 MAIN full

64/81


64 | P a g e

Figure 24: Customer Registration for Anonymous Users

Figure 25: Various Training Programs offered

7/31/2019 MAIN full

65/81


65 | P a g e

7.2 Customer Access:Customers have all access of anonymous user. The department for which customer has

attended the training; he/she can view FAQs from that respective department only.

However if a user has attended training of multiple departments he/she can view FAQs for

all those departments.

Also if a customer has a query, it can be solved by New Query link.

Figure 26: FAQs for Customer1

7/31/2019 MAIN full

66/81


66 | P a g e

Figure 27: Customer Query Window

Customer can view only those training related documents which have been attended by a

customer.

Figure 28: Training Material for Customer1

7/31/2019 MAIN full

67/81


67 | P a g e

7.3 Support Staff Access:Support Staff members have all access of anonymous users and customers except no access

for training material. Additionally support staff members have read only access to the

proposals.

Figure 29: Support Staff Members read only rights to the Proposals

7/31/2019 MAIN full

68/81


68 | P a g e

7.4 Developer Access:Developer Members have all access of Support Staff members. Additionally members have

read only access to all FAQs and contribute access to Training Materials.

Figure 30: Developers read only access to Manage FAQs

Figure 31: Developers Contribute access to all training material

7/31/2019 MAIN full

69/81


69 | P a g e

Figure 32: Developers access to upload new training Materials

7/31/2019 MAIN full

70/81


70 | P a g e

7.5 HOD Access:HODs have all access of Developer Members. Additionally HODs have contributed access to

view training transactions and also to add new training transactions in the list. Moreover

HODs, can add new proposals and Manage FAQ, can contribute Wiki documents. But has

no access to Administrator Only.

Figure 33: HODs access to add New FAQ Pop-up Window

Figure 34: HODs access to add New Proposal

7/31/2019 MAIN full

71/81


71 | P a g e

Figure 35: Proposal List view by hodpmo

Figure 36: Proposal View Format

7/31/2019 MAIN full

72/81


72 | P a g e

Figure 37: Adding new training transactions by hodpmo

Figure 38: HODs access all Training Transactions

7/31/2019 MAIN full

73/81


73 | P a g e

7.6 Administrator Access:Administrator has all access of the SharePoint Site (e.g. ASEC PMO Support System). Only

administrator has access to Wiki document and Manage FAQ. Apart from this User

permission can be arranged only by administrator.

Figure 39: Administrator User Permissions

Figure 40: Administrator Wiki Documents

Figure 41: hodpmo Wiki Documents

7/31/2019 MAIN full

74/81


74 | P a g e

Conclusion

7/31/2019 MAIN full

75/81


75 | P a g e

8 ConclusionThe objective of this thesis is to implement an Institution wide web based ASEC PMO

Support System which provides a comprehensive solution to manage different activities,tasks handled by different departments to fulfil their customer needs and Knowledge base

and training requirements by using SharePoint 2010. SharePoint 2010 is developed in such

user friendly manners that even a person without any technical skills can benefit from it to

the full extent.

The application and process will provide several key business benefits:

Provide better and more accurate way of managing different projects, trainingsand customers.

Set the stage for introducing a more structured training and FAQ process. Provide a centralized application for all level of users. Provide a basis for management decision regarding application development,

Proposals, trainings and FAQs.

During the project, a fictitious example has been created for testing purpose only. The real

implementation will be done by the company administrator.

This product is a new application/system to be developed. It is not a component of a larger

system(s) at this present time. This product is independent and totally self-contained. The

system is designed to allow future enhancements and also to integrate smoothly with new

interfaces.

7/31/2019 MAIN full

76/81


76 | P a g e

The followings are future implementations that will gain company site value to the top most

in the market.

Other Reporting needs and printing needs. Custom Branding and Navigation of SharePoint Site. Data Migration/Mining/Trending capacity Additional Attributes and related Workflows - e.g. Access control attributes,

Course fees payment and external email notifications to customers.

ERPs management for ASEC Groups and Lists/Libraries/Columns and their types are static names that can

be changed later to dynamic needs.

Finally, I would personally recommend Microsoft SharePoint Server 2010 to any extranet

site development as SharePoint has emerged as one of the top extranet solutions that

companies are considering. SharePoint is not only a collaboration website, but a framework

that developers can use to build entire applications. Out of the box, SharePoint includes

document management, search, change notification, and list functionality while

maintaining a high ease of use through its UI customization options. To finish out our

requirements list, all SharePoint content is stored within a SQL Server database, so security

can be well-controlled.

7/31/2019 MAIN full

77/81


77 | P a g e

Bibliography

7/31/2019 MAIN full

78/81


78 | P a g e

9 Bibliography

WRITTEN SOURCE1. Chris Geier; Cathy Dew; Wes Preston; Raymond Mitchell; Becky Bertram; KenSchaefer; Andrew Clark 2011, SharePoint 2010Six-in-One, Wiley Publishing Inc.

2. Charlie Holland 2011, The Complete Reference Microsoft SharePoint 2010 WebApplications, The McGraw-Hill Companies.

3. Dan Holme; Alistair Matthews 2011, MCTS EXAM 70-667 Configuring MicrosoftSharePoint 2010, Microsoft Press.

4. Balaji Kithiganahalli 2011, Microsoft SharePoint 2010 Development with VisualStudio 2010Expert Cookbook, Packt Publishing.

5. Dave Milner 2010, Pro ASP.NET SharePoint 2010 Solutions, Apress.

6. Wictor Wilen 2011, SharePoint 2010 Web Parts in Action, Manning PublicationsCo..

7. Paul J. Galvin; Udayakumar Ethirajulu 2012, Professional Workflow in SharePoint2010Real World Business Workflow Solutions, John Wiley & Sons, Inc.

8. Steven Mann 2011, PowerShell for SharePoint 2010 HowTo, Pearson Education,Inc.

9. Steve Wright; David Petersen 2011, Pro SharePoint Designer 2010, Apress.

7/31/2019 MAIN full

79/81


79 | P a g e

10.Jennifer Mason; Christian Buckley; Brian T. Jackett; Wes Preston 2012, MicrosoftSharePoint 2010 Creating and Implementing Real World Projects, OReilly Media,

Inc. Published with the authorization of Microsoft Corporation

11.Robert Garrett 2011, Pro SharePoint 2010 Administration, Apress.

WEB SOURCE

1. Michael T. Smith, Group By on more than 2 columns in a viewURL: http://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-

2.html, Quoted: 30.01.2011

2. Mohamed Faizal, Step by Step SharePoint Server 2010 Installation GuideURL: http://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-

Installation-G, Quoted: 20.09.2009

3. Microsoft Corporation 2012, Hardware and Software Requirements ofSharePoint Server 2010 URL:http://technet.microsoft.com/en-us/library/cc262485.aspx

,

Quoted: 08.07.2010

4. Michael T. Smith, Create a sub site in a publishing site names WorkflowtasksURL: http://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-

sharepoint.htmlQuoted: 25.03.2012

5. StackExchange Inc., Top Questions on SharePointURL:http://sharepoint.stackexchange.com/ , Quoted: 2012

6. SharePoint Hosting Providera division of Fpweb.net LC, Free SharePoint videotutorials URL:http://www.sharepointhostingprovider.com/sharepoint-tutorials/

Quoted: 1996-2012
http://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-2.htmlhttp://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-2.htmlhttp://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-2.htmlhttp://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-Installation-Ghttp://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-Installation-Ghttp://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-Installation-Ghttp://technet.microsoft.com/en-us/library/cc262485.aspxhttp://technet.microsoft.com/en-us/library/cc262485.aspxhttp://technet.microsoft.com/en-us/library/cc262485.aspxhttp://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-sharepoint.htmlhttp://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-sharepoint.htmlhttp://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-sharepoint.htmlhttp://sharepoint.stackexchange.com/http://sharepoint.stackexchange.com/http://sharepoint.stackexchange.com/http://www.sharepointhostingprovider.com/sharepoint-tutorials/http://www.sharepointhostingprovider.com/sharepoint-tutorials/http://www.sharepointhostingprovider.com/sharepoint-tutorials/http://www.sharepointhostingprovider.com/sharepoint-tutorials/http://sharepoint.stackexchange.com/http://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-sharepoint.htmlhttp://techtrainingnotes.blogspot.in/2012/03/names-you-cant-use-for-sharepoint.htmlhttp://technet.microsoft.com/en-us/library/cc262485.aspxhttp://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-Installation-Ghttp://www.codeproject.com/Articles/44219/Step-by-Step-SharePoint-Server-2010-Installation-Ghttp://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-2.htmlhttp://techtrainingnotes.blogspot.in/2011/01/sharepoint-group-by-on-more-than-2.html

7/31/2019 MAIN full

80/81


80 | P a g e

7. Isha Attlee, SharePoint Programming,URL:http://mysharepointwork.blogspot.in/2010/06/sharepoint-tutorials.html

Quoted: 18.06.2010

8. SharePoint Magazine, SharePoint 2010 Backup and Recovery ConfiguringBackup

URL: http://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-

configuring-backup Quoted: 19.04.2011

9. Microsoft Corporation, Backup and recovery for SharePoint Server 2010URL:http://technet.microsoft.com/en-us/library/ee662536 Quoted: 12.05.2010

10. SharePoint Magazine, Best Practices for SharePoint GroupsURL: http://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groups Quoted: 02.05.2011

11. KC Young, Permissions in SharePoint 2010URL:http://www.sharepointboost.com/blog/permissions-in-sharepoint-2010/

Quoted: 13.07.2011

12. Programming 4 US Administrator, SharePoint 2010: Assign Users Permissionson a Site

URL:http://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%

20Users%E2%80%99%20Permissions%20on%20a%20Site.aspx Quoted: 24.10.2010
http://mysharepointwork.blogspot.in/2010/06/sharepoint-tutorials.htmlhttp://mysharepointwork.blogspot.in/2010/06/sharepoint-tutorials.htmlhttp://mysharepointwork.blogspot.in/2010/06/sharepoint-tutorials.htmlhttp://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-configuring-backuphttp://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-configuring-backuphttp://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-configuring-backuphttp://technet.microsoft.com/en-us/library/ee662536http://technet.microsoft.com/en-us/library/ee662536http://technet.microsoft.com/en-us/library/ee662536http://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groupshttp://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groupshttp://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groupshttp://www.sharepointboost.com/blog/permissions-in-sharepoint-2010/http://www.sharepointboost.com/blog/permissions-in-sharepoint-2010/http://www.sharepointboost.com/blog/permissions-in-sharepoint-2010/http://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://mscerts.programming4.us/sharepoint/SharePoint%202010%20%20%20Assign%20Users%E2%80%99%20Permissions%20on%20a%20Site.aspxhttp://www.sharepointboost.com/blog/permissions-in-sharepoint-2010/http://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groupshttp://sharepointmagazine.net/articles/administrator/best-practices-for-sharepoint-groupshttp://technet.microsoft.com/en-us/library/ee662536http://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-configuring-backuphttp://sharepointmagazine.net/articles/sharepoint-2010-backup-and-recovery-configuring-backuphttp://mysharepointwork.blogspot.in/2010/06/sharepoint-tutorials.html

7/31/2019 MAIN full

81/81


13. Glyn Clough, New Permissions Tools in SharePoint 2010URL:http://www.glynblogs.com/2010/02/new-permissions-tools-in-sharepoint-2010.html

Quoted: 23.02,2010

14. Dotnetguts Administrator, SharePoint 2010 Development TutorialURL:http://dotnetguts.blogspot.in/2010/04/sharepoint-2010-development-tutorial.html

Quoted: 27.04.2010

15. Srikanth Reddy, Webpart Development: Creating Custom Web Part PropertiesURL: http://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-

creating.html Quoted: 08.06.2011

16. Jourdan Laik, Create a Custom Web Part for SharePoint 2010URL: http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-

2010/ Quoted: 09.09.2010
http://www.glynblogs.com/2010/02/new-permissions-tools-in-sharepoint-2010.htmlhttp://www.glynblogs.com/2010/02/new-permissions-tools-in-sharepoint-2010.htmlhttp://www.glynblogs.com/2010/02/new-permissions-tools-in-sharepoint-2010.htmlhttp://dotnetguts.blogspot.in/2010/04/sharepoint-2010-development-tutorial.htmlhttp://dotnetguts.blogspot.in/2010/04/sharepoint-2010-development-tutorial.htmlhttp://dotnetguts.blogspot.in/2010/04/sharepoint-2010-development-tutorial.htmlhttp://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-creating.htmlhttp://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-creating.htmlhttp://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-creating.htmlhttp://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/http://blog.concurrency.com/sharepoint/create-a-custom-web-part-for-sharepoint-2010/http://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-creating.htmlhttp://srikanthmicrosoft.blogspot.in/2011/06/webpart-development-part-creating.htmlhttp://dotnetguts.blogspot.in/2010/04/sharepoint-2010-development-tutorial.htmlhttp://www.glynblogs.com/2010/02/new-permissions-tools-in-sharepoint-2010.html