Modelación lógica

Requirements can be divided into the categories of functional and non-functional (Sqa.org.uk, 2007). Functional requirements are those that deal with specifics of what a system should do. For example, a functional requirement would be that the system must encrypt user passwords. A non-functional requirement is can be a constraint or criteria. For example, the user interface should be designed with an appealing color scheme. Non-functional requirements are usually put at a lower priority than the functional requirements.

3.8 FICS Analysis

The FICS analysis is used to visualize a usage scenario from the side of a system instead of a user like in the iPACT analysis (Larburu et al., 2013). The abbreviation FICs stands for Functions and events, Interaction and usability, Content and structure, and Style and aesthetics. Functions and events are what the system does and how it reacts to events, Interaction and usability, shows how the user is supported in carrying out an activity. Content and structure relates to how the system stores data and

3.9 System Architecture

System architecture is a model of the system that gives an overview of its various components and how these components are linked together. The iPACT and FICS analyses help model the requirements for the system from which the functionality can be determined. The system architecture can have multiple levels, where a deeper level would go into the workings of an individual component of the system. Flow charts and diagrams are used to model system architecture. The levels of the architecture are as follows: the first level is inputs and outputs of the system, the next level shows the various functionalities of the system represented by connected blocks and finally the third level will show the inner-workings of each of the blocks in the previous level. The arrows connecting the blocks indicate which components are connected and the order in which they are called upon.

3.10 Cognitive Walkthrough

“A Cognitive Walkthrough is a usability walkthrough technique that focuses primarily on the ease of learning a product.” (Wilson, 2014). The cognitive walkthrough will be used to guide the reader through the data processing in the system to provide them with a better understanding of how the algorithm functions. The walkthrough will use the help of an Activity diagram to help identify the major processes, how they are related and in what order they are performed.

3.11 Activity Diagram

An activity diagram is an overview of a usage scenario where activities are split between user and the system. The diagram shows the connection between activities and the triggers of certain events. A black circle indicates the beginning of a usage scenario, a diamond shape indicates a decision being made either by the user or the system (checking whether a condition has been met), a rectangle indicates an action or process occurring and finally a filled circle within another circle signifies the end of the scenario.

3.12 Evaluation

The program will be evaluated using four methods, a Functional Test, Code Tests, Expert Validations and Program Tests. A Functional evaluation is simply a checklist covering the various requirements specified in the Specification phase and checking to see whether they are accomplished. During Code Tests, components of the program are tested on various possible scenarios to ensure the program can handle

them. This goes hand in hand with the functional evaluation. For example, if a functional requirement is for the code to separate the data by the minute, then the code tests should make sure that the program can identify all the minutes in the code and segment the data by the minute accordingly. An expert validation involves approaching an expert in the field to comment on the project and methodology used. Finally, the program test, pits the program against a real world situation and checks whether it can find scheduled DBMs in a set of recorded data.

User evaluations are performed to validate and check if non-functional requirements have been met, however due to the technical scope of the requirements, this is being conducted using code tests.

4. Ideation

This chapter will answer the research sub-question:

“​What kinds of breathing features would users like to be presented for the purpose of feedback?​” The ideation phase will explore the user requirements and wishes through the use of a Stakeholder Analysis to identify influential and important individuals. An individual brainstorm will then be conducted in order to generate ideas for the experimental protocol, classification and feedback regarding the features presented to users. A group brainstorm will be conducted with a group of potential users to brainstorm ideas for features they would like to receive for feedback on their breathing. Interviews will then be conducted involving a sample of the previously identified

stakeholders. An Expert Review will be conducted based on the ideas generated from the brainstorms and interviews. An iPACT analysis will be performed in order to better understand user requirements from the system. Finally, a list of preliminary requirements will be drafted for the Specification phase. The breathing training wearable device will be referred to as Airleviate from here on. The term “diaphragmatic breathing moment” will be shortened to “DBM” and used as such from here on.

4.1 Stakeholder Analysis

Users

A potential user of the Airleviate service can essentially be anyone wishing to improve their breathing and experience the physiological benefits of diaphragmatic breathing. Young children may use it to ensure a varied breathing routine. Students and adults may use this service to reduce anxiety caused by their studies or work respectively. Athletes can prevent oxidative stress using this service to train diaphragmatic breathing. Physiotherapists and specialists may include it as part of a treatment against dysfunctional breathing, and anxiety, in which case both the patients and then specialists are users; the latter being an indirect user. It can also be used to train diaphragmatic breathing for the purpose of martial arts, yoga or meditation; thus novices in those disciplines are potential users too.