Information System Assignment: Case Study Analysis on Australian Labs
Question
Task: Australian Labs provides lab testing services for a variety of clients, mostly doctors’ offices and other small medical businesses throughout the country. Clients send test vials containing blood samples or other test requests to Australian Lab’s testing center, where the requested tests are performed, after which the results are sent back to the clients via fax. Jim Larsen, the head technician in the testing facility at Australian Labs, has approached you for help with the company’s outdated inventory tracking system. Business has picked up recently, and the turnaround for clients’ requested tests has been lengthening. To make matters worse, the lab technicians are seldom able to give customers an answer regarding where their requests fall in the testing queue or how long they can expect the turnaround to be. Much of this stems from an old, mostly paper-based inventory tracking system, which includes hand written labels put on each of the incoming test vials and a logbook with entries made for each vial at each stage of the testing process. Jim would like to streamline the inventory tracking process with updated information systems that uses barcodes and a modern database to keep track of customer test requests and the accompanying vials. He would like to enable technicians to provide accurate status updates and turnaround estimates, and generally shorten the turnaround time for test requests.
You need to identify all functional and non-function requirements for the development of stated Inventory Tracking Information System. After an initial analysis, you make the following estimations.
You will use these data as a part of your initial cost benefit analysis.
For Project Cost Benefit Analysis assume discount rate to be 10%. Total development cost (one time cost) is $80,000.00. Assume recurring cost to be $25,000.00 per year.
Answer
Introduction
The purpose of this report is to analyse the system requirement of the Australian Labs and to model the system requirement in the traditional system analysis and object-oriented system analysis. The requirement is based on the requirements of the system that is serving the medical tests to the local medical representatives and the doctors. These are the customers those will be interacting with the system and the system will allow them to perform relative cases. This document highlights the critical use cases, context level diagram, data flow diagrams, ERD, CRUD, Data elements, prototype design of the website, and the detailed contribution of each members in the group.
Critical Use Cases
Following are the critical use cases those needs to be considered while developing the system:
Registration: The database should allow the customers to register into the system for availing the services being offered by Australian Labs. This use case will be triggered when the primary actors (doctors and the local medical business owners) accesses the zsystem or the website online. The secondary actor in this system will be the admin that will be approving the customers for being registered into the database. The exceptions in this case are that the user must not have an existing account in the system. This use case includes personal details and the bank details those are necessary cases for the database to register a user.
Login: All the actors of the system must have to login into the system. The database must have their login details and account existing for allowing them to access the website. The [primary actors for this use case will be Customers and the head technician who will be working as the admin of the system. Inventory: The inventory use case includes Vail no, Type of test, and delivery date. The primary actor of this use case will be the head technician who will be labelling the samples collected from the users. The exclusion in this case is that the other actors of the business process must have collected the sample and updated into the system for the samples and other details.
Test results: The customers will receive the results after the testing is completed. The head technician will be the primary actor of the system that will be sharing the results of the tests with them. This includes the overall report of the tests and sample collection and the results of the tests.
Use cases
Figure 1: Use case diagram
(Source: Created by the author)
Context diagram
Figure 2: Context diagram
Source: (Created by the author)
The above diagram represents the context level diagram of the website of Australian labs. The different business processes includes the sample collection, inventory, customers, head technicians, and the results. The system will allow the different actors to accomplish these different processes using the system. The data and information related to all the processes will be stored and processed using database. It can be seen that the system will allow to keep the track of the inventory related details, sample related details, head technicians details, and the customer related all the information.
Level 0 DFD
Figure 3: Level 0 DFD
(Source: Created by the author)
ERD
Figure 4: ERD of the RME Inc.
(Source: Created by the author)
Data elements
Data entity Data elements
|
Data entity |
Data elements |
|
Customer |
cust.ID, TestID, SampleID, Name, Add, Contact |
|
Technician |
EmployeeID, CustomerID, Name, Add, Contact |
|
Payment |
Transactionid, paymentAmt, paymentID, paymentDate |
|
Sample |
SampleID, CustomerID, Date, Testtype |
Prototype
Contribution
|
Student ID and name |
Week |
Roles and the responsibilities |
|
1st Group member |
1 |
Selection of the team members was completed |
|
2 |
We were assigned with the case |
|
|
3 |
Arranged meeting with the other team members where I tried to motivate and lead them in right direction |
|
|
4 |
We agreed on doing the online research and the academic guidelines revision for assuring that we follow all the guidelines. We also took help from the youtube, google scholar, IEEE, and other open sources where we did get many information and guidance over the UML designing and prototyping |
|
|
5 |
After taking the important points we further proceed with the project and delivered it according to the plan. |
|
|
Student ID and name |
Week |
Roles and the responsibilities |
|
2ndGroup member |
1 |
Random selected members were divided into groups and we were allotted with the group names by the subject coordinator. Project work is also assigned to each of the group members |
|
2 |
A common group meeting is held with team members where the system related specifications where discussed. A regular meeting with the supervisor was also arranged. |
|
|
3 |
A meeting with the other team members representing as the clients was also arranged in which some requirement related queries were made. |
|
|
4 |
The field of the research and the sources were selected with the group members so that we can stick to the topic and proceed accordingly. |
|
|
5 |
Meeting with the supervisor is again arranged for having clarity over the system requirement. |
|
Student ID and name |
Week |
Roles and the responsibilities |
|
3rd Group member
|
1 |
The client details or the case and the group details were informed to us. No one was selected as the leader as there was none and we had to work in a group for handling the project activities. The behaviour and the deliveries of the individuals will be representing the leadership qualities and contribution towards the project. |
|
2 |
The information was exchanged with each of the team members regarding the deliveries of the project that was needed to make it good. |
|
|
3 |
The time table for working together using online medium or platform was set and informed to all the team members |
|
|
4 |
The online research was required for performing the project and that was done after we all decided to start the work |
|
|
5 |
After finalising the project case and the designs for the system, we proceed further with the project. |
Conclusion
It can be concluded that the above requirement analysis presents a sophisticated idea over the functional and non-functional requirements of the system those are considerable for the management and delivery of the assignment. It is necessary that the above considerations of the models and designs are considered to make sure that the system being developed for the Australian Labs meets or exceeds the needs and requirements of the end consumers. The above report presented the different use cases as per the case including the business processes and the database design that can be used as the plan for delivering the final website that can handle these business processes. The user interface principles were applied while developing the prototype of the system and it demonstrates the appearance of the system.
Bibliography
Dennis, A., Wixom, B.H. and Roth, R.M., 2018. Systems analysis and design.John wiley& sons.
Mollalo, A., Alimohammadi, A., Shirzadi, M.R. and Malek, M.R., 2015. Geographic information system based analysis of the spatial and spatio temporal distribution of zoonotic cutaneous leishmaniasis in Golestan Province, north east of Iran.
Zoonoses and public health, 62(1), pp.18-28.
Pedrycz, W., 2016. Granular computing: analysis an.d design of intelligent systems. CRC press.
Wildavsky, A., 2018. Policy analysis is what information systems are not. In The art and craft of policy analysis (pp. 7-23). Palgrave Macmillan, Cham.
Yandell, B., 2017. Practical data analysis for designed experiments.Routledge.
