The cognitive activities performed by systems designers during systems development include problem understanding, problem decomposition and solution specification.
Obtaining the solution specification together with the impaired user by using the inclusive technique defined with the therapists.
Those ideas must be elicited from the high-level solution generated in phase 2. Defining strategies with therapists to propose PD practices that allow the impaired user to participate in the solution specification.
Experience has taught us the answer: Specifications and engineering may define the ruggedness of the solution, but design addresses the human need and defines the level of adoption.
Going forward from the EPC solution and specifications as of 3GPP Rel-8, there are obviously several areas that may be exploited and developed in the future.
Phase 3, solution detailed specification with user, aims to detail functionalities for the solution indicated in phase 2. Detailed functionalities for the solution are designed with therapists by means of exploring techniques such as focus group discussions, brainstorming, and prototyping.
In the following phase, solution detailed specification, the process is repeated, as in the solution inception phase, but it is intended now to specify the details of the incepted solution with the child.
A complex traceability system can affect the practical solutions and specification of the information technology systems when implementing traceability.
It is a solution-independent specification, with the aim of making a clear and precise description of domain entities for the purposes of communication, learning and problem-solving.
Our process follows the twin peaks concept (Nuseibeh 2001) which separates problem structure and requirements specification from solution structure and architecture specification, producing progressively more detailed requirements and design specifications.
Exemplified for SDL, a solution for the specification of temporal aspects is shown.
