G6046 Software Engineering
Seminar session: Understanding requirements
Possible solution
There are many possible options. These are just some of them organised into a more useful set of requirements. Remember that good requirements are SMART (Specific, Measurable, Achievable, Realistic and Timely). Remember that your requirements are for the remote software system.
Copyright By PowCoder代写 加微信 powcoder
Functional requirements
Reference Description Mandatory/Desirable
The software shall communicate with the robot using a Bluetooth wireless link at a range of no less than 5m.
The software shall function over a paired Bluetooth link to ensure security and integrity of the link.
The gripper needs to be able to lift weights of no more than 50g when operated at the full lateral extent of the gripper arm. A full arm is 20cm long giving a total torque F*d =m*g*d = 0.05 * 10 * 0.2 = 0.1Nm. (g is the acceleration due to gravity).
The software shall detect when the joint is subject to a torque greater than this value (Remember the spec is for the software, not the robot hardware) and instruct the robot to stop if the load is too great.
Software commands shall include as a minimum ¡°walk¡± and ¡°stand up¡±. The speed and reliability of such operations needs to be discussed with the client (see non-functional requirements)
The software shall be able to issue commands to make the robot speak. Such commands shall be issued by typing the words to be spoken in plain English text on the host computer.
The range of words should not be limited to a single dictionary. The software should aim to pronounce any words using simple rules of English pronunciation.
The software should not permit the robot to speak profanities (to be discussed further with the customer).
Non-Functional requirements
Reference Description Mandatory/Desirable
Note: ¡°The robot shall cease motion if the wireless link is lost for more than 2 seconds. The robot shall not move until the wireless connection has been re-established¡± might seem obvious but it¡¯s a function of the robot, not the software.
Domain requirements
Reference Description Action needed
The software shall be written in Java to ensure maximum portability across platforms. The development shall use Java version 7.
The software should have a mean time between faults of no less than 3 continuous days of operation.
The robot needs to be aesthetically pleasing and not obviously offensive to any cultural group.
The appearance of the robot is not a software issue, but the actions the software can make it do are.
The software must be simple enough for a 10- year-old child to use and the interface needs to be simple and intuitive,
We need to talk to UI and educational specialists
Understanding the domain requirements will generate new functional and non-functional requirements.
If you understand this exercise, it¡¯s time to get moving on producing a first cut of your system requirements document for your group coursework. Good luck.
Dr Kingsley Sage Dr
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com