Design and implementation of a web portal on sustainable development in Cameroon

• CERTIFICATION
  
• DEDICATION
  
• ACKNOWLEDGEMENTS
  
• ABSTRACT
  
• RÉSUMÉ
  
• TABLE OF CONTENT
  
• LIST OF FIGURES
  
• LIST OF TABLES
  
• LIST OF ABBREVIATIONS
  
• CHAPTER ONE: GENERAL INTRODUCTION
  
  • 1. BACKGROUND AND CONTEXT OF THE STUDY
    
  • 2. STATEMENT OF THEPROBLEM
    
  • 3. RESEARCH QUESTIONS
    
  • 4. RESEARCH HYPOTHESES
    
  • 5. OBJECTIVES OF THE STUDY
    
  • 5.1. GENERAL OBJECTIVE
    
  • 5.2. SPECIFIC OBJECTIVES:
    
  • 6. SIGNIFICANCE OF THE STUDY OR ACHIEVEMENTS
    
  • 7. SCOPE OF THE STUDY
    
  • 8. DELIMITATION OF THE STUDY
    
  • 9. IMPORTANCE OF THE DISSERTATION FOR EDUCATION COMMUNITY
    
  • 10. DEFINITION OF TERMS
    
  • - 11. OVERVIEW OF DISSERTATION
    
• CHAPTER TWO: LITERATURE REVIEW
  
• INTRODUCTION
  
  • 1. OVERVIEW OF WEB APPLICATIONS
    
    • 1.1. History of web applications
      
    • 1.2. The Internet and the Web
      
    • 1.3. Types of websites
      
    • 1.4. Social Medias
      
    • 1.5. Web portals
      
      • 1.5.1. Types of web portals
        
  • 2. SUSTAINABLE DEVELOPMENT AND ICT
    
  • 3. LITERATURE REVIEW
    
• CONCLUSION
  
• CHAPTER THREE:RESEARCH METHODOLOGY AND MATERIALS USED
  
• INTRODUCTION
  
  • 1. WEB APPLICATION ARCHITECTURE
    
    • 1.1. The 2tiers architecture
      
    • 1.2. The 3-tiers architecture
      
    • 1.3. The n-tiers architecture
      
    • 1.4. The MVC architecture
      
  • 2. MODULES OF APPLICATION WEB SITE
    
  • 3. RESEARCH DESIGN
    
  • 4. ANALYSIS METHODS
    
    • 4.1. Object Oriented Methods
      
      • 4.1.1. UML method
        
        • 4.1.1.1. Advantages
          
        • 4.1.1.2. Limits
          
      • 4.1.2. UP method
        
        • 4.1.2.1. Advantages
          
        • 4.1.2.2. Limits
          
    • 4.2. Functional methods
      
    • 4.2.1. SADT method
      
      • 4.2.1.1. Advantages
        
      • 4.2.1.2. Limits
        
    • 4.2.2. MERISE method
      
      • 4.2.2.1. Advantages
        
      • 4.2.2.2. Limits
        
    • 4.3. Choose of a method
      
  • 5. MERISE STEPS
    
    • 5.1. MERISE levels
      
      • 5.1.1. Conceptual level
        
      • 5.1.2. Organizational level
        
      • 5.1.3. Logical level
        
      • 5.1.4. Physical level
        
    • 5.2. Data dictionary
      
    • 5.3. The Data Conceptual Model (DCM)
      
      • 5.3.1. Entities
        
      • 5.3.2. Properties
        
      • 5.3.3. Occurrence
        
      • 5.3.4. Identifier
        
      • 5.3.5. Associations and Cardinalities
        
      • 5.3.6. Normalisation rules
        
        • · Normalisation of names
          
        • · Normalisation of identifier
          
        • · Normalisation of attributes
          
        • · Normalisation of attributes of associations
          
        • · Normalisation of associations
          
        • 5.3.6.1. First Normal Form (1NF)
          
        • 5.3.6.2. Second Normal Form (2NF)
          
        • 5.3.6.3. Third Normal Form (3NF)
          
      • 5.3.7. Complete CDM
        
    • 5.4. Data Logical Model (DLM)
      
      • 5.4.1. Definition of concepts
        
        • 5.4.1.1. Tables, columns and rows
          
        • 5.4.1.2. Primary and foreign keys of each table
          
      • 5.4.2. From DCD to Data Logical Relational Data Model (DLRM) rules
        
        • 5.4.2.1. Entity and table
          
        • 5.4.2.2. Binary relation with cardinalities (X,1) - (X,n), X=0 or X=1
          
        • 5.4.2.3. Binary relation with the cardinalities (X,n) - (X,n), X=0 or X=1
          
    • 5.5. From Data Logical Relational Model (DLRD) to Data Physical Model (DPM)
      
    • 5.6. Data Physical Model
      
  • 6. MATERIALS USED
    
    • 6.1. Software
      
      • 6.1.1. HTML
        
      • 6.1.2. CSS: Bootstrap framework
        
      • 6.1.3. JavaScript
        
        • 6.1.3.1. AJAX
          
        • 6.1.3.2. JQuery
          
      • 6.1.4. PHP
        
      • 6.1.5. SQL
        
      • 6.1.6. WampServer
        
      • 6.1.7. Aptana Studio
        
      • 6.1.8. Web browsers
        
      • 6.1.9. Adobe Photoshop
        
      • 6.1.10. Power designer
        
    • 6.2. Hardware
      
  • 7. CONCEPTION AND REALIZATION OF THE APPLICATION
    
    • 7.1. Classification of needs of the future users
      
      • 7.1.1. Functional needs
        
      • 7.1.2. Non-functional needs
        
        • 7.1.2.1. Quality requirements
          
        • 7.1.2.2. Performance requirements
          
    • 7.2. Functional specifications
      
    • 7.3. The software life cycle
      
    • 7.4. Structure of the web application
      
  • 8. PARTIAL CONCLUSION
    
  • 1. HOMEPAGE
    
  • 2. CONNECTION / DISCONNECTION
    
    • 2.1. Subscribe
      
    • 2.2. Disconnection
      
  • 3. CONSULT PAGES
    
    • 3.1. Link page
      
    • 3.2. Article page
      
    • 3.3. Document page
      
  • 4. SEARCH
    
    • 4.1. Search in the website
      
    • 4.2. Google customize search
      
  • 5. PROPOSE CONTENT AND GENERAL ADMINISTRATION
    
    • 5.1. Link
      
    • 5.2. Article
      
    • 5.3. Document
      
  • 6. FORUM
    
    • 6.1. Read topics
      
    • 6.2. Read subjects
      
    • 6.3. Read and publish comment
      
  • 7. USER SPACE
    
    • 7.1. Private Messages
      
      • 7.1.1. Read messages
        
      • 7.1.2. Send messages
        
    • 7.2. Profile
      
    • 7.3. User list
      
  • 8. ADMINISTRATION
    
    • 8.1. Forum administration
      
    • 8.2. Users administration
      
  • 1. SUMMARY OF FINDINGS
    
  • 2. DIFFICULTIESENCOUNTERED
    
  • 3. RECOMMENDATIONS
    
  • 4. SUGGESTIONS FOR FURTHER STUDIES
    
• CONCLUSION
  
• REFERENCES
  
• APPENDICES