THE IT FACULTY BOARD

DIT037,  Project: Changing Software Development Process,  15.0 higher education credits
First Cycle

1. Confirmation
The course syllabus was confirmed by the IT Faculty Board on 2010-09-10, effective from 2011-08-29.
Field of education: Science 100%

Main field of studies | Specialization
Computer Science-Software Engineering and Tech | First Cycle, has at least 60 credits in first-cycle course/s as entry requirements

Department: Computer Science and Engineering

2. Position in the educational system

The course is an optional project course in the Software Engineering and Management Bachelor's programme and is part of this programme's curricular thread in Software Management.

3. Entry requirements
The course is only accessible for students with a completed first years studies at the Software Engineering and Management Bachelor´s programme.

4. Course content
The course consists of one item: an exploratory study of an emerging area of change related to organizations within Software Engineering and Management discipline. The purpose is to identify a problem area of relevance to industry as well as research , form specific research problems that are explored in accordance with what is generally considered an established research approach). This includes literature review, data collection, data analysis, and the writing of a research report in the form of a research paper. Examples of change areas include focusing on (1) concrete practices such as the use of reference architectures, test-driven development, pair-programming, distributed and/or community driven development; (2) tool use such as in code-generation, and requirements modelling; (3) the emergence of new software-related artifacts such as a new/changing software standard, or a new/changing programming language; and finally (4) changes in strategies for achieving long-term sustainability in development and/or introduction of changes, such as technology road-mapping, and strategic planning.  The study is conducted as a group project, and assists actual research projects or an industrial partner directly. Assistance is given on for what applicable for specific projects, but the above four examples may be considered as guiding principles for what is relevant for the course. Contact information to potential project owners (industrial or research) is supplied to the students, but student groups may also write their own project suggestions and thus provide industrial or research contacts themselves. It is, however, up to the student groups to establish and maintain such collaborations. The course is thus a great chance for furthering existing knowledge in an area of interest, or complementing such knowledge with a study of an area previously not covered in courses, including potential areas of interest for later bachelor thesis work.

5. Learning outcomes
After completion of this course, the student will be able to:
5.1. Knowledge and understanding

Display an understanding for how project goals are defined to capture research and practice relevance.

Understand the role of a theoretical framework in a research project.

Understand the role of a literature review in a research project.

Understand the role of data collection in a research project.

5.2. Skills and abilities

Show the ability to perform a literature review of relevant published research papers.

Perform a data collection.

Apply a theoretical framework to analyze collected data.

5.3. Judgment and approach

Plan and structure a research project.

Define problem statements on a relevant level.

Identify or define a relevant theoretical framework.

Identify an appropriate technique and set of questions relevant to perform a data collection.

Effectively use a theoretical framework to analyze collected data.

Place the analyzed data in relation to a current are of interest to research and practice (and in accordance with the problem statement made).

6. Literature

The course material will be decided specially for each project. The students will need to access research databases for literature review and subsequently read material relevant to the specific needs of their research project.
The course literature from DIT548 Software Process Improvement and DIT035 Change Management in Software Development Organizations may, however, be important for students to recap in order to identify potential areas of impact when introducing change.

7. Assessment
The course is given in English. All submissions must be in English.

The course is examined by written group report, as well as an individual report. The individual report outlines what the individual student would argue as particularly interesting and relevant parts to expand on if the group would continue with a second iteration of the research. Students may only rely on the group report for three examination occasions, as in (1) the original deadline, and (2) + (3) the two re-exam occasions all offered before the next time that the course runs. Failing after these three occasions means that the student must reenter the project and thus once again participate in a new research project (thereby essentially re-entering the course with the same examination requirements as all others in that year). A student who has failed a test twice has the right to change examiners,  if it is possible. A written application should be sent to the department.

8. Grading scale
Fail, Pass, Pass with distinction.
For grading purposes, the group report has 60% weight and the individual report 40%, and the two are combined into one grade. Both submissions are mandatory and one grade is given based on the combined score. For a high pass, the emphasis lies on exhaustiveness and precision rather than scope. In other words, high pass submissions show critical thinking that holds depth of analysis and the ability to generate well supported but novel results (i.e. intellectual ability and maturity for thinking beyond the obvious) that are well related to existing research, as key contributions.

Regarding the application of ECTS scales, please see Vice-Chancellors decision 2007-05-28, dnr G 8 1976/07.

9. Course evaluation
After completion of the course the students are to be given the possibility of participating in course anonymously. The processed results of the course evaluations are to be made accessible to students and also made available to new students at the beginning of the next course. Possible changes brought about as a result of course evaluations to be described.

10. Additional information
Language of instruction: English.