Module Details
Module Code: |
SOFT9023 |
Title: |
Source Code Analysis
|
Long Title:
|
Source Code Analysis
|
NFQ Level: |
Expert |
Valid From: |
Semester 1 - 2021/22 ( September 2021 ) |
Field of Study: |
4814 - Computer Software
|
Module Description: |
Software analysis is a set of techniques and processes that are utilised to provide an insight into the structure and quality of a software system.
In this module the learner will be introduced to modern methodologies for the analysis and evaluation of a software system's underlying codebase.
The student will undertake a critical analysis of production based code in order to identify required functionalities and an optimal strategy for the modernisation of legacy systems.
|
Learning Outcomes |
On successful completion of this module the learner will be able to: |
# |
Learning Outcome Description |
LO1 |
Analyse and configure a software parser to identify entities in source code. |
LO2 |
Create different types of relationships between the identified entities such as method calls, class inheritance and containment relationships. |
LO3 |
Evaluate and implement different analytics techniques (e.g., invocation analysis, call graph visualization, clone detection) on the identified entities to detect code smell and interpret the results. |
LO4 |
Evaluate feature location techniques (e.g., structural and textual) for detecting functionalities in the software system. |
LO5 |
Analyse different techniques such as clustering algorithms, formal concept analysis and text-based approaches to identify relevant software artefacts for different purposes (e.g., objectification, cohesive component identification). |
Dependencies |
Module Recommendations
This is prior learning (or a practical skill) that is strongly recommended before enrolment in this module. You may enrol in this module if you have not acquired the recommended learning but you will have considerable difficulty in passing (i.e. achieving the learning outcomes of) the module. While the prior learning is expressed as named MTU module(s) it also allows for learning (in another module or modules) which is equivalent to the learning specified in the named module(s).
|
|
Incompatible Modules
These are modules which have learning outcomes that are too similar to the learning outcomes of this module. You may not earn additional credit for the same learning and therefore you may not enrol in this module if you have successfully completed any modules in the incompatible list.
|
No incompatible modules listed |
Co-requisite Modules
|
No Co-requisite modules listed |
Requirements
This is prior learning (or a practical skill) that is mandatory before enrolment in this module is allowed. You may not enrol on this module if you have not acquired the learning specified in this section.
|
No requirements listed |
Indicative Content |
Parser and Source code entity identification
Different Java parsers and their applications. The advantage of using a parser to discover software's components/entities. Overview of a list of different source code entity relationships such as method calls, class inheritance and variable usages.
|
Software analysis techniques
Overview of a range of source code analysis techniques such as invocation analysis (dead code analysis), inheritance analysis and call graph visualisation. Identifying a sequence of source code that are implemented more than once (code clones). An overview of a range of different code smells.
|
Feature Location
Feature location and an overview of a number of different FL techniques such as textual and static FL techniques and other related techniques such as query enhancement technique.
|
Source Code Dependency
Overview of different techniques such as formal concept analysis, clustering algorithms to discover coherent source-code artefacts for various tasks such as source-code migration or modernising legacy code, (objectification).
|
Module Content & Assessment
|
Assessment Breakdown | % |
Coursework | 100.00% |
Assessments
No End of Module Formal Examination |
Reassessment Requirement |
Coursework Only
This module is reassessed solely on the basis of re-submitted coursework. There is no repeat written examination.
|
The University reserves the right to alter the nature and timings of assessment
Module Workload
Workload: Full Time |
Workload Type |
Contact Type |
Workload Description |
Frequency |
Average Weekly Learner Workload |
Hours |
Lecture |
Contact |
Theory and practical aspects of the module. |
Every Week |
2.00 |
2 |
Lab |
Contact |
Implementation of the practical aspects of the module. |
Every Week |
2.00 |
2 |
Independent Learning |
Non Contact |
Independent Study. |
Every Week |
3.00 |
3 |
Total Hours |
7.00 |
Total Weekly Learner Workload |
7.00 |
Total Weekly Contact Hours |
4.00 |
Workload: Part Time |
Workload Type |
Contact Type |
Workload Description |
Frequency |
Average Weekly Learner Workload |
Hours |
Lecture |
Contact |
Theory and practical aspects of the module. |
Every Week |
2.00 |
2 |
Lab |
Contact |
Implementation of the practical aspects of the module. |
Every Week |
2.00 |
2 |
Independent Learning |
Non Contact |
Independent Study. |
Every Week |
3.00 |
3 |
Total Hours |
7.00 |
Total Weekly Learner Workload |
7.00 |
Total Weekly Contact Hours |
4.00 |
Module Resources
|
Recommended Book Resources |
---|
-
Robert C. Martin. (2009), Clean Code : A Handbook of Agile Software Craftsmanship, Pearson Education (US), Upper Saddle River, United States, p.464, [ISBN: 0132350882].
-
Carleton DiLeo. (2019), The Qualities of Clean Code, Apress, Berkeley, CA, [ISBN: 978-1-4842-55].
| Supplementary Book Resources |
---|
-
Terence Parr. (2013), The Definitive ANTLR 4 Reference, 2. The Pragmatic Programmers, Raleigh, United States, p.325, [ISBN: 1934356999].
| Recommended Article/Paper Resources |
---|
-
Dit, Bogdan and Revelle, Meghan and
Gethers, Malcom and Poshyvanyk, Denys. (2013), Feature location in source code: a
taxonomy and survey, Journal of software: Evolution and
Process, 25 (1), p.53,
-
Farshad Ghassemi Toosi, Asanka Wasala,
Goetz Botterweck and Jim Buckley. (2018), Identification of potential classes in
procedural code using a genetic
algorithm, GECCO '18 Proceedings of the Genetic and
Evolutionary Computation Conference
Companion, July 2018, p.314,
| Supplementary Article/Paper Resources |
---|
-
Rubin, Julia and Chechik, Marsha. (2013), A survey of feature location techniques, Domain Engineering, May 2013, p.29,
-
Kaur, Gundeep and Sharma, Er Sumit. (2018), The Survey of the Code Clone Detection
Techniques and Process with Types (I,
II, III and IV), International Journal on Future
Revolution in Computer Science &
Communication Engineering, 4, p.392,
-
Roy, Chanchal Kumar and Cordy, James R. (2007), A survey on software clone detection
research, Queen’s School of Computing TR, 541, p.64,
-
Bellon, Stefan and Koschke, Rainer and
Antoniol, Giulio and Krinke, Jens and
Merlo, Ettore. (2007), Comparison and evaluation of clone
detection tools, IEEE Transactions on software
engineering, 33 (9), p.577,
-
Rattan, Dhavleesh and Bhatia, Rajesh and
Singh, Maninder. (2013), Software clone detection: A systematic
review, Information and Software Technology -
Elsevier, 55 (7), p.1165,
-
Razzaq, Abdul and Wasala, Asanka and
Exton, Chris and Buckley, Jim. (2019), The state of empirical evaluation in
static feature location, ACM Transactions on Software Engineering
and Methodology (TOSEM), 28, p.2,
| Other Resources |
---|
-
Ebook, Nicholas Smith, Danny van Bruggen, and
Federico Tomassetti. (2019), JavaParser: Visited, online, Lean Publishing,
|
|