Syllabus spring term 2007

Ingenjörsprocessen för programvaruutveckling

Credits: 6. Grading scale: TH. Compulsory for: C1. Course coordinator: Associate Professor Martin Höst,, Inst f telekommunikationssystem. Assessment: Project, reports and written exam. Parts: 3. Homepage:

Knowledge: The student should know the most important phases in the process of software engineering for development of information and communication systems. Important concepts to know are requirements, design, verification and validation and quality issues. The student should also know a project model and the purpose of project monitoring and control. Further, ths student should be aware of ethical and juridical aspects of software.

Skills: The student should be able to write a requirements specification and thereby take the user's situations into account, make a design and a test plan for a small system. Furthermore, the student should be able to utilize a project model in a small project, which includes writing a project plan, controlling and monitoring a project. The student should be able to relate to laws and ethical guidelines regarding intellectual property rights, patents and similar software related areas.

Attitudes: The student should get an insight of development of information and communication systems and know that this contains several different parts, from idea to product release. Furthermore, the student should get an insight of development work, which requires cooperation, specific roles, milestones and scheduling. The student should understand the purpose of project management, and the trade-off between the parameters: functionality (technical solution), cost and quality, which are important for software projects. Furthermore, the student should gain knowledge and understanding of the importance of quality improvement.

The course gives an introduction to the development of information and communication systems with a substantial share of software. Further, a basic project management model is presented and used in the course. Standards and guidelines for jurudical and ethical considerations are presented.

The course is of overview character and does hence not make any attempts to cover different variants of project and development processes, but focuses on one selected example.

Lectures and seminars in the course introduce the different topics, while a project assignment using aspecific scenario gives insights to the process from idea to finished software product, and gices training in using a project management model. Topics covered are:

The Software Engineering Process
Terminology: Requirements, design, implementation, verification
Documents: Requirements specification, design specification, verification plan.
Support: Process model, infrastracture for software engineering, configuration management

Project management:
Terminology: Planning milestondes, roles, measurements, monitoring
Documents: Project plan, status report
Support: Project management model

Ethics and law:
Terminology: Intellectual property rights, patents

Claes Wohlin, "Introduktion till Programvaruutveckling", Studentlitteratur, 2005 , ISBN 91-44-02861-X
Additional material assigned by the department.


Code: 0106. Name: Exercises and Reports.
Credits: 2. Grading scale: UG. Assessment: Active attendance in seminars and delivery of written reports. Contents: Seminars in teams and individual reports.

Code: 0206. Name: Project.
Credits: 2. Grading scale: UG. Assessment: Approved project. Contents: Project in teams.

Code: 0306. Name: Written Examination.
Credits: 2. Grading scale: TH. Assessment: Approved written exam. Contents: Written exam.