Evaluating software development

Evaluating software development

• 1.
  Evaluating Software DevelopmentTopic 11 - 11.1 © NCC Education LimitedV1.0 Evaluation of Software Development • Evaluation is required to check for: – Functionality – Efficiency – Reliability – Usability • It helps to ensure that the software is developed to the highest standards. • It can also help to improve productivity and enhance profitability.
• 2.
  Evaluating Software DevelopmentTopic 11 - 11.2 © NCC Education LimitedV1.0 Types of Evaluation Techniques • Software can be evaluated using a number of types of techniques, such as: – questionnaires – observations – Interviews • Whatever method is used, if it is performed by end users, it can provide clear statements of any problems.
• 3.
  Evaluating Software DevelopmentTopic 11 - 11.3 © NCC Education LimitedV1.0 Evaluation Criteria • The functionality, efficiency, reliability and usability of the software needs to be evaluated. • There are three main criteria that need to be included when evaluating the above. • What information is provided by the software – is it reliable and user friendly? • How effective is interaction with the software – how efficient and usable is it? • Are the technical aspects of the software appropriate – is it fully functional and reliable?
• 4.
  Evaluating Software DevelopmentTopic 11 - 11.4 © NCC Education LimitedV1.0 Evaluating Functionality • The main purpose of evaluating functionality is to ensure that the software performs the necessary commands as instructed. • Functionality should have been tested thoroughly and should be free of errors before an end user evaluates it. • An end user may, however, suggest enhancements even if the software is fully functional.
• 5.
  Evaluating Software DevelopmentTopic 11 - 11.5 © NCC Education LimitedV1.0 Evaluating Efficiency • The main purpose of evaluating efficiency is to check whether the software performs all functions consistently. • Are routine tasks automated? • Does it allow commands to be undertaken quickly, with the minimum of actions/keystrokes? • Are instructions to the user provided clearly? • Does it operate quickly? • Does it have the potential to help increase productivity?
• 6.
  Evaluating Software DevelopmentTopic 11 - 11.6 © NCC Education LimitedV1.0 Evaluating Reliability - 1 • The main purpose of evaluating reliability is to check that the software does what it is meant to do and does not perform any unexpected action. • Do all the links work? • Does it help the user recognise, diagnose and recover from an error?
• 7.
  Evaluating Software DevelopmentTopic 11 - 11.7 © NCC Education LimitedV1.0 Evaluating Reliability - 2 • Does it inform the user about the problem and suggest a solution in clear and unambiguous language? • It can also evaluate how secure the software is.
• 8.
  Evaluating Software DevelopmentTopic 11 - 11.8 © NCC Education LimitedV1.0 Evaluating Usability - 1 • The main purpose of evaluating the usability of the software is to check that it can be interacted with easily. – Is the language clear and understandable? – Is help available and if so, is it easy to understand? – Is it easy to navigate the software? – Are directions easy to understand? – Is information is accurate and up-to-date?
• 9.
  Evaluating Software DevelopmentTopic 11 - 11.9 © NCC Education LimitedV1.0 Evaluating Usability - 2 – Is the text is easy to read? – Are the graphics relevant? – Is the layout consistent? – Is feedback, such as an error message, clearly presented? – Is it easy to learn?
• 10.
  Evaluating Software DevelopmentTopic 11 - 11.10 © NCC Education LimitedV1.0 Identifying Successful User Interaction • Successful user interaction is achieved when after evaluation: – no weaknesses are identified. – the results of whatever evaluation technique has been used are positive. – there are no recommendations for improvements.
• 11.
  Evaluating Software DevelopmentTopic 11 - 11.11 © NCC Education LimitedV1.0 Identifying Software Enhancements and Improvements • When user interaction has been evaluated as successful overall, it may be that the testing technique has returned comments that recommend how the software could be enhanced, e.g. a user may suggest a colour or font style change, which does not affect the functionality of the software feature or function. • When improvements are suggested, this can mean that the software may not be not functioning as efficiently or reliably as it could.
• 12.
  Evaluating Software DevelopmentTopic 11 - 11.12 © NCC Education LimitedV1.0 Evaluation of Application Software – Some General Questions • Does it perform all of the required functions? • Can it be updated easily to accommodate changing user or business requirements? • Does it have links to other software, e.g. accounting software linked to logistics and payroll software?
• 13.
  Evaluating Software DevelopmentTopic 11 - 11.13 © NCC Education LimitedV1.0 An Evaluation Checklist • This should include questions on: – information provided by the program – user interaction with the software – technical aspects of the software – software strengths – software weaknesses
• 14.
  Evaluating Software DevelopmentTopic 11 - 11.14 © NCC Education LimitedV1.0 References • GNOME: Interface Guidelines. (2011). [Available Online] http://developer.gnome.org/hig-book/stable/ • Microsoft: Usability in Software Design. (2000). [Available Online] http://msdn.microsoft.com/en- us/library/ms997577.aspx • Usability First. (2011). [Available Online] http://www.usabilityfirst.com/ • Usability Net. (2011). [Available Online] http://www.usabilitynet.org/home.htm
• 15.
  Evaluating Software DevelopmentTopic 11 - 11.15 © NCC Education LimitedV1.0 Topic 11 – Evaluating Software Development Any Questions?