Visual Paradigm
online.
Use a text editor, for example: MS Word, to deliver you assessment. Copy + Paste your diagrams into the body of your assessment.
Upload this assignment in Brightspace when complete.
*Visual Paradigm grants Algonquin College
online UML tools,
BPMN tools,
Agile Story Mapping tools,
Task Management tools
under the
Academic Partner Program.
Scenario
The Minister of Environment and Climate Change Canada requested you to perform an analysis and design of a system. They have provided the following Requirements.
Statement
Under section 73 of the Species at Risk Act (SARA), the competent minister may enter into an agreement or issue a permit authorizing a person to engage in an activity affecting a listed wildlife species, any part of its critical habitat, or the residences of its individuals.
Business Requirement
BR001:
In order to comply with the Act, the competent ministers: Environment and Climate Change Canada ECCC, Department of Fisheries and Oceans DFO and Parks Canada Agency PCA, require a centralized platform where scientists and researchers can request permits and receive their responses after processing.
Stakeholder Requirements
SR001:
Scientists and researchers should be able to fill and send permit applications online, informing the species, description of activity, pre-conditions and start date.
SR002:
Competent ministers should be able to receive permits and process. Each competent minister is responsible for a set of species. Process with missing information, such as description and pre-conditions are declined. A permit receives a number and it is issued for a period of 1 year.
SR003:
Scientists and researches should be able to receive the permit results. The ministers inform whether the permit was issued or declined.
SR004:
General Public should be able to search for issued permits on the Public Registry
Functional Requirements
FR001:
System must provide a user interface for the scientists and researchers to register themselves to the system, informing name, contact information, organization details (if applicable) and email address.
FR002:
System must provide a user interface for the scientists and researchers to login into the system.
FR003:
System must provide a user interface for authenticated users request new permits. See SR001 for fields information. System to provide a list of species at risk to be selected when requesting a permit.
FR004:
System must retrieve the list of species at risk from an external data source called SAR. This data source provides an interface to retrieve the list of species and which Competent Minister each species belongs to.
FR005:
System doesn’t process the permit but must send the permit request to the Competent Minister (ECCC, DFO or PCA), based on the selected species, for processing.
FR006:
System must provide a user interface for authenticated users to search their permit statuses. A permit is created as Draft. When submitted by the user, the permit receives the status of Processing. If the user decides canceling the submission, it gets the status of Cancelled. A processed permit can have the statuses of either Issued or Declined.
FR007:
System must receive response from the Competent Ministers with permit results and send an email notification to the requester.
FR008:
System must send all Issued permits to the
Public Registry. The public registry is an external application.
Tasks
Based on the statement and requirements above, execute the following tasks 1 to 5.
Task 1: Project plan
• Create a brief description of your project. Choose one SDLC model for your project and justify why this model was chosen.
• Create a context diagram to represent the scope of the project and to illustrate the system and its relationship with the external agents
Task 2: Use Cases and stories
• Identify use cases and create a use case diagram
• Describe 1 (one) use case of your choice including the main flow and a sub-flow and an exception flow
• Represent the described use case with an activity diagram
• Create 2 (two) user stories and acceptance criteria
Task 3: Static diagram
• Identify objects and classes and represent the classes into a class diagram. Add attributes and methods to the class. Use as much as possible the 4 fundamentals of object orientation.
• Apply 1 (one) design pattern to the diagram and explain why this design pattern was chosen.
Task 4: Dynamic diagrams
• Represent in one sequence diagram, the interaction among classes and external data sources for the feature of requesting a permit (FR003, FR004 and FR005).
• Create a state machine diagram to represent the different permit statuses as described by the requirement FR006.
Task 5: Create test cases
• Create test cases for the requirements FR001, FR002 and FR003 including success and fail scenarios.
" inline="" style="display: inline; overflow-wrap: break-word; overflow: auto hidden;">Final Assignment: Systems Analysis and Design (20%)
This assignment relates to the following Course Learning Requirements:
CLR 1 Plan the tasks involved in the scheduling of a project team working on a system analysis and design project using knowledge from the project management book of knowledge (PMBOK).
CLR 2 Document the system requirements for a systems application using current methodologies and documentation guidelines.
CLR 3 Create UML artifacts, which model the static and dynamic aspects of a system as required by systems developers and programmers.
CLR 4 Include aspects of scalability and maintainability in the design of the system under study.
CLR 5 Develop high-level test plans for a system.
CLR 6 Use OO Design tools and project management tools to develop system artifacts and manage the project.
CLR 7 Identify and apply discipline-specific practices that contribute to the local and global community through social responsibility, economic commitment and environmental stewardship.
Objective of this Assignment
The objective of this assignment is to have you explore in a practical way, all of the concepts described in this course.
Pre-Assignment Instructions
You can revisit the previous modules content, including videos, readings and diagrams to support this assessment.
Your diagrams can be created on *Visual Paradigmonline.
Use a text editor, for example: MS Word, to deliver you assessment. Copy + Paste your diagrams into the body of your assessment.
Upload this assignment in Brightspace when complete.
*Visual Paradigm grants Algonquin Collegeonline UML tools,BPMN tools,Agile Story Mapping tools,Task Management toolsunder theAcademic Partner Program.
Scenario
The Minister of Environment and Climate Change Canada requested you to perform an analysis and design of a system. They have provided the following Requirements.
Statement
Under section 73 of the Species at Risk Act (SARA), the competent minister may enter into an agreement or issue a permit authorizing a person to engage in an activity affecting a listed wildlife species, any part of its critical habitat, or the residences of its individuals.
Business Requirement
BR001:In order to comply with the Act, the competent ministers: Environment and Climate Change Canada ECCC, Department of Fisheries and Oceans DFO and Parks Canada Agency PCA, require a centralized platform where scientists and researchers can request permits and receive their responses after processing.
Stakeholder Requirements
SR001:Scientists and researchers should be able to fill and send permit applications online, informing the species, description of activity, pre-conditions and start date.
SR002:Competent ministers should be able to receive permits and process. Each competent minister is responsible for a set of species. Process with missing information, such as description and pre-conditions are declined. A permit receives a number and it is issued for a period of 1 year.
SR003:Scientists and researches should be able to receive the permit results. The ministers inform whether the permit was issued or declined.
SR004:General Public should be able to search for issued permits on the Public Registry
Functional Requirements
FR001:System must provide a user interface for the scientists and researchers to register themselves to the system, informing name, contact information, organization details (if applicable) and email address.
FR002:System must provide a user interface for the scientists and researchers to login into the system.
FR003:System must provide a user interface for authenticated users request new permits. See SR001 for fields information. System to provide a list of species at risk to be selected when requesting a permit.
FR004:System must retrieve the list of species at risk from an external data source called SAR. This data source provides an interface to retrieve the list of species and which Competent Minister each species belongs to.
FR005:System doesn’t process the permit but must send the permit request to the Competent Minister (ECCC, DFO or PCA), based on the selected species, for processing.
FR006:System must provide a user interface for authenticated users to search their permit statuses. A permit is created as Draft. When submitted by the user, the permit receives the status of Processing. If the user decides canceling the submission, it gets the status of Cancelled. A processed permit can have the statuses of either Issued or Declined.
FR007:System must receive response from the Competent Ministers with permit results and send an email notification to the requester.
FR008:System must send all Issued permits to thePublic Registry. The public registry is an external application.
Tasks
Based on the statement and requirements above, execute the following tasks 1 to 5.
Task 1: Project plan
• Create a brief description of your project. Choose one SDLC model for your project and justify why this model was chosen.
• Create a context diagram to represent the scope of the project and to illustrate the system and its relationship with the external agents
Task 2: Use Cases and stories
• Identify use cases and create a use case diagram
• Describe 1 (one) use case of your choice including the main flow and a sub-flow and an exception flow
• Represent the described use case with an activity diagram
• Create 2 (two) user stories and acceptance criteria
Task 3: Static diagram
• Identify objects and classes and represent the classes into a class diagram. Add attributes and methods to the class. Use as much as possible the 4 fundamentals of object orientation.
• Apply 1 (one) design pattern to the diagram and explain why this design pattern was chosen.
Task 4: Dynamic diagrams
• Represent in one sequence diagram, the interaction among classes and external data sources for the feature of requesting a permit (FR003, FR004 and FR005).
• Create a state machine diagram to represent the different permit statuses as described by the requirement FR006.
Task 5: Create test cases
• Create test cases for the requirements FR001, FR002 and FR003 including success and fail scenarios.