1. UNIVERSITATEA “POLITEHNICA” DIN TIMISOARA
FACULTATEA DE AUTOMATICA SI CALCULATOARE
Wireless diagnosis and monitoring of the autovehicle
Software verification phase of one iteration of the
V cycle
Stefan Georgiu , An 1 AES
TIMIŞOARA 2014

2. Project overview
Start Date : 14.01.2014
End Date : 27.03.2014
2

3. Software verification phases
1. Test cases creation and requirements review
• Starts as soon as the start of preparation meeting is
completed;
2. Test cases review
• Is included at the end of the preparation phase
• The start of each module depends if the module was
completed in test cases preparation phase
3. Software verification phase
• When the test cases are finished and the software is released
to the verification team, the practical software verification can
start.
4. Meetings
3

4. Test cases creation
Start date, end date, resources and predecesors of each module
4

5. Test cases review
Start date, end date, resources and predecesors of each module
5

6. Software verification phase
Start date, end date, resources and predecesors of each module
6

7. Human resources
Because it is just a verification phase, it only uses Software verification
engineers and the software verification team leader.
7

8. Resources usage and module alocation
8

9. GANTT
Predecesors and dependencies can be easily seen.
9

10. Advantages of having a project plan
• Avoid Completion Confusion;
• Keep Everyone on the Same Page (tracking);
• Understand Task Relationships;
• Effectively Allocate Resources;
• Get a Handle on the Future.
10

11. Thank you for your attention!