Roger Sylvester System Architecture and Integration 3/25/2016 Table of Contents Contents BACKGROUND………………………………………….. 1 OBJECTIVES……………………………………………… 1 BUSINESS OR TECHNICAL NEEDS………………….. 2 Human Resource Management and Development:……….. 2 Customer Relationship Management:…………………… 2 Enterprise Performance Management:…………………. 3 MAJOR COMPONENTS OF THE PROJECT………… 3 Customer Relationship Management……………………. 3 Human Resource Management and Development………. 4 Enterprise Performance Management…………………… 4 PROJECT PLAN…………………………………………. 4 Table 1.1 Table showing project timeline……………….. 6 SYSTEM INTEGRATION BEST PRACTICES……….. 6 Figure 1.1. Diagram showing process flow for designing the systems integration architecture…………………………………………… 7 References…………………………………………………. 7 Requirements Specifications……………………………… 8 Stakeholders……………………………………………………… 9 Components……………………………………………….. 10 Interfaces………………………………………………….. 11 System Assumptions……………………………………… 13 References……………………………………………………………………16 Enterprise System Integration Analysis……………………………………………………………………….17 Systems Integration Approach Evaluation and Selection………………....19 References……………………………………………………………………..20 BACKGROUND The ShopRite Company is a mobile telecommunications company that deals with production and distribution of telecommunication equipment. In its operations, the company has over five hundred employees and different departments. To manage its taskforce and streamline its operations, the company resolved in developing an Enterprise Resource Planning system (ERP). This will see the company’s administrative, financial and human resource activities dedicated to the ERP.OBJECTIVES Implementation of the system will allow for a unified organization that will be efficient and effective in its daily activities. The main objectives of the ERP system are: · To establish a clear platform that will enforce a consistent execution and utilization of resource management principles and policies. · To facilitate an easier decision making process by improving access to enterprise management information. · To allow Information Communication Technology to support a fully integrated cohesive modern and strategic administrative infrastructure. · To provide an efficient and effective processes for personnel, performance management, recruiting, payroll and learning through workflow modules that are integrated to encourage collaborative working. · To provide a transparent system of monitoring the allocation and utilization of resources then comparing them against the expected results which will lead to an optimal utilization of resources available for achievement of particular goals and objectives. · To improve customer service by formation of a centralized repository for customer information. · To Use an amalgamated customer data to potentially increase revenues through a better understanding of customer needs.BUSINESS OR T ...

1. Roger Sylvester
System Architecture and Integration
3/25/2016
Table of Contents
Contents
BACKGROUND………………………………………….. 1
OBJECTIVES……………………………………………… 1
BUSINESS OR TECHNICAL NEEDS………………….. 2
Human Resource Management and Development:……….. 2
Customer Relationship Management:…………………… 2
Enterprise Performance Management:…………………. 3
MAJOR COMPONENTS OF THE PROJECT………… 3
Customer Relationship Management……………………. 3
Human Resource Management and Development………. 4
Enterprise Performance Management…………………… 4
PROJECT PLAN…………………………………………. 4
Table 1.1 Table showing project timeline……………….. 6
SYSTEM INTEGRATION BEST PRACTICES……….. 6
Figure 1.1. Diagram showing process flow for designing the
systems integration
architecture…………………………………………… 7
References…………………………………………………. 7
Requirements Specifications……………………………… 8
Stakeholders……………………………………………………… 9
Components……………………………………………….. 10
Interfaces………………………………………………….. 11
System Assumptions……………………………………… 13
References……………………………………………………………
………16 Enterprise System Integration

2. Analysis………………………………………………………………
……….17
Systems Integration Approach Evaluation and
Selection………………....19
References……………………………………………………………
………..20
BACKGROUND
The ShopRite Company is a mobile telecommunications
company that deals with production and distribution of
telecommunication equipment. In its operations, the company
has over five hundred employees and different departments. To
manage its taskforce and streamline its operations, the company
resolved in developing an Enterprise Resource Planning system
(ERP). This will see the company’s administrative, financial
and human resource activities dedicated to the
ERP.OBJECTIVES
Implementation of the system will allow for a unified
organization that will be efficient and effective in its daily
activities. The main objectives of the ERP system are:
· To establish a clear platform that will enforce a consistent
execution and utilization of resource management principles and

