Perform Documentation Analysis
During this sub-process the re-engineering documentation is collected and compiled. All the activities of this sub-process are optional and they can be performed at the same time. The final output of this process is the Documentation Set.
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity, domain information is collected and registered. This information can be used as an input for some extraction techniques. According to (Assunção et al., 2017), domain artifacts may contain information such as products description, user comments, documentation of systems in specific domain, and domain analysis.
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity a list of constraints and terms related to the system domain is collected and registered. These constraints may be collected in the system business rules or even non-functional requirements.
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity the requirement information is collected and registered. Requirements artifacts may be Requirements List, Use Cases, User Stories or any kind of requirements specification.
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity architectural information is collected and registered. This information may include: design patterns, architectural patterns. The artifacts used to register these can be class diagrams, state machine diagrams or even activity diagrams.
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity the information about artifacts types (extensions, formats, structures, etc) is collected and registered. This information can be used to decide which extraction techniques can be used.
- Source Code
- Requirements List
- Use Cases
- Business Rules
- Class Diagrams
- State Machine Diagrams
- Feature Models
- Activity Diagrams
- Reference Architecture
- Reference Requirements
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity the information about the developed products will be collected and registered. This information may include programming patterns, programming and development paradigms
This is an optional activity and will or will not be performed based on the need of its outputs artifacts. During this activity information about technologies used in each product are collected and registered. This information can be used to decide which is the best extraction technique or exclude the use of some techniques as well.
π Prepare, Assemble and Execute Process for SPL (PAxSPL)
-
π Process Structure
-
π Process Overview
-
π Guidelines
-
Static Analysis Techniques
-
Information Retrieval Techniques
-
Support Techniques
-
π Support Checklist
-
π» Tool Support
-
-
π Bibliography
PAxSPL is a project developed within the Laboratory of Empirical Studies in Software Engineering