Carmine GRAVINO | SOFTWARE METRICS AND QUALITY
Carmine GRAVINO SOFTWARE METRICS AND QUALITY
cod. 0522500087
SOFTWARE METRICS AND QUALITY
| 0522500087 | |
| COMPUTER SCIENCE | |
| EQF7 | |
| COMPUTER SCIENCE | |
| 2024/2025 |
| YEAR OF DIDACTIC SYSTEM 2016 | |
| SPRING SEMESTER |
| SSD | CFU | HOURS | ACTIVITY | |
|---|---|---|---|---|
| INF/01 | 6 | 48 | LESSONS |
| Objectives | |
|---|---|
| OBJECTIVE THE COURSE AIMS TO GIVE A PRACTICAL VISION OF THE USE OF SOFTWARE METRICS AS A TOOL TO MONITOR AND IMPROVE THE SOFTWARE DEVELOPMENT AND MAINTENANCE PROCESS, AS A DECISION SUPPORT AND TO EVALUATE AND IMPROVE THE QUALITY OF THE SOFTWARE PRODUCT. KNOWLEDGE AND UNDERSTANDING THE MAIN KNOWLEDGE ACQUIRED BY THE STUDENT WILL BE: •METRICS FOR OBJECT-ORIENTED SOFTWARE •USE AND EVALUATION OF METRICS TO BE USED DURING THE DEVELOPMENT PROCESS AND SOFTWARE MAINTENANCE •FUNDAMENTAL CONCEPTS FOR DESIGNING, PLANNING AND CONDUCTING EMPIRICAL STUDIES (AND EXPERIMENTAL EVALUATIONS IN GENERAL) •METHODOLOGIES AND TOOLS FOR DATA COLLECTION FROM THE VARIOUS SOURCES AVAILABLE DURING SOFTWARE DEVELOPMENT •STATISTICAL METHODS FOR DATA ANALYSIS •CONSTRUCTION OF PREDICTION MODELS FROM DATA COLLECTED ON SOFTWARE PRODUCTS AND SOFTWARE PROCESSES, OR AS A RESULT OF EXPERIMENTS APPLYING KNOWLEDGE AND UNDERSTANDING STUDENTS WILL BE ABLE TO: •IDENTIFY METRICS TO REPRESENT SPECIFIC ASPECTS TO BE MONITORED IN THE CONTEXT OF SOFTWARE DEVELOPMENT •USE OF A SYSTEMATIC AND ORGANIZED APPROACH TO DESIGN, PLAN AND CONDUCT EXPERIMENTAL EVALUATIONS •DESIGN EXPERIMENTS AND CASE STUDIES, AND THEN COLLECT AND ANALYZE THE RESULTS OF THE STUDIES CONDUCTED •BUILD PREDICTIVE MODELS (E.G., PREDICTION OF DEFECTS, PREDICTION OF COSTS) FROM DATA EXTRACTED FROM THE REPOSITORY SOFTWARE (E.G., PROMISE, CVS, SVN) MAKING JUDGEMENTS STUDENTS WILL BE ABLE TO: •SELECT AND EVALUATE POSSIBLE SOLUTIONS FOR THE SPECIFIC PROBLEM •IDENTIFY THE SOLUTION THAT BEST BALANCES DIFFERENT AND OFTEN CONFLICTING OBJECTIVES •MOTIVATE THE CHOICES MADE COMMUNICATION SKILLS STUDENTS WILL BE ABLE TO: •ENGAGE AND COMMUNICATE WITH DIFFERENT STAKEHOLDERS DYNAMICALLY ADAPTING TO THEIR DIFFERENT CHARACTERISTICS (KNOWLEDGE, NEEDS, DOMAIN, LANGUAGE) AND TO THE COMMUNICATION GOALS, BY ADOPTING AND SELECTING THE MOST EFFECTIVE COMMUNICATION TOOLS LEARNING SKILLS STUDENTS WILL BE ABLE TO: •USE IT ANALYSIS AND ARCHIVING RESOURCES; •PROCEED WITH THE CONTINUOUS UPDATING OF ONE'S KNOWLEDGE, USING TECHNICAL AND SCIENTIFIC LITERATURE •QUICKLY “ENTER” EVER NEW APPLICATION DOMAINS IN ORDER TO UNDERSTAND THEIR NEEDS AND TRANSLATE THEM INTO QUALITY SOFTWARE SYSTEMS. |
| Prerequisites | |
|---|---|
| PREREQUISITES STUDENTS MUST HAVE PREVIOUS KNOWLEDGE OF ALGORITHMS AND DATA STRUCTURES, PROCEDURAL PROGRAMMING AND OBJECTS, SOFTWARE TECHNOLOGIES FOR WEB, MANAGEMENT SYSTEMS, DATABASES, BASIC SOFTWARE ENGINEERING CONCEPTS. |
| Contents | |
|---|---|
| CONTENTS AFTER INTRODUCING THE NOTIONS OF MEASUREMENT AND SOFTWARE QUALITY, AND THE EXPERIMENTAL APPROACH IN THE SOFTWARE ENGINEERING FIELD, THE COURSE WILL FOCUS ON THE FOLLOWING TOPICS: •MEASURES IN THE SOFTWARE (2 HOURS) •USE OF PARADIGM GOAL-QUESTION-METRIC (2 HOURS) •QUALITY MODELS AND MEASUREMENTS (3 HOURS) •MEASURING TO CONTROL AND VALIDATE (3 HOURS) •THE EXPERIMENTAL APPROACH IN SOFTWARE ENGINEERING (2 HOURS) •EXPERIMENTAL PROCESS: DEFINITION; PLANNING; EXECUTION; ANALYSIS AND INTERPRETATION; PRESENTATION (10 HOURS) •EMPIRICAL STUDIES: SURVEY; CASE STUDIES; CONTROLLED EXPERIMENTS (10 HOURS) •DATA ANALYSIS: USING PLOTS AND DESCRIPTIVE STATISTICS; ANALYSIS OF DISTRIBUTIONS; HYPOTHESIS TESTING; USING R FOR STATISTICAL ANALYSIS (8 HOURS) •USING DATA EXTRACTED FROM THE REPOSITORY SOFTWARE AND CONSTRUCTION OF PREDICTION MODELS (FOR EXAMPLE OF THE DEFECTS, THE COSTS) (8 HOURS) |
| Teaching Methods | |
|---|---|
| THE COURSE INCLUDES 48 HOURS OF LECTURES PREDOMINANTLY THEORETICAL AND METHODOLOGICAL FOR THE TRANSFER OF KNOWLEDGE REGARDING THE CONTENT OF THE COURSE, WITH STUDY OF PRACTICAL ISSUES AND INTERACTION BETWEEN STUDENTS AND THE TEACHER (ABOUT 12 OUT OF 48 HOURS PLANNED). ALL THE DOCUMENTATION ABOUT THE ACTIVITIES CARRIED OUT DURING THE COURSE WILL BE AVAILABLE ON THE E-LEARNING PLATFORM OF THE DEPARTMENT OF COMPUTER SCIENCE. |
| Verification of learning | |
|---|---|
| TO REACH THE OBJECTIVE OF THE COURSE STUDENTS ARE ASKED TO PASS A FINAL EXAM (SCORE IN THE RANGE [1..30]) THAT IS COMPOSED OF A PRACTICE TEST AND A ORAL DISCUSSION. A PRACTICAL TEST INCLUDES A MEASUREMENT EXERCISE, THE PLANNING OF A STUDY/EXPERIMENT, AND THE CONSTRUCTION OF A PREDICTIVE MODEL (DURATION: 2 HOURS). THE EVALUATION CRITERIA WILL COVER THE COMPLETENESS AND CORRECTNESS OF LEARNING AND CLARITY. THE GOAL OF THE PRACTICE TEST IS TO VERIFY THE ABILITY OF: USING AND EVALUATING METRICS TO BE USED DURING THE DEVELOPMENT PROCESS AND SOFTWARE MAINTENANCE; DESIGNING, PLANNING AND CONDUCTING EMPIRICAL STUDIES; USING STATISTICAL METHODS FOR DATA ANALYSIS; AND BUILDING PREDICTION MODELS FROM DATA COLLECTED ON SOFTWARE PRODUCTS AND SOFTWARE PROCESSES. A DISCUSSION OF A PROJECT TO ASSESS THE SKILLS ACQUIRED PRACTICES (DURATION: 20/30 MINUTES). THE EVALUATION CRITERIA WILL COVER THE COMPLETENESS, CORRECTNESS AND SYNTHESIS OF THE PROJECT DOCUMENTATION. PRACTICE TEST (AS WELL AS ORAL DISCUSSION) IS POSITIVELY EVALUATED IF A STUDENT ACHIEVED A MINIMUM GRADE OF 18/30. PRACTICE TEST AND ORAL DISCUSSION EQUALLY CONTRIBUTE TO THE FINAL SCORE. |
| Texts | |
|---|---|
| •NORMAN E. FENTON, SHARI LAWRENCE PFLEEGER - SOFTWARE METRICS BY - PWS PUB CO. •CLAES WOHLIN, PER RUNESON, MARTIN HÖST, MAGNUS C. OHLSSON, BJÖRN REGNELL, ANDERS WESSLÉN - EXPERIMENTATION IN SOFTWARE ENGINEERING: AN INTRODUCTION - THE KLUWER INTERNATIONAL SERIES IN SOFTWARE ENGINEERING •L.M. LAIRD, M.C. BRENNAN, SOFTWARE MEASUREMENT AND ESTIMATION: A PRACTICAL APPROACH, IEEE COMPUTER SOCIETY PRESS, 2006, ISBN: 0471676225 |
| More Information | |
|---|---|
| E-LEARNING PLATFORM WEB SITE: HTTP://ELEARNING.INFORMATICA.UNISA.IT/EL-PLATFORM/ CONTACT INFORMATION: GRAVINO@UNISA.IT |
BETA VERSION Data source ESSE3 [Ultima Sincronizzazione: 2024-11-18]
