Can I have help with this question, which options are correct: Your company is developing a ticketing website, which allows users to book tickets for ballet shows in London. Your task is to develop a set of test cases for the main booking function. This takes a date, time, and a list of seat numbers, and returns a confirmation code if the booking was successful or an error code if not. Below are some suggestions your colleagues have offered for how you could go about selecting good test cases. Tick all that you agree with. Select one or more: a. All your tests should use the same sequence of seat numbers. This way, it’s much easier to read any error outputs. b. You do not need to test situations where the list of seat numbers is empty. c. You need to have at least one test case for each month in the year. This is called partition testing, and the different months are equality classes for your test. d. You should have tests that try to book the same seats on the same date multiple times. e. You need to have at least one test case where seats are still available on the given date and time and one where there are no more seats on that date and time. We expect the algorithm to behave differently in those cases, so these are test cases in different equality classes.

When doing user research, there is no reason not to divide the overall design into a range of different user views; in fact, there is no reason not to do so.

As part of the usefulness and user experience testing, they looked at how the goals for the test were set.

Scenario: The Best Events Company organizes events, and business is booming, so much so that they need your help to manage their service. They want you to create a software system to manage their employees, clients, suppliers, and events. A part of their software requirement is given below. You are required to do a self-study on how event-organizing companies work and create a design for managing the company's functions. In addition to the requirements below, you are encouraged to add more attributes and functionalities to the system. ​ The company has different types of employees, such as, Sales Managers, Salespersons, Marketing Managers, Marketers, Accountants, Designers and Handymen. Some details required for employees include name, employee ID, department, job title, basic salary, age, date of birth, and passport details are also stored in the system. The table below provides a glimpse of how employees are managed. It is clear from the table that Susan Meyers manages both Shyam…

If you're performing user research, it's a good idea to break down the overall design into many different user views.

I need to create a menu for the information that is given in this series of questions.  Not sure to how to start with a hierarchical drawing: This is the problem which is a continuence of the previous questions on this feed. After your presentation last week, the manager thinks an in-house solution is the way to go. Although our programmers have much experience with system integration and development, they have little experience with user design. You'll have to lay out all the pages of the system. For now, just create a hierarchical drawing of all the pages needed for this system. Think of the menu on the top of the screen and what you'd click on to move to the next screen. Once you finish the hierarchy, I'll need you to draw out examples of a few of the screens. For example, show a screen with a menu, another which requests user input, one that has methods to contact us, and the last one as an informational page. The menu screen can be an opening page or even a page to decide on types…