[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)

MorrisSegal12
  1. Chris Morris & Judith Segal
  2. Lessons learned from a scientific software development project
  3. IEEE Software Magazine V29n4(Jul/Aug 2012)pp9-12 [ software ]
  4. =EXPERIENCE AGILE SCIENTIFIC PROJECT LIMS LABORATORY INSTRUMENTATION BIOLOGY DATA
  5. Consider the software from the user's point of view. Clients are not always users.
  6. Users didn't give good descriptions of what was needed.
  7. High level goals stated at the start of the project may conflict with users actual needs.
  8. You have to understand the users.
  9. Start with what the users do now.
  10. If you have to write a guide so user can use the UI -- you've got a bad UI. The UI should reflect current systems.
  11. Personas help understanding.
  12. Communications within the team is vital. Teams spread across branches of the enterprise and world need special training.
  13. Plan for maintenance from the start. Who will pay?
  14. If adopting the software changes work practices you have an extra challenging project.

Search for bibliographic items containing a matching string.


(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.



To see the complete bibliography (1Mb+) select:[Bibliography]