Print as pdf if you want a pdf! If you want a nicer printout, click off the browser's automatically added header and footer.
Blekinge Institute of Technology
Department of Software Engineering
Revision: 2
Reg.no:
Course syllabus
Software-intensive Product Development
Software-intensive Product Development
12 credits (12 högskolepoäng)
Course code: PA2576
Main field of study: Software Engineering
Disciplinary domain: Technology
Education level: Second-cycle
Specialization: A1N - Second cycle, has only first-cycle course/s as entry requirements
Language of instruction: English
Applies from: 2024-11-01
Approved: 2024-11-01
1. Descision
This course is established by Dean 2019-05-23. The course syllabus is approved by Head of Department of Software Engineering 2024-11-01 and applies from 2024-11-01.
2. Entry requirements
Admission to the course requires completed courses in programming equivalent to 12 ECTS credits.
3. Objective and content
3.1 Objective
Software intensive systems are described as “any system where software contributes essential influences to the design, construction, deployment, and evolution of the system as a whole” [IEEE Std 42010:2011]. The objective of this course is to, provide knowledge on the fundamental software engineering processes such as specification, design, validation, evolution and maintenance of software intensive products. The intention of this course is to, through a practical case, apply the fundamental software engineering processes for developing software intensive products.
3.2 Content
The course covers the following topics:
- Requirements engineering: Requirements elicitation, analysis, specification, management, and also legal and ethical aspects in software intensive product development.
- Design and architecture basics: Object-oriented design concepts and basics of software architecture.
- Verification and validation: Verification and validation basics, theory and practical information about testing, test planning, test execution and interpretation of test results.
- Maintenance and evolution: Software maintenance fundamentals, need for maintenance, key issues in maintenance and maintenance process, techniques and tools for maintaining and evolving software intensive products.
4. Learning outcomes
The following learning outcomes are examined in the course:
4.1. Knowledge and understanding
On completion of the course the student should be able to:
- Present and discuss different lifecycle activities from requirements to maintenance phase
- Discuss, argue, and select suitable practices/techniques for the requirements, architecture, testing, development and maintenance phases of a software project.
4.2. Competence and skills
On completion of the course the student should be able to:
- Apply requirements, architecting, testing and maintenance principles in a real context.
4.3. Judgement and approach
On completion of the course the student should be able to:
- Discuss and argue legal, social and ethical aspects related to software intensive product development.
5. Learning activities
The teaching consists of lectures in which students are expected to participate through discussions, questions and personal experiences. The course also includes compulsory assessments with fixed deadlines. The students are expected to mostly work in groups in these assessments.
The course begins with an introductory lecture and continues with a series of lectures where a number of topics (see Contents) are introduced. Each lecture includes time for discussions and reflections. Teaching language and materials are in English.
6. Assessment and grading
Modes of examinations of the course
| Code | Module | Credit | Grade |
| 2005 | Written report 1 | 2 credits | GU |
| 2015 | Written report 2 | 2 credits | GU |
| 2025 | Project assignment 1 | 2 credits | GU |
| 2035 | Written report 3 | 2 credits | GU |
| 2045 | Project assignment | 2 credits | GU |
| 2055 | Project assignment 3 | 2 credits | GU |
The course will be graded G Pass, Ux Failed result, a little more work required, U Fail.
The examiner may carry out oral follow-up of written examinations.
The information before the start of the course states the assessment criteria and make explicit in which modes of examination that the learning outcomes are assessed.
An examiner can, after consulting the Disability Advisor at BTH, decide on a customized examination form for a student with a long-term disability to be provided with an examination equivalent to one given to a student who is not disabled.
7. Course evaluation
The course evaluation should be carried out in line with BTH:s course evaluation template and process.
8. Restrictions regarding degree
The course can form part of a degree but not together with another course the content of which completely or partly corresponds with the contents of this course.
9. Course literature and other materials of instruction
Agile Software Requirements (2011) by Dean Leffingwell. Publisher: Addison Wesley, ISBN: 978-0-321-63584-6
Software Architecture in Practice (3rd edition, 2013) by Len Bass, Paul Clements and Rick Kazman. Publisher: Addison Wesley, ISBN: 978-0-321-81573-6
Foundations of software testing: ISTQB certification (2008) by Graham, Dorothy, Erik Van Veenendaal, and Isabel Evans. Cengage Learning EMEA.
Software Evolution and Maintenance: A Practitioner's Approach (2015) by Priyadarshi Tripathy, Kshirasagar Naik, Wiley, ISBN: 978-0-470-60341-3
10. Additional information
This course replaces PA2540