September 20, 2023

Best project modelling practices

Targets

This training course presents project modeling in the broadest sense of the term, whatever the notation used, while putting things into practice through a detailed study of certain modeling languages. A state-of-the-art review of the subject and a market survey of tools are also provided. Following this training course, participants will have a precise view of what the market and technologies in this field have to offer, and which they can exploit.

Prerequisite

Basic knowledge of IT project analysis and modeling.Experience of a modeling language desirable.

Detailed content

Model-driven engineering
1. Introductive semantics
  1. Designer
  2. Finitude
  3. Conjectures
2. Software architecture
  1. Architect
  2. Key points of an architecture
  3. Challenges
  4. Agility
  5. Specification
    1. The System Architecture Document (SAD)
    2. The Component Design Guide
    3. The architectural prototype
    4. The Model
  6. Workflow
    1. Specification of requirements
    2. Architectural analysis
    3. Architectural design
    4. Object oriented design
3. Model-driven architecture (MDA)
  1. Foundations
    1. MOF
    2. XMI
    3. UML
    4. OCL
  2. MDA architecture
    1. Developmental Life Cycle
    2. Platform independent model (PIM)
    3. Platform specific model (PSM)
    4. Code
  3. Example
    1. PIM
    2. PSM database
    3. PSM C#
    4. Code
Project Modeling : Specifications
1. Requirements
  1. Formulations
    1. Café
    2. Code
    3. Tests
    4. Model
    5. Backlog
    6. Documents
  2. Stakeholders
  3. Typology of requirements
    1. Functionality
    2. Functional requirements
    3. Use cases
    4. Prototype
  4. Non-functional requirements
    1. Availability
    2. Reliability
    3. Flexibility
    4. Flexibility
    5. Performance
    6. Load rise
    7. Reuse
    8. Security
2. Engineering
  1. Capture
  2. Analysis
  3. Documentation
  4. Validation
  5. Management
3. Vision
  1. Business Requirements
    1. Foundations
    2. Business opportunity
    3. Business objectives and success criteria
    4. Customer needs
    5. Business risks
  2. Vision of the solution
    1. Statement of vision
    2. Major features
    3. Assumptions and dependencies
    4. Scope and limitations
    5. Perimeter of the initial version
    6. Perimeter of later versions
    7. Limitations and exclusions
  3. Business context
    1. Stakeholder profile
    2. Project priorities
    3. Performance environment
  4. Specification
    1. Introduction
      1. Intention
      2. Conventions
      3. Audience
      4. Project framework
      5. References
    2. General description
      1. Product perspective
      2. Product features
      3. User classes
      4. Operating environment
      5. Design and implementation constraints
      6. User documentation
      7. Assumptions and dependencies
    3. System features
    4. External interface requirements
      1. User interfaces
      2. Hardware interfaces
      3. Software interfaces
      4. Communication interfaces
      5. Non-functional requirements
    5. Appendix
  5. Modelling
    1. Functional model
      1. Requirements
      2. Reporting
      3. Requirements diagrams
      4. Use case diagrams
    2. Change management
      1. Traceability
      2. Matrix
Case of use
1. Usage Stories
  1. History
  2. Terminology
    1. Actor
    2. Scenario
    3. Step
  3. Formalism
    1. Everything dressed
    2. Relax>/li>
  4. Writing
  5. Classical errors
2. Diagrams
3. Use Case points
  1. Why use it?
  2. Adoption
  3. Authors
  4. Karner's method
4. Case study
  1. Requirements
  2. Case of use
    1. Full version
    2. Light version
  3. UML Model
  4. Cost estimates
    1. Estimation
    2. Conclusion