Print
Semester Project: Client/Server System
Code
IT-SEP2
Version
4.0
Offered by
ICT Engineering
ECTS
10
Prerequisites
Main purpose
The purpose is to develop and document a client/server system
The purpose of the PBL part of the course is to promote the students' competencies in collaboration, planning and problem analysis.
Knowledge
Apply all knowledge from all 2. semester courses
Skills
Professional skill learning objectives:
- Document the analysis and design of a software system using UML.
- Devise requirements, use case model, activity diagrams, system sequence diagrams, domain model.
- Design and implement (using SQL) a normalized relational database for data-persistence.
- Apply unit and use case testing based on requirements and code.
- Implement a client/server software system in Java according to design.
- Apply Scrum in combination with Unified Process (UP) and relevant tools in the project work.
PBL skill learning objectives:
- Be able to enforce and develop the group contract
- Can work based on the project group's own problem statement.
- Apply covered theories on personal profiles and cross-cultural aspects in the group.
- Apply knowledge about references and source management.
- Apply academic and technical writing style, report structure and rules for plagiarism.
- Communicate the results of the project work and learning process of the project group in a well-structured manner using technical terms in writing, graphically and orally.
Competences
Professional competency learning objectives:
- Carry out a software project with a clear connection between requirements, analysis, design, implementation, test, and documentation.
- Produce a software design which supports group collaboration.
- Apply relevant design patterns and principles, including SOLID, resulting in a maintainable and extendable software system.
- Perform and explain technical choices.
PBL competency learning objectives:
- Describe potential conflicts in the group and suggest solutions.
- Define and reflect on own learning aims from the current and previous semester.
Topics
Teaching methods and study activities
Group work on project tasks supported by process and technical supervision.
Online, video og class modules on key aspects.
Continuous evaluation and feedback
Compulsory feedback meetings, and on-going ad hoc meetings
Programme specific product
A product in the form of a model and a program.
Resources
Handed out on itslearning.
Evaluation
Examination
Exam prerequisites:
None
Type of exam:
Group exam with individual assessment.
Exam is based on the project report and process report, which must be submitted before deadline and apply with the formalities criteria stated under the Software Engineering specific Guidelines.
Group presentation approx. 20 minutes followed by a joint examination with a joint discussion and individual question rounds for approx. 20 minutes per student including voting.
Individual grades are given on the basis of an overall assessment of the submitted work as well as the individual´s performance during the examination.
Internal examiner.
Tools allowed:
All.
Re-exams:
Students who failed a semester must make a new project.
Students who fail a semester project must attend an information meeting at the end of the summer exam period.
At this meeting, students will be notified about the process of the re-exam and students will form groups.
Deadline for hand in of the project is mid-August (exact date will be informed at the meeting). There will be no guidance in the period up to hand in.
Oral assessment of the project takes place before the start of the autumn semester.
Grading criteria
Grading based on the Danish 7-point scale.
Additional information
Responsible
Troels Mortensen [trmo] (Mona W. Andersen (mwa) for PBL related topics)
Valid from
2/1/2024 12:00:00 AM
Course type
Keywords
Analysis, design, test, documentation, project method, Scrum, Unified Process (UP), UML
Cooporation, conflict management, cultural understanding, personal profiles, communication, group work