3. policies.
· To facilitate an easier decision making process by improving
access to enterprise management information.
· To allow Information Communication Technology to support a
fully integrated cohesive modern and strategic administrative
infrastructure.
· To provide an efficient and effective processes for personnel,
performance management, recruiting, payroll and learning
through workflow modules that are integrated to encourage
collaborative working.
· To provide a transparent system of monitoring the allocation
and utilization of resources then comparing them against the
expected results which will lead to an optimal utilization of
resources available for achievement of particular goals and
objectives.
· To improve customer service by formation of a centralized
repository for customer information.
· To Use an amalgamated customer data to potentially increase
revenues through a better understanding of customer
needs.BUSINESS OR TECHNICAL NEEDS
The ERP system will seek to satisfy the following Business
needs of ShopRite Company.Human Resource Management and
Development:
· Payroll.
· Personnel Management.
· Learning Management.
· Recruitment.
· Performance ManagementCustomer Relationship Management:
· Support for Customer-centric business practices.
· Support for Sales, Distribution and Marketing of products and
services.
· Customer information consolidation.Enterprise Performance
Management:
· Planning and Budgeting.
· Enterprise Reporting and Analytics.
· Results Based Management.MAJOR COMPONENTS OF THE

4. PROJECT
The main objectives of the ERP system will be improving the
management of the Human resources in the organization,
monitoring the Enterprise performance and Customer
Relationship Management. It is from these broad objectives that
we generate the major components of the ERP system.Customer
Relationship Management
According to Buttle, F. (2009), Customer Relationship
Management (CRM) is a business strategy that aims at
attracting, growing and retaining the right customers. To
achieve a better CRM, an organization needs to understand the
needs of a customer and work on fulfilling the said needs. For
this to be achieved, the ERP system will need to have a
dedicated CRM module that will integrate with other systems to
provide a consolidated customer base. This will help ShopRite
understand the needs of the customer and optimize its revenue
streams.Human Resource Management and Development
Human Resource Management is the process of managing the
human taskforce in an organization. The activities involved in
HRM include recruitment, Induction, Training and providing
proper appraisal. In a large organization like ShopRite, a large
human workforce can be tedious to manage manually.
Integrating an HRM module in the ERP will ensure that the
human workforce is properly managed and properly appraised to
see a properly motivated workforce and as a result increased
work output.Enterprise Performance Management
A strategic reporting tool to provide a basis for future reporting
and analytics will be integrated in the ERP. This will increase
the functionality and structure. To improve accountability, it is
imperative to have a strengthened Results Based Management
and the introduction of components that will help in budgeting,
planning performance assessment and monitoring.PROJECT
PLAN
The following are the deliverables that will be required for the
implementation of the project.
· Implementation of Planning and Budgeting

5. · Implementation of Reporting, Analytics, Monitoring and
Performance Assessment;;
· Implementation of Learning Management and Career
Development;
· Implementation of Recruitment;
· ERP Portfolio Vision, Conceptual Design, Accountability
Framework and Delegation of Authority
· Implementation of Performance and Position Management;
· Implementation of Core HR and Payroll
· Implementation of Customer Relationship Management
(CRM);
January
February
March
april
may
Project
1
2
3
4
5
6
7
8
9

6. 10
11
12
13
14
15
16
17
18
19
20
Personnel and Payroll
Performance Management

7. Learning Management

8. Recruitment
Planning and Budgeting

9. Enterprise performance Management
Customer Relationship Management

10. Table 1.1 Table showing project timeline
SYSTEM INTEGRATION BEST PRACTICES
System integration is the process of assembling the constituent
components of a system in a rational and cost effective manner
and comprehensively checking all exceptional and nominal
paths check out (Reeve,95).
The best practices to be observed during system Integration are
as follows;
i. Development of an integration plan during program planning.
ii. Proper requirements and design specifications should be
defined at every level of the system.
Figure 1.1. Diagram showing process flow for designing the
systems integration architecture.
References

11. Reeve, A. (n.d.). Managing data in motion: Data integration,
best practice techniques and technologies.
Buttle, F. (2009). Customer relationship management: Concepts
and technologies. Amsterdam: Butterworth-Heinemann.
Requirements Specifications
The project scope is the integration of customer service into the
current company systems in a way as to allow service delivery
over the system. The system therefore will facilitate and create
a Client Information Database (CID) which will include
· Identifying Information: Names, Company names, Account
numbers, Social Security numbers
· Contact Information: Mailing addresses, Home phone and Cell
phone numbers, E-mail addresses, Fax numbers and Client
website information. The database can also contain information
pertaining to the client's preferred contact methods.
· Client History: Order history, Customer service complaints,
Client feedback and stated client preferences. A database can
also contain a section for general notes about a client or
customer.

