The  case  for  great  Version  Control  

A  base  for  so4ware  quality  and    asset  management  

2

   

SYSTEMUTVECKLING � PROJEKTLEDNING & �CONFIGURATION MANAGEMENT��

TEST & VERIFIERING � INTEGRATION �

It  all  boils  down  to  

•  Asset  control  (=llgångar)  

•  Awareness    (medvetenhet)  •  AAtude    (aAtyd)  

Why  business  bookkeeping  

•  Eh…      isn’t  that  obvious?  

•  Tracking  results  •  Simplify  with  shared  procedures,  forms,  roles  •  Tracking  assets,  crea=ng  order  •  Laws,  taxes  

Why  SCM  bookkeeping  

•  Eh…      isn’t  that  obvious?  

•  Tracking  results  •  Simplify  with  shared  procedures,  forms,  roles  •  Tracking  assets,  crea=ng  order  •  Laws,  taxes  

•  And  simplify  reuse  

CM  Plan  

•  Sta=c  storage  •  Dynamic  storage  •  Accoun=ng  •  Release  

Product  structure  

•  Func=onal  products  •  Realised  products  •  Release  products    •  (market  products)  

•  Consists  of,  included  in  

•  This  is  NOT  a  system  architecture  

Document  structure  

•  Connect  documents  to  products  •  Structure  is  given  •  Write  a  document/release  matrix  

Interfaces  

•  Make  interfaces  into  individual  products!  

•  Will  improve  sw  quality  significantly  

Iden=fy  and  describe  interfaces  

Awareness  

•  Know  your  interfaces  Version  them!  Review,  discuss  between  teams  

•  Use  simple  metrics  to  find  ”roZen  apples”:  UCLOC,  TRs/KLOC  %  comments,  complexity  index  (Insight)  

•  Iden=fy:  cri=cal,  important,  trivial  

Improvements  

•  Use  metrics,  Importance  Review!    (Swarm)  

•  Test  coverage  •  Followup!  (Insight)  

More  Improvements  

•  Start  with  User  docs  •  Basic  test  •  Include  test  in  the  design  •  Find  out  at  what  stage  bugs  are  found  •  Inject  bugs  

AAtude  

•  ”I  don’t  ever  want  to  see  this  code  again”  •  Late  Tes=ng  is  not  a  quality  tool  •  Be  confident,  share,  talk,  ask  •  No  complicated  solu=ons