Experiences with Software Architecture Analysis of Usability

The present system uses measurement inputs which reveal fission product barrier functional characteristics for emergency event classification in nuclear generating stations. The process determines the functional status of barriers to fission product release under transient or emergency conditions. The first part of the present process specifies which key indicators within a nuclear plant provide data indicative of fission product barrier status, and develops a logic table or diagram relating specific key symptoms to barrier status such that a computer identifies the functional status of each fission product barrier. In the second part of the present process nuclear power plant operators utilize the computer to determine emergency event classification. The computer utilizes the present process, using the installed nuclear generating station instrumentation which indicates flow rates in fluid and air handling systems, pressures in pipes and vessels, temperatures in pipes and vessels, radiation levels and other indications of equipment status to determine whether the fission product barriers are functional at a given point in time according to the criteria established during the first part of the process. The implentation is an orderly process in which nuclear power plant operator uses the process as programmed on the computer to determine and correctly characterize the condition or status of each fission product barrier at any time. The process results in direct indication of the status of fission product barriers and of the categorization of the emergency event according to established classes of emergencies. If the computer is non-functional, the nuclear plant operator uses the process as presented in implementing procedures to determine the status of each fission product barrier and to determine the proper event clasification. The operator relies upon installed plant instrumentation to determine the functional status of the barriers according to the process.

[1]  Ergonomic requirements for office work with visual display terminals ( VDTs ) — Part 11 : Guidance on usability , 1998 .

[2]  Jan Bosch,et al.  A framework for capturing the relationship between usability and software architecture , 2003, Softw. Process. Improv. Pract..

[3]  Leonard J. Bass,et al.  SAAM: a method for analyzing the properties of software architectures , 1994, Proceedings of 16th International Conference on Software Engineering.

[4]  Jan Bosch,et al.  Software Architecture Analysis of Usability , 2004, EHCI/DS-VIS.

[5]  H. Rex Hartson,et al.  Developing user interfaces: ensuring usability through product & process , 1993 .

[6]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[7]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[8]  J. Knottnerus,et al.  Real world research. , 2010, Journal of clinical epidemiology.

[9]  David C. Rine,et al.  Integrated approaches in information technology and web engineering : advancing organizational knowledge sharing / [edited by] Ghazi Alkhatib, David Rine. , 2008 .

[10]  N. H. Beebe.  on Software Tools for Technology Transfer ( STTT ) , 2005 .

[11]  Jakob Nielsen,et al.  Heuristic Evaluation of Prototypes (individual) , 2022 .

[12]  G. G. Stokes.  "J." , 1890, The New Yale Book of Quotations.

[13]  Len Bass,et al.  Achieving usability through software architecture , 2001, ICSE 2001.

[14]  Chauncey E. Wilson,et al.  The Usability Engineering Framework for Product Design and Evaluation , 1997 .

[15]  Graham I. Johnson,et al.  Evaluating usability of human computer interfaces: a practical method (west sussex , 1989 .

[16]  B. J. Ferro Castro,et al.  Pattern-Oriented Software Architecture: A System of Patterns , 2009 .

[17]  Thomas K. Landauer,et al.  Trouble with Computers: Usefulness, Usability, and Productivity , 1996 .

[18]  Richard Rubinstein,et al.  The Human Factor: Designing Computer Systems for People , 1984 .

[19]  Y Yang,et al.  Evaluating usability of human-computer interfaces: a practical method , 1990 .

[20]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[21]  Marisol García-Valls,et al.  Assessment of Timing Properties of Family Products , 1998, ESPRIT ARES Workshop.

[22]  Peter G. Polson,et al.  Theory-Based Design for Easily Learned Interfaces , 1990, Hum. Comput. Interact..

[23]  Robert L. Nord,et al.  Applied Software Architecture , 1999, Addison Wesley object technology series.

[24]  Jan Bosch,et al.  Experiences with ALMA: Architecture-Level Modifiability Analysis , 2002, J. Syst. Softw..

[25]  Janice Redish,et al.  User and task analysis for interface design , 1998 .

[26]  Jan Bosch,et al.  Architecting for usability: a survey , 2004, J. Syst. Softw..

[27]  Larry L. Constantine,et al.  Software for Use - A Practical Guide to the Models and Methods of Usage-Centered Design , 1999 .

[28]  PerOlof Bengtsson,et al.  Architecture-Level Modifiability Analysis , 2002 .

[29]  Colin Potts,et al.  Design of Everyday Things , 1988 .

[30]  Peter Sommerlad,et al.  Pattern-Oriented Software Architecture , 1996 .

[31]  Mary Shaw,et al.  What makes good research in software engineering? , 2002, International Journal on Software Tools for Technology Transfer.

[32]  Alan L. Tharp,et al.  What users say about software usability , 1991, Int. J. Hum. Comput. Interact..

[33]  Fabio Vitali,et al.  Web information systems , 1998, CACM.

[34]  Rick Kazman,et al.  The architecture tradeoff analysis method , 1998, Proceedings. Fourth IEEE International Conference on Engineering of Complex Computer Systems (Cat. No.98EX193).

[35]  Philippe Kruchten,et al.  The 4+1 View Model of Architecture , 1995, IEEE Softw..

[36]  Peter T. Poon,et al.  a Recommended Practice for Architectural Description , 1996 .

[37]  Rick Kazman,et al.  An approach to software architecture analysis for evolution and reusability , 1997, CASCON.

[38]  Donna L. Cuomo,et al.  Understanding Usability Issues Addressed by Three User-System Interface Evaluation Techniques , 1994, Interact. Comput..

[39]  KruchtenPhilippe.  The 4+1 View Model of Architecture , 1995 .

[40]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[41]  Jakob Nielsen,et al.  Usability inspection methods , 1994, CHI 95 Conference Companion.

[42]  Jan Bosch,et al.  Bridging patterns: An approach to bridge gaps between SE and HCI , 2006, Inf. Softw. Technol..

[43]  Mira Mezini,et al.  Pi: a Pattern Language , 2009, OOPSLA.

[44]  Jan Bosch,et al.  Architecture level prediction of software maintenance , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).

[45]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[46]  Søren Lauesen,et al.  Six Styles for Usability Requirements , 1998, REFSQ.

[47]  Jan Bosch,et al.  Design erosion: problems and causes , 2002, J. Syst. Softw..

[48]  Philippe Palanque,et al.  Software Architecture Modelling: Bridging Two Worlds Using Ergonomics and Software Properties , 1998 .

[49]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[50]  P. Kidwell,et al.  The trouble with computers: Usefulness, usability and productivity , 1996, IEEE Annals of the History of Computing.

[51]  E. Burton Swanson,et al.  The dimensions of maintenance , 1976, ICSE '76.

[52]  Hallvard Trætteberg,et al.  Interaction Patterns in User Interfaces. , 2000 .

[53]  Patty Curthoys,et al.  Developing user interfaces: Ensuring usability through product and process , 1997 .

[54]  Jan Bosch,et al.  Design and use of software architectures - adopting and evolving a product-line approach , 2000 .

[55]  W. Buxton.  Human-Computer Interaction , 1988, Springer Berlin Heidelberg.