Social Network and Stakeholder Analysis †MyAssignmenthelp.com

Question: Discuss about the Social Network and Stakeholder Analysis. Answer: Introduction Information System is very much useful for any organization as it helps in safeguarding all the important data and give security to them. Information System also helps in reducing the redundant data and data search becomes quite easy. It also helps in storing large amount of data from and all the information can be made inter linked by connecting the data base with each other. The following is a web based application and how information system helps in gathering all the information about the doctors, patients and clinics. It also helps in connecting all the three with each other. Stakeholder Map Stakeholder Interest Impact Role Contribution System Developer Functionality and how the process goes on with the project Tries to develop the system from the very beginning and trying to implement all the required internal functions Internal stakeholder Creating all the required functional requirements and analyze all necessary components for the completion of the project so that it goes on smoothly. System Analyst Analyzes the system for better working Helps in making the system more user friendly and cost effective and try to make it run even with lowest requirements. Internal stakeholder Collects all the business requirements and tries to identify any major problem that might exist with the current system. Project Manager Main focus is on the quality of the project and time taken to complete the project and also to maintain the cost. Tries to create a working environment and help others to complete the task within the time limit and provide them with resources whatever needed. Also tries to sort out any differences if any between the employees. Internal Stakeholder Responsible for the communication with the project team members and tries to gather all the latest updates and send it back to the headquarters. Also listens to the problems and tries to provide all the resources that are required. Government Completion of the project by following rules and legislations Guides the project so that no law is broken External Stakeholder Pre-defined rules that the project manger and owner have to maintain in project lifecycle so no harm is brought to the state or nation Buyers They will try to get their hands on after the completion of the project and try to sell it to other vendors and promote it to users. There is no significant impact except of the promotion External Stakeholder Helps in the promotion for which many new customers will join the group. Users After the completion of the project, the users will use this application and try to enter their medical records. They will try to get as much information and give their feedback to the organization. External Stakeholder They will try to find out any flaws or system errors that they might face and give their suggestions as to make it much better. Tester They are responsible for testing the application to find its flaws. After the Flaws being found, they forward the message back to the team so that they can correct it. Internal Stakeholder They test the applications so that the users do not have to face any problem while using the application and also to make sure that there is no security flaws. Questionnaire Identification of Stakeholder: For the purpose of questioning, the patients, doctors and clinics will be shortlisted so that they can answer the questions that will be asked in the questionnaire session. Different Stakeholders have different needs that they seek from the system. For an example, the doctors want to access all the information about a particular patient but the patient may not want to share the same except his/her nearby doctors. Purpose of the Questionnaire: Through the whole questionnaire session, only a handful of questions will be asked to each of the stakeholders just to get a rough idea about the functionality of the system. The main purpose of conducting this questionnaire is to gather information from the stakeholders to make the system work much better. Use Case Diagram and Use Case Description Name Login and Register ID 1 Associated Actors Doctor Patient Description The new users need to set up their account and after the setup they can login via email and password that they have given to set up. Organizational Advantages Provides a better security with the administration so that fraud cases can be stopped. Frequency of use Regular Associative Use Case Contact and email verification Triggers The regular users would like to access all the functionalities that are present within the web application. Precondition Users should login via verified email and contact details. Post-condition After verification, the account is created and is saved onto the database. Exception Email id or contact number may be unreachable for some time being. Name Contact and email verification ID 2 Associated Actors Doctor Patient Description After registration, a verification link has been sent and a security code is sent to the provided number so to verify the account. Organizational Advantages Only the ones who have verified account can log in into the system. This makes the system safe and free from any fraud cases. Frequency of use Regular Associative Use Case None Triggers Needs to store all the verified email and number provided by the user. Precondition Both the assets should be active at the time of creation. Post-condition The email and contact number is registered Exception Due to some fault, verification link and security code is not being sent. Name Input health data ID 3 Associated Actors Doctor Description The doctors gives the necessary details about any individual. Organizational Advantages Better access of data Frequency of use Regular Associative Use Case Login Triggers The database is being updated by the doctor. Precondition The doctor should be a verified doctor in order to update any information. Post-condition The health data is saved Exception The system is unable to update the information. Name Restrict Data Access ID 4 Associated Actors Patient Description The patient can choose who is able to see his/her information from portal. Organizational Advantages Secure access of data Frequency of use Regular Associative Use Case Login Triggers Unauthorized users cannot access the data. Precondition The patient should have a verified account. Post-condition The data authorization is set Exception Due to some technical faults, it is unable to gather all the information. Name Access Health Data ID 5 Associated Actors Patient Doctor Description Patient and Doctor both wants to get an access to the health data. Organizational Advantages Doctors can access the data for different patients even if the patients is referred to some other clinic Frequency of use Regular Associative Use Case Restrict Data Access Triggers Only the authorized doctors can view the patients profile. Precondition Both Doctor and patient should have a verified account. Post-condition The access to data is granted Flow of Activities Actor System Doctor or patient request for a particular data User ID is collected. The system cross checks the given ID with the database to find a match. There may be many with similar names The users choses the most appropriate data. The system gathers information from all the clinics. The user access the data All the information are stored in temporarily over the cloud based technology. Exception Due to some technical fault, the system may not be able to reach out to the cloud services. Conclusion From the above, it can be concluded that information system is very much useful as it can help any organization to store huge amount of data and searching of data from the database also becomes quite easy. The development of the system will be more critical with the increase of database as it also needs to be interconnected for better working. The system should be made with proper planning because if anyone gets their hand on these databases, it would create a huge problem and privacy of the users will be at risk. Bibliography Caniato, M., Vaccari, M., Visvanathan, C., Zurbrugg, C. (2014). Using social network and stakeholder analysis to help evaluate infectious waste management: A step towards a holistic assessment. Waste Management,34(5), 938-951. Dahan, M., Shoval, P., Sturm, A. (2014). Comparing the impact of the OO-DFD and the Use Case methods for modeling functional requirements on comprehension and quality of models: a controlled experiment.Requirements Engineering,19(1), 27-43. Jha, P., Jena, P. P., Malu, R. K. (2014). Estimating software development effort using UML use case point (UCP) method with a modified set of environmental factors.International Journal of Computer Science and Information Technologies,5(3), 2742-2744. Lienert, J., Schnetzer, F., Ingold, K. (2013). Stakeholder analysis combined with social network analysis provides fine-grained insights into water infrastructure planning processes.Journal of environmental management,125, 134-148. Missonier, S., Loufrani-Fedida, S. (2014). Stakeholder analysis and engagement in projects: From stakeholder relational perspective to stakeholder relational ontology.International Journal of Project Management,32(7), 1108-1122. Nassif, A. B., Capretz, L. F., Ho, D. (2016). Enhancing use case points estimation method using soft computing techniques.arXiv preprint arXiv:1612.01078. Rhazali, Y., Hadi, Y., Mouloudi, A. (2014). Transformation method CIM to PIM: from business processes models defined in BPMN to use case and class models defined in UML.Transformation,13609, 9999213. Yue, T., Briand, L. C., Labiche, Y. (2015). atoucan: An automated framework to derive UML analysis models from use case models.ACM Transactions on Software Engineering and Methodology (TOSEM),24(3), 13.