Scribd
Upload
19 views

4.mapping Design To Code

Uploaded by

narikottamonlineeditors
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

4.mapping Design To Code

Uploaded by

narikottamonlineeditors
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Mapping design to code in Object-Oriented Analysis and

Design (OOAD) involves translating the conceptual models


and design principles into actual implementation in a
programming language. This process ensures that the software
system is built according to the specified architecture and
design, adhering to best practices and design patterns identified
during the analysis and design phases. Here’s how you can
effectively map design to code in OOAD:

Steps to Map Design to Code

1. Review Design Artifacts: Before starting


implementation, thoroughly review the design artifacts
created during the design phase. This includes UML
diagrams (such as class diagrams, sequence diagrams,
state diagrams), design patterns identified (like from
GOF), and architectural decisions.
2. Identify Classes and Responsibilities:
o Classes: Identify the classes from your design.
Each class should encapsulate a coherent set of
responsibilities and data.
o Responsibilities: Assign responsibilities to each
class based on the design principles (like GRASP
patterns) and design patterns used.
3. Translate Class Diagrams to Code:
o Attributes: For each class, implement the
attributes as private variables with appropriate
access modifiers.
o Methods: Implement the methods of each class
based on their responsibilities. Ensure that each
method performs a single, well-defined task.
o Relationships: Implement relationships between
classes using appropriate references or
associations. For example, if a class has a
composition relationship with another,
instantiate the related object within the class.
4. Implement Design Patterns:
o Identify where design patterns, such as Singleton,
Factory Method, Adapter, etc., are applicable
based on your design.
o Implement these patterns using the specific
syntax and structure of the programming
language you are using. For example, in Java,
Singleton can be implemented using static
methods and a private constructor.
5. Follow Coding Standards and Guidelines:
o Adhere to coding standards and guidelines set by
your team or organization. This ensures
consistency and readability across the codebase.
o Use meaningful variable and method names that
reflect their purpose and functionality.
6. Validate Against Design Principles:
o Ensure that your code adheres to the design
principles established during OOAD. For instance,
ensure that responsibilities are appropriately
assigned using the GRASP patterns, classes are
loosely coupled, and high cohesion is maintained
within classes.
7. Test Driven Development (TDD):
o Consider using Test Driven Development (TDD) to
guide your coding process. Write tests based on
design specifications and requirements, and then
implement code to pass those tests. This helps in
validating that the implemented code meets the
expected behavior.
8. Refactor as Necessary:
o Periodically review and refactor your code to
improve its structure, performance, and
maintainability. Refactoring ensures that the
code remains aligned with the evolving design
and business requirements.

You might also like