Arba Minch University

Institute of Technology
Faculty of Computing & Software
Engineering

SE TOOLS AND
P RA C T I C E S
(SENG4144)
Addisu M. (Asst. Prof) G4 IT - SUMMER
 CHAPTER 2

S Y N C H R O N I Z AT I O N
BETWEEN MODELS
A N D S O U RC E C O D E
INTRODUCTION

June 9, 2025
 In modern SW dev’t, alignment between
conceptual models and the corresponding source
code is crucial for maintaining consistency,

SEng4144 – SE Tools &

enhancing productivity, and ensuring quality.
 Synchronization between models and source code
involves the seamless integration of abstract
representations of system design—often created
using modeling languages like UML—with the
actual implementation in programming languages.
 Models – often represented using Unified Modeling
Language (UML) or other visual languages, serve as
high-level blueprints for software systems. 3
INTRODUCTION

June 9, 2025
 Models: In software dev’t, models are abstract
representations of a system, includes:
– UML Diagrams: Unified Modeling Language (UML)
diagrams like class diagrams, sequence diagrams, state

SEng4144 – SE Tools &

diagrams, etc., visually represent the structure and
behavior of the system.
– Data Models: Entity-relationship diagrams (ERDs) or
other schemas that depict the structure of the data
within the system.
– Process Models: Flowcharts, data flow diagrams, or
other representations of the system's workflow and
processes.
 Source Code: actual implementation of the SW
