Profiles

Talend Software Development Life Cycle Best Practices Guide

author
Talend Documentation Team
EnrichVersion
6.5
EnrichProdName
Talend Big Data
Talend MDM Platform
Talend Data Integration
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend Data Management Platform
task
Design and Development
Deployment
Administration and Monitoring
EnrichPlatform
Talend Repository Manager
Talend Studio
Talend Administration Center
Talend JobServer
Talend CommandLine
Talend Artifact Repository
Example set of the main persona that are involved in the phases of a product life cycle.
  • Alan the Project Manager (Analysis and Requirements / Specifications Phase): Alan drives the project architecture and picks technologies to be used. He is in charge of designing the specifications along with business managers and developers;

  • Jim the developer (Development and Tests + Maintenance Phases): Jim designs and implements Jobs and components in the Development environment. He also creates and run tests for the Jobs he designed, then passes these Jobs to Thomas. If needed, he can handle maintenance by fixing errors or improving the software to meet new technical requirements;

  • Thomas the Quality Assurance engineer (QA Tests Phase): Thomas creates and executes test suites on features and products using manual (based on user scenarios) and automated build tests (using Test Cases) in the QA environment. He also sends regular result reports to Megan;

  • Megan the Operation/Release Manager (Go Live Phase): Megan approves the release candidate build (RC) and deploys it to Production when she is sure all tests have passed.