Creating a web-portal

Creating a web-portal is hard and time-consuming. Before asking us for a price estimate, you should give us a description of functional requirements, non-functional requirements, graphic interface requirements and a web-portal’s budget. This is done so that we could advise you where to widen and where to simplify or even cut off the functional parts, all according to your budget..

Web-portal creation consists of the following steps:

1. Web-portal functional requirements description.
2. Web-portal non-functional requirements description.
3. Graphic interface requirements description.
4. Making a initial price quotation.
5. Making a technical project of the web-portal.
6. Making a detailed price quotation.
7. Designing the web-portal.
8. Testing the web-portal.
9. Project commissioning.
10. Providing a hosting and maintenance for a web-portal.
11. Web-portal advertising.

1. Web-portal functional requirements description.

You can describe the functional requirements of a web-portal with business use case or with the regular description of what the system has to do. It’s also necessary to inform us about the number of languages the web portal will be in.

For example:

- When you push the “register” button, the “register” field must appear, with various spaces, some of which are marked “necessary to fill”, while others may be left unfilled.
- When you send a correctly filled registration field, a user profile must be created and his/her name and e-mail added to newsletter module; the message with the text confirming the registration must be sent to the aforementioned e-mail.

The whole web portal functional must be described this way.

2. Web portal non-functional requirements description

The non-functional requirements are:

- security requirements (using SSL certificates, HTTPS, protection from the SQL injections, XSS and the rest)
- fault tolerance requirements
- documentation requirements (code comments, PHPdoc, UML architecture documentation).
- limitations (maximum number of users, maximum number of merchandise and such)

3. Graphic interface requirements description.

Graphic interface requirements description is necessary for the sole reason of making the web portal eye-catching and just the way you see it. Though it also affects what browser types and versions will the web portal work on.

The graphic interface requirements are:

- requirement for a website design creating
- logotype creating requirements
- banner creating requirements

4. Making an initial price quotation.

We only can give you an approximate price quotation on this stage, based on the data you’ve given us. The accuracy of an offer given depends only on how thoroughly you have detailed all the functional requirements of a web portal. If the expected price for the web portal is over your budget, then we can always offer you something cheaper or simply cut down on the functional requirements.

5. Making a technical project of the web-portal

Before making a final price quotation and get to work on a web portal, we have to meet you for a more detailed discussion on the functional requirements of the web portal and consultations on possible improvements.
Making a technical project of the web-portal is a pay service.

Making a technical project of the web portal includes:

   - target group and project aims.
   - detailed description of functional requirements.
   - description of non-functional requirements.
   - web portal graphic interface requirements.
   - integrated addons.
   - server settings requirements.
   - using technologies.

6. Making a detailed price quotation.

At this point we can be sure we know what you need and so we can offer you a detailed price quotation and get to work on the web portal.

7. Designing the web portal.

At this point, our designers and programmers make the ideas you’ve settled on a reality (all that done, of course, based on a technical project).

Web-portal designing consists of the following stages:

- creating a preliminary sample of the web portal design.
- getting a clients approval on the aforementioned design.
- making a main web portal design.
- programming.
- web portal modules and components proofing.

8. Web portal testing.

During this stage the testing of a portal is commenced, everything is tested to make sure it works without any errors. All found errors and oversights are quickly fixed.

9. Finishing the project.

We offer the client URLs to the website and the administrative section of the web portal, where he can become acquainted with it and check the web page for himself, as well as to make sure it corresponds to the aforementioned technical project. Later on we can teach the client to use the administrative section of the web portal.

10. Providing a hosting and maintenance for a web portal

Read more

11. Web portal advertising

Read more