Agile design
Download
1 / 9

Agile Design - PowerPoint PPT Presentation


  • 89 Views
  • Uploaded on

Agile Design. Problems with software designs . Rigidity Fragility Immobility Viscosity Needless Complexity Needless Repetition Opacity. Rigidity. Rigid software is difficult change One change requires mods in multiple modules Changes are more difficult than estimated. Fragility.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Agile Design' - sarila


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

Problems with software designs
Problems with software designs

  • Rigidity

  • Fragility

  • Immobility

  • Viscosity

  • Needless Complexity

  • Needless Repetition

  • Opacity


Rigidity
Rigidity

  • Rigid software is difficult change

    • One change requires mods in multiple modules

    • Changes are more difficult than estimated


Fragility
Fragility

  • The degree to which it is easy to break the program

  • Small changes generate unexpected side-effects


Immobility
Immobility

  • The code is not modular enough for reuse


Viscosity
Viscosity

  • Software Viscosity

    • When design-preserving methods of extending the software are less easily achieved than changes that are not in concert with the overall design (i.e., hacks are easier than following design) the design has “high viscosity.”

  • Environment Viscosity

    • The process of making changes (e.g., compiling, getting approval, configuration management) can also encourage a “quick-and-dirty” fix, rather than a fix better suited to the long-term maintainability of the system.


Needless complexity
Needless Complexity

  • Preparing for unknown extensions

    • Overly flexible

  • Bad Algorithms

  • Bad/Out-dated assumptions about system priorities


Needless repetition
Needless Repetition

  • Cut and paste is evil in software engineering.

    • How many places does the same processing occur?

      • That is the number of places that changes/fixes must be made

    • Do people understand what the cut and paste?

      • This is how software the literally no one understands enters the system.

    • The same code, with minor changes, makes the minor changes easy to miss.


Opacity
Opacity

  • How clear is the code

    • Code tends to get less clear as it is modified

    • Code tends to get less clear when you think about something else for a while

    • Code that is clear to you, might not be clear to others


ad