Skip to main content

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

Rss Feed Group items tagged

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

Community | requirements kenniscentrum - 0 views

www.requirementskenniscentrum.nl/community.asp

requirements engineering requirements management community requirements

shared by Peter Van der Straaten on 04 Apr 12 - No Cached
  • Peter Van der Straaten on 04 Apr 12
     
    Nicole de Zwart
Peter Van der Straaten

DREAM event - 1 views

www.dreamevent.nl

dream event requirements engineering business analysis informatieanalyse ++++ Atos requirements community

shared by Peter Van der Straaten on 01 Mar 10 - Cached
  • Welkom bij het DREAM Event Atos Origin organiseert op dinsdag 9 maart 2010 voor de tweede keer het Dutch Requirements Engineering and Management event. Het event is open voor de gehele Requirements community; voor iedereen die werkt met specificaties.
  • Hartelijk welkom op de website van DREAM (Dutch Requirements Engineering And Management). In 2014 is al voor de 5de maal het DREAM event succesvol georganiseerd (zie hier een terugblik op de afgelopen events). We willen ook de komende jaren een bijdrage blijven leveren aan het verder verspreiden van de kennis en het begrip betreffende alles wat te maken heeft met requirements; van business rules tot en met user stories, van functioneel ontwerp tot en met modellen van bedrijfsprocessen.
Peter Van der Straaten

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

alistair.cockburn.us/Why+I+still+use+use+cases

agile use case user story uml cockburn debate

shared by Peter Van der Straaten on 25 May 12 - Cached
  • 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

Introduction to SAMATE - SAMATE - 0 views

samate.nist.gov/...Introduction_to_SAMATE.html

software assurance security Information security management ++++ IEEE quality assurance IEEE610

shared by Peter Van der Straaten on 27 Aug 13 - No Cached
  • 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

Requirements Kenniscentrum - 0 views

www.requirementskenniscentrum.nl

requirements engineering requirements use case informatieanalyse community

shared by Peter Van der Straaten on 01 Dec 14 - No Cached
  • Peter Van der Straaten on 01 Dec 14
     
    Redelijk goede kennisbank voor requirements. LET OP: wordt niet meer bijgehouden!
1 - 9 of 9
Showing 20▼ items per page