Torkore Inc. (TI), a leading manufacturing company, recently purchased the Softrip system, an of- the-shelf package,...

 

Transcribed Image Text:

Torkore Inc. (TI), a leading manufacturing company, recently purchased the Softrip system, an of- the-shelf package, to implement a streamlined process supporting employee travel requirements in the company. The main focus of the implementation is on authorizing travel and reporting expenses. When an employee identifies a travel need, he uses Softrip to prepare a travel authorization request. The request specifies the destination(s) and the justification for the travel and an expense estimate for the trip in broad categories (air travel, ground transportation, meals, lodging, meeting fees, etc.). Once the employee has completed the request, he submits it through the system. The request is received first by the travel office, which will review it for technical correctness. If it is not technically correct, it will be sent back to the employee for review and resubmission. If the travel office finds no technical errors, the request will next move to the employee's immediate supervisor for his approval. If the amount of the requested travel expense exceeds an annually set limit, the authorization request will go to the divisional manager for additional review. If either the supervisor or the divisional manager rejects the request, they will inform the travel office and ask them to send a note of rejection with a justification to the employee. If, however, the authorization is accepted, the employee will move forward to book their travel. The actual travel booking is outside this process description but any expense incurred before the travel (such as flight reservation or prepaid hotel) needs to be recorded with the system. Once the trip has commenced, the same process continues: the employee can use a mobile device to specify travel After the trip has ended, the employee has up to two weeks to complete a final travel report. During this process, the employee may enter, timestamp, and justify new expenses and revise those submitted earlier in the process. Once the report is ready, the employee submits it using the system, which sends it to the travel office for technical review. If the travel office rejects the submission, the report is returned to the employee with clarifying questions. If the travel office accepts it, it will be sent to both the supervisor and the divisional manager simultaneously for approval. Only after both have responded will the travel office integrate the results. If they don't raise concerns, the travel report review results are sent to the employee for his final review. However, if there are concerns, the travel office initiates a formal expense review. The review itself is outside the scope of the regular travel process. Assignment Tasks Part 1 (20 marks) 1) Create a single comprehensive Use Case Diagram (indicating all actors and Use Cases) for Softrip. Part II (30 marks) 1) Write a fully developed use case description for the following Use Cases: a) Submit travel authorization request b) Record travel expense c) Conduct managerial review of a travel report Part III (20 marks) 1) Create a System Sequence Diagram for the Submit travel authorization request Use Case Part IV (30 marks) 1) Create a UI Storyboard for the Submit travel authorization request Use Case. Think about what the employee would need to see and do to complete the request and realize this use case. Grading factors: All models used in systems analysis have a purpose. That is, they have a specific goal or message that is to be conveyed to the reader via the model, it is important that your model clearly conveys this. Comprehensiveness: Does the model or set of models fully encompass the business problem? Are all relevant aspects of the business problem conveyed in the model(s)? Readability: Is it clear to the reader what the model represents? Can all parts of the model be easily deciphered? Is there redundancy in the model? Accuracy: Are aspects of the model such as relationships, multiplicity, cardinality, etc... correct? Is the notation used correctly? Are there modelling concepts being used incorrectly or are certain modelling concepts lacking when necessary? Is there consistency between models? Design quality: (Applies primarily to UML models) Does the system design make sense? Are there many foreseeable problems with the system design? Depending on the model, these grading criteria may be weighted differently. (ie. Readability may have a lower weight than the other criteria). Torkore Inc. (TI), a leading manufacturing company, recently purchased the Softrip system, an of- the-shelf package, to implement a streamlined process supporting employee travel requirements in the company. The main focus of the implementation is on authorizing travel and reporting expenses. When an employee identifies a travel need, he uses Softrip to prepare a travel authorization request. The request specifies the destination(s) and the justification for the travel and an expense estimate for the trip in broad categories (air travel, ground transportation, meals, lodging, meeting fees, etc.). Once the employee has completed the request, he submits it through the system. The request is received first by the travel office, which will review it for technical correctness. If it is not technically correct, it will be sent back to the employee for review and resubmission. If the travel office finds no technical errors, the request will next move to the employee's immediate supervisor for his approval. If the amount of the requested travel expense exceeds an annually set limit, the authorization request will go to the divisional manager for additional review. If either the supervisor or the divisional manager rejects the request, they will inform the travel office and ask them to send a note of rejection with a justification to the employee. If, however, the authorization is accepted, the employee will move forward to book their travel. The actual travel booking is outside this process description but any expense incurred before the travel (such as flight reservation or prepaid hotel) needs to be recorded with the system. Once the trip has commenced, the same process continues: the employee can use a mobile device to specify travel After the trip has ended, the employee has up to two weeks to complete a final travel report. During this process, the employee may enter, timestamp, and justify new expenses and revise those submitted earlier in the process. Once the report is ready, the employee submits it using the system, which sends it to the travel office for technical review. If the travel office rejects the submission, the report is returned to the employee with clarifying questions. If the travel office accepts it, it will be sent to both the supervisor and the divisional manager simultaneously for approval. Only after both have responded will the travel office integrate the results. If they don't raise concerns, the travel report review results are sent to the employee for his final review. However, if there are concerns, the travel office initiates a formal expense review. The review itself is outside the scope of the regular travel process. Assignment Tasks Part 1 (20 marks) 1) Create a single comprehensive Use Case Diagram (indicating all actors and Use Cases) for Softrip. Part II (30 marks) 1) Write a fully developed use case description for the following Use Cases: a) Submit travel authorization request b) Record travel expense c) Conduct managerial review of a travel report Part III (20 marks) 1) Create a System Sequence Diagram for the Submit travel authorization request Use Case Part IV (30 marks) 1) Create a UI Storyboard for the Submit travel authorization request Use Case. Think about what the employee would need to see and do to complete the request and realize this use case. Grading factors: All models used in systems analysis have a purpose. That is, they have a specific goal or message that is to be conveyed to the reader via the model, it is important that your model clearly conveys this. Comprehensiveness: Does the model or set of models fully encompass the business problem? Are all relevant aspects of the business problem conveyed in the model(s)? Readability: Is it clear to the reader what the model represents? Can all parts of the model be easily deciphered? Is there redundancy in the model? Accuracy: Are aspects of the model such as relationships, multiplicity, cardinality, etc... correct? Is the notation used correctly? Are there modelling concepts being used incorrectly or are certain modelling concepts lacking when necessary? Is there consistency between models? Design quality: (Applies primarily to UML models) Does the system design make sense? Are there many foreseeable problems with the system design? Depending on the model, these grading criteria may be weighted differently. (ie. Readability may have a lower weight than the other criteria).