Identifying and Engaging Stakeholders †Free Samples to Students

Question: Discuss about the Identifying and Engaging Stakeholders. Answer: Introduction: The introduction statement has been relevant to the questionnaire supplied. This statement has been explaining the reason behind the development of the questionnaire. The statement is shown below. In order to determine the systems or the solutions needed from the project, the set of questions are made. The basic objective of the activity is to recognize the functionalities. They have been helpful as the suggested application is taken into consideration. These questions are developed from the expertise of technical consultants. This is helpful to understand the detail perquisites as proposed. There have been ten particular questions to deliver the general comments. The responses could be anonymously and the respondents would possess the option to provide the contact information. Thanks to everyone, for taking your time and responding to the questions Is there any scope to extend the duration of treatments as required? Are you all satisfied enough with surfing the site? Do you have enough trust on Headspace? In order to access the sites have your decisions been given priority? Has there been any type of functionalities needed within the system? Can you mention some of the functionalities needed in the system? Has the system of the online payment been useful? Have there any logging-in and registration options provided within the system? Which individuals can authorize the system and what must be their departments? During the development is there any requirement to extend those funds? The use case diagrams and descriptions: Description Actors Patients It contains data of all the mental patients (Abdullah Ibrahim, 2013). Organizational service providers Provide service to the hospitals and clinics. Healthcare professionals. Providing services of treatment to all the patients (Seidl et al., 2015). Admin Managing every kind of staffs, business function stakeholders and the systems designed newly. System use case Register Stating every kind of users to register with the system (Almutairi et al., 2013). Login The user is able to login to access into the system to get services. Headspace home page The patient or the user must retrieve the data using the use case above (Almutairi et al., 2013). Managing Headspace account The user or the patient has been able to control the account effectively. Managing privacy, security, access The user is able to control or customize or manage the privacy and security of their accounts (Seidl et al., 2015). Medical treatments It has been indicating that the user has been able to request every kind of medical treatment. Hospital services It has been indicating the offers to gain every organizational service at the organization (Abdullah Ibrahim, 2013). Mental health record The guardian of the patent or the user might be able to make requests to different medical professional. Record of other users This points out to the restricted records that are needed to be accessed by the other users (Abdullah Ibrahim, 2013). Logout This indicates that the user could exit from the system. Description of the fully developed Use Case: The fully functional designing of the use case is completed. Next the actors and terms are needed to be discussed in details. All the terms are analyzed in the above three sectors with the in-depth analysis. It is done through identifying the roles of each of them. The use cases included are the controlling the Headspace homepage, security and privacy, login, registration, medicals services and hospital services. In this project, the registration: is chosen as the most important use cases. It has been helping all other kinds of users to go through the registration process. Thus they could access within the service. As it is not present, the user would become unable to receive the credentials of logging-in. Thus it cannot explore within the system. All the actors mentioned above, such as the service providers, patients, professionals and other are bound to go through the process of registration. Conclusion: At first the stakeholder map is demonstrated in the report. It has balanced and weighed all the demands that are competing at Headspace. It has also met the perquisites of the given project. The questionnaire has been useful to identify the extra information. It has been including the on-goings, challenges and the numerous approaches towards the system to solve the challenges. The report has also described the various use-cases such as the registration, logging-in, logging-out and others that have been considering the actors like the professionals, service providers and patents. Here the registration is identified to be the most useful use case. The reason behind this is that all the actors are needed to go through that at any point of time. References: Abdullah, M. R., Ibrahim, R. (2013). GenSRS: Generation of Software Requirements Specification From Use case diagram and Sequence Diagram. InProceedings of the Second Intl. Conf. on Advances in Computer and Information Technology--ACIT. Ajaykumar, S. D., Prasad, M. S. (2014). Transforming data flow diagram to use case diagram.International Journal of Management, IT and Engineering,4(1), 561. Almutairi, S., Abu-Samaha, A., Bell, G., Chen, F. (2013, October). An enhanced use case diagram to model Context Aware Systems. InScience and Information Conference (SAI), 2013(pp. 270-274). IEEE. Hazra, R., Dey, S. (2014). Consistency between Use Case, Sequence and Timing Diagram for Real Time Software Systems.International Journal of Computer Applications,85(16). Hossain, S., Karim, R., Sarma, D. (2014). Designing a Task Management System for a Banking System by Combining Relational Model with Use Case Diagram.International Journal of Computer Applications,108(8). Kumar, B. S., Krishnamurthi, I. (2016). Improving User Participation in Requirement Elicitation and Analysis by Applying Gamification Using Architects Use Case Diagram. InProceedings of the 3rd International Symposium on Big Data and Cloud Computing Challenges (ISBCC16)(pp. 471-482). Springer International Publishing. Poplawska, J., Labib, A., Reed, D. M., Ishizaka, A. (2015). Stakeholder profile definition and salience measurement with fuzzy logic and visual analytics applied to corporate social responsibility case study.Journal of Cleaner Production,105, 103-115. Seidl, M., Scholz, M., Huemer, C., Kappel, G. (2015). The Use Case Diagram. InUML@ Classroom(pp. 23-47). Springer International Publishing. Singh, A., Sharma, E. S. (2014). Functional Test Cases Generation Based on Automated Generated Use Case Diagram. Speller, S. (2016). Identifying and Engaging Stakeholders.The Innovation Tools Handbook, Volume 1: Organizational and Operational Tools, Methods, and Techniques that Every Innovator Must Know, 177.