Karteikarten
Maintenance
Karten in diesem Stapel (9)
- 1Potential problems of legacy systems- Not modular
- Over-optimized
- Lack of graphical UI
- Source code lost
- Dated language
- Unstructured
- Badly patched - 2When to scrapHigh value & quality = keep!
Low value & quality = scrap!
Medium value & quality = Justify answer! - 3Continuous integration+ Problems between developers discovered and repaired as soon as possible
+ The most recent system in mainline is definitive working system
- Large system takes time to build and test
- Not possible to run system tests in developer's private workspace - 4Reviewing code- Cheaper bug fixes
- Reduction of defect rates
- Increased maintainability - 5Pair programming+ Everything read by two people
- No benefit of distance
- Expensive - 6Over-the-shoulderProgrammer presents code and walkthrough
+ Light-weight
+ Can be used selectively
+ Explanations available
- Little time for reflection
- Easy to over-explain
- Coverage not guaranteed - 7Peer reviewReviewer inspects a chunk of source code and comments
+ Gives time for reflection
+ Can be on demand
+ lights documentation issues
- Can be seen as adversial - 8Pre-checkingEvery check-in inspected by owner of module before being accepted
+ Everything is inspected
+ Check-in message gives context
+ Knowledgeable reviewer
+ Frequent reviews
- Time consumption
- Legacy
- Tools needed - 9Formal meetingsSeveral reviewers and programmers sit together for a meeting to discuss previously inspected code
+ Many eyes on code
+ Can handle large change sets
+ Observer friendly
- Schedule meetings is hard/expensive
- Group dynamics and ego concerns
Informationen
- Beschreibung
- Information Technology Karteikarten am Maintenance, erstellt von Johan Isaksson am 20/10/2018.
- Erstellt von
- Johan Isaksson
- Aufrufe
- 4
- Bewertung