A project portfolio is a collection of works (text, program code, models (architecture, information, etc.) associated with practical workshops. The portfolio further includes a reflection document relating to at least three of the four core areas. The reflection document is 5 "normal pages" (of 2400 characters) per student relating practical experience with relevant theories from the Informatics core areas. The portfolio further includes a front page, table of content, literature list and appendices.

In the portfolio work you will work with industry standard techniques in relation to it systems architecture.

Knowledge:

The student will have practical knowledge of central theories linked to the core areas:

• Systems Development and Design: Core concepts of the systems architecture definition process, Organizational Systems Development, Paradigms of systems development, Soft Systems Methodology.

• Evaluation of IT: Architecture evaluation, Cognitive Engineering, Technochange prototyping, summative and formative evaluation.

• Implementation and Change Management: Nexus of Change management, Knowledge management systems, Computer-supported Collaborative Work, Diffusion of innovations.

• IT security: Privacy By Design, Information Security Management Systems, Identity Management Systems.

Skills: Know and be able to choose and use appropriate methods and techniques within the core areas to analyse complex use situations as relevant for the particular case.

• Systems Development and Design: CATWOE, Rich pictures, IT architecture development, including stakeholder analysis, Architecture Viewpoints and Perspectives, and Architecture Skeleton Construction.

• Evaluation of IT: Lifecycle evaluation, Architecture evaluation, Stakeholder evaluation, Cognitive Walkthrough, Pilot implementations, Phased implementation.

• Implementation and Change management: Organizational structure assessment, mitigation of technology-derived challenges.

• IT security: Privacy Impact Assessment, Risk analysis, Security Planning.

Know and be able to choose and use appropriate methods and techniques within the core areas for designing innovative IT usage tailor made for the users’ needs and competencies as relevant for the particular case.

• Systems Development and Design: Low- and high-fidelity prototyping, Evolutionary Development, Architecture Scenario Design.

• Evaluation of IT: Designing for IS Success from task benefits to organizational benefits.

• Implementation and Change management: Counter-counter implementation, Implementation types derived from technochange.

• IT security: Privacy By Design, Security By Design.

Competencies, to be able to:

• Work with IT related problems individually and with a team.

• Plan the architecture definition process in a case organization.

• Produce architecture models and views based on stakeholder viewpoints and perspectives in a case organization.

• Disseminate and document architectural descriptions understandable for relevant stakeholders and become part of design, development as well as implementation activities.

• Plan, conduct, analyze, evaluate, and document empirical activities for acquiring relevant information for the architecturing process.

• Critically reflect upon the use of specific methods.

• Systematically acquire understanding of new approaches within the core areas and individually take responsibility for one’s own professional development.

It is recommended to follow BUITA and Project Portfolio in the same semester.

In groups of 2 to 6 students you develop your own practice portfolio in relation to a chosen case company. At least three of the Informatics core areas are covered. Informatics core areas are: Systems Development, Implementation, including change management, Evaluation of IT applications, and IT security.

Group examination.

Oral exam based on the Project portfolio. In the exam each student has up til 5 minutes to present a topic of own choice from the portfolio work. The exam takes place as a conversation between the student(s) and examiners.

Two examiners (internal). Grading scale: 7-step grading scale.

The length of the exam, including considering marks and feedback is as follows:

• 1 student: 30 minutes
• 2 students: 60 minutes
• 3 students: 75 minutes
• 4 students: 90 minutes
• 5 students: 105 minutes
• 6 students: 120 minutes

Monday 20. June 2016.

Deadline for submitting the project report = 6 June 2016.

Group examination.

Oral exam based on the Project portfolio. In the exam each student has up til 5 minutes to present a topic of own choice from the portfolio work. The exam takes place as a conversation between the student(s) and examiners.

Two examiners (internal). Grading scale: 7-step grading scale.

The length of the exam, including considering marks and feedback is as follows:

• 1 student: 30 minutes

• 2 students: 60 minutes

• 3 students: 75 minutes

• 4 students: 90 minutes

• 5 students: 105 minutes

• 6 students: 120 minutes

Before end of August 2016.