Human factors has provided many applicable theories and techniques to analyze user requirements, design user interfaces, and conduct evaluation of usability in software development. However, it is common that contributions made by human factors practitioners are not incorporated in this development process, which impairs the ability of human factors practitioners to have significant impact in cross-functional teams.
This paper reviews the possible reasons that human factors efforts are frequently ignored in software design and development and proposes a conceptual framework for the integration of the methods and tools from both the user-centered design approach and the use case driven process to take advantages of the merit and recent progress in both human factors and object-oriented technology.
JacobsonI.BoochG.RumbaughJ. (1998). The Unified Software Development Process. Addison-Wesley, Massachusetts, pp. 112, 116, 140–142, 160–161, 366, 387.
6.
KaratC. (1994). A business case approach to usability cost justification. In BiasR. G.MayhewD. J., Cost-Justifying Usability. Academic Press, New York. pp. 45–70.
7.
KaratJ. (1997). User-centered software evaluation methodologies. In HelanderM.LandauerT. K.PrabhuP., Handbook of Human-Computer Interaction, Elsevier Science B.V, New York, pp. 689–704.
8.
LandauerT. K. (1995). The Trouble with Computers: Usefulness, Usability, and Productivity. A Bradford Book, The MIT Press, Cambridge, MA.
9.
MayhewD. J.ManteiM. (1994). A basic framework for cost-justifying usability engineering. In BiasR. G.MayhewD. J., Cost-Justifying Usability. Academic Press, New York. pp. 9–43.
10.
McDanielS.OlsonG. M.OlsonJ. S. (1994). Methods in search of methodology – combining HCI and object orientation. In proceedings of ACM CHI'94 Conference on Human Factors in Computing Systems. 1994 v.1 pp. 145–151.
11.
MeyerB. (1997). Object-Oriented Software Construction. 2nd Edition. Prentice Hall PTR, New Jersey, pp. 12, 1063.
12.
NeilsenJ. (1994). Guerrilla HCI: using discount usability engineering to penetrate intimidation barrier. In BiasR. G.MayhewD. J., Cost-Justifying Usability. Academic Press, New York. pp. 245–272.
13.
NeilsenJ. (1997). Usability testing. In SalvendyG., Handbook of Human Factors and Ergonomics. John Wiley & Sons, Inc.New York.
14.
NormanD. A.DraperS. W. (1986). User Centered System Design: New Perspectives on Human-Computer Interaction. Lawrence Erlbaum Associates, New Jersey.
15.
RasmussenJ. (1985). The role of hierarchical knowledge representation in decision making and system management. IEEE Transactions on Systems, Man, and Cybenetics. SMC 15, pp. 234–243.
16.
SchacS. R. (1999). Classical and Object-Oriented Software Engineering with UML and C++. WCB McGraw-Hill, New York. pp. 308–309.
17.
SheridanT. B. (1997). Task analysis, task allocation and supervisory control. In HelanderM.LandauerT. K.PrabhuP., Handbook of Human-Computer Interaction. Elsevier Science B.V, New York, pp. 87–105.
18.
SmithT. J.SmithK. U. (1988). The social cybernetics of human interaction with automated systems. In KarwowskiW.ParsaeiH. R.WilhelmM. R., Ergonomics of Hybrid Automated Systems I. Elsevier, Amsterdam, pp. 691–711.
19.
StevensP.PooleyR. (2000). Using UML.Updated edition. Addison-Wesley, Massachusetts, pp. 102.
20.
TowellD. (1999). Display Maintenance: a pattern language. In HarrisonN.FooteB.RohnertH., Pattern Language of Program Design 4. Addison-Wesley, Massachusetts, pp. 489–502.
21.
VicenteK. J.RasmussenJ. (1990). The ecology of human-machine system II: mediating “direct perception” in complex work domains. Ecological Psychology, 2(3), pp. 207–249.
22.
VlissidesJ. (1998). The software patterns series. In MartinR.RiehleD.BuschmannF., Pattern Language of Program Design 3. Addison-Wesley, Massachusetts.
