Topic Area Project Management: Content Content • Software Metrics • Survey : Expectations on the Course VL 2 • Properties of Metrics • Software Metrics Softwaretechnik / Software-Engineering • Scales . . • Motivation . • Examples • Vocabulary • Requirements on Useful Metrics VL 3 • Cost Estimation Lecture 2: Software Metrics • Excursion: Scales • Deadlines and Costs • Some positive/negative examples . . • Expert’s Estimation . • Example: LOC • Algorithmic Estimation VL 4 • Other Properties of Metrics 2018-04-19 • Project Management • Base Measures vs. Derived Measures • Project . • Subjective and Pseudo Metrics . . • Process and Process Modelling • Example: McCabe Prof. Dr. Andreas Podelski, Dr. Bernd Westphal • Procedure Models VL 5 • Discussion • Process Models Albert-Ludwigs-Universität Freiburg, Germany – 2 – 2018-04-19 – Sblockcontent – • Process Metrics – 2 – 2018-04-19 – Scontent – . – 2 – 2018-04-19 – main – . . • CMMI, Spice 2 /47 3 /47 Survey: Previous Experience 2018 vs. 2017 Project Management 30 0-(0/1/3)-8 20 10 average: 1.7188 average: 2.2069 median: 1 median: 1 0 1 2 3 4 5 6 7 8 9 10 Management 2018 Management 2017 Requirements Engineering Programming Excursion: Communicating Figures 30 30 0-(0/1/2)-8 1-(1/3/5)-10 20 20 average: 3.9844 average: 3.9432 10 10 median: 3 median: 3 average: 2.284 average: 1.531 median: 1 median: 1 0 1 2 3 4 5 6 7 8 9 10 0 1 2 3 4 5 6 7 8 9 10 RE Experience 2018 RE Experience 2017 Programming 2018 Programming 2017 Design Modelling Software Quality Assurance 30 30 0-(1/1/3)-9 0-(1/2/4)-10 20 20 10 10 average: 2.625 average: 2.5682 – 2 – 2018-04-19 – Sexperience – average: 2.1932 average: 1.9531 – 2 – 2018-04-19 – Smedian – median: 2 median: 1 median: 1 median: 1 – 2 – 2018-04-19 – main – 0 1 2 3 4 5 6 7 8 9 10 0 1 2 3 4 5 6 7 8 9 10 Modelling 2018 Modelling 2017 QA 2018 QA 2017 4 /47 5 /47 6 /47
Quartiles Content Requirements Engineering 30 0-(0/1/2)-8 20 • Survey : Expectations on the Course 10 • Software Metrics • Motivation • Arithmetic mean : 1.531 (not in the scale! → later) 0 1 2 3 4 5 6 7 8 9 10 • Vocabulary • Minimum and maximum : 0 and 8 • Requirements on Useful Metrics • Median : 1 (the value such that 50% of the probands have yields below and above) Back From Excursion: Communicating Figures • Excursion: Scales • 1st and 3rd Quartile : 0 and 2 (25%, 75%) • Some positive/negative examples • Example: LOC • Other Properties of Metrics • a boxplot visualises 5 aspects of data at once (whiskers sometimes defined differently): • Base Measures vs. Derived Measures • Subjective and Pseudo Metrics 100 % (maximum) • Example: McCabe 75 % (3rd quartile) • Discussion 50 % (median) average: 2.284 25 % (1st quartile) average: 1.531 – 2 – 2018-04-19 – Smedian – – 2 – 2018-04-19 – Scontent – median: 1 median: 1 0 % (minimum) – 2 – 2018-04-19 – main – RE Experience 2018 RE Experience 2017 7 /47 8 /47 9 /47 Expectations Expectations Cont’d Expectations Cont’d • general Introduction L 1: 16.4., Mon • project management cont’d Introduction L 1: 16.4., Mon • design Introduction L 1: 16.4., Mon Scales, Metrics, L 2: 19.4., Thu Scales, Metrics, L 2: 19.4., Thu Scales, Metrics, L 2: 19.4., Thu ✔ learn about tasks related to development of software ✔ how to prove or test the development process ✘ get experience towards coming up with good designs Costs, L 3: 23.4., Mon Costs, L 3: 23.4., Mon Costs, L 3: 23.4., Mon ✔ learn different aspects of working in a software producing team and how ( ✔ ) learn proper metrics to measure progress and check quality ( ✘ ) improve knowledge in [...] software design / software architecture T 1: 26.4., Thu T 1: 26.4., Thu T 1: 26.4., Thu to cope with them L 4: 30.4., Mon L 4: 30.4., Mon L 4: 30.4., Mon Development Development Development ( ✔ ) create management plan evaluate results of previous software projects ( ✘ ) learn how to design a software model that fulfills all predefined Process L 5: 3.5., Thu Process L 5: 3.5., Thu Process L 5: 3.5., Thu ✔ gain more insight with [...] challenges faced in socio-technical systems and use evaluation results requirements Requirements L 6: 7.5., Mon Requirements L 6: 7.5., Mon Requirements L 6: 7.5., Mon and practical ways to overcome those challenges ✔ communicate design specifications - 10.5., Thu - 10.5., Thu - 10.5., Thu ( ✔ ) useful tools for successful management of software projects ( ✔ ) learn what techniques are there for project management, planning a Engineering L 7: 14.5., Mon Engineering L 7: 14.5., Mon ✔ learn formalisms to avoid, e.g., going for an inappropriate architecture Engineering L 7: 14.5., Mon software project, communicate and cooperate with partners ( ✘ ) learn how project planning and management are done in the proper way T 2: 17.5., Thu T 2: 17.5., Thu T 2: 17.5., Thu ✔ concepts/models/ideas to plan software and verify concept before ( ✔ ) learning a systematic approach to developing a larger program - 21.5., Mon - 21.5., Mon - 21.5., Mon ( ✘ ) deep knowledge about management skills implementing it - 24.5., Thu - 24.5., Thu - 24.5., Thu ( ✔ ) hope that course content can directly be used in practice L 8: 28.5., Mon L 8: 28.5., Mon L 8: 28.5., Mon ✔ ! don’t expect being taught how to be a manager, learn conditions for success • Implementation ( ✔ ) explicit, precise, working methods - 31.5., Thu - 31.5., Thu - 31.5., Thu ( ✔ ) would like to see a lot of concrete examples of software projects L 9: 4.6., Mon L 9: 4.6., Mon ( ✘ ) keep software clean, modular and expansible L 9: 4.6., Mon • requirements T 3: 7.6., Thu T 3: 7.6., Thu T 3: 7.6., Thu ( ✘ ) concretise the role of computer science and software engineering in ✘ sustainably manage a codebase L10: 11.6., Mon ✔ communicate expectations, needs, information, and ideas without L10: 11.6., Mon L10: 11.6., Mon business Arch. & Design, L 11: 14.6., Thu misunderstandings to colleagues and clients Arch. & Design, L 11: 14.6., Thu Arch. & Design, L 11: 14.6., Thu • Quality Assurance Software- L 12: 18.6., Mon Software- L 12: 18.6., Mon Software- L 12: 18.6., Mon ✔ be able to formalise requirements ensure that they are formalised • project management T 4: 21.6., Thu T 4: 21.6., Thu T 4: 21.6., Thu ( ✘ ) make sure software is high quality ✔ investigate necessary requirements ✔ overview about modelling and organisation of a project, and how to Modelling, L13: 25.6., Mon Modelling, L13: 25.6., Mon Modelling, L13: 25.6., Mon ( ✔ ) organising quality assurance Patterns L14: 28.6., Thu ( ✔ ) learn what well-defined requirements look like, Patterns L14: 28.6., Thu Patterns L14: 28.6., Thu group different problems QA L15: 2.7., Mon how they can have impact on final product QA L15: 2.7., Mon ( ✔ ) how to satisfy wishes of customers and how to know if satisfied QA L15: 2.7., Mon ✔ be able to plan software development towards deadline and budget T 5: 5.7., Thu T 5: 5.7., Thu T 5: 5.7., Thu ✔ how to obtain software as planned and which does what it should do – 2 – 2018-04-19 – Sexpectations – ✔ plan larger projects, conduct safely , timely , reliably – 2 – 2018-04-19 – Sexpectations – – 2 – 2018-04-19 – Sexpectations – (Testing, Formal L16: 9.7., Mon (Testing, Formal L16: 9.7., Mon (Testing, Formal L16: 9.7., Mon Verification) L 17: 12.7., Thu Verification) L 17: 12.7., Thu Verification) L 17: 12.7., Thu ✔ skills required to take responsibility in managing software projects Wrap-Up L18: 16.7., Mon Wrap-Up L18: 16.7., Mon Wrap-Up L18: 16.7., Mon ✔ how to avoid mistakes or limit inflicted damage T 6: 19.7., Thu T 6: 19.7., Thu T 6: 19.7., Thu 10 /47 11 /47 12 /47
Recommend
More recommend
