CIS 5307 Final Project This is the final part of your CIS 5307 project. In this part, I expect you to provide a report that includes many aspects about the Professional and Scientific Staff Management (PSSM) you have been exposed to at the beginning of semester. Keep in mind that this submission is for most of the part a compilation of the assignments you have done throughout the semester. Make sure that your report looks organized professional. Your report must include the following (Point12 should be attempted; otherwise, a straight 50 mark deduction): Additionally, I expect you to look at existing research (e.g. research papers) related to your case to help you support your answers. Your report must include the following: 1. Identify and list the requirements for this project. Categorize these into functional requirements and non-functional requirements. 2. Describe the business value provided by this project. Categorize these as tangible and intangible benefits. 3. Identify and list the project constraints. 4. Identify and list the risks associated with the project. 5. What software development methodology do you recommend for the project? Why? 6. Identify and list the Use Cases and associated Actors for the project. 7. Draw the Use Case Diagrams and Activity Diagrams for the project. Additionally, please provide. Use Case Descriptions (see Chapter 4 for the proper format) for each Use Case. 8. Draw the Class Diagram for the project. List any assumptions you make. The classes should contain meaningful attributes and operations (methods). Show the relations between the classes. 9. Propose the hardware and software needed to accomplish the needs of the project. 10. Drawing on the design principles presented in the text (e.g., Chapter 10), describe the features of the user interface that will be most important to: a) experienced users, and b) novice users. 11. Develop a set of guidelines that can help a project team to design and select the most appropriate interface evaluation technique for the case. 12. Suggest a physical architecture design for the project, and portray it with a deployment diagram. This project’s final report is the combination of all of the project assignments that you have already submitted. After accommodating/including my feedback on your project assignment submissions you can just club/combine them in a single document. I think from the below question, from 1 to 11, you might have already covered your project assignments, so you can use them in this report; again, make sure you have incorporated my feedback for each of your project assignments prior to pasting it into your report. So, yes, you are already done with most of the topics of your report. However, please see the following requirements to double-check if you have missed anything. There are some additional tasks (see point 12) than your previous project assignments that you have to do for this final project report. So, please pay attention to the following requirements. Please submit the entire report in a single word document file. (No separate multiple files, no zip files, and hand drawn submission). Format of doc file:- On the first cover page, mention the course name, number, full name, semester, university name, department name, degree major, and professor’s full name. Font style Times New Roman, font size 12 pt for text, use headings/subheadings wherever necessary (14pt font size), keep the text-justify aligned wherever necessary These previous Project assignments are attached below in the correct order. PA 1 Grade with feedback: 89/100, Thank you for submitting this assignment, and I appreciate your efforts; please see below suggestions that you can accommodate in your final report at the end of the semester:- Instead of writing FRs like:- “Validation system of staffing.” This is one example. We write FR like:- “The system should be able to validate staffing requests submitted by clients.” “The system should be able to access the licensure, availability, and request history.” The lecture notes/help videos and textbook have this format. Also in tangible values, we write like:- “The system reduces manual effort in validation by 10% reduction in work hours.” We make tangible values with approximate qualitative measures in values. Also, please read the case again and identify a few more use cases and actors, as you missed the client as an actor. This is important as you might need this information for the next assignment. I hope all these help with your final report. All the best. PA 2 with grade and feedback: 94/100 , Overall, the attempts look good; however, please revisit Chapter 4,5 or the PPTs for the correct use case notaitons, like for actors, start, and stop of activity diagrams. I hope this helps. All the best. PA 3 with grade and feedback : 100/100, Everything looks okay. Please try to use some database related classes as well in the class diagram. All the best.