CSSE3002 Lecture Notes - Lecture 13: Teradyne, Package Diagram, Boeing
28 Jun 2018
School
Department
Course
Professor
Personal software process
-Usually called PSP
-A personal process
-Typically software processes are team processes (assumed as a team – how team perform
tasks)
-What an individual software engineer should do? – monitor and analyse what had been done
– improve
Properties
-How to individually improve your practices?
-CMM – process improvement framework – continuous optimisation of process – any task (not
just coding)
-PSP – 3 levels – 0, 1, 2
-Estimate – time and effort (graph shows the accuracy of estimation)
-PSP – improve quality (number of defects decreases – a spike in the middle due to
inspection: discovery of defects – then it continues to reduce)
Productivity results
-Record info of what you did and analyse them – overhead – but the further it goes through the
development there will be an increase overhead as well – but productivity is flat (do more
process activity but not reducing the amount of actual work for the project)
Learning by experience
-PSP: improve individual practices – start with current experience, introduce new techniques
and methods as you progress along – monitor what you do – analyse what you do –
techniques to improve the quality you produce
PSP Process stages
-Start with what you currently do, figure out on which part you’re spending a lot of time
-Introduce techniques to improve what you do (coding techniques, proposal)
-Measuring the size of task produced – more data at PSP 0.1 so that at PSP1 -> use
techniques to perform more accurate estimates & collect more details about testing practices
and test results.
-Do more detail planning for the work – put into schedule
-PSP 2 – Do reviews – design, review, write code, review, then test it
-PSP 3 – improved process, better idea of what you personally do, improve own practices
Process flow
-Like waterfall
-Entire system – small – doesn’t take huge amount of time, but needs planning
-PSP has guides – how to do planning, testing, review etc
find more resources at oneclass.com
find more resources at oneclass.com
-Also track defects – if consistently make the same type of errors, what can I do to avoid
making those in the future?
-Share information with team members for estimates etc
PSP 0:
-Start with what you already do
-Introduce some steps (planning, development, post-mortem)
-Gather data: how long did you spent (for development/post-mortem), how many defects you
found
-Introduce coding standard – coding approach – to improve quality & reduce defects
-size measurement standard – how to count the size
-put together a proposal for something that needs to be changed – improve quality
-Measures:
oSmall cycles – 20 minutes, record interruptions (15 mins on the phone etc)
oRecord defects - any change to make it work correctly (incl. compilation error)
oCount size – lines of code (easy to count, analyse progress) – writing from
scratch/modifying/reusing? – e.g. import other classes
oProcess scripts – guidelines, what to do in planning? (need to know what people
want, estimate size, collect data
-Time recording log – calculate actual time used to complete task, excluding interruption time
-Defect log – what defect discovered? – when did you remove it?
-What’s the most expensive thing in SE projects? Time & people – time is money, most
expensive factor – must optimise time usage
-Create a plan – keeps people on track and less distraction – more focused to accomplish it
-Why record defect? – record type of defect, improve skill, product less defect-prone, and
fixing defects cost money & time
-every change made is considered a defect (for PSP) including enhancement of code (fixing
anything)
PSP1:
-started on process improvement – been collecting & analysing data, made some changes to
reduce defects – now will use data more rigorously
-estimation technique – PROBE – estimate size and time based on personal data – estimate
quality – use regression to see how accurate is the estimate -give feedback & try to be more
accurate for the next cycle
-framework –
oestimate size – use data – got records of how long it takes to do the database logic/
format javascript etc
oestimate resource – what do we need to finish this task – productivity database
find more resources at oneclass.com
find more resources at oneclass.com
Document Summary
Typically software processes are team processes (assumed as a team how team perform tasks) Monitor and analyse what had been done. Cmm process improvement framework continuous optimisation of process any task (not just coding) Estimate time and effort (graph shows the accuracy of estimation) Psp improve quality (number of defects decreases a spike in the middle due to inspection: discovery of defects then it continues to reduce) Psp: improve individual practices start with current experience, introduce new techniques and methods as you progress along monitor what you do analyse what you do techniques to improve the quality you produce. Start with what you currently do, figure out on which part you"re spending a lot of time. Introduce techniques to improve what you do (coding techniques, proposal) Measuring the size of task produced more data at psp 0. 1 so that at psp1 -> use techniques to perform more accurate estimates & collect more details about testing practices and test results.
