Revision - Version Control Flashcards

(14 cards)

1
Q

What is UML version control?

A

The practice of managing changes to UML models over time. Enable teams to collaborate, maintain consistency, and synchronize design files

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Why is UML version control important?

A

Prevents team members from overwriting each other’s work, supports rollback, tracks changes across iterations, and keep design documentation aligned with implementation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

How is UML version control different from source code version control?

A

UML files are often binary model files, which made it harder to merge and conflicts are more difficult to detect and resolve

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

List out 3 advantages of UML Version Control

A
  1. Enables collaborative among team members
  2. Supports continuous documentation on system evolution
  3. Keep track between design and implementation
  4. Enhances maintainability through structured updates
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

List out 5 problems solve when using Version Control in UML Team Projects

A
  1. Prevents design conflicts or overwriting between team members
  2. Track changes across iterations or Agile sprints
  3. Allows rollback to previous states
  4. Support distributed and parallel development
  5. Keeps design documentation aligned with implementation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

List out 3 tools that support UML Version Control

A
  1. Visual Paradigm
  2. MagicDraw
  3. Argo UML
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a common strategy for versioning large UML models?

A

Model Fragmentation, by dividing big UML model into smaller modular packages

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What does the locking mechanism do in UML Version Control?

A

It allows only one person to edit a diagram at a time to reduce merge conflicts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is branching and merging used for in UML version control?

A

It enables team members to perform parallel development to work on different model versions and later combine the changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Why are change logs and annotations useful?

A

It records what was changed and why it was changed, which improves traceability and accountability

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What do model comparison tools do in UML Version Control?

A

Detect visual or semantic differences between model versions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

List out 4 ways to maintain UML Integrity

A
  1. Validate models after every merge
  2. Enforce consistent naming and package structures
  3. Align UML updates with Agile sprint deliverables
  4. Use round-trip engineering to sync diagrams with source code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

List out 4 Key Challenges of UML Version Control

6 In Total

A
  1. Merge Conflicts in complex XML-based model files
  2. Binary formats limit merging
  3. Fragmented Models loose dependency tracking
  4. Human Errors: Inconsistent naming or untracked edits
  5. Different Vendors causes difference in version and style of UML
  6. Complex merge conflicts in binary format files
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

List out 5 Best Practices for Teams regarding UML Version Control

A
  1. Keep UML models modular and organized by subsystem
  2. Commit frequently with descriptive messages
  3. Automate model validation
  4. Review UML changes at the end of each sprint
  5. Maintain repository backups and milestone tags
How well did you know this?
1
Not at all
2
3
4
5
Perfectly