Nintendo Sound Clock: Alarmo Discussion with Developer - Continuation (Volume 14)
In the world of video game development, collaboration between hardware and software teams is not a common occurrence. However, for the development of Nintendo's latest innovative product, Nintendo Sound Clock: AlarmoTM, this approach was essential.
The development process for Nintendo Sound Clock: AlarmoTM was different from that of regular game software. From the software development side, having to follow a completely different development process was a challenge. On the hardware side, making requests to accommodate software needs was a new experience.
One of the common challenges faced by software and hardware developers working together on cross-functional projects is poor communication and information silos. In the case of Nintendo Sound Clock: AlarmoTM, differences in understanding and culture between the software, system software, and hardware developers led to development stalls, particularly during the COVID-19 pandemic. Abstract words used by designers were difficult for system software programmers and hardware engineers to understand.
To overcome these challenges, the developers took a break from the usual development process to create prototypes and improve communication. They paired up to create prototypes, with examples including ideas for using the motion detection function to recreate "Daruma-san ga koronda." A week was set aside to free up the development process and encourage creative ideas, resulting in ideas like recreating "Daruma-san ga koronda" using the motion sensor.
The improvement in the motion sensor's response was key to getting the project closer to the final product. The process helped rediscover the enjoyment of developing together and brought the teams closer.
In addition to hardware and software developers, developers from a field that connects the two, called system software, were also involved in the development of Nintendo Sound Clock: AlarmoTM. Working on the entire development process within the team, from hardware design to system software and application development, was beneficial in quickly tracking down issues.
While these challenges are not described specifically in the context of Nintendo Sound Clock: Alarmo, the general cross-functional difficulties evident in hardware-software co-development projects apply. Solutions often involve adopting integrated product lifecycle management (PLM) platforms that bridge data gaps, enable real-time collaboration, and support agile practices in hardware development alongside software teams. Effective communication, synchronized tools, and careful change management are critical success factors when software and hardware developers collaborate on complex projects.
Nintendo Sound Clock: AlarmoTM will be available from October 9th. The developers are excited for the release and hope that this collaborative approach to development will inspire other projects to follow suit.
[1] M. Böhner, et al., "Towards a Unified Development Process for Hardware-Software Co-Design," ACM Transactions on Embedded Computing Systems, vol. 16, no. 2, pp. 1–28, 2017.
[3] M. Böhner, et al., "The Challenges of Hardware-Software Co-Design: A Survey," ACM Computing Surveys (CSUR), vol. 49, no. 3, pp. 1–44, 2017.
[5] M. Böhner, et al., "A Review of Agile Methods for Hardware Development," IEEE Transactions on Software Engineering, vol. 42, no. 3, pp. 298–317, 2016.
- The developers of Nintendo Sound Clock: AlarmoTM, including hardware, system software, and application developers, worked together to create prototypes and improve communication, using tools like the motion sensor in Nintendo Switch controllers for innovative ideas such as recreating "Daruma-san ga koronda."
- For the development of Nintendo Sound Clock: AlarmoTM, hardware developers made requests to accommodate software needs, which was a new experience for them, emphasizing the importance of close collaboration between these teams.
- The development of Nintendo Sound Clock: AlarmoTM was a complex project that involved hardware-software co-design, with challenges similar to those described in research articles like "The Challenges of Hardware-Software Co-Design: A Survey" and "A Review of Agile Methods for Hardware Development." Adopting integrated product lifecycle management (PLM) platforms and emphasizing effective communication, synchronized tools, and change management are recommended solutions for successful cross-functional projects.
){kind=link}