Skip to main content

Home/ BARE+IA Requirements Engineering Information&Business Analysis/ Contents contributed and discussions participated by Peter Van der Straaten

Contents contributed and discussions participated by Peter Van der Straaten

Simple Middle Filter: All | Bookmarks | Topics
Peter Van der Straaten

EXIN-proefexamen - 0 views

www.bislfoundation.nl/oundation-exin-proefexamen.htm

exam certification bisl training qbest informatiemanagement

shared by Peter Van der Straaten on 03 Apr 18 - No Cached
Peter Van der Straaten

EXIN Business Information Management Foundation with reference to BISL | EXIN - 0 views

www.exin.com/...foundation-reference-bisl-exam

exam certification bisl training qbest

shared by Peter Van der Straaten on 03 Apr 18 - No Cached
  • Peter Van der Straaten on 03 Apr 18
     
    The BiSL foundation certification is offered by Exin (around 225 euro).
Peter Van der Straaten

Key words for use in RFCs to Indicate Requirement Levels - 0 views

www.ietf.org/rfc2119.txt

requirements specification rfc standards MoSCoW qbest requirements engineering requirements management

shared by Peter Van der Straaten on 19 Sep 16 - Cached
  • The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Peter Van der Straaten

The PMI-PBA vs. IIBA CBAP or CCBA - 0 views

www.bridging-the-gap.com/e-pmi-pba-vs-iiba-cbap-or-ccba

certification CBAP CCBA PMI-PBA business analysis

shared by Peter Van der Straaten on 22 Jul 15 - No Cached
  • Through the new practice guide and PMI-PBA certification, PMI will drive an awareness of the role globally that IIBA® has simply not had the resources to do
  • To obtain a PMI-PBA, first you complete an application that verifies you meet the following requirements: Minimum of 3 years (4,500 hours) of business analysis experience within the past 8 consecutive years if you have a bachelor’s degree. (Or 5 years/7500 hours of experience if you do not.) (For comparison, the CBAP® requires 7,500 hours of experience and the CCBA® 3,750.) 2,000 hours working on project teams within the past eight consecutive years. 35 business analysis education (contact hours).
Peter Van der Straaten

Hightech Events: Scrum - 0 views

www.runbysoftware.com/...scrum

scrum Agile SAFe 2015 SPIder

shared by Peter Van der Straaten on 08 Jul 15 - No Cached
  • Scrum works very fine within small teams, adding new functionality in an incremental way. But how to transform traditional developers into a scrum way of working and how to align the multiple teams? How to maintain piles of legacy code? And how to go about solving the specific issues the high tech industry has with Agile? The session ‘Scrum is not enough!’ will give an overview of these challenges and presents best practices to address them.
  • Peter Van der Straaten on 08 Jul 15
     
    Inclusief presentaties
Peter Van der Straaten

FAQ | IT-Staffing - 0 views

www.it-staffing.nl/FAQ.aspx

zzp informatieanalyse career

shared by Peter Van der Straaten on 01 Apr 15 - No Cached
  • Welke kennis wordt veel gevraagd? Antwoord: IT-ers met kennis van Cisco, Oracle, Java, SAP, Peoplesoft, testen, informatie analyse zijn gewild en kunnen over het algemeen snel aan opdracht geholpen worden. Ook andere expertises zijn over het algemeen prima in te zetten.
  • Peter Van der Straaten on 01 Apr 15
     
    IT-ers met kennis van informatieanalyse zijn in trek, stelt IT staffing.
Peter Van der Straaten

Alistair.Cockburn.us | Use cases, ten years later - 1 views

alistair.cockburn.us/Use+cases,+ten+years+later

requirements engineering use case training cockburn debate

shared by Peter Van der Straaten on 05 Feb 15 - No Cached
  • Is a use case a requirement or just a story? Is a scenario just another name for a use case? Is a use case a formal, semi-formal, or informal structure? Is there a linking structure for use cases, or do they just come in piles?
  • make use cases “rigorous
  • People want a fairly informal medium in which to express their early thoughts
  • ...28 more annotations...
  • handling all the variations a system must handle.
  • Using these semi-formal structures, we can both Assert that use cases really are requirements and need a basic structure, and also Allow people to write whatever they want when they need to.
  • Here is the semi-formal structure
  • Linking use cases to actors’ goals
  • If the software supports those goals, the software will yield the greatest business value.
  • goals sometimes fail
  • failure handling
  • Therefore, a use case is structured into two sections: the sequence of actions when everything goes well, followed by various small sequences describing what happens when the various goals and subgoals fail.
  • Why do we write things in the use case that are not externally visible behaviors?
  • contract between stakeholders
  • Here are four key pieces of advice that you should note from the evolution of use cases.
  • there remained a split between those who still wanted to keep use cases short and informal and those who wanted them to be detailed
  • The Stakeholders and Interests model fills the holes in the Actors and Goals model
  • Prepare for Multiple Formats
  • Only Use Them When the Form is Appropriate
  • Be Aware of Use Case Limits
  • Use cases should not be used to describe UI designs
  • use case is normally intended as a requirements document, and the UI design is a design
  • The same system feature is likely to show up as a line item in multiple use cases
  • Use cases have a basic mismatch with feature lists
  • Use cases are not test plans or test cases
  • Avoid the Standard Mistakes in Use Cases
  • The two most common and most costly to the project are including too many details and including UI specifics
  • it’s just that by the time I get subgoals at a good level and remove the design specifics, the task is less than nine step
  • The greatest value of the use case does not lie in the main scenario, but in alternative behaviors
  • If the main scenario is between three and nine steps long, the total use case might only be two or three pages long, which is long enough.
  • readable use cases might actually get read
  • Originally published in STQE magazine, Mar/Apr 2002
Peter Van der Straaten

User story - Wikipedia, the free encyclopedia - 0 views

en.wikipedia.org/User_story

use case debate user story

shared by Peter Van der Straaten on 05 Feb 15 - Cached
  • Comparing with use cases
  • Kent Beck, Alistair Cockburn, Martin Fowler and others discussed this topic further on the c2.com wiki (the home of extreme programming).[16]
  • "User Story And Use Case Comparison". c2.com.
« First ‹ Previous 41 - 60 of 181 Next › Last »
Showing 20▼ items per page