• Analyze Goals and Plans
• Define Decision Model
• Define Domain Scope
• Define System Actor
• Identify Stakeholders
• Identify Stakeholders for MAS-PL
• MAS Application Engineering Requirement Analysis
• xxIdentify Stakeholders for SPL Final Product
• xxxAnalyze Goals and Plans for SPL Final Product

• Define Feature Model
• Perform Feature to Design Mapping
• Perform MAS Domain Implementation Testing
• Perform MAS Final Product Testing
• Refine Commonalities and Variabilities
• xxxMTV Map between Feature Model and Analysis Artifacts

• Decision Model
• Domain Definition
• MAS Application Engineering New Requirements
• MAS Feature Selection
• Tropos Actor Diagram
• Tropos Goal Diagram

• MMF Application Requirement Analysis with ApelEtAl  >  Perform MAS Application Requirement Analysis  >  System Analyst
• MMF Define SPL Feature Model with FODA  >  Define MAS-PL Feature Model  >  System Analyst
• MMF Detail Requirement with Tropos  >  Detail Requirement with Tropos  >  System Analyst
• MMF Domain Scope with Synthesis  >  Gather Requirements with Synthesis  >  System Analyst
• MMF Gather Requirement with Tropos  >  Gather MAS-PL Requirement with Tropos  >  System Analyst
• MMF Identify Additional Requirement with Tropos  >  Identify Additional Requirement with Tropos  >  System Analyst
• MMF Identify Initial Requirement with Tropos  >    Identify Requirement with Tropos  >  System Analyst
• MMF Identify SPL Requirement with Synthesis  >  Identify Domain Requirement with Synthesis  >  System Analyst
• MMF Map Commonalaty&Variability to Domain Design Artifacts with Meduse  >  Map Comm&Variability to Design Artifacts  >  System Analyst
• MMF Refine SPL Commonalities and Variabilities with Meduse  >  Refine Commonalities and Variabilities  >  System Analyst
• MMF Test MAS Final Product  >  Test MAS Final Product  >  System Analyst
• MMF Test SPL MAS Components with Meduse  >  Test MAS-PL components  >  System Analyst
• PD_GaiaFMAnalysis  >  Domain Engineering Iteration 1..n  >  Domain Analysis Phase  >  Define MAS-PL Feature Model  >  System Analyst
• PD_TroposDMAnalysis  >  Domain Engineering Iteration 1..n  >  Domain Analysis Phase  >  Define MAS-PL Decision Model  >  System Analyst
• Tropos PL Variant 2  >  Domain Engineering Iteration 1..n  >  Domain Analysis Phase  >  Detail Requirements with Tropos  >  System Analyst
• Tropos PL Variant 2  >  Domain Engineering Iteration 1..n  >  Domain Design Phase  >  Refine Commonalities and Variabilities  >  System Analyst
• Tropos PL Variant 2  >  Domain Engineering Iteration 1..n  >  Domain Design Phase  >  Map Features to Domain Design Artifacts  >  System Analyst
• Tropos PL Variant 2  >  Domain Engineering Iteration 1..n  >  Domain Implementation Phase  >  Test MAS-PL components  >  System Analyst
• xxxMMF_Gather SPL Final Product Requirement with Tropos  >  Gather Final Product Requirement with Tropos  >  System Analyst
• xxxMMF Map Feature Model to Domain Analysis Artifacts  >  Map Feature Model to Analysis Artifacts  >  System Analyst
• xxxxxMMF Define Decision Model with Synthesis  >  Define MAS-PL Decision Model  >  System Analyst

An Analyst needs the following knowledge, skills, and abilities:

• Expertise in identifying and understanding problems and opportunities
• Ability to articulate the needs that are associated with the key problem to be solved or the opportunity to be realized
• Ability to collaborate effectively with the extended team through collaborative working sessions, workshops, JAD sessions and other techniques.
• Good communication skills, verbally and in writing
• Knowledge of the business and technology domains or the ability to quickly absorb and understand such information

This role can be assigned in the following ways:

• One (or more) team member performs this role exclusively. This commonly adopted approach is suitable for complex requirements that are difficult to gather.
• One (or more) team members performs both this role and tests the software. This is a good option for smaller or resource-constrained test teams.