Designing interactive software is complex, requiring an understanding of human beings, software systems and the interaction between the two. Understanding people involves input from at least three social sciences. Psychology explores how the human sensory motor, perceptual and memory systems work, Sociology explores how people interact with each other, and Anthropology explores how people operate in the context of their daily activities. Developing interactive software also requires input from software engineering, including system architecture, programming languages, interaction techniques, as well as distributed computing and the use of a wide variety of hardware input and output devices. Creating innovative and aesthetically-pleasing designs requires input from trained designers, including graphic or interaction design and increasingly architecture and industrial design. Interaction design not only involves the “static” interface, but also involves the “dynamic” interactive change, which is in response to user activity of dynamic behaviour. Moreover, interaction design model needs to consider two aspects: users who use the software and developers who develop the software. Given this sense of complexity, the research focuses on how a recording and tracking system in interactive design development would help improve the decision space in development. Recording and tracking design decision systems are in existence for architects and system designers who need to know their design model well. It helps them to keep track of decision, and also the transformation of customer requirements over time, which demands changes to be made in design decision making accordingly. The recording and tracking design systems also function as an efficient documentation element in those cases where a project staff member might have to leave and newer project members have to immediately enter the design space. In addition, it is often required that requirements analysts model a design solution already in the analysis phase. Such hasty design decisions may cause solution-speciﬁc restrictions which are not appropriate. Stakeholders not involved in the design decisions, such as that of customers, project managers and developers would have a hard time to understand the signiﬁcance of realization relationships between customer requirements and services. This often leads to misinterpretations among them. There could be also Ad-hoc changes to design that might end up being unmindful of the existing dependencies to other design aspects. The use of a Recording and tracking design decisions model will reduce the distance between the users and developers and will increase the space and innovation attributes in design.