How stan6/se-paper works
Components
• Content Modules: Treat each major section of the software engineering paper as a component. These include:
• Introduction
• Background (optional)
• Motivating Example
• Methodology (which is suggested to be written first)
• Evaluation (flagged as the easiest to write)
• Threats to Validity
• Lessons Learned (Experience Report)
• Related Work (to be combined with Introduction when finalizing)
• Conclusion
• Abstract (written last along with the Introduction)
• Supplemental Resources: Represent “Tools.md” as a supporting component that supplies additional instructions or references to useful tools (for example, for LaTeX support).
• Guidelines & Notes: Capture the “Notes” blocks that specify what language to use or avoid (e.g., avoid strong adjectives) and the overall recommendations on structure (for instance, “use structure like...”).
Relationships and Data Flow
• End with the Introduction/Related Work and Abstract.
Architectural Patterns and Design Principles
• Modular Documentation: Although it’s not a software system with code modules, the “architecture” here is best represented using a modular approach. Each section is a separate “module” which interacts with others in a specific order.