Documente Academic
Documente Profesional
Documente Cultură
2. https://medium.com/omarelgabrys-blog/software-engineering-software-process-and-software-
process-models-part-2-4a9d06213fdc
4 paradigme:
-model linear
-prototipizare
-componente reutilizabile
-metode formale
Paradigme evolutive: -support pentrru procese iterative
--metode incremetal
-model spiral
-model ingenerie concurente
4. -
6. /7
Epic - A general use case that is a collection of features (user stories). (Use Fibonacci numbers to
estimate.)
User Story - Represents a user feature. (Use Fibonacci numbers to estimate.)
Task - We used to call these "Dev Stories" (in a pre-Jira project) - represents a set of engineering work
that is not directly related to a user story.
8. A sprint is a fixed time period where teams complete work from their product backlog. Sprints
are usually one, two, or four weeks long. At the end of the sprint, a team will typically have built
and implemented a working product increment.
9. The backlog is like a to-do list for your next-gen Software project. It's a dedicated space for keeping
track of tasks that you want to do in the future, if you're sick of keeping all your to-do's in a column
on your board.