Software Development Glossary

O. Widder. (2013). geek&poke. Available: h8p://geek-­‐and-­‐poke.com h8p://home.hit.no/~hansha/?page=so#ware_development So#ware Glossary Simply Explained! Hans-­‐Pe8er Halvorsen, M.Sc. 1 User friendly 2 High Availibility 3 Bugs vs. Features “It's not a bug -­‐ it's an undocumented feature” “For as long as I've been a so#ware developer and used bug tracking systems, we have struggled with the same fundamental problem in every single project we've worked on: how do you tell bugs from feature requests?” 4 Dogfooding Ea]ng your own dog food, also called dogfooding, is a slang term used to reference a scenario in which a company (usually, a computer so#ware company) uses its own product to demonstrate the quality and capabili]es of the product. Example: Microso# uses Windows PCs and Visual Studio to create their so#ware. 5 Code Review 6 Test Driven Development -­‐ TDD O. Widder. (2013). geek&poke. Available: h8p://geek-­‐and-­‐poke.com 7 Agile So#ware Development 8 Manifesto for Agile So#ware Development We are uncovering be8er ways of developing so#ware by doing it and helping others do it. Through this work we have come to value: •  Individuals and interac]ons over processes and tools •  Working so#ware over comprehensive documenta]on •  Customer collabora]on over contract nego]a]on •  Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the le# more. Agile Alliance. (2013). Agile Manifesto. Available: h8p://agilemanifesto.org 9 Daily Scrum 10 Burn Down Chart • 
• 
• 
• 
• 
A burn down chart is a graphical representa]on of work le# to do versus ]me. The outstanding work (or backlog) is o#en on the ver]cal axis, with ]me along the horizontal. That is, it is a run chart of outstanding work. It is useful for predic]ng when all of the work will be completed. It is o#en used in agile so#ware development methodologies such as Scrum. However, burn down charts can be applied to any project containing measurable progress over ]me. 11 Test User 12 HTTP Error 500 Internal Server Error The Web server (running the Web Site) encountered an unexpected condi]on that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL. This is a 'catch-­‐all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condi]on in its response to the client. In addi]on to the 500 error no]fied back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs. This error can only be resolved by fixes to the Web server so#ware. It is not a client-­‐side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further informa]on about the error. 13 Pair Programming 14 So#ware Development Process 15 Development-­‐Driven Tes]ng (DDT) •  DDT is all about giving more responsibility to developers specifically, and the development process in general. It works especially well when using test cases as requirements, and having the developers write these test cases •  Development-­‐driven tes]ng makes all the sense in the world for those who prac]ce Agile 16 Test-­‐Driven Development (TDD) 17 Development-­‐Driven Tes]ng (DDT) •  DDT is all about giving more responsibility to developers specifically, and the development process in general. It works especially well when using test cases as requirements, and having the developers write these test cases •  Development-­‐driven tes]ng makes all the sense in the world for those who prac]ce Agile 18 Code Freeze/Feature Freeze 19 Logfiles 20 System Documenta]on 21 References •  I. Sommerville, So2ware Engineering: Pearson, 2010. •  O. Widder. (2013). geek&poke. Available: h8p://geek-­‐and-­‐poke.com •  B. Lund. (2013). Lunch. Available: h8p://www.lunchstriper.no, h8p://www.dagbladet.no/tegneserie/lunch/ •  S. Adams. Dilbert. Available: h8p://dilbert.com •  Agile Alliance. (2013). Agile Manifesto. Available: h8p://agilemanifesto.org 22 Hans-­‐PeCer Halvorsen, M.Sc. Telemark University College Faculty of Technology Department of Electrical Engineering, InformaTon Technology and CyberneTcs E-­‐mail: hans.p.halvorsen@hit.no Blog: hCp://home.hit.no/~hansha/ 23