Unit 7:

Design and Implementation (5 Hrs.)

Compiled by : Madan Nath (B.Sc. CSIT, TU)

1
 Contents:
q Introduction;
q Object-Oriented Design using UML;
q Design Patterns;
q Implementation Issues;
q Open-Source Development;

2
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Unit-7
Design and Implementation
• Software design and implementation is the stage in the
software engineering process at which an executable software
system is developed.
• Software design is a creative activity in which you identify
software components and their relationships, based on a
customer's requirements.
• Implementation is the process of realizing the design as a
program. These two activities are invariably inter-leaved.

3
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design and Implementation

• In a wide range of domains, it is now possible to buy

commercial off-the-shelf systems (COTS) that can be adapted
and tailored to the users' requirements.
• COTS: Software and hardware that already exists and is
available from commercial sources. It is also referred to as off-
the-shelf.
• When you develop an application in this way, the design
process becomes concerned with how to use the configuration
features of that system to deliver the system requirements.

4
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Object-oriented design using the UML

Structured object-oriented design processes involve developing a

number of different system models. They require a lot of effort
for development and maintenance and, for small systems, this
may not be cost-effective. However, for large systems
developed by different groups design models are an important
communication mechanism. Common activities in these
processes include:
• Define the context and modes of use of the system;
• Design the system architecture;
• Identify the principal system objects;
• Develop design models;
5 • Specify object interfaces.
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 System context and interactions

• Understanding the relationships between the software that is

being designed and its external environment is essential for
deciding how to provide the required system functionality and
how to structure the system to communicate with its
environment.
• Understanding of the context also lets you establish
the boundaries of the system. Setting the system boundaries
helps you decide what features are implemented in the system
being designed and what features are in other associated
systems.

6
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 System context and interactions

• A system context is a structural model (e.g., a class

diagram) that demonstrates the other systems in the
environment of the system being developed.
• An interaction model is a dynamic model (e.g., a use case
diagram + structured natural language description) that shows
how the system interacts with its environment as it is used.

7
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 System context and interactions

8
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 System context and interactions

System Weather station

Use case Report weather
Actors Weather information system, Weather station
The weather station sends a summary of the weather
data that has been collected from the instruments in the
Description

collection period to the weather information system.

The data sent are the maximum, minimum, and average
ground and air temperatures; the maximum, minimum,
and average air pressures; the maximum, minimum, and
average wind speeds; the total rainfall; and the wind
9 direction as sampled at five-minute intervals.
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 System context and interactions

System Weather station

The weather information system establishes a satellite
Stimulus communication link with the weather station and
requests transmission of the data.
The summarized data is sent to the weather
Response
information system.
Weather stations are usually asked to report once per
Comments hour but this frequency may differ from one station to
another and may be modified in the future.

10
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Architectural design

• Once interactions between the system and its environment

have been understood, you use this information for designing
the system architecture.
• You identify the major components that make up the system
and their interactions, and then may organize the
components using an architectural pattern (e.g. a layered or
client-server model).

11
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Architectural design

12
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Architectural design

Identifying object classes is often a difficult part of object

oriented design. There is no 'magic formula' for object
identification. It relies on the skill, experience and domain
knowledge of system designers. Object identification is an
iterative process. You are unlikely to get it right first time.
Approaches to object identification include:
• Use a grammatical approach based on a natural language
description of the system.
• Base the identification on tangible things in the application
domain.

13
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Architectural design

• Use a behavioral approach and identify objects based on

what participates in what behavior.
• Use a scenario-based analysis. The objects, attributes and
methods in each scenario are identified.

14
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design models:

Design models show the objects and object classes and

relationships between these entities. Static models describe the
static structure of the system in terms of object classes and
relationships. Dynamic models describe the dynamic
interactions between objects.
Subsystem models show logical groupings of objects into
coherent subsystems. These are represented using a form of class
diagram with each subsystem shown as a package with enclosed
objects. Subsystem models are static (structural) models.

15
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design models:

Sequence models show the sequence of object interactions.

These are represented using a UML sequence or a collaboration
diagram. Sequence models are dynamic models.

16
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design models:

17
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design models:

State machine models show how individual objects change their

state in response to events. These are represented in the UML
using state diagrams. State machine models are dynamic models.
State diagrams are useful high-level models of a system or an
object's run-time behavior.

18
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Design models:

19
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

• Object interfaces have to be specified so that the objects and

other components can be designed in parallel.
• Designers should avoid designing the interface representation
but should hide this in the object itself.
• Objects may have several interfaces which are viewpoints on
the methods provided.
• The UML uses class diagrams for interface specification but
Java may also be used.

20
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

• A design pattern is a way of reusing abstract

knowledge about a problem and its solution.
• A pattern is a description of the problem and the essence of its
solution. It should be sufficiently abstract to be reused in
different settings.
• Pattern descriptions usually make use of object-oriented
characteristics such as inheritance and polymorphism.

21
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

Design pattern elements:

