Design and realisation of a knowledge base

• Table of Contents
  
• LIST OF FIGURES
  
• LIST OF TABLES
  
• Appreciation
  
• Dedication
  
• General Introduction
  
• State of the art
  
• Chapter 1 State of the art
  
  • 1.2. Study of the current situation
    
  • 1.3. Description of the existing
    
  • 1.4. Project presentation
    
    • 1.4.1. Provided services
      
    • 1.4.2. Provided features
      
  • 1.5 Methodology of development
    
    • 1.5.1 Waterfall model
      
  • Fig1. Waterfall model
    
  • Fig2. V-cycle model
    
    • 1.5.3 Spiral model
      
  • Fig3. Spiral model
    
    • 1.5.4 Chosen methodology
      
  • Tab1. Comparison between Lifecycle-models
    
  • 1.6. Conclusion
    
• Specification and Analyses of Needs
  
• Chapter 2 Specification and Analyses of the needs
  
  • 2.1 Introduction
    
    • Whether we design an application we should know what it must present, so we can't progress without studied and marked the output specifications of our final product.
      
  • 2.2 Specification of the needs (functional and non functional)
    
    • 2.2.1 Functional needs
      
    • 2.2.2. Non functional needs
      
  • 2.3. Actors
    
  • 2.4. Use cases
    
    • 2.4.1. Use cases by priority
      
  • Tab2. Use cases by priority
    
    • 2.4.2 Interactions actors /system
      
  • Tab3. Use cases: general textual description
    
    • 2.4.3. Use case diagrams
      
  • Fig4. Administrator Use case diagram
    
  • Fig5. Visitor use case diagram
    
  • Fig6. Teacher use case diagram
    
  • Fig7. Student use case diagram: Student
    
    • 2.4.4. Use case diagram: Detailed textual description
      
      • 2.4.4.1 Conduct of use case: Activity diagram
        
    • Textual case scenario "Authentication"
      
  • Tab4. Authentication scenario
    
  • Fig8. Activity diagram: Authenticate
    
    • Textual case scenario "Consult privileged space"
      
  • Tab5. Consult privileged space scenario
    
  • Fig9. Activity diagram: Consult privileged space
    
    • Textual case scenario "Search document"
      
  • Tab6. Search document scenario
    
  • Fig10. Activity diagram: Search document
    
    • Textual case scenario "register for training"
      
  • Tab7. Register for training scenario
    
  • Fig11. Activity diagram: Register for training
    
    • 2.4.4.2. Diagram of sequences system
      
    • Textual case scenario "Request for registration"
      
  • Tab9. Request for registration scenario
    
  • Fig12. Sequence diagram: request for registration
    
    • Textual case scenario "Propose online test"
      
  • Tab10. Propose online test scenario
    
  • Fig13. Sequence diagram: propose online test
    
    • 2.7.2 Register for training
      
  • Fig14. Sequence diagram: Register for training
    
  • 2.8. Conclusion
    
• Design of the solution
  
• Chapter 3 Design of the solution
  
  • 3.2. Architectural Conception
    
    • 3.2.1. Technical architecture
      
  • Fig15. N-tier type architecture
    
    • 3.2.2 Logic application architecture (three-layer)
      
  • Fig16. Layers of three-tier logic architecture
    
    • 3.2.2.1 Presentation layer
      
    • 3.2.2.2 Business logic layer
      
    • 3.2.2.3. Persistence layer
      
  • 3.3. Detailed design
    
    • 3.3.1. Design pattern
      
      • 3.3.1.1. MVC
        
  • Fig17. Model-view-controller
    
    • Participants & Responsibilities
      
    • Strategies
      
    • 3.3.1.2. DAO
      
  • Fig18.Data Access Object class diagram
    
    • Data Source represents a data source implementation. A data source could be a database such as an RDBMS, OODBMS, XML repository, and so forth.
      
    • Transfer Object represents a Transfer Object used as a data carrier. The Data Access Object may use a Transfer Object to return data to the client. The Data Access Object may also receive the data from the client in a Transfer Object to update the data in the data source.
      
    • 3.3.1.3. Session Facade
      
  • Fig19. Session facade class diagram
    
    • 3.3.2 Data base conception
      
  • Fig20.  Package diagram
    
    • 3.3.4 Class Diagram:
      
      • 3.3.4.1 Models package
        
  • Fig21.  Models Package: class diagram
    
    • 3.3.4.2 Session Beans package
      
  • Fig22. Session beans package: class diagram
    
    • 3.3.4.3 Controller package
      
  • Fig23. Management process package: Class Diagram
    
  • TrainingController, QuestionController, ResponseController, DocumentController, PersonController, KnowledgeController and knowledgeController.
    
    • Functional structure of the application
      
  • Fig25. Functional structure of the application: user-side
    
    • 3.3.5 Interaction Diagram
      
  • Fig24. Data Access Object sequence diagram
    
  • Fig25. Session Facade sequence diagram
    
    • Textual case scenario "upload document"
      
  • Tab8. Upload document scenario
    
  • Fig26. Sequence diagram: Upload document
    
    • Textual case scenario "Manage teacher skills dashboard"
      
  • Tab8. Manage teacher skills dashboard
    
  • Fig27. Sequence diagram: Manage teacher skills dashboard
    
  • 3.4 Conclusion
    
• Implementation and validation
  
• Chapter 4 Implementation and validation
  
  • 4.2 Working Environment
    
    • 4.2.1 Hardware Environment
      
    • 4.2.2 Selection of programming language
      
      • 4.2.3.2 JSF: Java Server Faces Technology
        
• 4.2.2.2 JPA: Java Persistence API Technology
  The Java Persistence API (JPA abbreviated) is a Java API that allows developers to organize relational data in applications using the Java platform .
  
  • 4.2.2.3 EJB: Enterprise Java Beans
    
  • Fig27. Typical example of a J2EE architecture
    
    
    • 4.2.4 Software Environment
      
      • 4.2.4.1 Net Beans Technical Reasons
        
      • 4.2.4.2 Choice of MySQL 
        
  • 4.3 Deployment Diagram
    
  • Fig28. Deployment diagram
    
  • 4.5 Timing diagram
    
  • Fig32. Gantt diagram (sequencing tasks / time)
    
  • 4.6 Conclusion
    
• General conclusion
  
• Netography