23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
# Assigment 4
|
||
## The end
|
||
This [video](videos/assigment4.mp4) describe the final status of the project.
|
||
|
||
The [commit graph](https://code.33co.de/ehofmann/ERP-samk/graph) can give an idea about the change historic in this repository, normally before deadlines.
|
||
|
||
## What is not there
|
||
|
||
> Your work is almost done, congratulations! It’s time to return your final portfolio. How does your report look like? Do you have something in every project phase? Probably not?
|
||
> 1. Fill the gaps by adding short explanations what should be under the empty phases in this kind of project.
|
||
|
||
Looking into the [milestones](https://code.33co.de/ehofmann/ERP-samk/milestones?state=closed&q=), created at begining of the course, that now are considered closed.
|
||
1. Discovery & Planning
|
||
2. Design
|
||
3. Development
|
||
4. Testing
|
||
5. Deployment
|
||
6. Support & Updates
|
||
|
||
Up to number 5, has been covered by this project. Item 6 is after the ERP implementation, that could be managed by the same team, or be transfered to another team. It includes improvements based on users feedback and software updates or upgrades when needed.
|
||
|
||
|
||
[back HOME](https://code.33co.de/ehofmann/ERP-samk) |