Chapter 7 – Design and Implementation

Lecture 1
Design and implementation
 It is the stage in the software engineering process at which an executable
software system is developed.
 These activities are always inter-leaved.
 Software design is a creative activity in which software components and
their relationships are identified on the bases of customer’s requirements.
 Implementation is process of realizing of design to program.
Build or buy
 In a wide range of domains (area), it is now possible to buy commercially off-
the-shelf systems (COTS) that can be adapted and fitted to the users’
requirements.
 For example, if you want to make a medical records system, you can buy a
system that is already used in hospitals. It can be cheaper, faster to use this
approach.
 When you build an application this way, designing is concerned with using that
system's configuration options to deliver the system requirements.
An object-oriented design process
 It Involve developing a number of different system models.
 Lot of effort for development and maintenance of these models and, for small
systems, if may not be cost-effective.
 For large systems developed by different groups these models are important for
communication.
System models are simplified representations of how complex systems work. They help us
understand and analyze about how different parts of a system interact.

Process stages
 There are a variety of different object-oriented design processes that depend
on the organization use.
 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.
 Specify object interfaces.
System context and interactions
Understanding how the software interacts with its surroundings is essential for
determining how to provide the needed functions and how to structure the system to
communicate with its environment.
Understanding the context also helps in define the limits of the system. Establishing
these boundaries helps to decide which features are implemented in the system
being developed and which features are in other related systems.