1. HOW TO BUILD A WEBSITE
USING A CMS
-Proiect Software Project Management-

2. DESCRIPTION
What does CMS stand for?  Content Management System
Getting everything set up properly will be a technically challenging
project, because even the simplest CMS has a lot of complex programming.
There’s a wide variety of different content management systems available, and
the best one to choose for your needs depends on what features you want to
have on your site.
First of all you have to:
talk to client
choose a CMS depending on scope
make it unique and functional

3. DESCRIPTION
After you’ve chosen the best CMS that suits your needs you have to:
-download the copy from the CMS website
-unzip the archive to your local folder
-copy the files to your web server through a FTP program
-create a MySQL database, along with a user(with name and password) to use
the database
-specify the database path, name and the user login and password
-set the CMS settings, strucjture and layout as an admin
After doing the basic steps it’s pure software development.
Designing the looks and functional modules that the client requires involves
following the steps described in the ACTIONS presentation.

4. RESOURCES
Human Resources:
-Project Manager: Ionut Pirvulescu
-Manegement: Ionut Pirvulescu, Iurie Panfilii
-Developers: Ionut Pirvulescu, Iurie Panfilii, Dorin Paunescu, Adrian Bar
-Testers: Ioan Brudariu, Claudiu Badea, Sergiu Vasi
-Trainers: Dorin Paunescu, Marinescu Bogdan, Sergiu Vasi
-Technical Communicators: Ionut Pirvulescu, Dorin Paunescu
-Analysts: Ionut Pirvulescu, Dorin Paunescu
-Deployment team: Dorin Paunescu, Iurie Panfilii

5. RESOURCES
Technical Resources:
Hardware:
- 3 laptops;
- wi-fi router;
- learning board;
- projector;
Software:
- Corel Draw Suite;
- Filezilla;
- Adobe Suite(Dreamweaver, Illustrator, InDesign, After Effects);
Money:
- Client advance
- Sponsorship from CMS module companies

6. CONSTRAINS
In order to exceed our main constrain we intend to code our own modules
with functionalities and build our own template for the site.
The modules can and will be sold to third party companies that may need the
same functionalities.

7. ACTIVITIES
The main activities are:
 Scope
 Analysis/Software Requirements
 Design
 Development
 Testing
 Training
 Documentation
 Pilot
 Deployment
 Post Implementation Review

8. MAIN VIEW

9. SCOPE & ANALYSIS/SOFTWARE
REQUIREMENTS

10. DESIGN & DEVELOPMENT

11. TESTING

12. TRAINING

13. DOCUMENTATION

14. PILOT & DEPLOYMENT

15. POST IMPLEMENTATION REVIEW

16. TIMESCALE PICTURES

17. CONCLUSIONS
 Plan way ahead
 Go step by step
 Give your visitors and clients a way to cooperate/communicate
 Less is more (number of pages/plugins/links on page/modules/etc)
 Quality beats quantity
In case of unsuccessful implementation of one of the modules, we will appeal
to buy some of them so we won’t be behind schedule and continue with the
central plan. That means cutting off a percentage of the salary.