![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Title: Tight Coupling
Rating: PG-13
Summary: Post board meeting.
Disclaimer: Not mine. All Marvel’s.
A/N: I have titled my entries into the![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-community.gif)
pepperony100 table Tight Coupling. They will (hopefully) combine into a larger story. Some chapters may be longer than others. We may just have to see where this is going. This is technically Chapter Three. Go here for Chapters One and Two.
Thank you to everyone who has left me reviews. Sorry this one is so short. I am getting somewhere I promise. Please, please let me know what you think!
Tight Coupling - causes a system to be hard to understand and change because
-changes in one place will require changes somewhere else. Requiring changes to be made in more than one place is problematic since it is time-consuming to find the different places that need changing, and it is likely that errors will be made.
-A network of interdependencies makes it hard to see at a glance how some component works (ref: Object Oriented Software Engineering Database, Univ. Ottawa)
If that isn't Tony Stark and Pepper Potts in a nutshell, I don't know what is.
( Chapter Three – Relax (84) )
Rating: PG-13
Summary: Post board meeting.
Disclaimer: Not mine. All Marvel’s.
A/N: I have titled my entries into the
pepperony100 table Tight Coupling. They will (hopefully) combine into a larger story. Some chapters may be longer than others. We may just have to see where this is going. This is technically Chapter Three. Go here for Chapters One and Two.Thank you to everyone who has left me reviews. Sorry this one is so short. I am getting somewhere I promise. Please, please let me know what you think!
Tight Coupling - causes a system to be hard to understand and change because
-changes in one place will require changes somewhere else. Requiring changes to be made in more than one place is problematic since it is time-consuming to find the different places that need changing, and it is likely that errors will be made.
-A network of interdependencies makes it hard to see at a glance how some component works (ref: Object Oriented Software Engineering Database, Univ. Ottawa)
If that isn't Tony Stark and Pepper Potts in a nutshell, I don't know what is.
( Chapter Three – Relax (84) )
