-
Notifications
You must be signed in to change notification settings - Fork 10
Writing a module
Bob Thomas edited this page May 4, 2017
·
17 revisions
W.I.P - results of management meeting at 2017-05-02
To start writing your module we have a set of questions to answer first. These questions will give you insight in what the module should consist of.
- Is my module self contained (is it dependent on a specific module)?
- Is my module atomic (not further devisable)?
- Does my module process logic?
- Does my module provide added value to the company and customers?
- Can my module be sold individually?
- Are the functionalities of my module clear and identifiable?
- Are the input and outputs of the system defined?
- Are the restrictions and usability of my module easy to read and is its purpose clear?
- Can my module be implemented into multiple projects?
- Are any necessary materials clearly described? Can they be ordered immediately?
- Is it clear how the module is invoked or how this module can be communicated with?
Add a markdown template for a refined module
# *Module title*
---
## Description
-
## Requirements
- list with requirements
## Functionalities
### Exposed functionalities
- list of functionalities visible to the user or module interfacing with this module
### Internal functionalities
- list of internal functionalities (implementation choices)
## Required hardware
## Backlog-items
- link backlog item cards here
The following steps need to be taken to ensure a complete and correct module.
- Create a card in the list "To be refined".
- Write a module card according to the template.
- Once you're done, place the card in the list "modules". Here it is ready for other people to review.
- Once feedback, questions or suggestions are given on the card using a comment, the one who gave the comment will place your card back to "To be refined".
- Reply to the comment and improve your if necessary the module.
- Move the card back to "Modules" where it can receive feedback again.
Information
- Main page
- Project Workflow
- Development Workflow (getting started)
- Git Workflow
- Definition of Ready
- Definition of Done
- Code Guidelines
- Scrum Guidelines
- Writing a module
- Writing a backlog item
- Scrum Teams
- GIT Statistics
- Wiki Statistics
Modules
- Autonomous Drone Ship
- [GAS] Gas Safety System
- [CARRIER] Indoor Driving Platform
- [OBJTRAPRE]Object trajectory prediction
- [FINGSCAN] Identification with a fingerprint scanner
- [NAVSYS] Navigation system
- [RFID] RFID validating system
- [ROBOARM] Robot arm
Hardware
- Arduino ADC
- MQ-4 gas sensor
- MQ-5 gas sensor
- MQ-7 gas sensor
- NEMA17 stepper motor and DRV8825
- Playing audio files (os based systems only)
- Raspberry Pi camera
- ET-SGM51-B Motor
- MDD10A motor driver
- Swivel wheel 135kg
- Arduino Due
- 28015 PING Ultrasonic Sensor
- HC SR04 Ultrasonic Sensor
- MFRC522 RFID Sensor
- Raspberry Pi
- KY-003 Hall Sensor
- 44E402 Hall Sensor
- KY-024 Hall Sensor
- Carrier Platform
- Qik 2s12v10 motor controller
- Hoverboard Motor
- Raspberry pi 7" touch screen
- Raspberry Pi Zero W
- ESP8266 Wifi Module
- M-LSP-12 speaker
- Parallax 4x4 Matrix Membrane Keypad
- MCP23017 I/O Extender
- SD card reader
- Max7219 LED matrix
Software