Skip to main content

Home/ BARE+IA Requirements Engineering Information&Business Analysis/ Group items tagged development

Rss Feed Group items tagged

Peter Van der Straaten

http://www.abelia.com/docs/122_016.pdf - 0 views

  •  
    Comparison IEEE/EIA 12207, J-STD-016, ISO/IEC 12207, J-STD-016, MIL-STD-498  for Acquirers and Developers Opm: rws j-std-016 (waterportaal, havik2)
Peter Van der Straaten

"The Forrester Wave(tm): Agile Development Management Tools, Q2 2010," Forrester Resear... - 0 views

  • MKS Named a Leader in Forrester’s Analysis of Agile Development Management Tools
  • MKS is pleased to offer you a complimentary copy of this independent research
Peter Van der Straaten

BDD,Cucumber,Gherkin,User Stories,use cases,TDD - IT Jobs Watch Search - 0 views

  • TDD34-8£60,000-6,064 (6.48%)1,470
  • BDD109-29£60,000+3.44%2,823 (3.02%)607
  • User Experience43+8£55,000-5,279 (5.65%)1,045
  • ...9 more annotations...
  • User Stories1730£55,000-1,814 (1.94%)335
  • DescriptionRank6 Months to27 May 2021RankYoY ChangeMedian SalaryMedian SalaryYoY ChangeHistoricalPermanentJob AdsLiveJobs
  • Cucumber279-20£60,000+14.28%1,051 (1.12%)143
  • User Acceptance Testing284-56£47,500-5.00%1,039 (1.11%)193
  • Business Cases311-71£56,878-5.20%932 (1.00%)210
  • Use Case3170£63,500+10.43%917 (0.98%)206
  • User Experience Designer443-30£52,500-4.54%581 (0.62%)101
  • Gherkin598-4£52,500-331 (0.35%)45
  • Epic User Stories616+64£57,542-7.93%304 (0.33%)50
Peter Van der Straaten

Behavior-Driven Development - 0 views

  •  
    LinkedIn Learning BDD course (payed)
Peter Van der Straaten

The beginner's guide to BDD (behaviour-driven development) - 0 views

  • to support the ability for systems to change, we should be able to safely make big changes (supported by automated scenarios), as well as the small ones (supported by automated object specifications).
  • Impact mapping
  • mind mapping
  • ...19 more annotations...
  • business goal, one or more actors, one or more impacts and one or more ways to support or prevent these impacts
  • You always start with the business goal; it is your map’s root node. You then grow the map out from the goal by first identifying all the actors (e.g. the customer or the team) that could help or prevent the project from achieving the goal. Each actor could have multiple ways to help or hinder achieving the goal, we call these impacts. The last layer of an impact map defines what the project or delivery team can do in order to support or prevent particular impacts from happening, and this is the layer where your software options come into play.
  • In BDD we use Cynefin to identify which features require the most attention
  • Value and complexity analysis
  • reuse
  • outsource
  • Cynefin to make strategic planning decisions based on value/complexity analysis
  • Planning in examples
  • Usage-centered design
  • Ubiquitous language
  • eliminate the cost of translation
  • borrowed from DDD (Domain Driven Design)
  • 'Given, describes the initial context for the example'When' describes the action that the actor in the system or stakeholder performs'Then' describes the expected outcome of that action
  • Introducing the three amigos
  • no single person has the full answer to the problem
  • business person, a developer and a tester.
  • Development through examples
  • The BDD loops
  • How we use it
Peter Van der Straaten

