ASAD Project Report
- 1. MSIS 5653 - ADVANCED SYSTEM ANALYSIS AND DESIGN Final Project Deliverable (P5) Physician - Patient Relationship Management Tool Built in Collaboration with ProFee & Riipen Team Cowboy: Ashish Kumar (A20102781) Ishan Malpotra (A20104861) Souparna Lodh (A20101631)
- 2. 2 Table of Contents 1. Executive Summary…………………………………………………………………….3 2. Problem Analysis………………………………………………………………………..4 a. Fishbone Diagram………………………………………………………………4 b. Empathy Map Diagram…………………………………………………………5 c. Business Needs…………………………………………………………………5 d. Business Constraints…………………………………………………………...6 e. System Architecture…………………………………………………………….6 3. Requirements and Design Specifications…………………………………………….7 a. Physical Dataflow Diagram…………………………………………………….7 b. User Interface Design…………………………………………………………..7 c. Database Design………………………………………………………………11 d. Data Dictionary………………………………………………………………...12 e. Use cases………………………………………………………………………16 4. Working Code / System URL………………………………………………………...17 5. Quality Assurance……………………………………………………………………..18 a. Test Plan………………………………………………………………………..18 b. Test Cases……………………………………………………………………..19 6. Project Management…………………………………………………………………..22 a. Project Management Spreadsheet…………………………………………..22 b. Gantt Chart……………………………………………………………………..25 7. Problem Solving Recommendations………………………………………………...25 8. User Manual……………………………………………………………………………26 9. Prototype………………………………………………………………………………..26 10.Problem Solving Techniques…………………………………………………………33 a. Actual Methodology Used…………………………………………………….33 b. How the System could’ve been managed better if we were not students.33 11.Reflections from the Project…………………………………………………………..33 a. Technical Learning…………………………………………………………….34 b. Soft Skills Development……………………………………………………….34 12.Appendix………………………………………………………………………………..34 a. Client’s Details…………………………………………………………………34 b. First Interaction with the Client……………………………………………….35 c. Questionnaires…………………………………………………………………35 13.Conclusion……………………………………………………………………………...37
- 3. 3 1. Executive Summary In the fifth and final phase of the project deliverable, we have to deliver the prototype of our project based on the requirements gathered and analysis done in the former phases. In our earlier meetings with our client (especially the CEO and CTO of Pro Fee LLC), we discussed to finalize the requirement analysis, finding out the perfect solution for the interface design and database design, etc. They suggested us the solutions which they felt were great for the system we were trying to build. We suggested whatever we felt was the most feasible option according to us and we arrived on a mutual solution finally. The Requirement gathering, Analysis, Database Design and Interface Design faces were done in the earlier phases of the project. In the fifth and final phase of our project, we implemented what we had discussed on to build a system according to the client’s requirements. We are developing a Customer Relationship management (CRM) system to fit our client’s needs. As there was not any CRM tool present for Healthcare domain, we decided to build it from scratch. In our CRM system, there are three main components- Front end, Web security layer and Back end Database. This report contains everything whichever was required to build this system such as Requirement Analysis phases, Physical dataflow design, Database design, User interface design and Test cases, Working code, Prototype and the best recommended solutions for the same.
- 4. 4 2. Problem Analysis At present, ProFee LLC. doesn’t have any tool or software to find out if a Physician is already stressed out or not. Ultimately, they are trying to find out a way to reduce physician burnout. With the CRM tool, they want to improve the experience of physicians with patients, make medicine a great environment to work in, and reward/recognize employees for doing the right thing for the right reasons. The Analysis of this problem was done with the help of Fish-bone diagram as well as the Empathy Map Diagram as mentioned below. 2. a. Fish Bone Diagram (or) Ishikawa Diagram The fishbone diagram mentioned above explains the different ways or the different components of our analysis of the problem. The components shown in the blue boxes such as “Security Login”, “Client Survey”, “Employee Level Login”, “Patient CRM Feedback Form”, “Word of mouth CRM” and “User Interface” are the components which would help in arriving at the final solution which is mentioned as “CRM for Healthcare” in the above diagram.
- 5. 5 2. b. Empathy Map Diagram The empathy map diagram for the problem Analysis purpose is mentioned below. This diagram mentions the components which are required in the final system in a better visualized format as given below in the empathy map diagram. 2. c. Business Needs The CRM tool needed to be developed which would do the following things: 1. A Database to store the details about the patients, store the patient’s feedback. 2. A website where the patients can fill up their details and their feedback. 3. A webpage where the physicians can see their details and feedback from the patients. 4. An interface which can reduce the physician burnout.
- 6. 6 2. d. Business Constraints A few of the high level business constraints faced in the start of the project are mentioned below: 1. A system which needs to be developed shouldn’t be dependent on any particular platform, so that it can run on any kind of platform. 2. The programming code written for this system (or) tool should be flexible and made in such a way that it should run on any tool. 2. e. System Architecture The system contains three main components as mentioned below: 1. Front End – Which we are developing in Java and ASP.Net. Front end will be responsible for gathering data from the User or the web services and displaying the data to the user. 2. Web services – This is responsible for security, business logic and accessing data from the database. 3. Database – We are going to create the database in Microsoft SQL server. We are going to store all the details of Patients and Physicians and the user complaints and feedbacks in different Tables.
- 7. 7 3. Requirements and Design Specifications The requirements and design specifications are mentioned below with the help of the various diagrams given below. 3. a. Physical Dataflow Diagram The Physical dataflow diagram shows the data flow through all the components in a virtually physical manner. The physical dataflow diagram is mentioned below for the same. 3. b. User Interface Design The user interface design as specified by the client is mentioned below in the following diagrams. Below mentioned six diagrams show the interface which the client requested us to work on according to their specific requirements.
- 8. 8 Fig 1. Beginning screen of a Physician entering his/her personal details Fig 2. Physicians entering their personal details
- 9. 9 Fig 3. Physicians entering their complaints Fig 4. Summary of the complaints entered for the physicians
- 10. 10 Fig 5. Screen of entering project details Fig 6. After entering all the details, this is the employee Dashboard
- 11. 11 3. c. Database Design The backend database design is mentioned below for the system built. All the tables are in 3NF and the partial and transitive dependencies have been taken care of. The backend database has been created in Microsoft SQL Server.
- 12. 12 3. d. Data Dictionary The data dictionary for the above database design is mentioned below. Every table has the column name and the datatype in which it is defined. Table: Company Table: Usertable Column Name Datatype User_id Integer User_name Varchar(255) User_passwd Varchar(255) Email_address Varchar(255) Company_id Integer Table: Role Column Name Datatype Role_id Integer Role_name Varchar(255) Column Name Datatype Company_id Integer Company_name Varchar(255) Company_domain Varchar(255)
- 13. 13 Table: Userrole Column Name Datatype User_id Integer Role_id Integer Table: Survey Column Name Datatype Survey_id Integer Survey_name Varchar(255) Table: Question Column Name Datatype Question_id Integer Question_name Varchar(255) Survey_id Varchar(255) Question_Text Varchar(1024) Table: Answer Column Name Datatype Answer_id Integer Answer_name Varchar(255)
- 14. 14 Question_id Integer Answer_text Varchar(1024) Table: Surveyanswer Column Name Datatype User_id Integer Answer_id Integer Survey_answer_date DateTime Table: Complaint Column Name Datatype Complaint_type Varchar(255) Table: Usercomplaint Column Name Datatype User_complaint_id Integer User_id Integer Complaint_type Varchar(255) Complaint_date DateTime Complaint_text Varchar(1024)
- 15. 15 Table: Project Column Name Datatype Project_id Integer Project_name Varchar(255) Project_description Varchar(1024) Owner_user_id Integer Project_start_date DateTime Estimation_completion_date DateTime Table: Activity Column Name Datatype Activity_id Integer Project_id Integer Activity_name Varchar(255) Activity_description Varchar(255) Is_completed Varchar(10) Table: ActivityUsers Column Name Datatype Activity_id Integer User_id Integer
- 16. 16 Table: Usercomplaint Column Name Datatype User_complaint_id Integer User_id Integer Complaint_type Varchar(255) Complaint_date DateTime Complaint_text Varchar(1024) 3. e. Use Cases Several use cases were written to identify the requirements in a better way describing the behavioral modelling of this project.
- 17. 17 The use cases for the above diagram are described below: • Physicians registers their complaint in the website. • Physicians view the feedback which were put in by the patients. • Patients can also register their complaints about the physicians. • Patients can give feedback of the physicians. • Patients will fill information. • Patients can rate the physicians. • Admin’s job is to maintain the website. 4. Working Code / System URL The working code of both the front end prototype and the database design is mentioned in the table given below. The table contains the link of all the required working components of this project. Tasks Location Working code for local desktop version https://drive.google.com/drive/folders/16dHrT kFekxGhTzOqDyLAbWDybXPFQf1W Database files https://drive.google.com/drive/folders/1xfEcM Zl3pzKDNy0l-NV41OodiCgscGiy Project Management sheets https://drive.google.com/drive/folders/1Wq4v LHY2WpDKIFtfFSPg4qh5_cJ_4YO6?usp=shar ing
- 18. 18 5. Quality Assurance Quality assurance checks and methods were performed on this project to check if the requirements specified were fulfilled according to the client’s needs or not. To check these, Test Plan and various test cases were drafted and executed accordingly. 5. a. Test Plan Introduction: This document is a test plan for the Physician-Patient Relationship Management Tool. It explains the testing strategy and the approach that the testing team will use to validate the quality of this project prior to the release. The focus of Physician-Patient Relationship Management tool is to make it easier for the physicians to register their complaints and for the patients to give their feedback. Below are the features of this system: a) Physician/Patient registration b) Register Complaints c) Submit feedbacks d) Complete surveys e) View complaints f) View Feedbacks Equipment Requirements: Windows OS, ASP. Net, SQL Server Test Tool: Manual testing only
- 19. 19 Staffing Responsibilities: Ashish Kumar: Creating test plan Ishan Malpotra: Creating test cases Souparna Lodh: Executing test cases Consolidation of the results is done by all of us together. Training: Tester must be familiar how the system works overall. He should also be familiar with the expected outputs for the respective inputs from the user. Features to be tested: a. User Registration b. User login c. Complaint file d. View Complaint e. Fill Surveys Test Deliverables: a. List of test cases executed and respective results. b. Test data 5. b. Test Cases Several test cases for the project are mentioned below. We have listed down five different test cases to test the functionality of the web based interface built using ASP .NET and the backend built using Microsoft SQL Server.
- 20. 20 Test Case Id 1 Test Description User registration Function to be tested User’s info is successfully stored in the database Environment Windows 10 Test Execution Enter user’s info Expected Result User’s information should be saved correctly in the database and should be retrieved accordingly Actual result To be tested Test Case Id 2 Test Description User login Function to be tested Validation of user login Environment Windows 10 Test Execution Enter username and password Expected Result If the user is not registered, he/she won’t be able to login with incorrect credentials Actual result To be tested
- 21. 21 Test Case Id 3 Test Description Complaint file Function to be tested Submission of complaint to the correct database Environment Windows 10 Test Execution Submit the complaint Expected Result The registered complaint should be stored successfully in the respective database Actual result To be tested Test Case Id 4 Test Description View Complaint Function to be tested Viewing the complaint Environment Windows 10 Test Execution View the complaint for the respective physicians Expected Result The correct complaints respective to the physicians logged in should be visible Actual result To be tested
- 22. 22 Test Case Id 5 Test Description Fill Surveys Function to be tested Incomplete surveys should be visible to the users Environment Windows 10 Test Execution Only the incomplete surveys should be visible for the users and they should be able to fill it Expected Result The filled surveys should be submitted successfully to the database Actual result To be tested 6. Project Management To complete a project on a timely basis, the project and its resources needs to be managed properly. Hence, we’ve made use of the Gantt Chart and the spreadsheets to keep a count of the same. 6. a. Project Management Spreadsheet The project management spreadsheet mentioned below tracks the work of every resource in the team and the dates corresponding to it. List of Tasks Duratio n Start Date End Date Resources Involved Feasibility Phase 31 18-Jan 18-Feb Executive Summary 1 18-Jan 19-Jan David & Dan Current Problem 11 19-Jan 30-Jan David, Dan, Ashish, Ishan, Souparna
- 23. 23 System Objectives 3 30-Jan 2-Feb David, Dan, Ashish, Ishan, Souparna Solution Description 8 2-Feb 10-Feb Ashish, Ishan, Souparna Resources Needed 2 10-Feb 12-Feb Ashish Cost Estimate 3 12-Feb 15-Feb Ishan Technical and functionality 3 15-Feb 18-Feb Souparna Analysis Phase 12 19-Feb 3-Mar Executive Summary 1 19-Feb 20-Feb Souparna Revised Cost 1 20-Feb 21-Feb Ashish Revised Schedule 1 21-Feb 22-Feb Ishan Behavioral Model 3 22-Feb 25-Feb Ashish, Ishan, Souparna Dynamic Modelling 2 25-Feb 27-Feb Ashish Data Modeling with ERD 2 27-Feb 1-Mar Ishan Object Modeling with UML 2 1-Mar 3-Mar Souparna Design Phase 20 4-Mar 24-Mar Executive Summary 1 4-Mar 5-Mar Souparna Alternate design Summary 2 5-Mar 7-Mar Ashish System Architecture 4 7-Mar 11-Mar Ishan
- 24. 24 Data Flow Diagram 4 11-Mar 15-Mar Ashish, Ishan, Souparna User Interface Design 4 15-Mar 19-Mar Ashish, Ishan, Souparna Test Plan 5 19-Mar 24-Mar Ashish, Ishan, Souparna Implementation Phase 28 24-Mar 21-Apr Executive Summary 1 24-Mar 25-Mar Souparna Problem Analysis 2 25-Mar 27-Mar Ashish Requirement Specification 2 27-Mar 29-Mar Ishan CRM Tool Code 14 29-Mar 12-Apr Ashish, Ishan SQL Database Implementation 4 12-Apr 16-Apr Ishan, Souparna Quality Engineering & Assurance 4 16-Apr 20-Apr Ashish, Souparna Problem Solving 1 20-Apr 21-Apr Souparna User Manual 2 22-Apr 24-Apr David, Dan, Ashish, Ishan, Souparna Project Report 3 24-Apr 27-Apr Ashish, Ishan, Souparna
- 25. 25 6. b. Gantt Chart Gant Chart tracks the project activity along with the time to keep a track of the ongoing activity and blockers, if any. The Gantt Chart for this project is given below. 7. Problem Solving Recommendations Client specified requirements had a lot of limitations which we had to overcome. The limitations are given below: • There was no existing CRM tool present for the healthcare domain. • Client wasn’t sure of the softwares and the interface to be used for building the system. • Client didn’t have any sufficient financial resources to fund the project. These limitations were overcome by the following recommendations
- 26. 26 • We built a CRM tool from the scratch for the healthcare domain to solve the problem. • We suggested various tools and technologies to the client to build the system on and ultimately agreed on the one which our client was most convinced with after finding it feasible for us. • We made use of the freeware languages, tools and technologies to make sure that the system is cost effective and doesn’t need to be invested in unless client is convinced with the prototype. 8. User Manual A video has been uploaded in the below mentioned location which explains the complete usage of the application step by step. https://drive.google.com/file/d/1zlaxa5UC0giLlRF8Aa9SCetMGRkGRc02/view?ts=5ade 8890 9. Prototype The prototype was developed in two different phases. The backend was developed in Microsoft SQL Server and the Front-end was developed using ASP .NET in the tool Microsoft Visual Studio 2017. The screenshots of the same in the order as mentioned in the requirements are given below:
- 27. 27
- 28. 28
- 29. 29
- 30. 30
- 31. 31
- 32. 32
- 33. 33 10. Problem Solving Techniques Various problem solving techniques were used in this project to arrive at the optimum solution. Some recommendations were taken from the client and some were suggested by us to them as well. We took some suggestions from the persons who actually worked on building CRM tool earlier as well. 10. a. Actual Methodology Used The Actual methodology used in this project was a mini sprint model in which the requirement gathering, analysis, designing and the implementation was done at the same time in a parallel manner. The client and the working team worked on it together by having weekly stand up call either on every Tuesday or on every Thursday. 10. b. How the System could’ve been managed better if we were not students If we would not have been students, then the company we would have been working for would have adopted a proper agile (or) waterfall model instead of a mini sprint model. Adopting an agile methodology or waterfall model would have taken a lot of resources and the cost would’ve gone high as well. 11. Reflections from the Project One gets to learn a lot by doing a project and our team learnt a lot from this project as well. Our learning was not just defined to the technical processes whereas we improved our soft skills as well as this was our first interaction with an American based Client after joining Oklahoma State University.
- 34. 34 11. a. Technical Learning We three had technical expertise with the SQL language and but all of us were not that well versed with coding in ASP .NET and Java. We gained considerable knowledge on the web security, building a front end user interface and the database design for a real time project. By this project, we gained real time experience in Microsoft SQL Server, Visual Studio 2017, ASP .NET, Java, etc. which would improve our profile a lot. 11. b. Soft Skills Development Apart from the technical learning, our soft skills and the ability to communicate with the client improved a lot as well. We did our project for a real time client from United States of America with the help of our Professor Dr. Nikunj Dalal and a company named Riipen which connects the industry with the students. Having a weekly stand up call kept us both in pace with the project and improved our communication as well as project management skills as well. Overall, this has been a great learning experience. 12. Appendix 12. a. Client’s Details We worked for a company named Pro Fee LLC from Massachusetts. We got in touch with this company with the help of a company named Riipen. The client details are mentioned below: David Batulis CEO, ProFee LLC. (603)746-1278 dbatulis@gmail.com
- 35. 35 12. b. First Interaction with the Client Our first interaction with the Client involved the talk over the email and a video call over Zoom in which we discussed about the client’s requirements and signing the mutual NDA document. The screenshot of the same is mentioned below: 12. c. Questionnaires Most of our questions were cleared over the weekly stand-up call itself. However, there were some questions which were discussed over the email, if required and the screenshot of the same is mentioned below.
- 36. 36
- 37. 37 13. Conclusion The prototype of the system has been created successfully as per our client’s requirements. We developed a website and a database to be coupled with web security. Apart from the system, a video has been uploaded which will act as the user manual to help the user understand the process and flow of the system.