What are the problems?
End user’s perspective
- Many projects just not get finished
- The system works but it’s dreadful to use
- The system looks pretty but does not do all the work
A client’s perspective
- Many projects (50% approx., Standishgroup, 1994, 2001) exceed the budget
- Many projects are delivered late — may be of no use at the time of completion
- The deployment was a mess, caused some major disaster in operation – the staffs do not trust the system
- Some stakeholders may try to prevent the success of a project for some benefit
- The business, the requirements have changed over the period – a completely new system is required now
A developer’s perspective
- Developers feel they built what was wanted; the clients or the end users still are not happy; the clients/end user’s may have changed their minds in the meantime or they did not understand the developers’ specification; or there were misunderstandings in the beginning about requirements
- Pressure from different sources may limit developers’ ability to produce an excellent system. Pressure: Budget, time limit, see the result
- The developers may be inexperienced with the particular techniques they must use – still they are highly skilled and basically talented
- No documentation, explanation on the existing work. Not well written code – developers may have much difficulty to understand them before able to modify.
- The goals may be impossible to implement. Developers may have warned…but nobody listened..so the project failed.
- Many developers may feel — ‘The system is fine .. the users are the problem’ – without being prepared to examine critically their own preconceptions
Aspects of Poor System Usability
- Poor interface design
- Inappropriate data entry
- Incomprehensible error messages
- Unhelpful help
- Poor response times
- Unreliability in operation
Why things go wrong?
Quality Problems
- The wrong problem is addressed – system conflicts with business strategy
- Wider/Long term/future influences/consequences are ignored
- Incorrect analysis, design, and implementation [method/strategy]
- Project was initiated with wrong reason – going online without analyzing the benefit – just to follow the trend
Productivity Problems
- Users have changed their minds
- External factors like a new legislation have changed the environment
- Implementation infeasible
- Poor project control like having inexperienced project managers
Hidden Costs of Poor Design
- Illogical screen layout: Wasted time, loss of confidence in the system
- Difficult to read screens: increased frustration, increased sickness
- Unhelpful help messages: increased error rate, increased absenteeism, greater staff turnover
- System response is slow:increased operating costs
- Lost data: extra work, reduced income
- Inaccurate outputs: extra work checking outputs, loss of customer confidence, lost sales
Ref: Object oriented Analysis and Design using UML by S. Bennett et. al.
From: http://sitestree.com/?p=4939
Categories:Software Engineering
Tags:
Post Data:2010-10-15 11:01:23
Shop Online: https://www.ShopForSoul.com/
(Big Data, Cloud, Security, Machine Learning): Courses: http://Training.SitesTree.com
In Bengali: http://Bangla.SaLearningSchool.com
http://SitesTree.com
8112223 Canada Inc./JustEtc: http://JustEtc.net (Software/Web/Mobile/Big-Data/Machine Learning)
Shop Online: https://www.ShopForSoul.com/
Medium: https://medium.com/@SayedAhmedCanada