Alistair.Cockburn.us | Why I still use use cases - 1 views

  • XP pretty much banned use cases, replacing them with the similar sounding “user stories”
  • Scrum did similar, using the “product backlog” instead of user stories
  • Yet as I go around projects, I keep running across organizations suffering from three particular, real, painful, and expensive problems
  • ...15 more annotations...
  • User stories and backlog items don’t give the designers a context to work from
  • don’t give the project team any sense of “completeness
  • don’t provide a good-enough mechanism for looking ahead at the difficulty of upcoming work
  • Staring at the set of extension conditions in a use case lets the analysts suss out which ones will be easy and which will be difficult, and to stage their research accordingly
  • Here 5 reasons why I still write use cases
  • The list of goal names provides executives with the shortest summary of what the system will contribute to the business and the users
  • The main success scenario of each use case provides everyone involved with an agreement as to what the system will basically do, also, sometimes more importantly, what it will not do.
  • The extension conditions of each use case provide the requirements analysts a framework for investigating all the little, niggling things that somehow take up 80% of the development time and budget
  • The use case extension scenario fragments provide answers to the many detailed, often tricky business questions
  • The full use case set shows that the investigators have throught through every user’s needs, every goal they have with respect to the system, and every business variant involved
  • how much should be written up front to get the project estimate into a safe place
  • several sticky parts for people using use cases
  • iteration/sprint lengths are so short that it is not practical to implement an entire use case in just one of them.
  • Writing good use cases (or any other requirements) requires thinking, communicating, and thinking again. It is much easier just to write user-story tags on index cards and let the project blow up later
  • We have adopted many of the concepts of Agile development—such as daily build and test, build the smallest piece of functionality that delivers value, etc.—but have retained our up-front work. It’s worked extremely well
Peter Van der Straaten

IT Job Market, Processes & Methodologies Category - 0 views

  • Agile Software Development21+4£45,000-10114 (8.23 %)
  • Scrum35+10£47,500-6778 (5.51 %)
Peter Van der Straaten

MKS Inc. - Wikipedia, the free encyclopedia - 0 views

  • In 2008 Forrester proclaims MKS as the leader in requirements management in the independent research report
  • MKS positioned in the 'Leaders' quadrant in Gartner's first ever Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platforms
  • Gartner positioned MKS as a leader in the 2009 Magic Quadrant for Software Change and Configuration Management (SCCM) for Distributed Platform
  • ...1 more annotation...
  • Forrester named MKS as a leader in Agile development management tools in Forrester Research Inc., May 2010
Peter Van der Straaten

Free BDD Behavior Driven Development Tutorial - Basics of BDD for Beginners | Step-by-S... - 0 views

  • This course will teach you the very basics and foundation of BDD along with examples & workflow
  • You will learn and witness how BDD starts in an Organization along with a BDD Workshop
  • What are the different phases of BDD, BDD in Sprints and Agile Teams, BDD Roles and Responsibilities
Peter Van der Straaten

(119) What is Behavior Driven Development? (4 minute cartoon on BDD) - YouTube - 0 views

  •  
    Intro to BDD as compared to TDD
Peter Van der Straaten

(24) BDD - Business Driven Development | LinkedIn - 0 views

  •  
    The B stands for ...
Peter Van der Straaten

Introduction to SAMATE - SAMATE - 0 views

  • establish a methodology for evaluating software assurance tools
  • Source Code Security Analyzers – This class of software tools examines source code files for security weaknesses and potential vulnerabilities
  • Web Application Vulnerability Scanners – These tools crawl a web application’s pages and search the application for vulnerabilities by simulating attacks on it
  • ...3 more annotations...
  • A new effort on Binary Code Scanners - Similar to source code security analyzers, this class of tool analyzes a compiled binary application, including libraries, and provides a report of code weakness over the entire application.
  • The SAMATE Reference Dataset (SRD) - A community repository of example code and other artifacts to help end users evaluate tools and developers test their methods
  • Third annual Static Analysis Tools Exposition, which is in progress. The goals are to enable empirical research based on large test sets, encourage improvement of tools, and speed tool adoption by objectively demonstrating their use on real software.
Peter Van der Straaten

eBook: Requirements Definition and Management for Dummies - Blueprint Software Systems - 0 views

  • Requirements Definition and Management for DummiesSmart businesses know that high-quality requirements are the cornerstone of any successful software development project. This fun and friendly ebook is an introduction to the role that is central to requirements: the Business Analyst. It explains why the role is so critical and how Business Analysts are transforming software projects.
    • Peter Van der Straaten
       
      Content quite superficial; It's somewhat usefull for RE, RM and BA newbies. Mostly advertises the blueprint tool
  •  
    VALT TEGEN: Relatief oppervlakkig, en meer een vehikel om eigen tool aan de man te brengen.
Peter Van der Straaten

Hightech Events: Scrum - 0 views

  • 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.
  •  
    Inclusief presentaties
1 - 20 of 30 Next ›
Showing 20 items per page