Prerequisite/Recommended prerequisite for
participation in the module
The students should have basic programming experience.
Content, progress and pedagogy of the
module
To provide students with knowledge in different development
methods for development of software. This involves understanding of
process models (plan-driven as well as agile), analyses for
requirements as well as software validation and evolution.
Learning objectives
Knowledge
- Must understand about requirements engineering and
specification
- Must know about different process models for software design
and development
- Must understand the difference between a plan driven process
model and an incrementable agile process model
- Must know the Waterfall model, the Spiral model, Extreme
Programming and SCRUM, amongst others
- Must understand when to use which process model for a given
project
- Must be able to link user requirements and technical
requirements for a specific IT software
- Must be able to explain the interaction between a system and
users
- Must be able understand different methods for validation and
testing
Skills
- Must be able to identify and compare different use situations
for a particular IT product
- Must be able to identify, analyse and compare different
methodologies for elicitation of requirements
- Must be able to describe and use different techniques for
requirements analysis and specification
- Must be able to use UML as part of the requirements analysis
and specification development
- Must be able to define verifiable criteria for a software or
parts of a software
- Must be able to evaluate and validate different software
solutions
- Must be able to plan and perform evaluations of software or
parts of the software
- Must be able to design and conclude on a requirement
specification for a given application
Competences
- Must be able to develop a requirement specification for
particular software
- Must have competences in discussing and documenting different
approaches to development of software competences
- Must have competences in carrying out the different phases of a
software engineering process
- Must be able to evaluate the process of software engineering
and the single elements in relation to the purpose of the software
being developed
Type of instruction
Types of instruction are listed at the start of ยง17; Structure
and contents of the programme.
The types of instruction for this course are decided according
to the current Joint Programme Regulations and directions are
decided and given by The Study Board of Electronics and IT.
Exam
Exams
Name of exam | Software Engineering |
Type of exam | Written or oral exam |
ECTS | 5 |
Assessment | 7-point grading scale |
Type of grading | Internal examination |
Criteria of assessment | The criteria of assessment are stated in the Examination
Policies and Procedures |