Skip to main content

Table 2 Identifying components in ASD

From: Identifying components existing in Agile software development for achieving “light but sufficient” documentation

Studies

Methodology

Domain

Components

[16]

Multiple case studies

Components concerned with quality requirement gathering through documentation in Agile

-Technical writers

-Story cards

-Management Document

-Mitigation Strategy

[7]

Empirical Study

Evaluation of process and product documentation

-User document

-Design document

-Project overview

-Requirement document

-Support document

-Operations document

-Vision statement

-System documentation

-Contract model

[9]

Empirical study

Evaluation of General user requirements and product documentation

-Product requirement

-Organizational requirements

-External requirements

-Vision statement

-System documentation

-Contract model

[8]

Empirical

User activities involved in gathering user requirements

-Use cases

-Technical writers

-Test-driven Development

[12]

Multiple case studies

Determine the components of RE activities

-Req. elicitation

-Req. analysis

-Req. document

-Req. validation

-Req. management

[15, 17]

Empirical

Existence of software quality factors in ASD

-Reliability

-Correctness

-Usability

-Flexibility

-Maintainability

-Reusability

-Efficiency

-Interoperability

-Functionality

-Testability

-Communicativeness

-Completeness

-Traceability

-Operability

-Training

-Expandability

-Scalability

-Modularity

-Integrity

-Portability

-Modularity

-Performance

[11]

Empirical

Existence of customer satisfaction, environmental and organizational working regarding SCRUM based software

-Customer location

-Customer knowledge

-Customer requirement

-Customer feedback