Анализ требований пользователей John Sabou, MSc Milos Ulman, PhD

Содержание

Слайд 2

Overview

Data Governance Strategy
Enterprise Strategy/Business Model
User Analysis Requirements
Basics of Project Management

Overview Data Governance Strategy Enterprise Strategy/Business Model User Analysis Requirements Basics of Project Management

Слайд 3

Data Gov. Strategy for Business Model

Data Gov. Strategy for Business Model

Слайд 4

Enterprise IS Strategy

Enterprise IS Strategy

Слайд 5

Information Management Lifecycle

Information Management Lifecycle

Слайд 6

The System Development Lifecycle (SDLC)

The System Development Lifecycle (SDLC)

Слайд 7

User Analysis to improve a product

Better software involves three goals:
The right

User Analysis to improve a product Better software involves three goals: The
product
Done right
Managed right

Слайд 8

Use Cases

Use Cases

Слайд 9

Client Interactions

When designing a product, one of the most important

Client Interactions When designing a product, one of the most important things
things to take into consideration is the end-user.
End-users are the people who will use the product. They are among the stakeholders of the project.

Слайд 10

User Considerations

A product should be designed to be something users can navigate

User Considerations A product should be designed to be something users can
and want to use. This is primarily accomplished through good user interface (UI) design.
UI is what is seen when using the product, and it can encompass anything an end-user interacts with—features such as windows, buttons, scrollbars, checkboxes, and text boxes.

Слайд 11

Elicitation

The activity of eliciting requirements is an interactive and investigative process, which

Elicitation The activity of eliciting requirements is an interactive and investigative process,
occurs when meeting with the client and users. E.g. Feasibility studies with focus groups, Observing how end-users use the product.

Слайд 12

Expression

Once client needs have been established by eliciting requirements, the activity of

Expression Once client needs have been established by eliciting requirements, the activity
expressing requirements comes into play. Expressing requirements involves framing the requirements identified through discussion in a way that allows a product to be built.

Слайд 13

Wireframes

One of the most important techniques of product development is the use

Wireframes One of the most important techniques of product development is the
of wireframes. A wireframe, also known as a mock-up, can be thought of as a kind of early blueprint. It is a basic visual representation of the product.

Слайд 14

Prioritization

Once a vision of what needs to be done for the project

Prioritization Once a vision of what needs to be done for the
has been established through both eliciting and expressing requirements, it is important to prioritize client needs.

Слайд 15

Example: Story board

Example: Story board

Слайд 16

Analysis

The process of examining the listed requirements of a project to ensure

Analysis The process of examining the listed requirements of a project to
that they are clear, complete, and consistent is known as analyzing requirements.
Analyzing requirements helps ensure that the product is the best one possible. It is an important process, and a constant one. A project must be continually evaluated and requirements improved as it progresses.

Слайд 17

Storyboarding Cont’d

Storyboarding Cont’d

Слайд 18

Management

The activity of managing requirements is also a continuous process. It involves

Management The activity of managing requirements is also a continuous process. It
the organizing and re-organizing of requirements and possibly reusing subsets of requirements in different stages.
It also involves keeping track of priorities, analyses, and changes in requirements. This is very important because everything is connected in a project.
If something changes in one requirement, it will affect other requirements and the development of the product.

Слайд 19

Types of Requirements

Business requirements
Business rules
User requirements
Functional requirements
Non-functional

Types of Requirements Business requirements Business rules User requirements Functional requirements Non-functional
requirements
External interfaces
Physical product settings
Development constraints

Слайд 20

User Interaction

User Interaction
Имя файла: Анализ-требований-пользователей-John-Sabou,-MSc-Milos-Ulman,-PhD.pptx
Количество просмотров: 39
Количество скачиваний: 0