Duy Tan University

----------

SYSTEM INTEGRATION
CASE STUDY I -

LECTURER: NGUYEN MINH NHAT

MEMBER: Le Hoang
Le Thi Thuy Thanh
Le Phi Hiep
Tran Van Ly
GROUP: 10


Da Nang, 2012
 <ACME Company>

Version <1.01>

Revision Document History

 Date Version Description Author
<20/3/2012> <1.0> Write plan <Group 10>
<6/4/2012> <1.01> Update plan <Group 10>

3
Table of Contents
1. Introduction.............................................................................................................................................1
1.1. Purpose.................................................................................................................................................1
1.2. Scope....................................................................................................................................................1
1.3. Definitions, Acronyms and Abbreviations.............................................................................................1
1.4. References............................................................................................................................................1
1.5. Overview..............................................................................................................................................1
2. PROBLEM STATEMENT............................................................................................................................2
3. Stakeholder and User Descriptions..........................................................................................................3
3.1. Stakeholder Summary..........................................................................................................................3
3.2. User Summary......................................................................................................................................5
3.3. User Environment.................................................................................................................................5
3.4. Stakeholder Profiles..............................................................................................................................6
3.5. User Profiles:........................................................................................................................................7
3.6. Key Stakeholder or User Needs............................................................................................................8
4. Overview.................................................................................................................................................9
4.1. Perspective...........................................................................................................................................9
4.2. Summary of Capabilities.....................................................................................................................10
4.3. Assumptions and Dependencies.........................................................................................................10
5. Constraints............................................................................................................................................11
6. Precedence and Priority........................................................................................................................11
7. Other product requirements.................................................................................................................12
7.1. System Requirements.........................................................................................................................13
7.2. Performance Requirements................................................................................................................13
7.3. Environmental Requirements.............................................................................................................14
8. Documentation Requirements..............................................................................................................14
8.1. User Manual.......................................................................................................................................14
8.2. On-line Help........................................................................................................................................14
8.3. Installation Guides, Configuration, Read Me File................................................................................14
9. Appendix 1 - Feature Attributes............................................................................................................15
9.1. Status..................................................................................................................................................15
9.2. Benefit................................................................................................................................................15
9.3. Effort...................................................................................................................................................15
9.4. Risk.....................................................................................................................................................15
9.5. Stability...............................................................................................................................................16
9.6. Target Release....................................................................................................................................16
9.7. Assigned To.........................................................................................................................................16
9.8. Reason................................................................................................................................................16

1. INTRODUCTION
This document outlines the vision for the System Integration project of ACME
Company. The System includes 2 applications: Payroll System, HR system. The payroll
system has lots of employee data, some of the same data that the HR system contains,
some different. This document provides a plan to accomplish the work. It would also be
helpful to see some drafts of the interface so that we can make sure the team is on track
with our needs.
1.1. Purpose
The purpose of project is CEO can see our employee status and payroll information all
together.
1.2. Scope
The scope of the document is limited to the coordination and facilitation of software
requests between customers and the Company.
1.3. Definitions, Acronyms and Abbreviations
ACME: Alaska Construction Management Enterprises
 HR: Human Resources.
1.4. References
 Vision_Document_6089
 Human Resources Document
 Payroll Resources Document
1.5. Overview
The rest of the Vision document contains stakeholders and users and information,
features of system. It also plans to accomplish the work for project. This document helps
stakeholders have overview vision about project. It would also be helpful to see some
drafts of the interface so that we can make sure the team is on track with needs
2. PROBLEM STATEMENT
The problem of Enters data into both systems
Affects Staff
the impact of which is Staff, employers, data of payroll system a
a successful solution Can access data into both System
would be

The problem of - There are employees in payroll that aren’t in

the HR system, and in HR that aren’t in payroll
yet
Affects Employers
the impact of which is
a successful solution ?????
would be

The problem of Doesn’t have a way of seeing our employee

status and payroll information all together
Affects CEO
1
the impact of which is
a successful solution
would be

The problem of Be able to see all the information about

employees and payroll without having to login
to two different systems
Affects CEO
the impact of which is CEO, Employers, Staff, Network and data at
the both systems
a successful solution Monitoring sources on the both Systems
would be

The problem of Must maintain integrity of both products

