• Represent events as classes, structures, and attributes.
• Update the class diagram of the model component.

• (Re-)Design your user interface to support the patterns related to user perception. Describe which patterns you used and the considerations made.
• (Re-)Design your user interface to include navigation signs. Describe which signs you used and the considerations made.

• List class and event candidates systematically
• Produce the resulting event table

• Create behavioral patterns from event traces.
• Study common events.
• Derive class attributes from behavioral patterns.

• Base the design on function types and create a class diagram with operations and specifications of complex operations.
• Specify complex operations

• Design your user interface to support the users' working memory. Describe how well you did this and the considerations made.
• Design visuals to direct users’ attention towards relevant information and functions. Describe how you did this and the considerations made in terms of striking the right balance between having the right amount of attention-grabbing elements vs. overloading users with visual elements.

The scraper must be able to save data to the database, which will simulate and appear like realistic data. It must generate a baseline for Hotel Kompas and use this value for generating random prices for its competitors within a certain range. The random prices should have a certain probability to reach beyond the threshold margin, which will then trigger a notification.

The scraper must update prices for multiple booking sites. Multi-sites, single (competitors own site), which must also be added to the static booking site table in the database.

Write in findings.

• Take usability feedback into consideration
• Look back on MoSCoW and what we originally thought
• Describe what we'll do now

The web scraper must be able to function on all competitors booking sites.
Make sure the class is able to easily implement new booking sites with a variety of layouts.

More information on page 128 in the SU book.

• Design all the icons (that you are aware of so far) illustrating functionality within your semester project system: that is, icons used to activate the functionalities. Apply Hortons icon checklist to inform your designs and discuss why you use particular items on the checklist while other may be less prioritized.
• In the physical design you are making now, consider how you will design for all of Nielsens heuristics, e.g. “recognition rather than recall”, “visibility of system status” etc.

• Create a list of possible companies for collaborations, including probable issues those businesses may be facing.

• Create a "first contact" formula, ensuring that all the right information is given to the company and the right questions are answered.

• Discuss methods for collecting data (to obtain understanding) in the domain of your semester project. Which are you considering to apply? Why? Discuss pros and cons.

• Consider the data gathering method "contextual inquiry" (from Benyon). In relation to your semester project, list which people you would interview and what aspects of their jobs you would focus upon and observe.

• Consider the data gathering method "Artefact collection" (from Benyon). In relation to your semester project, consider and list the artefacts that are relevant to collect from - or study in - the domain.

• Determine the application domain with use cases.
• Assess social changes in the application domain.

• Criteria
• Component

Dette bliver i form af moscow, som får uddybende text og forklaring.

• List at least 10 functional and 10 non-functional requirements for the system of your semester projects (based on the empirical data collected)
• Prioritize these requirements. Discuss why they are prioritized in that order

Discuss techniques to envision the requirements:

• Which are you considering to apply? Why? Discuss pros and cons
• Select the most appropriate envisionment technique at this stage in your project and envision the most highly prioritized requirements.

• People: Physiological differences, Psychological differences, Social differences, Domain Expertise
• Activities: Purpose of activities to be supported by the system, Temporal aspects, Collaboration, Complexity, Safety criticality, Nature of system content
• Contexts: Physical, Social, Organizational
• Technologies that could support users in the domain

Note that, since we may be in an early stage in our projects, this may very well change over time. This is perfectly normal, but at some point we will need to consider PACT aspects anyway. Let's start now!

We want the framework to be able to craft HTML calendars both for the website and for the email. It is important that it functions for both options as it must appear similar in design.

• Collect all content in a document for the other group.
• Write descriptions for all content (2-3 pages total)
• Include background information and problem formulation
• Send the document to the other group
• Perhaps we should create a schedule for the remainder of the project period?
• Create PP presentation about all content

• Prepare an agenda for the meeting
• Write a list of things we will want them to know about our project and how our collaboration is going to work
• Determine what questions we need answered
• Prepare questions in a structured manner
• Prepare all we need to be able to start the system definition, class activity, structure activity, and behavioral activity, which will begin immediately after the first meeting
• Make a note to schedule a new meeting with Kompas at the end of the first meeting

We must receive all the information we need to begin the first phases of the problem domain analysis process.
In addition to these tasks, include any task that comes up, or that I may have forgotten.

Consider the following:

• Who are the users?
• What are the tasks they do?
• Formulate tasks to solve during a usability test
• What are you going to measure? How?
• What data are you going to collect during the evaluation? And how?
• Who will take on what role(s) during the test?

The Handbook of Usability Testing contains a chapter on how this plan is formulated. There are also templates for test plans if those are relevant for our test. These are linked in the book.

Explain why we are no longer focusing on scraping, why we will use a test class to generate realistic prices, and the reason why not to scrape without permission (robots.txt)

This issue must be solved after #13 has been completed.

Create an email-sending method that is able to process an HTML calendar, much like the one shown in the dashboard (so that the user is familiar with the layout).

Consent form

Make a pilot test of your setup to make sure this works as intended.

During the pilot test you should take note of this:

• Do the tasks make sense for an "outsider", i.e. a person not involved in phrasing these?
• How long time do the tasks take to complete?
• Can they be completed within a time frame of 45 min. per participant?
• Does the introduction script make sense for outsiders?
• Are you sure you have all necessary questions for the debriefing and demographics?
• Other matters?

Transcribe the following interviews:

• Interview 1 (initial)
• Interview 2 (clarification)

The process in which we created our event table in relation to the classes.

• Identify all functions.
• Specify only complex functions.
• Check consistency with use cases and the model.