Software Development Management Tools Working Group

This working group has a shared interest in tools being used for managing a SW development project - including tools for version control, issue tracking, documentation, etc.

Members

• Arne Styve
• Hallvard Trætteberg
• Michael Tollefsen
• Rune Hjelsvold
• Simon McCallum

Classes of tools

Code repository

A code repository provides the possibility to share code, create versions (time- and tag-based) and branches (topic-based). There are typically two levels of organisation: repositories and organisation (often called group or project). The repository is where the code is stored, and any user will typically be able to create new repositories and grant other uses access. An organisation may be defined as the owner of several repositories, so they can be more easily managed by the organisation. E.g. a course (emne) may the organisation which manages repositories, one for each student project group.

Examples are git and mercurial (core system) and gihub (cloud provider), gitlab (cloud provider and software), 

Issue tracking

Issues are a way of managing development tasks based on requirements spanning from feature requests to bug reports. Issues can be entered by both developers, e.g. as a feature from a queue for a sprint, or uses, e.g. as feature requests or bug reports. Issues typically go through phases and may are assigned to people. Branches often refer to issues.