Mostrar mensagens com a etiqueta Acronyms. Mostrar todas as mensagens
Mostrar mensagens com a etiqueta Acronyms. Mostrar todas as mensagens

quarta-feira, 11 de maio de 2016

Standards: Terminology Standards (Acronyms and Definitions "for all")

Your company has for sure a Glossary of terms that you should read and know from the start to the very end. Do you?

If not, you can always start learning a little bit more about terminology of the [software] industry (as well as UXD terms and other related disciplines) in these standards and/or googable / purchasable documents:
  • ECSS, Glossary of Terms, ECSS-P-001 Issue 1 Rev., 11 June 1997. ECSS-P-001
  • ISO, Space systems. Glossary of terms, BS EN 13701:2001, CU, 15 July 2001 BS EN 13701:2001
  • CMU/SEI, CMMI for Development, CMU/SEI-2006-TR-008, Version 1.2., August 2006, CMU/SEI-2006-TR-008
  • ISO, Quality management systems. Fundamentals and vocabulary, BS EN ISO 9000:2005, October 2005, BS EN ISO 9000:2005
  • ECSS, Space Engineering – Software, ECSS-E-40B Draft 1, 15 February 2002. ECSS-E-40B
  • NATO, NATO Supplementary Software Quality Assurance Requirements to AQAP 2110, AQAP-2210 NATO, Edition 1 – November 2006, AQAP-150
  • NATO, NATO Quality Assurance Requirements for Design, Development and Production, AQAP-2110 NATO, Edition 3 –November 2009, AQAP-2110
  • SynSpace, Software Engineering Glossary, www.synspace.com, N/A
  • ISO, Human-centred design processes for interactive systems, 13407:1999, 1st June 1999. ISO13407:1999 (now outdated)
  • Morgan Kaufmann, Usability Engineering, Jakob Nielsen, 23rd September 1993. 978-0125184069
  • IS/ISO, Quality Management – Customer Satisfaction – Guidelines for Complaints handling in Organizations, ISO 10002 (2004), January 2006, ISO 10002:2004
(2016-09-30: reordering)


segunda-feira, 2 de maio de 2016

The MoSCoW requirements prioritization method

The MoSCoW method is a prioritization technique on which each non-O letter refers to the priority of each requirement (Must have, Should have, Could have, and Would like but won't get). Some RFPs will use this method to state clearly what the proposals shall have, what is a nice to have, what is optional and what could be left for further versions of the information system to be delivered).

For more information: https://en.wikipedia.org/wiki/MoSCoW_method