BIBV3050 Web development Course description

This course introduces the tools, workflows, and design principles that underpin modern web-based application and user interface development. Students explore how structured data, information architecture, and APIs interconnect, and apply this knowledge to planning, specifying, and prototyping real-world applications. The course makes use of contemporary tools and development practices and is suitable for students from a range of backgrounds, including those interested in information-rich domains such as libraries and archives. No programming experience is required, and the course is accessible to students with diverse academic backgrounds.

The teaching language is in English.

None.

After completing the course, the student should have the following overall learning outcomes defined in terms of knowledge, skills and general competence:

Knowledge

The student

• has knowledge of structuring data, information architecture principles and the use of API's
• has knowledge of modern front‑end development, usability and styling approaches
• has an understanding of how modern tools and processes support the development of web-based applications

Skills

The student

• is able to write and iterate on requirement specifications based on modern development processes
• is able to organize and structure content in a web application, build usable information architectures, and fetch, process, and present data through API calls.
• is able to translate designs into interactive prototypes using modern tools and methods
• is able to generate and refine UI concepts using modern front-end development and styling approaches.

General competences

The student has a general understanding of modern processes and practices for designing and prototyping web-based applications.

The course consists of a combination of lectures, group work, labs and homework. The course is campus-based.

To be eligible to submit the exam, the student must complete two milestone discussions, both of which must be approved.

Milestone 1: Planning, Requirements, and Design

This session covers:

• requirement specifications and development processes
• information architecture and content structuring
• early UI/UX concepts and design planning

Milestone 2: Prototyping, Data Integration, and Final Review

This session covers:

• interactive prototypes and usability considerations
• API-based data fetching and presentation
• front-end implementation progress and final readiness check

General Rules

• Milestones must be completed with the same group that submits the final project.
• Each session is scheduled during clinic/lecture hours and lasts 15-20 minutes.
• Discussions are not graded but marked complete or not complete at the group level.
• To be marked complete, at least one group member must attend and participate. If no one attends, the milestone is marked as not complete.

Aims of the Requirement

The milestone discussions aim to support steady progress in the group project and to provide timely feedback at key stages. They help students refine requirements, information architecture, design concepts, prototypes, and API integration, ensuring the project develops iteratively and in line with professional practices for modern web-based applications.

Deadline and Make-Up Policy

All coursework discussions must be completed by the deadlines listed in the course schedule for the student to take the exam. If a group misses a scheduled discussion (i.e., no members attend), the session will be marked as not complete. The group will be given one opportunity to reschedule and complete only one missed discussion before the final deadline. If more than one discussion is missed, the coursework requirement will not be approved, and the group will not be eligible to submit the final project or sit for the exam. Groups are responsible for coordinating attendance and ensuring at least one member is present and actively participating.

Full details about each milestone discussion will be published on the course space on Canvas.

Assessment in Design and Prototyping of Modern Web-Based Applications consists of two submissions, each accounting for 50% of the final grade. Students must pass both components to pass the course.

1. Individual Report (50%)

The individual report (approx. 5 pages) evaluates the student’s personal understanding of the project. This report focuses on individual reasoning and conceptual understanding, independent of group performance.

It must include the student’s own:

• analysis of user needs and requirement specifications
• rationale for information architecture and design decisions
• reflection on prototyping, tools, development processes, and learning
• description of their individual contribution to the group project

2. Group Project Report and Demonstration (50%)

The group submission documents the web-based application prototype developed by the team. This report focuses on the collective practical work and the delivery of the final product.

It must include:

• the group’s final requirements and project plan
• information architecture and content structure
• UI/UX designs, prototypes, and screenshots
• technical implementation, including API data integration

Students awarded a fail grade are given one opportunity to submit an improved version for assessment. If the project work receives a failing grade, the whole group needs to sit a new examination.

All aids are permitted, as long as the student follows the rules for examinations, source use and referencing, and OsloMet's guidelines for using artificial intelligence (AI) in student assignments.

Letter grading A-F.

The exam papers are assessed by one internal and one external examiner. At least 10% of the exam papers or at least 10 exam papers will be assessed by two examiners. The grades awarded for the papers assessed by two examiners form the basis for determining the level for all the exam papers.