system written in a programming language (e.g., Java,
4
MODELING

June 9, 2025
Modeling – process of creating a simplified
representation of real-world system or concept
to understand, analyze, and predict their

SEng4144 – SE Tools &

behavior
 This representation can take various forms, such
as mathematical equations, diagrams, computer
simulations, or physical models.
Primary objective of modeling tools is to provide
graphical view to organize and visualize the
structure and components of software system.
It uses UML notation to design different kinds of
5
MODELING

June 9, 2025
It supports an approach to SE where the UML
modeling tools are completely integrated
with in RAD studio IDE.

SEng4144 – SE Tools &

It provides
features needed to design & build OO SW
systems, allowing the entire dev’t team to
collaborate using common language,
diagrams and software.
business people, developers, and projects
managers a single platform with a consistent
6
MODELS IN SOFTWARE

June 9, 2025
DEV’T
 Types of Models

Conceptual Models
 used To outline high-level ideas and r/nships

SEng4144 – SE Tools &

within a system
 Examples:
– Entity-Relationship (ER) diagrams for data
modeling.
– Use case diagrams showing user interactions
 Structural Models
 Used to represent organization & static aspects of
a system
 Examples:
7
MODELS IN SOFTWARE

June 9, 2025
DEV’T
 Types of Models
 Behavioral Models
 Used to capture dynamic aspects of the system and
how it responds to events

SEng4144 – SE Tools &

 Examples:
– Sequence diagrams showing order of message
exchanges b/n objects
– State machine diagrams representing states &
transitions of object
 Architectural Models
 Used to provide a blueprint of the system
architecture, including components, modules, and
their relationships.
 Examples:
8
MODELS IN SOFTWARE

June 9, 2025
DEV’T
 Types of Models

Process Models
 Used to represent workflows and processes

SEng4144 – SE Tools &

involved in software development.
 Examples:
– Agile methodologies like Scrum or Kanban
boards for tracking tasks.
– Waterfall model stages outlining sequential
phases of development.

9
MODEL ELEMENTS AND

June 9, 2025
THEIR RELATIONSHIPS
 To model elements and their relationships, use various
approaches depending on the context, such as UML for
software design, ERD for databases, or simple
conceptual frameworks

SEng4144 – SE Tools &

 Identify Key Elements
– Entities/Objects: Identify the primary entities involved
(e.g., Users, Applications, Servers, Services).
– Attributes: Define key attributes for each entity (e.g., User
ID, Application Name, Server Location)
 Define Relationships
– One-to-One (1:1): Each entity in one set is related to one
entity in another set (e.g., User has one Profile)
– One-to-Many (1:N): One entity is related to multiple
entities (e.g., Application can have multiple Users)
– Many-to-Many (M:N): Multiple entities are related to
multiple entities (e.g., Users can access multiple 10
MODEL ELEMENTS AND

June 9, 2025
THEIR RELATIONSHIPS
 Example:
– Entities and Relationships
 User
– Attributes: UserID, UserName, Email

SEng4144 – SE Tools &

– Relationships:
• Accesses → Application (1:N)
 Application
– Attributes: AppID, AppName, Version
– Relationships:
• Has → Server (N:1)
• Accessed by → User (N:M)
 Server
– Attributes: ServerID, Location, Capacity
– Relationships:
• Hosts → Application (1:N) 11
SOURCE CODE

June 9, 2025
MANAGEMENT
 SCM – a vital aspect of SW dev’t that involves
tracking and managing changes to source code
over time.

SEng4144 – SE Tools &

 allow teams to collaborate efficiently, track
modifications, and maintain a history of
changes.
 Key Concepts of Source Code Management
– Version Control:
 SCM systems keep track of every change made to
the codebase, allowing developers to revert to
previous versions if needed.
12
SOURCE CODE

June 9, 2025
MANAGEMENT
 Benefits of SCM
– Collaboration and Teamwork:
 allows multiple developers to work together efficiently,
reducing conflicts and improving communication.

SEng4144 – SE Tools &

– Change Tracking:
 Every change is logged, providing a clear history of
modifications, which is useful for audits and debugging.
– Backup and Recovery:
 acts as a backup system. If something goes wrong,
developers can revert to a previous stable version of the
code.
– Branching and Feature Development:
 Developers can work on new features or bug fixes in
isolated branches without affecting the main codebase.
– Code Quality and Review:
 systems often integrate with code review tools, ensuring13
SOURCE CODE

June 9, 2025
MANAGEMENT
 Popular SCM Tools
– Git: distributed version control system that allows
developers to work offline and manage repositories
efficiently

SEng4144 – SE Tools &

– GitHub: web-based platform that hosts Git,
providing additional features such as issue tracking,
pull requests, & project collaboration
– GitLab: Similar to GitHub, it offers a full DevOps
platform, including CI/CD integration, issue
tracking, and project management features
– Mercurial: distributed version control system
similar to Git, known for its simplicity and ease of
use 14
MODEL-CODE

June 9, 2025
SYNCHRONIZATION
process of maintaining consistency
between abstract models and their
corresponding implementation in source

SEng4144 – SE Tools &

code within sw dev’t

ensures that any changes made to the

models—whether they represent system
architecture, design elements, or business
processes—are accurately reflected in the
15
MODEL-CODE

June 9, 2025
SYNCHRONIZATION
 Importance of Model-Code Synchronization
– Consistency: Ensures that the design reflected in
the models is accurately implemented in the code,

SEng4144 – SE Tools &

reducing discrepancies and potential errors.
– Efficiency: Automating synchronization processes
helps developers save time and effort, allowing
them to focus on higher-level design and coding
tasks.
– Traceability: Facilitates tracking of changes, making
it easier to understand how design decisions impact
code implementation and vice versa.
– Collaboration: Enhances commn among team 16
MODEL-CODE

June 9, 2025
SYNCHRONIZATION
 Approaches to Achieve Synchronization
– Model-Driven Development (MDD):
 Emphasizes the use of models as primary artifacts,
often generating code directly from these models.

SEng4144 – SE Tools &

– Round-Trip Engineering:
 Involves continuous updates between models and
code, allowing changes in one to be reflected in the
other automatically.
– Version Control Systems:
 Utilizing systems like Git to manage changes in both
models and source code, ensuring that updates are
tracked and coordinated.
– Continuous Integration and Deployment (CI/CD):
17
MODEL-DRIVEN

June 9, 2025
DEVELOPMENT
 Model-Driven Development (MDD) - an
approach to software dev’t that emphasizes the
use of models as primary artifacts in the dev’t

SEng4144 – SE Tools &

process
 allows developers to create, analyze, and refine
software systems more effectively, reducing the
complexity often associated with traditional coding
practices
What is MDD?
 a software dev’t methodology that utilizes models to
define the structure, behavior, and requirements of a
system. 18
BENEFITS OF MDD

June 9, 2025
 Increased Abstraction: MDD allows developers to
work at a higher level of abstraction, making it
easier to understand and manipulate complex

SEng4144 – SE Tools &

systems.
 Improved Consistency: By using models,
developers can ensure that all parts of the system
are aligned with the defined requirements,
reducing inconsistencies.
 Enhanced Communication: Models serve as a
common language among stakeholders, including
developers, designers, and business analysts,
19
MODELING LANGUAGES

June 9, 2025
MDD often employs standardized modeling
languages, such as:
 Unified Modeling Language (UML): Widely

SEng4144 – SE Tools &

used for modeling software systems,
encompassing various diagram types for
different aspects of design (e.g., class diagrams,
sequence diagrams).
 Business Process Model and Notation
(BPMN): Used for modeling business processes
and workflows.
20
CASE STUDIES

June 9, 2025
ILLUSTRATING MDD IN
Case Study #1: Airline Reservation
PRACTICE
System
 Overview
 An airline company aimed to develop a new reservation

SEng4144 – SE Tools &

system to improve user experience and operational
efficiency.
 decided to adopt MDD to streamline the development
process.
 Implementation
 Modeling: team used UML to create use case diagrams
that captured user interactions & class diagrams to define
system's structure.
 Code Generation: Using tools like Eclipse Modeling
Framework (EMF), team generated the initial codebase 21
CASE STUDIES

June 9, 2025
ILLUSTRATING MDD IN
Case Study #2: Banking Software
PRACTICE
System
 Overview
 financial institution needed to develop banking software

SEng4144 – SE Tools &

system that complied with regulatory requirements &
offered a user-friendly interface
 MDD was chosen to enhance the development process.
 Implementation
 Requirements Gathering: Use case models were created
to capture various banking operations, including account
management and transaction processing.
 Business Process Modeling: BPMN was used to model
business workflows, ensuring that all processes were aligned
with regulatory standards.
 Code Generation and Integration: The models were 22
MDD PROCESS

June 9, 2025
Model Creation
 Developers create abstract models that define the
system's architecture, components, and

SEng4144 – SE Tools &

relationships; involves
– Gathering requirements from stakeholders.
– Creating conceptual, logical, and physical models .
Model Transformation
 Models are transformed into executable code
through:
 Code Generation: Automated tools generate code
based on the models, adhering to specified
templates and frameworks. 23
MDD PROCESS

June 9, 2025
Code Implementation
 Generated code is then implemented, tested, and
validated to ensure it meets the specified

SEng4144 – SE Tools &

requirements defined in the models.
Maintenance and Evolution
 As requirements change or new features are
introduced, models must be updated, and the code
regenerated accordingly.
 This iterative process helps maintain
synchronization between models and code
24
MODELING TECHNIQUES

June 9, 2025
Types of Models
1. Conceptual Models
– provide a high-level view of the system, focusing on the

SEng4144 – SE Tools &

key entities and their r/nships without delving into
implementation details.
– help stakeholders understand the overall structure and
functionality of the system.
– E.g.: Entity-Relationship Diagrams (ERD), Use Case
Diagrams
2. Logical Models
– refine the conceptual models by adding more detail
about how the system will operate, including data structures
and relationships.
25
MODELING TECHNIQUES

June 9, 2025
Types of Models
3. Physical Models
– represent the actual implementation of the system,

SEng4144 – SE Tools &

including specific technologies, databases, and
deployment strategies.
– provide details on how the system will be built,
including data types, storage mechanisms, and
hardware specifications.
– Examples: Database Schemas, Deployment
Diagrams.
26
CREATING & USING UML

June 9, 2025
DIAGRAMS
 Unified Modeling Language (UML) – a
standardized modeling language that provides a
set of diagrams for visualizing the design of a

SEng4144 – SE Tools &

system.
 Key UML diagrams include:
 Class Diagrams: Illustrate the static structure of
the system, showing classes, attributes, methods,
and relationships.
 Use Case Diagrams: Represent functional
requirements by depicting actors, use cases, and
their interactions.
 Sequence Diagrams: Detail the dynamic
27
CREATING & USING UML

June 9, 2025
DIAGRAMS
Steps to Create UML Diagrams
 Identify Key Components: Determine the main
entities, processes, and relationships in the

SEng4144 – SE Tools &

system.
 Select the Appropriate Diagram Type: Choose
the UML diagram that best represents the aspect of
the system you want to model.
 Draw the Diagram: Use UML notation to sketch
the diagram, ensuring clarity and accuracy.
 Review and Refine: Collaborate with stakeholders
to validate the diagram and make necessary 28
TRANSITIONING FROM

June 9, 2025
MODELS TO CODE
Code Generation
 Automated Code Generation: Use tools to
automatically generate code from models, reducing
manual coding errors and speeding up dev’t.

SEng4144 – SE Tools &

 Example Tools: Eclipse Modeling Framework,
Acceleo, and other MDD tools.
Manual Coding
 Refinement: After generating initial code,
developers may need to refine and optimize it to fit
specific requirements or performance criteria.
 Integration: Ensure that the generated code
integrates seamlessly with existing codebases and
29
CODE GENERATION FROM

June 9, 2025
MODELS
 Code generation from models is a key aspect of
MDD
 It involves the automatic creation of source code
from high-level abstract models, significantly

SEng4144 – SE Tools &

enhancing dev’t efficiency and ensuring consistency
b/n design and implementation.
 This process helps bridge the gap b/n conceptual
designs and executable software.
Code Generation
 process of converting models—such as UML
diagrams, domain-specific languages (DSLs), or
other abstractions—into actual source code in a
30
TOOLS FOR AUTOMATED

June 9, 2025
CODE GENERATION
Automated code generation tools can enhance
productivity and reduce errors in software
development.

SEng4144 – SE Tools &

List of some popular tools:
 Model-Driven Development (MDD) Tools
– Eclipse Modeling Framework (EMF): Allows
developers to create models and automatically
generate Java code, XML schemas, and more
from Ecore models.
– Acceleo: transforms models into text using
templates, primarily integrated with EMF.
 Code Generators 31
TOOLS FOR AUTOMATED

June 9, 2025
CODE GENERATION
List of some popular tools:
 Framework-Specific Tools
– Spring Roo: A RAD tool for Spring applications,

SEng4144 – SE Tools &

generating Java code and configurations.
– Rails Generators: Part of Ruby on Rails, these
allow developers to quickly create models,
controllers, and views.
 API Generation Tools
– Swagger/OpenAPI Generator: Automatically
generates client libraries, server stubs, and API
documentation from OpenAPI specifications.
– Postman: Offers code snippets in various
32
TOOLS FOR AUTOMATED

June 9, 2025
CODE GENERATION
List of some popular tools:
 Database Code Generation
– Hibernate Tools: Generates Hibernate mapping files
and Java classes from database schemas.

SEng4144 – SE Tools &

– Entity Framework Core: Generates models and context
classes from an existing database schema using the
Scaffold-DbContext command.
 Low-Code/No-Code Platforms
– OutSystems: A low-code platform that allows
developers to build applications quickly with visual
development tools.
– Mendix: Provides a low-code environment for rapid
application development with built-in code generation
capabilities. 33
CUSTOMIZING CODE

June 9, 2025
GENERATION TEMPLATES
 Customizing code generation templates is
essential for tailoring generated code to meet
specific project requirements and coding

SEng4144 – SE Tools &

standards.
 A guide on how to effectively customize these
templates, focusing on common tools like
Acceleo, JHipster, and others.
 Understanding the Template Structure
– Syntax: Familiarize yourself with the
template language used (e.g., Acceleo's M2T
syntax, or Mustache).
34
CUSTOMIZING CODE

June 9, 2025
GENERATION TEMPLATES
 Using Existing Templates
– Start with Default Templates: Use out-of-the-box
templates provided by the tool as a base. This saves
time and helps you understand the framework.

SEng4144 – SE Tools &

– Documentation: Refer to the tool's documentation
for guidance on how templates are structured and
how to modify them.
 Modifying Templates
– Change Output Format: Adjust the code style
(e.g., indentation, naming conventions) to match
your project's standards.
– Add Conditional Logic: Use conditional statements
to generate different code structures based on
model attributes 35
CUSTOMIZING CODE

June 9, 2025
GENERATION TEMPLATES
 Creating New Templates
– Define New Templates: If existing templates
don’t meet your needs, create new ones from
scratch, defining the required output format and

SEng4144 – SE Tools &

structure.
– Use Template Inheritance: Leverage
inheritance to create a base template that can be
extended by more specific templates.
 Testing and Iteration
– Generate Sample Code: test the templates by
generating sample code to ensure that
modifications work as intended.
– Iterate Based on Feedback: Gather feedback36
CUSTOMIZING CODE

June 9, 2025
GENERATION TEMPLATES
 Integration with Build Processes
– Automate Generation: Integrate the
code generation process into your build

SEng4144 – SE Tools &

system (e.g., Maven, Gradle) to ensure
that code is generated consistently and
automatically

 Version Control
– Manage Templates: Keep your templates
in version control (e.g., Git) to track
changes and collaborate with team 37
SYNCHRONIZATION

June 9, 2025
CHALLENGES
 Complexity of Models: Models often have complex
r/nships and dependencies that can be difficult to
track, leading to inconsistencies when underlying
code changes.

SEng4144 – SE Tools &

 Evolving Requirements: As project requirements
evolve, both models and code need to be updated,
which can result in divergent paths if not managed
properly.
 Tool Limitations: Different tools for modeling and
coding may not easily integrate, leading to
challenges in keeping them in sync.
 Communication Gaps: Lack of commn b/n team
members working on models and those working on 38
 ???
39
Any Question

SEng4144 – SE Tools &

June 9, 2025