Profiles - 6.3

Talend Software Development Life Cycle Best Practices Guide

EnrichVersion
6.3
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
task
Administration and Monitoring
Deployment
Design and Development
EnrichPlatform
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Repository Manager
Talend Studio

Here is an example set of the main personas 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.