This page includes commentaries for specific best practices that could be adopted by Software Development Teams (SDTs). The commentaries explain the rationale behind each best practice, the associated recommendations and possible risks. Some of the commentaries also include examples and operational hints concerning the adoption.
Please note that commentaries are in PPTX format and could be used for assembling custom presentations for the SDTs.
The commentaries are grouped by Target Areas based on the established GEANT Software Maturity Model. Links for each Target Area is provided for further detail on the context of the CBP and their commentaries.
1. Requirements engineering
Requirements engineering is a collection of processes for elicitation of needs, analysis and transformation into requirements, traceability, validation and over all management of requirements.
2. Design and implementation
Related to activities usually associated with software design, development and delivery, including the relevant practices, elements of development environment and tools used in software development.
 | ||
|
3. Quality assurance
The actual coding is currently not elaborated here but may be added in relation to addressing of secure coding or in relation to privacy-related requirements. Integration of QA tools in the work of the development team, external consultancy or reviews and other QA related practices, tools, and measures
4. Team organisation
Plan of training and knowledge building for the software development team exists. Diversification and capture of experience, expertise and knowledge through collaboration, tutoring and role switching. People are proactively prepared for their forthcoming assignments and possible changes within the team.
Effective communication channels are developed that cover both internal (in-team) and external (with stakeholders) communication. There is an agreed, approved and effective method of making decisions within the team. Schedules and and assignments management is in place in order for individual plans, commitments and assignments of all team members are managed, so that the work and the use of resources are conducted in an optimal way.
5. Software maintenance
The focus is proper planning and validation of the changes that will be conducted within maintenance. Maintenance-related requirements should be captured with other customer and stakeholder requirements, and they should be initiated during development. The development of actual maintenance solutions and their verification are conducted within Development and Implementation and Quality Assurance target areas: planning and designing for maintainability, handling of maintenance issues, assessment of modification options, implementation of modifications
