Commit 11c18fe1 authored by Jonas Johan Solsvik's avatar Jonas Johan Solsvik
Browse files

add proprog.md

parent 91dd8880
.obsidian/
# imt3602-2021
# imt3602-2021 Submission Info
## Requirements
NOTE: We're interested in the 'HOW' and the 'WHY/WHY NOT' in the report.
The repo you submit will have a proprog.md file. This file will at minimum cover:
- A list of the name of the students in the team
- A list of links to any other repos connected to the project
- Group discussion
- Strengths and weaknesses of languages you used in your project
- How you controlled process and communication systems during development
- Use of version control systems, ticket tracking, branching, tagging/versioning
- Link to programming style guide including how to comment code
- Use of and integration of libraries, modules, and other ways for modularisation of your product
- Professionalism in your approach to software development
- Use of code review
- You will include an individual discussion on
- A link to, and discussion of, code you consider good
- A link to, and discussion of, code you consider bad
- A link to two pieces of code, a before and after refactoring. This will include a discussion of why the code was refactored
- A personal reflection about professionalism in programming
## Proprog.md format
- One single markdown file named "proprog.md", which first contains the group discussion, and then the individual discussions.
## Submission Deadline
- Submission deadline is 28th May 2021, you're supposed to submit through Inspera.
- More information about when the Inspera room will open etc. comes after easter.
- If you're working in a non-public environment/repository please create a version of the repository here on Gitlab that I can access, if that breaks your CD/CI or something, please mention that in the report, so we're not overlooking it.
## Grading information
- The grade will be a combination of the group and individual sections, 70% for the group section and 30% for the individual section.
\ No newline at end of file
# Proprog.md
NOTE: We're interested in the 'HOW' and the 'WHY/WHY NOT' in the report.
**Group:** 23, Identity Wallet, DID CLI
**Students**: Jonas Johan Solsvik
**Repo Implementation**: https://github.com/DIN-Foundation/bcs-ntnu-2021
**Repo Thesis**: https://github.com/Arxcis/thesis-NTNU
## 1 Group discussion
### 1.1 Strengths and weaknesses of Rust
#### Strengths
#### Weaknesses
### 1.2 How we controlled process and communication systems during development
- Discord
- Google hangouts
- MSTeams
### 1.3 Use of version control systems, ticket tracking, branching, tagging/versioning
### 1.4 Programming style guide including how to comment code
### 1.5 Use of and integration of libraries, modules, and other ways for modularisation of your product
### 1.6 Professionalism in your approach to software development
### 1.7 Use of code review
## 2 Individual discussion
### 2.1 A link to, and discussion of, code you consider good
### 2.2 A link to, and discussion of, code you consider bad
### 2.3 A link to two pieces of code, a before and after refactoring.
This will include a discussion of why the code was refactored
### 2.4 Personal reflection about professionalism in programming
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment