Scribd
Upload
10 views35 pages

Topic 9 10 System Architecture and Vendor Profiles

Uploaded by

ngoclannguyenduy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
10 views35 pages

Topic 9 10 System Architecture and Vendor Profiles

Uploaded by

ngoclannguyenduy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 35

System Architecture

Content
1. Introduction
2. EIS as an Information system project
3. IS/IT project management results
4. System Architecture and EIS
5. Open source EIS
6. Systems designed aspects of EIS
7. External EIS Operation and Support
1. Introduction
An Enterprise Information system
architecture:
An elusive analysis of an Enterprise system
apart from the particulars of
implementation, algorithms and data.
Many architecture modeling notations and
support tools.
Architecture-based software expansion
facilitates and directs the focus to coarser-
gained building blocks and their
interconnections rather than on the code
level.
Example:
1. Introduction
The issues of managing an EIS project:
Dilemma: there is not a single method that
fits all setting.
Example of an situation in which system
architecture is drawn “Agile Architecture
Principle”.
Agile Architecture
Principle
Agile Architecture
Principle
System architecture is a role collaboration
(Agile Architecture Principle #6 )
These system-level teammates work together with
the component teams to decide what the
architecture needs to be.
 And when in doubt, they code it out (principle #3)
though a series of design spikes inside iteration or
release boundaries.
It is only by working together and by maximizing
the contribution of all team players that we can
hope to beat the competition by mastering systems
of the complexity that we are crafting today.
2. EIS as an Information system project

 Information systems (IS) projects involve relatively higher


levels of uncertainty than most other types of projects.
 EIS implementations tend to be the large IS project.
 Implementation’s options:
1. Adoption of a full EIS package from a single vendor
source.
2. Single EIS vendor source with internally developed
modifications.
3. Best-of-breed: adoption of modules from different
vendors.
4. Modules from vendor sources with internal
modifications.
5. In-house development.
6. In-house development supplemented by some vendor
2. EIS as an Information system
project
The option 1 is the easiest method but this
isn’t necessarily the least expensive option or
the greatest beneficial solution.
The option 3 is reasonable in case the vendors
do not have the best practice in all business
modules.
Option 5 is not recommended, but if this
method is adopted it will require a strong IS/IT
project management.
Option 7 means that the EIS could be
outsourced through application service
providers.
2. EIS as an Information system
project
Strategy Percentage US Percentage
Korea
Single ERP package with 50 43
modifications
Single ERP package 40

Vendor package with modifications 5

Best of breed 4 27

In-house plus specialized packages 1 14

Total-in-house system 0.5 16

ASP Missing missing

Relative use of ERP implementation strategies


(Mabert et al, 2006)
3. IS/IT project management results
Project management is one of the most
important fields in Information system.
? Completion on time, within budget
and meeting specifications
30% IS projects exceeded the original
budget, time frame or did not conform
to specifications (E. Booker, 1994).
Success rate was only 9% (R. Cafasso,
1994).
Reason
Poor project planning and
management
3. IS/IT project management results
Implementation states:
Typical problem is under-estimation of
time to get an EIS system working.
However, the vendors have a vested
interest in making EIS installation less
risky and more predictable.
Basic EIS is becoming less
problematic.
EIS enhancement is still a issue.
4. System Architecture and EIS
System architecture displays the layout of
computer used to support an organization.
Traditionally, EIS systems were focused
internally. It use a closed systems on dedicated
servers, access to organizational data could be
strictly controlled.
EIS that integrate CRM and SCM need open
system architecture (running on e-commerce
environments).
Data can be distributed over many systems.
Many problem raised during exchange data cross
different systems.
4. System Architecture and EIS
 Hasselbring’s proposal (2000):
Three architectural layers (business architecture
layer, application architecture layer, technology
architecture layer)
The business architecture layer: defines
organizational hierarchy and workflows for business
processes and rules.
The application architecture layer: defines
implementation of business concepts in terms of
enterprise applications.
The technology architecture layer: defines the
information and communication infrastructure, where
IT does the work required by the business users.
4. System Architecture and EIS
Open EISs:
Usually done through messaging
services.
Messaging services are still required to
integrate autonomous EIS systems.
There are products specializing in
application adapters, data
transformations, and messaging
services across EIS systems based on
different vendor products.
5. Open source EIS
Web services provide a convenient way to
access existing internal and external
information resources.
SOA gives the picture of what can be done
with Web services. SOA exploits the
business potential of web services, which
can lead to a type of convergence by
enabling organizations to access better
methods at lower cost through technology.
5. Open source EIS
SOA is a strategy based on turning
applications and information sources which
reside in different organizations, different
systems and different execution
environments into “services” that can be
accessed with a common interface
regardless of the location or technical
makeup of the function or piece of date.
SaaS offer EIS as a service that clients can
access via the internet. Smaller companies
are spared the expenses associated with
software installation, maintenance and
upgrades.
5. Open source EIS
Definition: SOA is a paradigm for organizing
and utilizing distributed capabilities that
may be under the control of different
ownership domains. It provides a uniform
means to offer, discover, interact with and
use capabilities to produce desired effects
consistent with measurable preconditions
and expectations.
OSS EISs (Open Source Software EISs)
allows small and medium sized businesses
access to EIS.
5. Open source EIS
The benefit of Open source
software:
Increased adaptability.
Decreased reliance on a single
supplier.
Reduced costs.
6. Systems designed aspects of
EIS
6.1 The waterfall model
6.2 Prototyping
6.3 The spiral model
6.1 the waterfall model
Stages:

Stage feedback
determinant
System feasibility Validation
Software plans and Validation
requirements
Product design Verification
Detailed design Verification
Code Unit test
Integration Product
verification
Implementation System test
6.1 the waterfall model
The waterfall model recognizes feedback loops
between stages of software development to
minimize rework.
There are variations in the stages for different
types of projects.
Each stage involves a test, either validation or
verification.
Validation is the process of evaluating software to
ensure compliance with specification
requirements.
Verification is the process of determining whether
or not the software component functions correctly.
6.1 the waterfall model
In the original waterfall model, problems
accumulated over stages and not noticed
until project completion resulted in very
expensive code.
Feedback loops were added, along with
prototyping, to catch problems early.
6.1 the waterfall model
In the original waterfall model, problems
accumulated over stages and not noticed
until project completion resulted in very
expensive code.
Feedback loops were added, along with
prototyping, to catch problems early.
Xác định yêu
cầu hệ thống
Kiểm chứng

Xác định yêu


cầu phần mềm
Kiểm chứng

Thiết kế
căn bản
Kiểm chứng

Thiết kế
chi tiết
Kiểm chứng

Lập trình

Gỡ lỗi

Kiểm thử

Chạy thử

Vận hành
Bảo trì
2
Kiểm chứng lại
6
6.2 Prototyping
 When the ideal system is not well defined, the
systems development approach has proven
ineffective.
 Prototyping is an evolutionary approach.
Useful for evaluating systems applied in unstructured
environments.
Involving building a small-scale mock-up system.
User can try the prototype and ask for modifications
based upon a better idea of what the system could do.
 This method might result in much lower
development cost and time, especially when there
are many uncertainties about what the system
should consist of.
Mô hình chế thử

Nghe Khách Tạo / sửa


trình bày bản mẫu

Khách kiểm tra


bản mẫu

2
8
6.3 The Spiral model
The spiral model uses iterative prototypes.
This approach was developed for software
project involving high levels of risk.
Implementation of EIS vendor software
involves major iterations.
In each cycle:
Begins with the identification of objectives
Involves risk analysis -> plan
Then prototypes are developed
Mô hình xoắn ốc

Lập kế hoạch
Phân tích rủi ro

Giao tiếp
khách hàng
Khái niệm Kỹ nghệ

Làm mới

Nâng cấp
Khách hàng Xây dựng &
đánh giá Xuất xưởng
Bảo trì

3
0
7. External EIS Operation and
Support
New trend: Hire out large portions of
Information processing, or outsourcing.
Many functions can be outsourced.
Including:
Data center management,
Telecommunications,
Disaster recovery,
Legacy system maintenance,
ect.
-> Application service providers (ASPs).
7. External EIS Operation and
Support
ASPs can offer:
Low costs EIS.
Increased flexibility.
Avoiding the waste of resources.
Risks:
Application and Data are controlled by
others.
Service failure,
Confidentiality failure,
Performance issues
ect.
Vendor profiles

Cu Nguyen Giap
Do Thi Thu Hien
Information resource
Update during the time.
Devised by region.
Vietnamese market:
FPT
FAST
Bravo
.v.v.
Mainly focus on MIS.
Question?

You might also like