Course Details for A.Y. 2014/2015

Course Objectives

This course aims, on one hand, at in-depth enhancing the students’ knowledge acquired in the Software Engineering course, on the other end at introducing new topics. The latter ones can be summarized as: dealing with functional and non-functional properties of component-based systems, studying quantitative properties of software systems like reliability and performance, introducing advanced notions on UML and related technologies. The course is intended to develop students’ capabilities for modeling and analyzing software systems, as well as capabilities of getting use to different tools that support such activities. This experience shall make them able, in future, to fully exploit the functionalities of any tool they will be exposed to.

Course Content

• Software Architectures
• Model-Driven Engineering
• UML profiling
• Non-functional Validation of Software
• Performance Analysis
• Reliability Analysis

Learning Outcomes (Dublin Descriptors)

On successful completion of this course, the student should

Prerequisites and Learning Activities

The maturity of a graduate student mostly consists in being able to choose the better tools (i.e. models, methodologies, software tools, documentation) to accomplish a certain task

Assessment Methods and Criteria

Pre-Assessment There is no formal pre-assessment, but Course pre-requisites are clearly stated on the Module website. Fulfilment of such pre-requisites is verified by formative assessment. Formative Assessment The formative assessment is performed via interactive interaction beteween teacher and students during lectures. Students are aware since the beginning of the Course that they will be involved (in turns) in: - Questioning and discussion, by means of open oral questions to the class or to single students. Summative Assessment Group project followed by an optional oral exam. The group project is aimed at: (1) verification of theoretical competences, and in particular of knowledge and comprehension of Course contents; (2) verification of skills in understanding and solving significant problems, and in explaining the proposed solutions, (ii) capability of collaborative work. This in order to verify the ability of application of techniques learnt during the Course, of analysis of problems and synthesis of suitable solutions, and of evaluation of alternative solutions. Criteria of evaluation will be: the level of knowledge and practical ability; the property of use of the technical/mathematical language; the clarity and completeness of explanations. The oral exam will occur within one week of the project delivery and will typically cover the areas of the project that need clarification plus additional subjects proposed by the teacher. The oral test takes place for all students. Assessment breakdown: 100% end-of-semester summative assessment.

Textbooks

• C.U.Smith, L.Williams, Performance Solutions , Addison Wesley. 2002.    
• Scientific papers and other references provided during the course    
• Ian Sommerville, Software Engineering , Addison-Wesley.    

Internet Resources

Course page updates

• A.Y. 2010/2011
• A.Y. 2011/2012
• A.Y. 2012/2013
• A.Y. 2013/2014
• A.Y. 2014/2015
• A.Y. 2015/2016
• A.Y. 2016/2017
• A.Y. 2017/2018
• A.Y. 2018/2019