Merge pull request #15 from ManoManoTech/4-domain-language-rename-tas…

…k-to-mission

Task -> Mission

FUNCTIONAL_REQUIREMENTS.md

@@ -1,27 +1,27 @@
-## HeroesDesk: task tracker for heroes :)
+## HeroesDesk: mission tracker for heroes :)
 
-No time tracking, no endless workflow customizing, only tasks that need to be done. Or not: let the heroes decide :)
+No time tracking, no endless workflow customizing, only missions that need to be done. Or not: let the heroes decide :)
 
 There are the following user types:
 
-- users: able to see all and create tasks (title and description)
-- heroes: as users plus ability to modify all in tasks in their squads
-- admin: define squads, used for tasks, as well as heroes allowed to work on each squad
+- users: able to see all and create missions (title and description)
+- heroes: as users plus ability to modify all in missions in their squads
+- admin: define squads, used for missions, as well as heroes allowed to work on each squad
 
-A task is made of:
+A mission is made of:
 
 - squad: one among the squads defined by the admin
 - title: mandatory, updatable, single line, 1 up to 255 chars
 - description: optional, updatable, multi line, up to 1024 chars
 - creator: mandatory, fixed at creation
-- id: unique among all tasks, fixed at creation, made of the squad key, a dash and a unique number, 2 to 73 chars
-- assignees: can be empty, updatable. Always empty for done task.
-- a task can be pending, in progress or done: default to pending
+- id: unique among all missions, fixed at creation, made of the squad key, a dash and a unique number, 2 to 73 chars
+- assignees: can be empty, updatable. Always empty for done mission.
+- a mission can be pending, in progress or done: default to pending
     - each state can be moved to any of the 2 others
-    - if a task without assigned is set to in progress, the hero doing the action is automatically added as assignee
-    - when a task is done, then all its assignees are removed
+    - if a mission without assigned is set to in progress, the hero doing the action is automatically added as assignee
+    - when a mission is done, then all its assignees are removed
 
-Multiple tasks with same title or description can be created.
+Multiple missions with same title or description can be created.
 
 A squad has:
 - a name, 1 up to 255 chars, unique among all squads, updatable, must be unique

README.md

@@ -66,7 +66,7 @@ It's even better when most of the bugs can't happen by design.
 
 When doing a tech showcase, which business model to use is often tricky.
 
-A made up application, called HeroesDesk, is the functional target. It's a task tracker for heroes: familiar to
+A made up application, called HeroesDesk, is the functional target. It's a mission tracker for heroes: familiar to
 developers, yet allowing some complexity and with a clear mission statement.
 
 Read more about the requirements in [Functional requirement](FUNCTIONAL_REQUIREMENTS.md).

heroesdesk-inmemory-adapters/README.md

@@ -1,7 +1,7 @@
 Provide the following in memory adapters for the HeroesDesk application:
 ```
-org.hexastacks.heroesdesk.kotlin.adapters.inmemory.TaskRepositoryInMemory
-org.hexastacks.heroesdesk.kotlin.adapters.inmemory.UserRepositoryInMemory
+org.hexastacks.heroesdesk.kotlin.ports.inmemory.MissionRepositoryInMemory
+org.hexastacks.heroesdesk.kotlin.ports.inmemory.UserRepositoryInMemory
 ```
 
-Correspondingly, the default HeroesDesk test class is `org.hexastacks.heroesdesk.kotlin.HeroesDeskImplTest` and uses the above in memory adapters.
+Correspondingly, the default HeroesDesk test class is `org.hexastacks.heroesdesk.kotlin.test.AbstractHeroesDeskTest` and uses the above in memory adapters.