MIE354F_2023_Lab5_Test

.pdf

School

University of Toronto *

*We aren’t endorsed by this school

Course

354

Subject

Computer Science

Date

Jan 9, 2024

Type

pdf

Pages

2

Uploaded by dqwkygefiwh on coursehero.com

MIE 354H- Business Process Engineering Fall 2023 MIE354 Lab 5 Test This is an open book and notes , invigilated test. The work in this test must be completed in person during the lab session and working individually without any consultation at all. Therefore, you are not allowed to communicate or share notes in paper or electronically (i.e., no email, no instant messaging, no USB keys, etc.). While at the lab you cannot run on any device any communication program (email, instant messaging, etc.). This test represents 6% of the course grade. The deliverables for the lab exercise must be submitted by committing and pushing your work to the remote GitHub repository that you used for your Lab 5 Preparation generated by GitHub Classroom, following the instructions provided in the Lab5_Test_Submission_Template.docx. Q0: Read and follow the instructions in Lab5_Test_Submission_Template.docx, add and then Commit and Push the Lab5_Test_Submission_Template.docx to your Lab 5 Preparation GitHub Classroom repo. Q1: Commit the following files in the appropriate directories from Quercus to your repo: 1. Lab5_4.bpmn 2. Lab5_4_UnitTest.java 3. ReviewApprovals.java 4. GeneratePurchaseOrder.java The diagram in Lab5_4.bpmn models a simple approval process for making a purchase order. In this process, a purchase requisition is first created and then sent for approval by the appropriate approvers (e.g., Finance approval and Manager-level approval). As approvals are received, the decisions are reviewed. If approved, the purchase order is generated. The “Submit finance approval” task is not yet functional. Add a form field to capture the decision (similar to “Submit manager approval”) and update Lab5_4_UnitTest.java to test that it works. For Q2-Q4 The approval process is changing to add an additional control for large purchases and streamline smaller purchases. In the new process if the total amount of the purchase is greater than or equal to $10,000.00, then Director-level approval is required and if the total amount is less than $1000.00, then Manager-level approval is no longer required. Q2 Modify Lab5_4.bpmn to model the described process by (1) introducing a new user task called “Submit director approval” that includes a form with a Boolean field that represents the approval decision and (2) updating the conditions of the sequence flows. Hint: Refer to “Submit manager approval” task, refer to the form in “Create purchase requisition” task and refer to the alternate paths in Lab5_1.bpmn.
Q3 Modify ReviewApprovals.java such that the purchase requisition is only approved if the correct number of approvals are received. Q4 Modify myTest in Lab5_4_UnitTest.java to exercise this new requirement and briefly justify your new testcases in your submission document. For Q5-Q7 The current diagram does not model what happens in the case of rejection. A purchase is rejected if any one of the approvers decides to reject the purchase. Q5 Modify ReviewApprovals.java such that a new “rejected” variable is set as “true” when any of the approvers decide to reject (e.g., managerApproval == false). Q6 Modify Lab5_4.bpmn to model the described process using a new user task called “Reject purchase requisition” that simply prints out “Rejecting purchase requisition…”. Hint: use your new “rejected” variable from part (A) to design alternate paths. Q7 Modify myTest in Lab5_4_UnitTest.java to exercise this new requirement and briefly justify your new testcases in your submission document. REMINDER - your Lab 5 Test submission consists of ALL of your commits and push to GitHub, and you must have a separate commit and push for each question.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help