Conferences for professionals in the information technology industry

Куприянов Юрий



Requirements analysis from UX point of view


When the analyst collects and analyzes the requirements, the last thing that she cares about - an analysis of requirements in terms of user interface design and information structure. Indeed, this is interface designers job, right? So, often the analyst does not know - what is important for the design of interfaces and interaction, and moreover - what kind of information she needs to provide the designer to work with. Because of this, analysts and designers are beginning to "hog the blanket" - UX designer begins to independently collect the necessary requirements, and the analyst begins to issue the interface solutions instead of the requirements. In this talk, I will tell - what's really important for designing UX, and what the analyst must give the UX-designer for his work.

Audience level
Regular Talk (40 min)

Using storytelling and projective tests for requirements elicitation and validation

Requirements identification is always a challenge for business- or systems-analyst . Especially when processes are not precisely defined or stakeholders do not have a clear understanding of user interaction in the system. The analyst must capture all the ideas and assumptions of each stakeholder , and only in order to discover their incompleteness and inconsistency. Also, you should always remember that customers usually do not say what they want , and certainly not what they actually need. And here we can use psychodiagnostic methods , such as storytelling and projective tests . Ask Stakeholder tell the story which included your system . Ask them to play user interaction on the dolls. Ask them to draw abstract vision of system or construct it from Lego blocks . Remove verbal communication channel - and all the distortions associated with it . And the clients can clearly demonstrate you their needs and concerns.
Audience level
Regular Talk (40 min)

Lightweight quality assurance framework based on the SEMAT Essence

The SEMAT initiative (Software Engineering Method And Theory) in 2011 introduced the draft standard "Essence: Kernel and Language for Software Engineering Methods", containing a description of the framework for monitoring progress and health of the software development endaevor. A simple and lightweight model allows to check the current status of the project, identify areas of potential risk and impact. The model tolerant to the software development methodology (from the classic waterfall to agile), and allow any team to assess the quality assurance and detect weaknesses long before the moment when they begin to bear real harm. In the workshop this model will be presented and demonstrated simple games with the Essence Deck.
Audience level
Regular Talk (40 min)
Code copied to clipboard