IV1300 Software Engineering 7.5 credits

Programvaruteknik

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-driven development and customer on site.

Offering and execution

Course offering missing for current semester as well as for previous and coming semesters

Course information

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 during lectures and seminars.
  • participated actively in a software project using a combination of plan-driven techniques and agile ones.

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-driven development and customer on site.

Having successfully completed the course, the student should be able to:

  • describe 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 the agile methods of Scrum and XP.
  • describe several techniques (both classical software engineering ones and agile ones) for:
    - requirements elicitation and requirement management
    - resource planning
    - risk analysis and risk management
    - test planning
    - version management
    - time and cost estimations
  • 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.
  • evaluate projects and analyse what caused successes and failures for use in future projects.

Course Disposition

The course is given in parts of lectures and seminars, an exam and a software project. The goal of the software project is to get practical experience of using software engineering techniques.

Literature and preparations

Specific prerequisites *

  • Completed upper secondary education including documented proficiency in Swedish corresponding to Swedish B and English corresponding to English A. For students who received/will receive their final school grades after 31 December 2009, there is an additional entry requirement for mathematics as follows: documented proficiency in mathematics corresponding to Mathematics A. And the specific requirements of mathematics, physics and chemistry corresponding to Mathematics D, Physics B and Chemistry A.
  • Good knowledge in programming.

Recommended prerequisites

Good knowledge in programming

Equipment

No information inserted

Literature

  • Ian Sommerville:
    Software Engineering, 9

    ISBN-10: 0137035152
    ISBN-13:  9780137035151

    Publisher:  Addison-WesleyAlistair

  • (Cockburn: Agile Software Development, Addison-Wesley, 0-321-48275-1)

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 *

  • PRO1 - Project, 4.5 credits, Grading scale: P, F
  • TEN1 - Examination, 3.0 credits, Grading scale: 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.

Opportunity to complete the requirements via supplementary examination

No information inserted

Opportunity to raise an approved grade via renewed examination

No information inserted

Examiner

Mira Kajko-Mattsson

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

Further information about the course can be found on the Course web at the link below. Information on the Course web will later be moved to this site.

Course web IV1300

Offered by

EECS/Computer Science

Main field of study *

Technology

Education cycle *

First cycle

Add-on studies

No information inserted

Supplementary information

Older course information, until fall 2010:
http://people.dsv.su.se/~beatrice/IV1300/