|Credits:||7.5 ECTS (=5.25 old credit points)|
|Period:||periode 2 (week 46 t/m 5, dwz 14-11-2005 t/m 3-2-2006; herkansing week 12)|
|Participants:||up till now 37 subscriptions|
|Schedule:||Dit is een oud rooster!
A software architecture describes the global structure of a software system, its components/parts and relationship between those parts, the way these components cooperate, etc.. Choosing an architecture is important, for example because an architecture forms the starting point for design, implementation and reuse of components between systems. If a software architect makes a wrong choice a great deal of effort is often involved to repair this in a working system. Therefore, when creating an architecture attention has to be paid to aspects like flexibility, adaptability and maintainability. Different stakeholders may impose different and often contradictory requirements.
Undergraduate students wishing to take this course as part of the Software Engineering minor can be accepted on the condition that they have completed the Software Project.
|Literature:||Martin Fowler, Patterns of Enterprise Application Architecture. Addison-Wesley, Boston, 2003. ISBN 0-321-12742-0.|
|Course form:||Four weeks of lectures; an architecture project in teams of 5; a presentation about the project; a review of a different team's architecture.|
|Exam form:||A multiple choice test halfway through counts for 1/3 of the final mark; the project work (as described in written reports and presentations) contributes the other 2/3. However, the architecture document must be judged with a passing grade. If this is not the case it is not possible to get a passing grade for the course.|
|Minimum effort to qualify for 2nd chance exam:||Anyone who has participated in the project is allowed to repeat the multiple choice test; the new grade for this will replace the old one.|
Anyone who has participated in the project is eligible for a supplementary project task. The grade for this will not replace the grade for the architecture document, but will be used to modify judgment of some aspects.
|Description:||You will cooperate in a team to create an architecture for a client. The main deliverable will be a written description of the architecture which discusses alternatives and makes statements about (a.o.) the feasibility and adaptability.|