What is System Implementation?

System Implementation is the third phase in the JISC infoNet lifecycle

• the hardware and software system components are installed;

Simple, isn't it? No, it isn't. System implementation projects are long
difficult journeys by which organisations move from an old set of
technology to a new one. Following a trend that goes back to the 1980s,
these projects are far more common now than software development
projects. Few colleges or universities have the combination of size,
uniqueness and a wealth of technical resources to justify developing
systems from scratch. Coupled with increasingly-dynamic external changes
for both inputs and outputs to these systems, most tend to buy systems if
they are available. Commercial systems developed for business purposes
may demand major changes to traditional administrative approaches and
result in cultural clashes. These issues are equally, if not
more, evident where the implementation of learning management systems
challenges accepted pedagogic practice.
The JISC is looking at alternatives to the implementation of large-scale
'monolithic' systems for e-Learning. The e-Learning Frameworks and
Tools programme is developing a resource base providing advice and
'glueware' code to enable sets of e-Learning tools to interoperate, thus
reducing dependence on commercial suppliers. Using bundles of such tools
may prove cost-effective for some institutions but planning, consultation
and consideration of process remain equally important in this type of
scenario.
To implement a system successfully, a large number of inter-related tasks
need to be carried out in an appropriate sequence. Utilising a well-proven
implementation methodology and enlisting professional advice can help but
often it is the number of tasks, poor planning and inadequate resourcing
that causes problems with an implementation project, rather than any of
the tasks being particularly difficult. Similarly with the cultural issues it is
often the lack of adequate consultation and two-way communication that
inhibits achievement of the desired results.

bject-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects.
Each object represents some entity of interest in the system being modeled, and is characterised by its class, its state (data elements),
and its behavior. Various models can be created to show the static structure, dynamic behavior, and run-time deployment of these
collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling
Language (UML).

Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented
design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD
on how the system does it.

Contents
[hide]

• 1 Object-oriented systems

• 2 Object-oriented analysis

• 3 Object-oriented design

• 4 Literature

• 5 See also

• 6 References
 • 7 External links

[edit]Object-oriented systems
An object-oriented system is composed of objects. The behavior of the system results from the collaboration of those objects.
Collaboration between objects involves them sending messages to each other. Sending a message differs from calling a function in that
when a target object receives a message, it itself decides what function to carry out to service that message. The same message may be
implemented by many different functions, the one selected depending on the state of the target object.

The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the
objects being communicated with.

[edit]Object-oriented analysis
Object-oriented analysis (OOA) looks at the problem domain, with the aim of producing a conceptual model of the information that exists in
the area being analyzed. Analysis models do not consider any implementation constraints that might exist, such
as concurrency, distribution,persistence, or how the system is to be built. Implementation constraints are dealt during object-oriented
design (OOD). Analysis is done before the Design[citation needed].

The sources for the analysis can be a written requirements statement, a formal vision document, interviews with stakeholders or other
interested parties. A system may be divided into multiple domains, representing different business, technological, or other areas of
interest, each of which are analyzed separately.

The result of object-oriented analysis is a description of what the system is functionally required to do, in the form of a conceptual model.
That will typically be presented as a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also
include some kind of user interface mock-up. The purpose of object oriented analysis is to develop a model that describes computer
software as it works to satisfy a set of customer defined requirements.

[edit]Object-oriented design
Main article: Object oriented design

Object-oriented design (OOD) transforms the conceptual model produced in object-oriented analysis to take account of the constraints
imposed by the chosen architecture and any non-functional – technological or environmental – constraints, such as transaction
throughput, response time, run-time platform, development environment, or programming language.

The concepts in the analysis model are mapped onto implementation classes and interfaces. The result is a model of the solution domain,
a detailed description of how the system is to be built.
Structured Analysis and Design Technique (SADT) is a diagrammatic notation designed specifically to help people
describe and understandsystems[1]. It offers building blocks to represent entities and activities, and a variety of arrows to relate boxes.
These boxes and arrows have an associated informal semantics.[2] SADT can be used as a functional analysis tool of a given process,
using successive levels of details. The SADT method allows to define user needs for IT developments, which is very used in the industrial
Information Systems, but also to explain and to present an activity’s manufacturing processes, procedures.[3]

The SADT supplies a specific functional view of any enterprise by describing the functions and their relationships in a company. These
functions fulfill the objectives of a company, such as sales, order planning, product design, part manufacturing, and human resource
management. The SADT can depict simple functional relationships here and can reflect data and control flow relationships between
different functions.