The university of warwick
Systems Engineering Principles – Resit Assignment for Practical Test. To be completed in own time, does not need to be sat as a test.
Learning Outcomes
• Write requirements which cover functional and non-functional uses and behaviours including failure mode avoidance
• Describe the difference between verification and validation and specify suitable verification and validation criteria
• Write and critique a test report for acceptance of design
Feedback from original test
Students scoring a high first (above 80) showed that they had demonstrated comprehensive knowledge and accuracy incorporating multiple aspects of the module and using some kind of novel or additional implementation. Even without novel or additional requirements students scored a first by demonstrating understanding and knowledge of all aspects required. A 2.i was given to students showing good knowledge where everything was done well but not excellently, a simple but working extension of the lab model to include doors which were tested but not exhaustively for example would score a 2.i. A 2.ii was awarded for competent work where most aspects were performed and knowledge demonstrated in most areas but there might have been issues with one part (e.g. incorrect requirements or testing). The threshold of a pass was given when students had clearly demonstrated some knowledge, often this was a set of good requirements and an attempt at implementing but students had faced issues, perhaps due to lack of practice. A score of 32 is significantly below the expected standard but shows some evidence of study whereas a 25 is poor quality with no evidence of study. Anything below is probably because the workshops were attended but nothing else.
Remember: your functional requirements should describe the active/dynamic behaviour of the system whereas your non-functional requirements should describe how the system should be.
• Consider a system which controls the power window in a vehicle and is open and closed by a rocker switch which can be used to select ‘up’ and ‘down’. By holding the switch down, the user can also request that the window fully opens or fully closes.
• Re-write the following requirements in the correct sentence structure and indicate if they are functional or non-functional giving a reason why.
• The window needs to open or close in 3.5-4.5 seconds regardless of conditions or age
• If the user presses up or down for longer than 0.5 seconds the window should go up or down completely
• The window should include a feature which prevents objects becoming trapped by detecting force above a threshold and fully opening.
• The window glass should stop moving at the top and bottom of the window
• Create a state-flow implementation of a power window which fulfils the requirements from part a). You should link the state-flow transitions to requirements.
• Describe the model behaviour and explain how it implements the requirements (include screenshots here), an activity diagram will help you describe the model.
• Design and perform a full-factorial test of the window system. Write a clear report of your method and findings. For each requirement you should explain how you have verified that the requirement has been met by the model.
• Write a system test plan for testing the control on a real automotive electronic control unit. Consider different types of test that you might perform.
END