Please ensure Javascript is enabled for purposes of website accessibility

Μάθημα : Διαδραστικές Τεχνολογίες (Διδασκαλία 2026-2027)

Διαδραστικές Τεχνολογίες (Διδασκαλία 2026-2027)

ECE_ΓΚ904 - Νικόλαος Αβούρης, Κωσταντίνος Μουστάκας, Χρήστος Σιντόρης

Περιγραφή Μαθήματος

Μάθημα

Επιδιωκόμενα μαθησιακά αποτελέσματα     

Με την ολοκλήρωση αυτού του μαθήματος ο φοιτητής θα πρέπει να γνωρίζει τις βασικές θεωρητικές αρχές που διέπουν την αλληλεπίδραση του χρήστη με μηχανές στον σύγχρονο κόσμο. Επίσης να γνωρίζει τις τεχνολογίες, μεθόδους και εργαλεία για τη σχεδίαση και ανάπτυξη εύχρηστων διαδραστικών συστημάτων λογισμικού.

Δεξιότητες

Με την ολοκλήρωση του μαθήματος ο φοιτητής αναμένεται να έχει αποκτήσει λειτουργική γνώση των μεθόδων και εργαλείων για την μέτρηση ευχρηστίας και εν γένει της ποιότητας διαδραστικών συστημάτων λογισμικού καθώς και τη σχεδίαση της διεπαφής χρήστη τέτοιων συστημάτων.

Προαπαιτήσεις

Καλή γνώση γλωσσών προγραμματισμού, κατά προτίμηση web stack, ή/και Python ή Java. Εισαγωγικές γνώσεις στατιστικής.

Λέξεις Κλειδιά: διαδραστική τεχνολογία, ευχρηστία, μοντέλο ανθρώπινου επεξεργαστή πληροφορίας

 

Περισσότερα στον κανονισμό του μαθήματος

 (5)     |  8 αξιολογήσεις
 |  Σχόλια (0)
  • Assignment 1 - Requirements analysis

    The goal of our first assignment is to practice identifying and documenting functional and non-functional requirements based on the Volere framework, through a familiar and practical design subject.

     

    The assignment has two parts:

    1. In class (45 min): identify stakeholders, find one conflict between them, and write four Volere requirement cards.
    2. At home (report): expand and refine your in-class work into a complete, prioritized requirements specification.

    In-class Assignment

    In this exercise, you will work in teams of two to analyze and specify the requirements for a Smart Shopping Cart system. The activity aims to help you understand how to translate a design idea into a structured set of requirements that can guide implementation and evaluation.

     

    1. Form teams of two; read the scenario.
    2. List the top 4 stakeholders (at least one non-shopper) and name one conflict between them
    3. Write 4 Volere cards: 2 functional, 2 non-functional
    4. Share-out: 3–4 random teams present one card each; the class tests it against the Quality Gateway (slide 97): is it complete, correct, measurable, unambiguous?

     

    Scenario

    A mid-size supermarket chain wants to pilot smart carts in one store. Each cart may have a barcode scanner, a screen, a built-in scale, a payment terminal. Shoppers scan items as they shop and pay at the cart, skipping the checkout queue. The chain also wants to use cart data for personalized offers. Typical shoppers might include, among others, parents with small children, older shoppers who prefer cash, tourists who do not read Greek, people with visual impairments. Saturday mornings are the busiest time.

     

    Deliverable

    Submit a report by next Monday using the single column ACM Master Article Template (find it in STEP 1 in section The Workflow and Templates) in PDF format.

     

    The short report, in English or Greek, should be delivered on the assignment (one submission per team - it's okay if only one of you makes the submission). Recommended length: approximately 2–3 pages, excluding the appendix.

     

    Report should consist of

    • Title: Assignment 1: Smart Shopping Cart – Requirements Analysis
    • Team Members: List the names and matriculation numbers of both team members.
    • Overview (50–100 words): Briefly describe the purpose of the “Smart Shopping Cart” system and the main goal of this assignment.
    • Context (short lists): Stakeholders, constraints, assumptions.
    • Requirements table (not counted): 4 functional and 3 non-functional requirements
    • Conflicts and prioritization (100–150 words): How you resolved at least one conflict and why your Must requirements are Must
    • Process and Method (100–150 words): How you worked, and where elicitation was hard or ambiguous.
    • Reflection (150-250 words): What you learned and what you would do differently.
    • Appendix: Your in-class notes and cards, plus any notes, sketches or revisions made after discussion.

     

    Requirements table fields. Give each requirement:

    • ID and type (volere category, slides #99-#101)
    • description
    • rationale
    • source (which stakeholder)
    • fit criterion
    • priority (Must, Should, Could, Won't have)
    • conflicts or dependencies, if any
    • one validation idea: how you would check the fit criterion

    Your report should refine the in-class cards. If you changed a card after class, say what changed and why in the appendix.

Ημερολόγιο

Ανακοινώσεις

Όλες...