7.2. Functional specifications
Of course the platform must be accompanied by a database.
Which database should be updated automatically from the forms of the portal.
And save each item must contain all necessary references to a possible recovery
to be displayed on a page of the site then be modified or deleted view of the
database. This applies to articles, documents and links.
The personal data of users will be protected just as the
transmission of data to the database.
7.3. The software life cycle
Laurent AUDIBERG (2008) defines the life cycle of software as
all stages of software development, from conception to its demise. The goal of
such a division is to define intermediate milestones for validation of software
development, that is to say, the compliance of the software with the expressed
needs, and verification of the development process, it is -to say the
appropriateness of the methods implemented.
The origin of this division comes from the fact that the
errors have a higher cost as much as they are detected late in the
implementation process. The life cycle can detect errors earlier and thus to
control the quality of the software, the time of its implementation and the
associated costs.
The software life cycle typically includes at least the
following steps:
- Goal Setting: This step is to define the
purpose of the project and its inclusion in a comprehensive strategy.
- Needs analysis and feasibility: that is to
say the phrase, collecting and formalizing requirements of the applicant (the
client) and the set of constraints, and estimate the feasibility of these
requirements.
- Specifications and overall design: This is
the development of specifications of the general architecture of the
software.
- Detailed Design: This step is to clearly
define each subset of the software.
- Coding (implementation or programming): it
is the translation into a programming language features defined during design
phases.
- Unit Testing: They allow you to
individually verify that each subset of the software is implemented according
to specifications.
- Integration: The objective is to ensure
that the interfacing of different components (modules) of the software. It is
the subject of integration testing in a document.
- Qualification (or recipe): That is to say,
the verification of compliance software to the initial specifications.
- Documentation: It aims to produce the
information needed to use the software and further developments.
- Put into production: the deployment
software site.
- Maintenance: It includes all corrective
actions (corrective maintenance) and scalable (scalable maintenance) on the
software.
The sequence and the presence of each of these activities in
the life cycle depend on the choice of a life cycle model between the client
and the development team. The life cycle can take into account the technical,
organizational and human aspects.
7.4. Structure of the web application
Taking into account the objectives of our platform,
architecture and the examples set by other portals of the same type, we have
set up this structure.
USERS SPACE
FORUM CATHEGORYIES
SUGGEST LINKS
SUGGEST DOCUMENT
SUGGEST ARTICLE
LIBRARY
USEFUL LINKS
SUGGEST CONTENT
FORUM
ADMIN
CONTENT SUGGESTED
HOME
INSCRIPTION
UPDATE LINKS
UPDATE ARTICLES
UPDATE DOCUMENT
FORUM SUBJECT
COMMENTS
PRIVATE MESSAGES
USER PROFILE
USERS LIST
Figure 8: Structure of the
application
| 
