Erinevus lehekülje "Final Documentation" redaktsioonide vahel

Allikas: Kursused
Mine navigeerimisribale Mine otsikasti
(Uus lehekülg: 'Description of final project documentation for ITI8740 The purpose of documentation is to understand the system, how to use it and if needed how to develop it further. You shoul...')
 
1. rida: 1. rida:
 
Description of final project documentation for ITI8740
 
Description of final project documentation for ITI8740
  
The purpose of documentation is to understand the system, how to use it and if needed how to develop it further. You should already have created most of the documentation during the course and the primary focus is packaging it into single document. The documentation should be uploaded to Gitlab and link provided to the lecturer via Teams direct message by '''Saturday, January 15, 23:59'''.
+
The purpose of documentation is to understand the system, how to use it and if needed how to develop it further. You should already have created most of the documentation during the course and the primary focus is packaging it into single document. The documentation should be uploaded to Gitlab and link provided to the lecturer via Teams direct message before '''Sunday, January 15, 23:59'''.
  
 
The approximate length for documentation is ~5 pages.
 
The approximate length for documentation is ~5 pages.

Redaktsioon: 7. detsember 2022, kell 21:56

Description of final project documentation for ITI8740

The purpose of documentation is to understand the system, how to use it and if needed how to develop it further. You should already have created most of the documentation during the course and the primary focus is packaging it into single document. The documentation should be uploaded to Gitlab and link provided to the lecturer via Teams direct message before Sunday, January 15, 23:59.

The approximate length for documentation is ~5 pages.

The documentation should be presented in English and must contain the following:

  • General information about the project:
    • Team members and roles
    • A link to issue tracker and source code
    • A link to the application on web and/or appstore
  • Project background
    • General information about the project (purpose, scope, goals), 1 A4 max
    • The most recent lean canvas
    • A list of project features and requirements
    • A list to scienticic articles being used
  • Validation
    • A brief summary how validation was performed, method, results and conclusions
    • If you have any quantitative data, links to surveys etc. provide it here
  • Implementation
    • A list of implemented features and description of primary functionality
    • Installation manual (if needed)
    • User manual (if needed)
  • Project summary
    • Max 1 A4 summary that describes what goals where met and what were not, if the inital idea changed then how. What would be the next steps.