SERVICES BEST PRACTICES

Contact an expert today to talk about your project at 514 276-3934

Best practices

Rational Unified Process (RUP)

Each discipline is broken down into phases, each phase into iterations

Each discipline is broken down into phases, each phase into iterations

The phases :
  • Initialization : project scope, main use cases, identify risks. Go No Go
  • Planification ; Estimation, planning, architecture, eliminate high risk
  • Define the use cases remaining, detailing sequence diagrams, complete model (attributes and methods), coding, test scenarios
  • Construction : Define the remaining use cases, detailing sequence diagrams, complete model (attributes and methods), coding, test scenarios
  • Transition : Correction, delivery, deployment, training

Séquences RUP

Eliminate risks at the begining of the project

Élimination des riques RUP

The supporting disciplines are configuration, change management and project and environment management

Séquences RUP

eXtreme Programming (XP)

Discover the advantages and disadvantages
Strenghts :
  • Iterative with soft planification
  • Easy to implement
  • Made an emphasis on the technical aspects : prototypes, rules development, testing ...
  • Innovative: programming duo, kick-off meetings  …

Weaknesses :
  • Do not cover the phases upstream and downstream development : capture needs, support, maintenance, integration testing ...
  • Avoids the analysis phase, so that it can spend its energy to make and unmake
  • Quite vague in its implementation: which stakeholders, what deliverables ?


Best practices

The modeling to :
  • Simplify the realty
  • Understand the system to develop
  • Facilate the communication

How : via diagrams that are graphical representations of the model


The best practices to :
  • Develop iteratively
  • Manage what is required
  • Modelize visually (UML)
  • Check constantly the quality
  • Manage the change


Process

A process is the way forward in the design
A process is the way forward in the design

A process allow to :

  • Define tasks order
  • Specify artifacts to be developed  : model, document, source code ...
  • Guide the developers
  • Give criterias about the follow-up and evaluation