Kursusbasen

Kursusoversigt

Kursusbeskrivelse

Kursusnavn (dansk):	Analyse, design og softwarearkitektur
Kursusnavn (engelsk):	Analysis, Design and Software Architecture
Semester:	Efterår 2017
Udbydes under:	Bachelor i softwareudvikling (bswu)
Omfang i ECTS:	15,00
Kursussprog:	Engelsk
Kursushjemmeside:	https://learnit.itu.dk
Min. antal deltagere:	1
Forventet antal deltagere:	0
Maks. antal deltagere:	150
Formelle forudsætninger:	The student must have the following skills to register for this course: familiarity with at least one object-oriented programming language such as Java, C++, C#, Objective-C, or Eiffel be able to design, implement, and test medium-sized object-oriented programs that includes the use of concepts such as classes, encapsulation, inheritance/polymorphism, interfaces, packages, data structures (arrays, collections, lists, etc.), threading, IO operations (files, streams, and serialization), and basic GUI programming These background skills are achieved by following the Basic Programming courses in the 1st and 2nd semester at the IT University's Bachelors degree program in Software Development. ----- Information om studiestruktur Dette kursus indgår på tredje semester på bacheloruddannelsen i softwareudvikling.
Læringsmål:	After completing the course and its project work students should be able to: describe and apply object-oriented methods for analysis and design, explain the principles of software architecture, including the variety of common architectures and design patterns and their use, understand and be able to execute all the primary facets of software development within software engineering including analysis, design, implementation, testing, validation, and verification, be able to document the analysis, design, and software architecture of large systems through the use of common standards for documentation including UML and C#'s documentation tools, design and implement software using the C# programming language, including the use of C# data structures (arrays, collections, strings, regexp), delegates, events, generics, LINQ, data access, multi-processing and threading, distributed programming, testing and NUnit, user interface programming, and Web programming, be able to continuously change (re-factor) a software system through adjustments in its architecture or refinements in its configuration, be able to construct useful, coherent, large-scale systems of up to approx. 10 KLOC in size in the C# programming language, including the ability to perform system and domain analysis for a given problem, propose an appropriate software architecture, write a system specification and its implementation, and validate the implementation against its specification.
Fagligt indhold:	object-oriented analysis and design using UML as modeling language software architectures and design patterns principles of software engineering the C# programming language and the .NET platform advanced programming in an OO language
Læringsaktiviteter:	12 forelæsninger + lejlighedsvis øvelser i forbindelse med undervisningen 12 lectures + 10 exercise sessions. Teaching and learning interactions are primarily in the form of lectures, small group exercises, and assignments in the first two-thirds of the course. The last third of the semester focuses on a software engineering project. Assignments will be given each week and they will be due in one week, but for the break in week 42. Each assignment will be specified to be individual or group-based. Individual assignments must be completed individually; group assignments must be completed with a group. Groups will be determined at the beginning of the term. Project work begins mid-November.
Obligatoriske aktivititer:	To access the exam, students will have to get approved all the 5 mandatory activities throughout the course. Be aware: The student will receive the grade NA (not approved) at the ordinary exam, if the mandatory activities are not approved and the student will use an exam attempt.
Eksamensform og -beskrivelse:	X: Eksperimentel eksamensform., (7-scale, external exam) At the beginning of the course, students will be given a project and a mandatory final hand-in in the form of a technical report will have to be submitted to access the exam. The exam will be a 4 hours written exam on paper with neither access to books or electronic aids. The Technical report and written exam will be assessed independently; one single grade will be computed based on a 30/70 ratio between hand-in and written exam respectively. However, both the hand-in and the written exam will have to receive a grade of at least 2 to successfully pass the exam. Submission of the technical report will follow the normal ITU submission timeline.
Litteratur udover forskningsartikler:	Course Books: [OOSE] Object-Oriented Software Engineering by Bernd Bruegge and Allen H. Dutoit. 3rd. edition. 2010. [OOSE] is the main text book for the course, which we shall follow. Most of this book will be used and will be the basis for most of the OOSE lectures. [PrC#] Programming C# 6.0 by Ian Griffiths. This book gives a thorough introduction to C# version 6.0 and the whole .NET platform. This book will be used for most of the C#/.NET lectures. Additional Literature: [C#P] C# Precisely by P. Sestoft and Henrik I. Hansen. [C#P] is a distillation of the ECMA C# standard for the reader who knows Java and for those not interested in digesting the entire 500+ page standard.