DUY TAN UNIVERSITY INFORMATION TECHNOLOGY SYSTEM INTEGRATION CASE STUDY I LECTURER: Nguyen Minh Nhat MEMBER: Tran Dac Lam Huynh Trong Nghia Nguyen Binh Minh Nguyen Truong An Nguyen Huu Giap Da Nang , month 09 year 2016 Table of Contents Table assignments Name Nguyen Huu Giap Nguyen Truong An Nguyen B Tran Dac Lam Huynh Trong Nghia Huynh Trong Nghia Assign work Introduce a reason, synthetic reference(Part 1) Overview the problem (Part 2) Stakeholder and user descriptions(Part 3) The advantages and disadvantages of the alternatives, Approach (Part 4,5) Write plan, problem statement,synthetic reviews from teammates and presentation 1 Introduction This document can help us find ways to meet requests from the CEO The requirements of the CEO give is how to integrate the two systems Human Resources and Payroll System From there to meet the requirement that the CEO needs , such as how can monitor working days and holidays , the average salary of an employee,Average benefits paid to shareholders and nonshareholders to date by benefits plan Also after the integrated system while maintaining good security, accuracy and timeliness of information 1.1 Purpose This document will help to understand and grasp business need, the issues, problem that companies face Documents describe overview the solution Document is like the contract, approval the project with customer 1.2 Scope Problem Solving, business needs, the system will be integrated 1.3 Definitions, acronyms and abbreviations ACME: Alaska Construction Management Enterprises HR: Human Resources CEO: Chief executive officer 1.4 References Casestudy1_Proposal Document_K16CMUTPM CEO_Memo SICaseStudy1 VisionDoc_Template Project Overview The corporate staff enters data into both systems Sometimes the people entering the data make mistakes CEO doesn’t have a way of seeing our employee status and payroll information all together Sometimes there are employee in Payroll systems that aren’t in the Human resource system Since both systems have sensitive information, not all information can be shared between the two systems CEO would like to be able to see all the information about employee and payroll without having to login to two different systems Stakeholder and user descriptions 3.1 Stakeholder summary Name Description CEO Who will pay for the project Requirements Engineers This stakeholder works with customers and stakeholders to translate needs into requirements This stakeholder is a primary lead in the Software Architect development of the app Project Manager This stakeholder leads development of the app Responsibilities Provide requirements suggestions and participation in working groups, responsible for legal contracts Specifies domain, nonfunctional, and functional requirements Refines requirements as needed Responsible for overall architecture of the system, and guides overall design and implementation of system Plans, manages and allocates resources, decides priorities, coordinates interactions with customers and users, and keeps the project team focused 3.2 User summary Name Description SEO View all information from new system Staff View, edit data in new system Employ ers View information from new system Responsibil ities Stakehol der Self Data enter into system Self Self 3.3 User environment Medium company staffs about 150-175 people Having more data of staff information on database Users of the software are persons who don’t work or work in the field of IT, so the company need a system is easy to use, simple and interface is easy to use Payroll systems have a lot of data, some data in the HR system is same, but some data different Users have access to the system from anywhere with internet a) 3.4 Stakeholder profiles CEO Description View all information from new system Type This is a user has full control to the system Responsibilities Using the new system for managing all users Success Criteria The success is defined as the customers continuing to use our system Involvement We will have sample customers to evaluate our system which will guide our vision b) Staff Description View, edit data of employers in new system Type This is the user who have experience with the system Ensure that the necessary functions exist in the system to allow effective communication Responsibilities and emergency service support Ensure that functions exist to support the Success Criteria user The success is defined as the customers continuing to use our system Involvement We will have sample customers to evaluate our system which will guide our vision c) Employers View information of employer from new Description system Type This is the user who don’t have experience with the system Responsibilities Ensure that the necessary functions exist in the system to allow effective communication and emergency service support Success Criteria The success is defined as the customers continuing to use our system Involvement We will have sample customers to evaluate our system which will guide our vision Approach Plan 1: − Each unit has one manager , the manager can use one management software for that department − Each software includes : management information department and the department's activities − When you need to provide information , managers are responsible for searching information in the software department and reported it to higher level managers Plan 2: − Set up a Web-based portal includes many functions The advantages and disadvantages of two alternative approaches Plan 1:  Pros: • •  Database independent , not interdependent Only one user so management function is not complicated Cons: • Cost manpower to use the software but only has a new manager to have access to data so happens many errors • • Two independent operating software , so when the data needs of both parts , the two managers need to work together to lookup Database disjointed , unable to meet all requirements of the company Plan 2:  Pros: • • • • • •  The system operates based on the position of each person logging into the system Profile of the two parts are tightly constrained , avoid duplication and redundancy Notifications are sent promptly and without delay No need staff to manage that just maintenance personnel systems Meet all requirements of the company Employees have access to the necessary information to detect errors and alert to make timely adjustments Cons: • Complex data • System permissions complex functions • For data backup and regular system maintenance Risk Risk Resource Technical Technology Cost Risk Description Members are sick or absent Technology is always changing and difficult to understand and absorb all Cost of developing application cannot be estimated accurately Solution Over time and resource reserves Staffs have been training on new techniques this feature may need extra resources