Affects Both Systems
the impact of which is Network and data at the both systems
a successful solution Maintaining the consistency at the both systems
would be

The problem of The both systems have sensitive information,

not all information can be shared between the
two systems
Affects The both systems
the impact of which is Network and data at the both systems
a successful solution Easy to send data between the Systems
would be

2
3. STAKEHOLDER AND USER DESCRIPTIONS
3.1. Stakeholder Summary
Non-User Stakeholders
Name Description Responsibility
System Analyst This is a stakeholder that Leads and coordinates requirements
works with the elicitation and use-case modelling by
stakeholders to gather outlining the system's functionality and
their needs. delimiting the system; for example,
identifying what actors exist and what
use cases they will require when
interacting with the system.
Requirements This is a stakeholder that Specifies the details of one or more a
Specified works with the Analysts parts of the system's functionality by
to correctly translate describing one or the aspects of the
requests/ needs into requirements, this will include
requirements to be used functional and non-functional.
for design.
Technical This is a stakeholder that Responsible for contributing feedback
Reviewer must be involved to the review process. This role is
regularly to maintain the involved in the category of review that
development cycle. deals with the technical review of
project artefacts. This role is
responsible for providing timely,
appropriate feedback on the project
artefacts being reviewed.
Software This is a stakeholder that Responsible for the software
is primary for leading architecture, which includes the key
3
Architect the system development. technical decisions that constrain the
overall design and implementation for
the project.
Ensures that the system is going to be
maintainable and the architectural
solution supports the functional and
non-requirements.
Project This is a stakeholder that Plans, manages and allocates resources,
Manager is primary for leading shapes priorities, coordinates
the system development. interactions with customers and users,
and keeps the project team focused.
Also establishes a set of practices that
ensure the integrity and quality of
project artefacts.

3.2. User Summary

Name Represents Role
CEO See Dashboard See Dashboard
VP Final See Dashboard about Final See Dashboard about Final
VP Operations See Operations Dashboard See Operations Dashboard
Payroll Help for do Payroll Help for do Payroll
HR Director See dashboard about HR See dashboard about HR
HR Assistant Help for do Update and Help for do Update and
Project managers management HR management HR
Site Superintendents Management Project Management Project
Staff Get salary and all from Get salary and all from
both Systems both Systems

4
 3.3. User Environment
 Website for HR System
 Application for Payroll System
 Using database My SQL
 Operation System: Window Server 2000

3.4. Stakeholder Profiles

3.4.1. CEO
Representative CEO
Description May be see all dashboard of Employer
Type Boss
Responsibilities All
Success Criteria Using system help for your job, by see dashboard from both
systems
Involvement Node
Deliverables Integration Systems
Comments / Node
Issues

3.4.2. VP Final
Representative VP Final
Description May be see all dashboard of Employer about Final
Type Management
Responsibilities All in Payroll System
Success Criteria Using system help for your job, by see dashboard from Payroll
systems
Involvement Node
Deliverables Node
5
Comments / Node
Issues

3.4.3. VP Operations
Representative VP Operations
Description May be management all operation both systems
Type Management
Responsibilities Both Systems
Success Criteria Using system help for your job, operation both systems
Involvement Node
Deliverables Node
Comments / Node
Issues

3.4.4. Payroller
Representative Payroller
Description Do all activity buy Payroll system to help him job
Type Employer
Responsibilities Payroll System
Success Criteria Using system help for your job
Involvement Node
Deliverables Node
Comments / Node
Issues

3.5. User Profiles:

Representative Staff
Description Provide information and get salary
6
Type Employer
Responsibilities Get salary and all from both Systems
Success Information is exactly
Criteria
Involvement None
Deliverables None
Comments / None
Issues

3.6. Key Stakeholder or User Needs

Need Priority Concerns Current Proposed Solutions
Solutio
n
Secured High Management of None Manage user access with
access private user PIN numbers and encryption
information
Scalable Moderate None None Allow ample number of
access channels for end
users, managed with high
volume server hardware.
Easy to use High Ability to provide None Provide user friendly,
intuitive navigation highky intuitive, help guided
for all wireless navigation in application
devices regardless of wireless device
in use.
Responsive Moderate Ability to rely on None Create business partnerships
to High third party with third party providers to
communication ensure prompt response
links for prompt
7
 response times times.
