Skip to main content

ID1009 Agile Software Construction 9.0 credits

Level: Fundamental

Course offering missing for current semester as well as for previous and coming semesters
Headings with content from the Course syllabus ID1009 (Spring 2009–) are denoted with an asterisk ( )

Content and learning outcomes

Course contents

To successfully plan and lead a non-trivial software project, it is important to possess knowledge of all project activities in a software project. The course focuses on teaching activities such as project planning and management, quality assurance, version management, basic cost and time estimation, basic software metrics, making and analysing requirements specifications and basic validation and verification of software.
After the course, the student will have:
* participated actively in discussions on lectures and seminars
* written an essay on a topic relevant for software developing
projects
* presented the essay in a seminar
* written a feedback document for another student’s essay
* presented the feedback in a seminar

Intended learning outcomes

The purpose of software engineering is to enable repetitively successful software development, that is software projects where the software is developed according to its specification and within given time and budget boundaries. In a world of increasing complexity and growing demands on flexibility it is necessary to combine software engineering principles with agile methods like test-first development and extreme programming.
Having successfully completed the course, the student should be
able to:
* describe what is the difference between plan-driven and agile
processes and motivate the description
* account for what is significant for a software engineering
approach to software development and the principles behind it
* account for what is significant for a plan-driven approach to
software development and the principles behind it
* account for what is significant for an agile approach to
software development and the principles behind it
* describe several techniques (both classical software engineering
ones and agile ones) for:
o requirements elicitation and requirement management
o resource planning
o risk analysis and risk management
o test planning
o version management
o time and cost estimations
o project automation
* make judgements about applicability of a these techniques in some
known project, possibly combining plan-driven techniques with
agile ones
* decide and motivate why some technique is suitable for use in a
plan driven software project
* decide and motivate why some technique is suitable for use in an
agile software project
* find suitable software engineering methods for his or her work
in future projects
* easily adapt to work processes using software engineering
techniques

Course disposition

The course is given in parts of lectures and seminars, an exam, the writing of an essay and a feedback report for another student’s essay.

Literature and preparations

Specific prerequisites

No information inserted

Recommended prerequisites

No information inserted

Equipment

No information inserted

Literature

To be decided.

Examination and completion

If the course is discontinued, students may request to be examined during the following two academic years.

Grading scale

A, B, C, D, E, FX, F

Examination

  • INL1 - Exercise, 1,5 hp, betygsskala: P, F
  • PRO1 - Project, 4,5 hp, betygsskala: P, F
  • TEN1 - Examination, 3,0 hp, betygsskala: A, B, C, D, E, FX, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

Other requirements for final grade

* Active participation during lectures and seminars (1,5 hp)
* Essay, feedback document, essay seminars (4,5 hp)
* Take-home exam (3 hp)
For the exam, the entire grade scale A/B/C/D/E/Fx/F will be used while the active participation during lectures and seminars, and the essay only will be graded pass or fail (P/F). To get a grade for the entire course, all three examination points have to be graded at least pass or E. The grade for the entire course will be based on the grade of the take-home-exam.
Students that are decided to be close to pass the exam will be given a possibility to do some additional work to complete the exam. This will mean that the student can get the grade pass (E) on the written exam, but not a higher grade. The course co-ordinator will inform the students that will be given this possibility in connection to the announcement of the exam results. The additional work has to be handed in before the decided deadline and can only be used to reach the grade E for the exam at hand.

Opportunity to complete the requirements via supplementary examination

No information inserted

Opportunity to raise an approved grade via renewed examination

No information inserted

Examiner

Profile picture Beatrice Åkerblom

Ethical approach

  • All members of a group are responsible for the group's work.
  • In any assessment, every student shall honestly disclose any help received and sources used.
  • In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

Further information

Course web

No information inserted

Offered by

ICT/Systems Science (SU)

Main field of study

Technology

Education cycle

First cycle

Add-on studies

No information inserted

Contact

Beatrice Åkerblom, beatrice@dsv.su.se, 08-164988