12. http://smallbusiness.chron.com/client-information-needed-
database-42984.html
Stakeholders
The primary stakeholder in the company is the client. The
system is built around everything for the client’s use such as
letting the client to easily access the company’s services. The
company owners part won’t be publicly visible to other
stakeholders apart from the executive administration and the
investors. Financial institutions which will include creditors and
banks will be part of the stakeholder title and will be depended
on for financial support as the company expands.
System Components and Interfaces
Mobile apps will communicate with services using API’s based
on REST interfaces. The key components will be
· Vendor Framework that provide access to device capabilities
from the mobile network
· Enterprise Development Kits that provide the ability to
support the communication with mobile services through SDK’s
that are consumable for mobile developers
The MDM will focus on managing the devices from business to
employee scenario and provide services to keep track of the
company’s owned devices and also will manage devices that are
connected to the company’s networks using the management
agents on the devices to provide Enterprise App Distribution,
Security, Device Management, and Device Analytics
.
Components
The network components will be the Enterprise User Directory
to provide storage for the user, authentication, authorization,
and profile data. Enterprise Data, and applications that will run

13. processes and logic within the existing systems The completion
of the integration process of the system will see the interlinking
of a few sections of the company using different interfaces
Interfaces
Several interfaces will be used in this case as a common system
development and in line with the other clients and stakeholders.
The greater part of the system will be made available to users
through a graphical user interface which the implementation
will include:
· UI designers create the UI requirement specifications using
text, graphic, illustrations, and relevant multimedia
representation
· UI programmers implement according to the specification
· The created UI is verified against the UI requirement
specification by UI designers
A UI template generator will be used for UI designers to lessen
the workload. The UI template can be reused to create a new UI
prototype for a new mobile phone service.
Functional Requirements
The ShopRite mobile client will enable the delivery, creation,
and metadata of ShopRite contents on mobile devices. The
content will be delivered on the basis of certain search filters,
whereas the create content is enriched with metadata specifying
certain values of these filters. The ShopRite mobile client will
be part of a client-server infrastructure using the ShopRite
services.
http://scn.sap.com/community/mobile/blog/2013/06/25/mobile-
app-requirements-specification-creation
Non Functional Requirements
The correct specification and adherence of non-functional
requirements similarly plays at least an equal, if not a greater

14. role in the success of mobile applications for the reasons of:
· Mobile devices are uniquely constrained in several aspects
such as multi-tasking support, available network bandwidth,
screen real estate etc.
· Mobile applications need to operate successfully within a wide
spectrum of operating conditions, such as a range of supported
screen resolutions and form factors, network bandwidth
situations and network types
· Mobile applications need to operate successfully within a wide
spectrum of operating conditions, such as a range of supported
screen resolutions and form factors, network bandwidth
situations and network types.
· Users expect a different quality of user experience from an
application running on the mobile device than they do from
their desktop computer.
CPU & Memory
For any given OS, the supported devices could have a very wide
range of capabilities in terms of CPU speed and available
memory. If the application makes extensive use of arithmetic
and logic operations such as streaming and decompression of
audio and video and animations, it should specify minimum
CPU and memory requirements for the application
Support for different network protocols
Mobile devices can communicate with the network on one or
more protocols. For a network application, it is crucial to
evaluate each network-enabled feature of the application from
the point of view of determining the protocol that is requires
Screen resolution and screen form factors
Keep a set of target screen resolutions in mind while designing
the user interface of a mobile application. Practically, you will
need to identify one or more screen resolution (or alternately
screen size) families that you want to support.
Battery usage
On a mobile phone, the battery should remain maximally
available for the phone application i.e. for making and receiving

15. phone calls. Your application may therefore fall by the wayside
or even get uninstalled by the user, if it drains too much battery.
http://www.ibm.com/developerworks/topics/non%20functional%
20requirement%20for%20servicess%20mobile%20health%20pdf
/
System Assumptions
One of the main assumptions of the system is that all the system
stakeholders, especially those actively involved in the
interlinking of the payment procedures are in agreement with
company corporate protocols and are therefore on behalf of the
company authorizing the payments for their own business
development. Otherwise the above requirements may never be
met. Also, in the above specification, it is assumed that the
client or customer is able to use the system from his/her end and
understands the logical operations of the system, is clear of
mind with the steps offered on the site and is informed enough
to know which online practices may not be safe for him/her,
especially when it comes to financial authorization. Finally, the
above requirements specification are specific to this system, it
is however, assumed that all the other general system
development requirements are met such as security,
administration, monitoring, maintenance are viable from their
respective ends.
Pros and Cons of Mobile Apps
Pros:
A high percentage of the population use smart phone technology
and are app savvy. Apps keep your brand prominent in the
market place, ahead of the competition. Apps help increase
customer retention and loyalty, as they are always at hand, first
port of call. Users tend to spend longer on Apps than on
portfolio websites. App technology allows you to demonstrate
products and services more creatively, connect with clients,
provide more in-depth information and give users a better
customer experience. Apps usually load faster than mobile sites.
Mobile apps are available offline apart from transactions where

