User talk:Emddom
ELIKO PROJECT 1.1 ROADMAP (VERSION 1.3)
Definition of the design domain
[edit]Overview
[edit]Domain of embedded systems
[edit]Common characteristics of our design domain
[edit]- HRT: Hard Real-Time
- Embedded systems
- Distributed systems
Our choice
[edit]Motivation (criteria, decision table, SWOT?)
[edit]Description
[edit]Our domain encompasses the following subdomains
[edit]- Telecomm/Wireless
- Embedded Medical devices
Implementation/ adaption plan (action plan)
[edit]- Eliko 2.4. project
- RFID project
Design process model and methodology
[edit]Overview
[edit]Design Process
[edit]Lifecycle models, e.g. T-lifecycle, 3V
Development and Testing should be integrated, e.g.
- Analysis - Test objectives
- Design - Test design
- Implementation - Unit/Module tests
- Integration - Integration/System tests
- Operation/Maintenance - Online tests
Methodology/approach
[edit]- Action-oriented
- Aspect-oriented (?)
- HW-SW co-design
Our choice
[edit]Motivation (criteria, decision table, SWOT?, constraints)
[edit]Description
[edit]MOBIES T-lifecycle model
Alternatives (overview possibly in Appendix)
[edit]Implementation/adaption plan (action plan)
[edit]Selection of tools supporting that methodology
[edit]Overview
[edit]What’s missing from the toolchain, e.g. 3V model’s missing links
Our choices
[edit]Motivation (criteria, decision table, SWOT?, constraints)
[edit]Our constraints: lack of human resources => use ready components that can be easily modified, e.g. open source Tool also for modeling the process
Description
[edit]A variety of tools to be chosen
Testing tools used for Communication software:
- Telelogic TAU, Solinet SAFIRE, DANET, DaVinci, TestingTech
Implementation/adaption plan
[edit]Other alternatives (Overview)
[edit]Integration principles of tools
[edit]Research challenges: Developing an approach that will upgrade existing tools with semantic adaptors towards tools supported by other paradigms.
[edit]Integration platform (Eclipse) and plug-in technology
[edit]Standards used: XMI, XML, ADML, TTCN-3, ASN.1
[edit]UML profile for testing
[edit]| Architecture concepts | Behavior concepts | Data concepts | Time concepts |
| SUT | Test objective | Wildcards | Timer |
| Test components | Test case | Data pools | Timer zone |
| Test suite | Defaults | Data partitions | |
| Test configuration | Verdicts | Data selectors | |
| Test control | Coding rules | ||
| Arbiter | |||
| Scheduler | |||
| Utility part |
- Links
- The UML 2.0 Testing Profile and its Relation to TTCN-3
- Integrated Application of TTCN by Dieter Hogrefe
- UML Testing Profile Tutorial at ECOOP 2004 by Schieferdecker,Haugen
- The UML 2.0 Testing Profile presentation by Schieferdecker, Grabowski
References and links
[edit]Appendices
[edit]Kampo.jpg listed for deletion
[edit]An image or media file that you uploaded or altered, Kampo.jpg, has been listed at Wikipedia:Images and media for deletion. Please look there to see why this is (you may have to search for the title of the image to find its entry), if you are interested in its not being deleted. Thank you. —MetsBot 18:57, 9 December 2006 (UTC)
