|Period:||periode 2 (week 46 t/m 5, dwz 12-11-2007 t/m 1-2-2008; herkansing week 11)
|Participants:||up till now 46 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.
|Literature:||Stephen T. Albin, The Art of Software Architecture: Design Methods and Techniques. Wiley, 2003 (ISBN 0-471-22886-9).|
|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:||Om aan de aanvullende toets te mogen meedoen moet de oorspronkelijke uitslag minstens 4 zijn.|
|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.