IT-Universitetet i København
  Tilbage Kursusoversigt
Kursusnavn (dansk):Software Acquisition and Requirements, MSc 
Kursusnavn (engelsk):Software Acquisition and Requirements, MSc 
Semester:Forår 2018 
Udbydes, Digital Innovation & Management (dim) 
Omfang i ECTS:7,50 
Min. antal deltagere:15 
Forventet antal deltagere:
Maks. antal deltagere:33 
Formelle forudsætninger:General IT-competences are sufficient. Moreover the student must meet the admission requirements of the IT University. 
Læringsmål:After the course, the student will be able to:
• Describe various levels of requirements and choose the right level in a specific context.
• Write a requirements specification for a complex system. The specification must comprise functional requirements as well as quality requirements.
• Ensure traceability of the requirements, in particular that business goals are reflected in the requirements and that the requirements are verifiable.
• Explain various methods for requirements elicitation and use the appropriate ones in the given context.
• Plan the acquisition process, including deployment in the organization, and choose a suitable way of cooperating with the supplier during the acquisition.
• Describe the legal aspects of an acquisition, and for a specific project identify the risks the contract should deal with.
• Explain how the course relates to software development theory. 
Fagligt indhold:The goal of the course is to enable you to manage acquisition of an IT system from the first idea to the system is in operation (deployed). The system may be a COTS system (Commercial off the shelf, e.g. an ERP system), a system developed in-house, a product to be marketed, or a system developed by others, for instance through off-shore outsourcing. You learn methods that can be used in all kinds of processes, agile as well as traditional.

Acquisition of an IT system may have large consequences for a company or an organization. It is not just a matter of the system cost and organizational implementation cost. It is also about harvesting the benefits you expected. The key to all of this is the requirements specification.

Unfortunately, people who can write good requirements specifications are rare. This is a major cause of disaster in IT projects.

You can find a detailed plan for the course, documents for download, etc. on the course home page: 
Læringsaktiviteter:14 ugers undervisning bestående af forelæsninger, øvelser og vejledning

Each week we look at some theory and techniques behind the learning outcomes. Most weeks there are optional assignments where you try to apply all of it in a realistic acquisition project. You are expected to take the first step of the assignments during exercises with teacher assistance. You make the rest at home and hand it in at the next lecture. The next week you get detailed feedback from the teacher. A few times you have to read a scientific paper at home.
Some of the techniques are so hard that most of you miss in the first assignment. You have to try a few times before you attack the compulsory mini-project that completes the course. During the first part of the course you practice on real-life projects where the first part of the analysis has been made already. At the same time you establish contact to a company or an organization where you in the second half of the course carry out a mini-project and write a report. Most of the report is a requirements specification that in principle could be given to a supplier.

The report is the basis for the oral exam. You may work in teams of up to 4 persons. Reports may be in English or in Danish. It is your own responsibility to find a suitable mini-project or a team you can join. It must be a project with real users and non-trivial requirements. Many students have a project already at the start of the course. 

Obligatoriske aktivititer:Der er ingen obligatoriske aktiviteter. Vær venlig KUN at ændre denne tekst når der er obligatoriske aktiviteter./
There are no mandatory activities. Please, change this text ONLY when there are mandatory activities. 
Eksamensform og -beskrivelse:D22: Aflevering med mundtlig eksamen suppleret af aflevering., (7-scale, external exam)

Hand-in: Report.
Students should expect to produce around 50 pages. There is no absolute minimum or maximum of pages.

Duration of the oral exam: 30 minutes.

Form of group exam: Mixed exam 3
See Study Guide -> Exams -> Course Exams -> Exam Forms for more information.  

Litteratur udover forskningsartikler:Text book: Soren Lauesen: Software Requirements - Styles and Techniques. Pearson/Addison-Wesley, 2002.

Søren Lauesen: Vejledning til kravskabelon SL-07 – Problem-orienterede krav v5. Create Space og Lauesen Publishing, 2017.

Or the English version: Soren Lauesen: Guide to Requirements SL-07 – Problem-Oriented Requirements v5. Create Space og Lauesen Publishing, 2017.

Both editions are available from Amazon, fx