|1.0||Feb. 11, 2013||GU Minyi, FENG Xu, GUO Tianming||SRS of the project||-||-|
The purpose of this document is to present a detailed description of Arduino STM32 Discovery. It will explain the purpose and features of the system Arduino, what the system will do,how we use the carte STM32 in the environment Arduino, the constraints under which it must operate ,how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system.
1.2 Scope of the project
Our objective is to use the STM32 Discovery cards, especially F3 and F0, with the same simplicity and an environment comparable to Arduino. So our system is based on Arduino, we added the library of STM32 and the Board of STM32 into it . We use this system to put some programmes into the cards of the arms, in order to realize some functions.
We hope that these cards can be used for TPs and project initiation technology embedded.
1.3 Definitions, acronyms and abbreviations
|Arduino||This is an open-source electronics prototyping platform based on flexible, easy-to-use hardware and software. It's intended for artists, designers, hobbyists, and anyone interested in creating interactive objects or environments.|
|STM32 Discovery||It is an ultra-low-cost and convenient starter platform, the STM32 Discovery Kit is particularly suited to the STM32 Value Line microcontrollers.|
|F0, F3||They are the different types of STM32.|
|TP||It’s ‘Des Traveaux Pratiques’ in French. They are prepared for students to practice.|
|Stakeholder||Any person with an interest in the project who is not a developer.|
|Software Requirements Specification||A document that completely describes all of the functions of a proposed system and the constraints under which it must operate. For example, this document.|
- IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998
1.5 Overview of the document
The next chapter, the General Description section, of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product.
Both sections of the document describe the same software product in its entirety, but are intended for different audiences and thus use different language.