Name: A meaningful pattern identifier.
Problem description: A common situation where this pattern is
applicable
Solution description: Not a concrete design but a template for a
design solution that can be instantiated in different ways
Consequences: The results and trade-offs of applying the pattern

22
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

23
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

Pattern name Observer

Separates the display of the state of an object
from the object itself and allows alternative
Description displays to be provided. When the object state
changes, all displays are automatically notified
and updated to reflect the change.

24
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

In many situations, you have to provide multiple

displays of state information, such as a graphical
display and a tabular display. Not all of these may be
known when the information is specified. All
alternative presentations should support interaction
Problem and, when the state is changed, all displays must be
description updated.
This pattern may be used in all situations where
more than one display format for state information is
required and where it is not necessary for the object
that maintains the state information to know about
25 the specific display formats used.
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Interface specification

The subject only knows the abstract Observer and

does not know details of the concrete class.
Therefore there is minimal coupling between
these objects. Because of this lack of knowledge,
Consequences
optimizations that enhance display performance
are impractical. Changes to the subject may cause
a set of linked updates to observers to be
generated, some of which may not be necessary.

26
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Reuse

• From the 1960s to the 1990s, most new software was

developed from scratch, by writing all code in a high-level
programming language.
• The only significant reuse or software was the reuse of
functions and objects in programming language libraries.
• Costs and schedule pressure mean that this approach became
increasingly unviable, especially for commercial and Internet-
based systems.
• An approach to development based around the reuse of
existing software emerged and is now generally used for
business and scientific software.
27
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Reuse

Levels of reuse:
The abstraction level: don't reuse software directly but use
knowledge of successful abstractions in the software design.
The object level: directly reuse objects from a library rather than
writing the code yourself.
The component level: components (collections of objects and
object classes) are reused in application systems.
The system level: entire application systems are reused.

28
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Reuse

Costs of reuse:
• The costs of the time spent in looking for software to reuse
and assessing whether or not it meets your needs.
• Where applicable, the costs of buying the reusable software.
For large off-the-shelf systems, these costs can be very high.
• The costs of adapting and configuring the reusable software
components or systems to reflect the requirements of the
system that you are developing.
• The costs of integrating reusable software elements with each
other (if you are using software from different sources) and
with the new code that you have developed.
29
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Configuration management

Configuration management is the name given to the general

process of managing a changing software system. The aim of
configuration management is to support the system integration
process so that all developers can access the project code and
documents in a controlled way, find out what changes have been
made, and compile and link components to create a system.
Configuration management activities include:
• Version management, where support is provided to keep
track of the different versions of software components.
Version management systems include facilities to coordinate
development by several programmers.
30
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Configuration management

• System integration, where support is provided to help

developers define what versions of components are used to
create each version of a system. This description is then used
to build a system automatically by compiling and linking the
required components.
• Problem tracking, where support is provided to allow users
to report bugs and other problems, and to allow all developers
to see who is working on these problems and when they are
fixed.

31
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Host-target development

Most software is developed on one computer (the host,

development platform), but runs on a separate machine (the
target, execution platform).
A platform is more than just hardware; it includes the installed
operating system plus other supporting software such as a
database management system or, for development platforms, an
interactive development environment (IDE).
Development platform usually has different installed software
than execution platform; these platforms may have different
architectures.
Mobile app development (e.g. for Android) is a good example.
32
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Host-target development

Typical development platform tools include:

• An integrated compiler and syntax-directed editing system
that allows you to create, edit and compile code.
• A language debugging system.
• Graphical editing tools, such as tools to edit UML models.
• Testing tools, such as JUnit that can automatically run a set of
tests on a new version of a program.
• Project support tools that help you organize the code for
different development projects.

33
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Open source development

Open source development is an approach to software

development in which the source code of a software system
is published and volunteers are invited to participate in the
development process.
Its roots are in the Free Software Foundation, which advocates
that source code should not be proprietary but rather should
always be available for users to examine and modify as they
wish.
Open source software extended this idea by using the Internet to
recruit a much larger population of volunteer developers. Many
of them are also users of the code.
34
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Open source development

The best-known open source product is, of course, the Linux

operating system which is widely used as a server system and,
increasingly, as a desktop environment.
Other important open source products are Java, the Apache web
server and the mySQL database management system.
A fundamental principle of open-source development is
that source code should be freely available, this does not mean
that anyone can do as they wish with that code.

35
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Open source development

Typical licensing models include:

• The GNU General Public License (GPL). This is a so-called
'reciprocal' license that means that if you use open source
software that is licensed under the GPL license, then you
must make that software open source.
• The GNU Lesser General Public License (LGPL) is a
variant of the GPL license where you can write components
that link to open source code without having to publish the
source of these components.

36
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 Open source development

• The Berkley Standard Distribution (BSD) License. This is

a non-reciprocal license, which means you are not obliged to
re-publish any changes or modifications made to open source
code. You can include the code in proprietary systems that
are sold.

37
Compiled by : Madan Nath (B.Sc. CSIT, TU)
 ~ END ~

38
Compiled by : Madan Nath (B.Sc. CSIT, TU)