Flexible High Ability to provide a Provide a simple, yet robust,
(configurable) truly customized None ability for the end user to
user experience customize the application to
enhance their user
experience.

4. OVERVIEW
This section provides a high level view of the Information System capabilities,
interfaces to other applications, and systems configurations. This section usually consists
of five subsections, as follows:
 Information System perspective
 Summary of Capabilities
 Assumptions and dependencies
 Cost and Timing
 Quality Ranges
4.1. Perspective
Integrate the requirement into a software tool that will support the enterprise
engineering function by exploring alternative organization models spanning organization
structure and behaviour. The Enterprise Engineering system allows for the exploration of
a variety of enterprise designs. The process of exploration is one of design, analysis and
re-design, where the system not only provides a comparative analysis of enterprise design
alternatives, but can also provide guidance to the designer.
The process of design system is performed through the creation, analysis and
modification of the enterprise from within each of the perspective visualizations.
Provide clients with the customized software and services they need to translate their
knowledge and data into improved decision making.

8
 Develop solutions using a unique combination of computer skills and
environmental expertise. This approach allows us to fully understand the challenges and
requirements of our clients, and to identify, design and develop the best computer tools
for meeting these needs.
4.2. Summary of Capabilities
Customer Support System
Customer Benefit Supporting Features
New support staff can Knowledge base assists support
quickly get up to speed. personnel in quickly identifying
known fixes and workarounds
Customer satisfaction is Problems are uniquely itemized,
improved because nothing classified and tracked
falls through the cracks. throughout the resolution
process. Automatic notification
occurs for any aging issues.
Management can identify Trend and distribution reports
problem areas and gauge allow high level review of
staff workload. problem status.
Distributed support teams Replication server allows
can work together to solve current database information to
problems. be shared across the enterprise
Customers can help Knowledge base can be made
themselves, lowering available over the Internet.
support costs and improving Includes hypertext search
response time. capabilities and graphical query
engine

4.3. Assumptions and Dependencies

 Assumptions:
9
 o Our shareholders often ask for information about our employees and
both departments have to stop their work to gather the information to
answer their questions
o Systems to let them know when certain conditions exist or special
events take place, such as employment anniversaries.
o Neither system provides them with the ability to manage by exception.
 Dependencies:
o Engagement with regulatory bodies such as ABC and other third parties
dependent on appropriate support and buy-in from the Executive Board
Directors
o Dependency that the party supplier CEO Memo will be able to modify.

5. CONSTRAINTS
 Software projects have constraints, probably have customer demands to satisfy.
Likely have a limited number of available programmers, a finite amount of time,
and exhaust able resources.
 We probably have to work with other people who have different visions of what’s
important and what the eventual successful outcomes might be.
 Sometimes these focus the mind. Sometimes they don’t. We are not sure why it
can be difficult to communicate the idea that the pure thought-stuff of software
6. PRECEDENCE AND PRIORITY
Number Feature Priority
1 Feature 1: View total earnings by shareholder, gender, ethnicity, High
part-time, and full- time employee to date and the previous year,
by department
2 Feature 2: View total number of vacation days taken by High
shareholder, gender, ethnicity, part-time, and full-time employee
to date and the previous year

10
Number Feature Priority
3 Feature 3: View average benefits paid to shareholders and non- High
shareholders to date by benefits plan
4 Feature 4: Alerts about hiring anniversary of an employee (work High
in a certain number of days)
5 Feature 5: Alerts about an employee has accumulated more than High
a certain number of days of vacation
6 Feature 6: Alerts about a change to benefits plan made by High
employees that affects their payroll
7 Feature 7: Alerts about birthdays of all employees within the High
current month
8 Feature 1.1: Calculate total earnings(earnings and deduction) by High
shareholder to date and the previous year(include Basic Pay,
Overtime, Insurance, Medical…)
9 Feature 1.2: Filter the shareholder information including gender, High
ethnicity, part-time, and full-time employee.
10 Feature 2.1: Calculate the amount of holidays of employees to High
date and the previous year (Sickness, Tet,..)
11 Feature 2.2: Feature 1.2 High
12 Feature 4.1: Calculate working time of employees(by month) High
13 Feature 5.1: Calculate vacation time of employees(by month) High
14 Feature 7.1: Get birth-month information of employees High
15 Feature 3.1: Calculate average benefits of shareholder and non-
shareholder by Benefits plan (shares of company, borrow car..)

