- •Give the definition of interaction and interface.
- •Explain the fact that there are several kinds of styles of private interfaces.
- •What is a system?
- •What properties must the object have to be called a system?
- •Give an example of the object that can be called a system.
- •What is a model?
- •What models are used in the process of creating software?
- •Verification phases:
- •Validation phases:
- •How is the model of software user created?
- •Why do users create a conceptual model of interaction with something new, for example - with a new computer game?
- •Give examples of the use of analogies from the external world that were used for development of software products known to you.
- •What is the difference between a designer model and a programmer model?
- •Is the user model more important than the designer or programmer model? Explain it.
- •Describe different kinds of system models.
- •What does standard formalism mean?
- •What are model-based methods?
- •Describe main interface issues.
- •Describe main interaction models.
- •What kinds of interface testing do you know?
- •Describe the list of mandatory issues for Through Cognitive analysis.
- •What is groupware?
- •What types of groupware? Give example.
- •What would be an appropriate prototyping approach to enable you to test the design using the usability metrics specified, and why?
- •Explain iso standards that relate to usability.
Give an example of the object that can be called a system.
What is a model?
Model is the real, symbolic or imaginary system, which imitates, reproduces, displays the principles of inner organization or functioning, features, attributes or characteristics of investigated object.
Model also can be referred to as the some material or imagined object or the phenomena, which is the simplified version of the modeled object or prototype, which represents the features of it, which are enough for the means of concrete modeling. (some insignificant features are missed).
What models are used in the process of creating software?
The waterfall model defines a sequential development process
The first description of the waterfall model was given in 1970 by Winston W. Royce.
To follow the waterfall model, one proceeds from one phase to the next in a purely sequential manner.
Classic waterfall model: Requirements, Design, Implementation, Verification, Maintenance.
Spiral Model of development combines the features of the prototyping model and the waterfall model.
The spiral model is intended for large, expensive and complicated projects.
The spiral model was defined by Barry Boehm in his 1988.
The spiral model promotes quality assurance through prototyping at each stage in systems development.
The prototyping model: Обеспечивает создание ПО в двух экземплярах. Первый экземпляр называется прототипом и используется для уточнения требований. После того как требования согласованы прототип выбрасывается и ПО создается заново. Лозунг модели “давайте строить дважды”.
The V-model represents a software development process (also applicable to hardware development) which may be considered an extension of the waterfall model. Instead of moving down in a linear way, the process steps are bent upwards after the coding phase, to form the typical V shape. The V-Model demonstrates the relationships between each phase of the development life cycle and its associated phase of testing. The horizontal and vertical axes represents time or project completeness (left-to-right) and level of abstraction (coarsest-grain abstraction uppermost), respectively.
Verification phases:
Requirement Analysis
System design
Architecture Design
Module Design
Validation phases:
Unit testing
Integration testing
System testing
User Acceptance testing
Release testing
How is the model of software user created?
У процесі створення та машинної реалізації моделей користувача здійснюють такі етапи:
• побудова концептуальної моделі;
• побудова алгоритму згідно з концептуальною моделлю системи;
• створення комп’ютерної програми;
• машинні експерименти з моделлю системи.
Побудова концептуальної моделі складається з таких кроків:
• постановка задачі моделювання;
• визначення вимог щодо первісної інформації та способів її отримання;
• формування гіпотез і припущень;
• визначення параметрів та змінних моделі;
• обґрунтування вибору показників і критеріїв ефективності системи;
• складання змістовного опису моделі.
Розроблення програми для ПК включає такі кроки:
• вибір обчислювальних засобів;
• програмування (чи налаштування відповідних параметрів існуючих програмно-методичних комплексів);
• тестування програмних засобів.
