After presenting the 2018 budget, the Federal Government allocated funds and requested to Environment and Climate Change Canada ECCC to guarantee that the Species at Risk Act is enforced. The minister of the environment does not have a system that manages the Recovery Strategies and Action Plans for the species at risk in Canada. Today the documents are manually created and published.

ECCC has hired you to execute a project; elicit and document requirements; perform system analysis and design, and create a test plan and test cases.

Project Scope

Recovery of Endangered, Threatened, and Extirpated Species (Sections 37 to 55) of SARA. These sections of the law detail the process and rules which Environment Canada must follow to recover the species identified at any level of risk.

In a nutshell, Environment and Climate Change Canada ECCC must follow 4 major steps when it comes to Species at Risk:

1. A Committee on Status of Endangered Wildlife in Canada (COSEWIC) assesses the level of risk of species that are believed to be at risk (We will be covering this step together along the course)

2. Species considered at risk are listed to the Schedule 1 as defined by the law

3. Recovery strategies and action plan documents have to be created for the listed species and published to the Public Registry (This is the scope of your project)

4. Species and their habitats must be protected based on the recovery strategies

Regarding the Sections 37 to 55, some considerations of the scope of your project include:

• ECCC needs a document management system in which Recovery strategies and action plans can be created, tracked, and published to the Public registry

• Competent Ministers are the different Government of Canada departments that are responsible for a species. They are stakeholders and users of the system. These 3 are as follows:

  • Environment and Climate Change Canada ECCC: Responsible for all terrestrial species

  • Department of Fisheries and Oceans DFO: Responsible for all aquatic species

  • Parks Canada: Responsible for species located within any National Park

• Provincial governments, indigenous groups and private land owners where species are located are also contributors of the documents

• A recovery strategy and an action plan are technical documents and the document management system tracks:

  • The documents lifecycle: From creation to publishing the final version to the public registry

  • Information to support document creation, such as Contact lists, land information where species are located, species information and threats (covered during step 1 of the process along our course)

Project Tasks

Your final deliverable should have the following sections:

Project Plan

1. Project description: A paragraph describing what the project is about

2. Project scope (context diagram developed on Visual Paradigm)

3. Process model (current and future states refined on module 4 - developed on Visual Paradigm)

4. Requirements plan

5. Stakeholder Management plan (RACI matrix)

WBS

6. WBS (developed on Visual Paradigm)

7. Gantt chart (suggested tool: excel)

Requirements

8. Identify business events (based on context diagram)

9. Create a traceability matrix in excel and list all stakeholder requirements with a unique identifier each.

Agile Approach

10. Identify the Epics and user stories

11. Develop the acceptance criteria for each user story

12. Create a story map (developed on Visual Paradigm)

13. Add the user stories to the traceability matrix created in item 9. The stories will be traced against the requirements. You may have more than one user story per requirement since they have more details than the stakeholder requirements

Modeling Use Cases with UML

14. Identify solution requirements based on stakeholder requirements and user stories

15. Create a use cases diagram (Visual Paradigm): Use cases can be identified based on business events developed in item 8

16. Add the solution requirements and use cases to the Traceability matrix

Describing Use Cases and Representing using Activity Diagrams

17. Describe the use case scenarios of each use case identified

18. Create activity diagrams for each use case (developed on Visual Paradigm)

Introduction to OO and structural models

19. Identify the objects based on the use cases process described during the previous module. A list of identified objects is sufficient.

20. Create the classes, attributes and methods using as much as possible the 4 fundamentals of object orientation (developed on Visual Paradigm)

21. Create the class diagram (developed on Visual Paradigm)

Dynamic Models

22. Create at least 2 sequence diagrams for the identified classes defined during the previous module (developed on Visual Paradigm)

23. Create a state machine diagram (developed on Visual Paradigm)

Module 10: Design Patterns

24. Create interfaces to your classes to promote polymorphism (developed on Visual Paradigm)

25. Apply at least 3 of the 23 GoF design patterns to your models. Indicate which patterns you are applying (developed on Visual Paradigm)

Refining Modeling

26. Add your packages and customize the diagram provided in this module (developed on Visual Paradigm)

Test Plan

27. Create a test plan

28. Add test activities to your WBS and Gantt chart

29. Update the RACI matrix including test activities to the stakeholders involved to the test

Test Cases

30. Create test cases for:

stakeholder requirements

solution requirements (both functional and non-functional)

Use cases

User stories (review the acceptance criteria in case they are not testable)

Design model

31. Add the test cases to the traceability matrix

Submission

It’s expected you deliver your project assignment in the following formats:

1. One Excel file (or equivalent) for the Gantt chart and traceability matrix

2. One Word document (or equivalent) for the remaining tasks

3. Submit to this submission folder when all deliverables are complete.