A. Data Collection
We collected data primarily through face-to-face semi- structured interviews with agile practitioners who design or use architecture, or who are otherwise architecture stakeholders. The average interview length was 70 minutes.
We asked participants to select a project that they had been involved with to discuss during the interview. Types of projects varied hugely, from green field to system redevelopment, from standalone systems to multi-team enterprise systems, and from start-up service providers and ongoing mass market product development to bespoke business systems. Systems varied from highly mission-critical systems such as flight control and health record management, to business critical systems such as banking and retail, through to largely non- critical administration and entertainment broadcast systems. We also obtained documentation, such as software architecture documents, which were able to confirm the decisions made and why they were made, and copies of architecture models, which provided overviews of the architectures. Additional data in the form of discussions by email and telephone clarified earlier interviews and documentation where necessary.
A. Data CollectionWe collected data primarily through face-to-face semi- structured interviews with agile practitioners who design or use architecture, or who are otherwise architecture stakeholders. The average interview length was 70 minutes.We asked participants to select a project that they had been involved with to discuss during the interview. Types of projects varied hugely, from green field to system redevelopment, from standalone systems to multi-team enterprise systems, and from start-up service providers and ongoing mass market product development to bespoke business systems. Systems varied from highly mission-critical systems such as flight control and health record management, to business critical systems such as banking and retail, through to largely non- critical administration and entertainment broadcast systems. We also obtained documentation, such as software architecture documents, which were able to confirm the decisions made and why they were made, and copies of architecture models, which provided overviews of the architectures. Additional data in the form of discussions by email and telephone clarified earlier interviews and documentation where necessary.
การแปล กรุณารอสักครู่..