[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php
Bibliographic Item (1.0)
- Chris Morris & Judith Segal
- Lessons learned from a scientific software development project
- IEEE Software Magazine V29n4(Jul/Aug 2012)pp9-12
[ software ]
- =EXPERIENCE AGILE SCIENTIFIC PROJECT LIMS LABORATORY INSTRUMENTATION BIOLOGY DATA
- Consider the software from the user's point of view.
Clients are not always users.
- Users didn't give good descriptions of what was needed.
- High level goals stated at the start of the project may conflict with users actual needs.
- You have to understand the users.
- Start with what the users do now.
- 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.
- Personas help understanding.
- Communications within the team is vital.
Teams spread across branches of the enterprise and world need special training.
- Plan for maintenance from the start. Who will pay?
- If adopting the software changes work practices you have an extra challenging project.
Search for bibliographic items containing a matching string.
Search for a specific bibliographic item by name.
To see the complete bibliography (1Mb+) select:[Bibliography]