Undergraduate Course: Software Design and Modelling (INFR10064)
|School||School of Informatics
||College||College of Science and Engineering
|Credit level (Normal year taken)||SCQF Level 10 (Year 3 Undergraduate)
||Availability||Available to all students
|Summary||This course introduces the design and modelling of software systems using object-oriented techniques. We start by exploring the use of modelling in software development. Students learn to document designs in the Unified Modeling Language, UML, with emphasis on class, sequence and state diagrams and the Object Constraint Language, OCL. We use modern model-driven development tools and discuss their strengths and weaknesses. We study criteria that make one design better than another in context and introduce design principles and patterns that capture good practice.
This course replaces INFR10056 - Software Engineering with Objects and Components.
The course begins by placing design and modelling in the context of the various software engineering processes in widespread use today. Via labs, lectures and self-study using readings, videos and formative exercises, it teaches students to produce (initially straightforward) designs and to document them using UML models, both on paper and with an appropriate tool. We discuss the different affordances of these modes and how models may be used (i) purely informally, (ii) as reviewed documentation for designs, and/or (iii) in model-driven development in which models are formal artefacts and code may be generated from them.
The second part of the course focuses on identifying and producing good designs. What principles should a good object-oriented design follow? We learn some common design patterns and their role in development and learning.
Finally we turn to practical model-driven development: how can the cost-benefit ratio of modelling be improved, now and potentially in the future? Students will learn about model transformations, both model-to-model and model-to-text (e.g., code generation) and be introduced to current tools supporting these. We discuss the role of domain specific languages and the integration of model driven development with agile processes. Throughout the course, we identify the deficiencies as well as the benefits of the fast-changing state of the art, aiming to equip students to critically evaluate tools and techniques that become available to them in future.
Information for Visiting Students
|High Demand Course?
Course Delivery Information
|Academic year 2016/17, Available to all students (SV1)
|Learning and Teaching activities (Further Info)
Lecture Hours 15,
Seminar/Tutorial Hours 14,
Feedback/Feedforward Hours 1,
Summative Assessment Hours 4,
Revision Session Hours 1,
Programme Level Learning and Teaching Hours 4,
Directed Learning and Independent Learning Hours
|Assessment (Further Info)
|Additional Information (Assessment)
||Coursework element is an individual exercise done in the scheduled lab session. It concentrates on assessing the first 3 learning objectives (50%).
The written examination concentrates on assessing the last two learning objectives, plus the "on paper" part of the second (50%).
||Exercises in the weekly lab will be supported by automated feedback where possible. The lab sessions will be run interactively with opportunities to compare answers with other students, raise questions about them, and get help from the TA and the lecturer.
Where appropriate the course will provide online quizzes with immediate feedback.
Students will be encouraged to interact on the Piazza or similar group, where the TA and lecturer will also be available for feedback on questions that need it.
Notes and explanatory videos will be provided on formative exercises, as appropriate.
The summatively assessed coursework will be marked by a combination of automated and human feedback, provided as soon as may be and certainly within two weeks. A lecture will be dedicated to discussion and matters arising.
As is standard in Informatics, individual feedback will not be provided on the written exam. The lecturer will produce brief notes on what was done well or badly, common errors and points to note.
||Hours & Minutes
|Main Exam Diet S1 (December)||2:00|
On completion of this course, the student will be able to:
- Design simple object-oriented systems.
- Create, read and modify UML diagrams documenting designs, both on paper and in an appropriate tool.
- Determine whether a UML model and a body of Java code are consistent; if they are inconsistent, identify the inconsistencies precisely and propose remedies.
- Evaluate and evolve object-oriented software designs, making use of common design patterns if appropriate.
- Discuss the use of modelling and model-driven development tools in software development, e.g. why and how models of software can have varying degrees of formality, capabilities and limitations of the tools.
- Timothy Lethbridge and Robert Langaniere. Object oriented software engineering: practical software
development using UML and Java. McGraw Hill, 2002.
- Perdita Stevens with Rob Pooley. Using UML. Pearson (second edition).
|Course organiser||Prof Perdita Stevens
Tel: (0131 6)50 5195
|Course secretary||Mrs Victoria Swann
Tel: (0131 6)51 7607
© Copyright 2016 The University of Edinburgh - 3 February 2017 4:25 am