7. OTHER PRODUCT REQUIREMENTS

 Applicable standards: legal, regulatory, communications
 Hardware or platform requirements: Can choose a particular hardware platform
depending upon different factors as listed below:
11
 o Usually UNIX workstations are costly to buy and maintain. On the other
hand, PC-based workstations are cheap and the maintenance cost is also low.
o Performance Usually UNIX workstations have high performance and
stability as compared to PC-based solutions
o Tools also need to keep in mind availability of development tools on a particular platform
o Development Type If the target system is the same as the host system on
which development is done, the development is relatively easy and native
tools are cheap as well, compared to cross-platform development tools.
Depending upon these factors, may make a choice from the available hardware plat-
forms for development.

7.1. System Requirements

 Support common server OS : Linux and Windows
 Installing Net framework 2.0 and the Java JDK.
 Required hardware and software enclosed with:
o Minimum 128 MB Ram.
o CPU 400MH or higher.
o Installation Net framework 3.0.
o Management System in SQL Server 7.0 database.
7.2. Performance Requirements
 Show summary information about their employees and payroll and benefits
information of these employees
 Be able to open more applications, some applications to support the software
(if necessary).
 Online system can run on all browsers of Linux and Windows
 The system shall provide access to the database with no more than 10 second
latency.
 Use parallel functions.
12
 7.3. Environmental Requirements
 The program always excuse extra database to store when suddenly turned off
(due to the problem).
o The virus on the net is easy to cause loss of information, can change the
data or structure data.
o The protection and privacy are very necessary and important to the
browser.
o The database is provided by the company should the security. Because this
is the software for management of the information employee
 The System Administrator should have:
o administrator access to the database (including SQL Server credentials)
o administrator access to the operating system

8. DOCUMENTATION REQUIREMENTS
8.1. User Manual
The User Manual describes the use of the application. It describes the use of the
System on OS. The user manual should be available as a hard copy and also as online
help.
8.2. On-line Help
Many applications provide an on-line help system to assist the user. The nature of
these systems is unique to application development as they combine aspects of
programming (hyperlinks, etc) with aspects of technical writing (organization,
presentation). Online help is provided for each and every feature provided by the system.
8.3. Installation Guides, Configuration, Read Me File
Instructions included:
 The system’s minimum requirements
 Command structure to Installation
 The clear parameter for the configuration
13
  The customer‘s support information
How to ask for Upgrades?
Read Me File will contain all the information about Installation and include:
 The characteristics of the new version
 Identify errors and solutions
9. APPENDIX 1 - FEATURE ATTRIBUTES
9.1. Status
Proposed None
Approved All features listed in Section 5 of this
document
Incorporated All features listed in Section 5 of this
document will be incorporated into the final
release.

9.2. Benefit
Critical None
Important None
Useful None

9.3. Effort
The estimated cost calculated using the basic COCOMO would be $5000. It gives
the development cost of the project, which contains 5000 lines of code, and the average
Cost Rate ($/PM) is taken as $150 approximately. The estimated effort is 4 person
months and it would take about 2 months to complete the project.

9.4. Risk
Risk Severity
14
Changes to requirements due to lack of elicitation High
Delays in development due to absence of team members Low
Requirements are either incomplete or too vague to produce an effective Medium
design document
Lack of skill sets in the development team can delay the development of the Medium
application
Projects experiences delays in development. Medium
Misunderstanding/misinterpretation of the stake-holder and/or user High
requirements.
Changing technology Medium

9.5. Stability
Most of the features are stable, as approved by the management and developers.
The statistical reports are to be determined in the near future.
9.6. Target Release
All features in this document will be implemented in the initial release of the
application.
9.7. Assigned To
All features will be assigned to the current team of application developers which
consists of Le Thi Thuy Thanh, Le Phi Hiep, Tran Van Ly, Le Hoang.
9.8. Reason
All the requirements that have been set for this system will provide stability,
reliability, portability, high performance, security and easiness.

15