Determine hardware and software requirements project server 2010

However, because the SQL Server tier will be the bottleneck, you may find that this constrains your ability to scale out to additional front-end web and Application servers. If data load is the bottleneck, you may find that additional front-end web and Application servers do not produce an improvement in throughput. For a large data set, we recommend that you invest in additional resources on the SQL Server tier of your topology. The following are the minimum and recommended specifications for the SQL Server tier of a large dataset topology.

This section describes the software requirements for Project Server This includes the following:. SharePoint Server and Project Server are available only in bit editions, and they require bit editions of Windows Server R2 or Windows Server Project Server requires the following Windows Server server roles on each Application server in the farm:.

In addition to these server roles, Project Server also requires that Microsoft PowerShell be enabled. Both the server roles and Microsoft PowerShell are configured automatically by the SharePoint Server prerequisite installation tool if they are not already enabled.

Project Server runs as a SharePoint Server service application. For more information about SharePoint Server hardware and software requirements, see Hardware and software requirements SharePoint The following table describes software requirements for use of specific Project Server features that you may want to use.

When you are planning system requirements for Project Server , you must also consider hardware and software requirements for the client users who need to connect to the server. These client users include the following:. If you plan to upgrade from an earlier version of Project Server, you must consider whether your current Project Professional clients will be compatible with Project Server Project Server does not provide a "backward compatibility" connectivity feature for any previous Project Professional client versions.

For more information about Project Professional requirements, see Microsoft Project Professional Project for Office is a subscription-based online offering of Project Professional through Office Project for Office has the same system installation requirements as Project Professional. For Project Web App in Project Server , you can use any of the following supported web browsers:.

Please try again later or contact support. If you contact support, please provide these details. Underlying error code: Table: Business Sector. Underlying error message: AnalysisServices: A connection cannot be made.

Ensure that the server is running. DataSourcePath: This is the home page of e-Administration of computer labs. Through this page, students, tech staff, and nontech staff can access information pertaining to different labs. The reason behind testing was to find errors. Every program or software has errors in it, against the common view that there are no errors in it if the program or software is working.

Executing the programs with the intention of finding the errors in it is therefore testing; hence a successful test is one which finds errors. Testing is an activity, however, it is restricted to being performed after the development phase is complete, but is carried parallel with all stages of system development, starting with requirement specification.

Test cases were devised with a purpose in mind. A test case is a set of data that a system will process as normal input. The software units developed in the system are modules and routines that are assembled and integrated to perform the required function of the system.

Test results once gathered and evaluated, provide a qualitative indication of the software quality and reliability and serve as the basis for design modification if required. In this phase, testing is done at different levels. Actually testing phase of the implementations works accurately and efficiently before live operation commences.

Unit testing was done after the coding phase. The purpose of the unit testing was to locate errors in the current module, independent of the other modules. Some changes in the coding were done during the testing phase. Finally, all the modules were individually tested following bottom to top approach, starting with the smallest and lowest modules and then testing one at a time. This method of software testing tests the functionality of an application as opposed to its internal structures or working i.

Test cases are built to specifications and requirements, i. It uses external descriptions of the software, including specifications, requirements, and design to derive test cases. These tests can be functional or non-functional, though usually functional. The test designer selects valid and invalid inputs and determines the correct output.

This method of software testing tests internal structures or workings of an application, as opposed to its functionality i. In white-box testing, an internal perspective of the system, as well as programming skills, are required and used to design test cases. The tester chooses inputs to exercise paths through the code and determine the appropriate outputs. Once the unit was over, all the modules were integrated for integration testing.

External and internal interfaces are implemented and work as per design, the performance of the module is not degraded. At the culmination of integration testing, the software is said to be completely assembled as a package; interfacing errors have been uncovered and corrected. Then as a final series of software test, validation tests were carried out.

This is the final stage in the testing process before the system is accepted for operational use. Any requirement problem or requirement definition problem revealed from acceptance testing are considered and made error free. It eases the tasks of the administrator, instructors, technical staff, HODs of various departments and students.

The administrator creates different users and assigns specific privileges to users. He is responsible for handling most of the tasks such as extra lab requests, assigning tasks to instructors, etc.

Here the user lodges a complaint about improper functioning of the lab equipment. This complaint will be automatically assigned to technical staff based on the nature of the problem. The instructor maintains the documentation of software, hardware and also reports the condition of equipment to the admin.

He also gets alerts via SMS about the warranty or expiry of the product, if it is outdated. HODs of the various departments can also send a request for the extra lab. For Self disposal and decision-maker for delegated disposal enrollment signifiers, the information Fields must be blank on the first burden of the signifier.

The system will non auto-generate usernames for decision-makers for delegated disposal. When the web site user receives the invitation electronic mail and clicks the URL to lade the enrollment signifier, the username on the signifier will be pre-populated and not-editable. Auto-complete must be set to murder. Password and replies to security inquiries must be obscured. The username can non be an email reference. The website user must put up 4 security inquiries, of which 2 will be indiscriminately shown during future hallmark procedures.

Security replies must non: Be clean; Repeat replies across the inquiries; Be an individual figure or character replies. The replies to the security inquiries will be a minimal 3 alphameric characters, with a maximal 20 alphameric characters and must non incorporate the undermentioned particular.

The format of the username will be a minimal 6 alphameric characters, with an upper limit of 20 alphameric characters and must non incorporate the undermentioned particular. The format of the watchword will be a minimal 8 alphameric characters, with an upper limit of 20 alphameric characters and must be instance sensitive.

Provide registered and logged in website users with self disposal capableness to alter their generic security inside information. A website user will non be able to amend the username. The system must direct an electronic mail to the registered web site user when an amendment has been made to their inside information. The electronic mail must province which inside information has been amended, but on what the inside information has been changed from or to.

If the web site user has amended their electronic mail reference, the system must direct an electronic mail to the old and new electronic mail references advising of the amendment. Provide decision-makers with delegated disposal capableness to make history for external web site users. Provide decision-makers with the ability to advise website users of their enrollment inside information via an invitation electronic mail.