Scribd
Upload
14 views5 pages

Confirming Server Specifications

The document outlines the process of confirming server specifications with a client, emphasizing the importance of validating project information and client needs. It details the requirements that need to be documented, including business objectives, IT infrastructure, and functional specifications. Additionally, it highlights technical requirements such as hardware, software, security, and backup policies necessary for the server's operation.

Uploaded by

melaku Sabure
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
14 views5 pages

Confirming Server Specifications

The document outlines the process of confirming server specifications with a client, emphasizing the importance of validating project information and client needs. It details the requirements that need to be documented, including business objectives, IT infrastructure, and functional specifications. Additionally, it highlights technical requirements such as hardware, software, security, and backup policies necessary for the server's operation.

Uploaded by

melaku Sabure
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Confirm Server Specification

A network server is a computer designed to process requests and deliver data to other (client)
computers over a local network or the Internet.
Confirm server design with client

 The first step in building and configuring a server is to confirm that the information about the
project is correct, current and that the client agrees with documented specifications and
design.
 How it will function with the remaining IT infrastructure, and the required configuration.

Requirements issues
 One of the first and most important activities to get on when confirming server specifications
is to confirm client needs and to ensure that they acknowledge that requirements have been
captured correctly
 So one of the tasks in confirming client needs is to document the requirements.
• The business case • Maintenance and backup
requirements
• What the client considers the project’s
main objectives are, including the • Bandwidth issues that may affect the
services that are to be performed project

• What IT infrastructure is already in place • Role definition of parties involved


• Basic specifications • The nature of the data (eg text,
multimedia)

• Conflicting or overlapping requirements


• Security needs (eg levels of user
access and privileges)
• Available support resources & costing
Functional requirements specification

 The functional specification describes what the system will do, as opposed to how it will be
done. This distinction is important because

 The client may not be interested in the details of how a function is implemented, and the
technical details may simply cause confusion for the client

 The implementation details may need to change during the design and development of the
project

 You don’t want to have to negotiate changes to the functional specification just to change
details of implementation

 The technical specification for large projects will be detailed in a separate document, and you
should not entangle one with the other.
Technical requirements

What types of computers/operating systems will the users operate?

Are their desktops all the same?

What bandwidth restrictions occur presently?

What security (login) will they need?

What backup policies need to be in place?

Who will have administration rights?

What will the business do if the system fails at any stage?

What does management expect the system will do and won’t do?
Identify specifications

Hardware

Software

Stages:- A project is divided into many stages

You might also like