16. users will need to log-in. Their specific use can be targeted to
different users – dealers/customers /end-users/ staff.
Most Apps are easy to use: training your mobile workforce to
use them will take very little time and effort. Apps can be easily
downloaded by your B2B sales leads from app stores such as
iTunes, Google play, and Facebook’s app store. Once business
clients use your App (especially if it is web-based), you can
stay connected wherever your clients are. You can glean
valuable user generated data from your app that could help you
create even more targeted lead generation marketing campaigns
in the future.
Cons:
A mobile App needs to be made to suit each platform, Android,
Windows, iPhone, etc. which can be costly and timely. Mobile
Apps require on-going care both as regard to fresh content and
technological updates. They are not as simple to optimize as a
mobile website. Apps can be expensive – the more functionality
they have, the more they cost, and can be hard to update. A
mobile app that’s just a smaller version of your website won’t
work hard enough for you and could even damage the
perception of your brand.
http://sproutsocial.com/insights/mobile-app-vs-mobile-website/

17. References
http://smallbusiness.chron.com/client-information-needed-
database-42984.html
http://scn.sap.com/community/mobile/blog/2013/06/25/mobile-
app-requirements-specification-creation
http://www.ibm.com/developerworks/topics/non%20functional%
20requirement%20for%20servicess%20mobile%20health%20pdf
/
http://sproutsocial.com/insights/mobile-app-vs-mobile-website/
Enterprise System Integration Analysis
Functional Testing- This would be the testing software process
that is used within the software development to ensure that the
software conforms to all the requirements. Functional Testing is
a way to check the software to be sure that it has all the
required functionality that is specified within its functional
requirements to verify that a piece of software is providing the
specified output as required by the end-user
Expert Technology Assessment – Technology assessment is
carried out by a team of experts which includes input from the
stakeholders. Technology assessment is a form of research that
examines short and long-term consequences of an application.
This assessment provides policy makers with information of
alternatives.
Evaluation Tool – An approach that will assess technology
proposals Functional Testing- This would be the testing
software process that is used within the software development
to ensure that the software conforms to all the requirements.
Functional Testing is a way to check the software to be sure that
it has all the required functionality that is specified within its
functional requirements to verify that a piece of software is

18. providing the specified output as required by the end-user
Expert Technology Assessment – Technology assessment is
carried out by a team of experts which includes input from the
stakeholders. Technology assessment is a form of research that
examines short and long-term consequences of an application.
This assessment provides policy makers with information of
alternatives.
Evaluation Tool – An approach that will assess technology
proposals
Survey Worksheet- Different groups are surveyed to retain
feedback from different groups such as stakeholders and clients.
The surveys will give the company feedback about the
company’s product and also the company itself as to how
improvements and/or tweaks can be made better for the clients.
Graphical Tool- Tool that allows quick comparison that
represents the criteria that the technology is being assessed
against. The tool aids in understanding the numerous
relationships reflected in data. The tool will help reveal
departures from assumed models and distributions from the
models by displaying features of the data that were
unanticipated before the analysis
.
Vertical Integration is the process of integrating subsystems
according to the functionality by creating entities. This is
performed only to specific vendors and is performed quickly.
Star Integration is the process where each system is
interconnected to each of the remaining subsystems where the
subsystems are exporting heterogeneous or proprietary
interfaces.
Horizontal Integration is the method in which a specialized
subsystem is dedicated to communication between other
subsystems allowing the number of connections to be cut down
to only one per subsystem which is directly connected to the
ESB.

19. Systems Integration Approach Evaluation and Selection
Systematic Inquiry: A systematic data –base evaluation that
requires quality data including defensible indicators which leads
to credible findings. Two kinds of logic is used which is
inductive and deductive. Inductive will start with an observation
then come to a conclusion while deductive will start with
general knowledge and predict a specific observation
A decision Matrix is an array presenting on one axis a list of
alternatives that allows decision makers to structure, and then
solve the problem by specifying and prioritizing the needs with
a list then evaluating, rating, and comparing the different
solutions, then it will select the best solution
References
http://www.rfp-templates.com/What-is/Decision-Matrix
http://ittoday.info/Articles/Effective_Methods_for_Software_an
d_Systems_Integration.pdf
http://www.sei.cmu.edu/productlines/frame_report/softwareSI.ht
m
8