Skip to main content

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

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
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
  • there remained a split between those who still wanted to keep use cases short and informal and those who wanted them to be detailed
  • Here are four key pieces of advice that you should note from the evolution of use cases.
  • readable use cases might actually get read
  • 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.
  • The Stakeholders and Interests model fills the holes in the Actors and Goals model
  • Originally published in STQE magazine, Mar/Apr 2002
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

2013 Best and Worst Careers -- Ranking - WSJ.com - 0 views

online.wsj.com/...4874204578439154095008558.html

career software engineering information analysis business analysis

shared by Peter Van der Straaten on 22 Jul 13 - No Cached
  • Peter Van der Straaten on 22 Jul 13
     
    Interesting: Software engineer and Computer systems analist get third place and tenth place as best job in 2013.
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

Alistair.Cockburn.us | A user story is the title of one scenario whereas a use case is ... - 0 views

alistair.cockburn.us/contents+of+multiple+scenarios

agile use case user story uml cockburn debate

shared by Peter Van der Straaten on 25 May 12 - Cached
  • As a … I want… so that…” is a new-fangled user story format. The original XP user story format had no rules, so you could simply highlight any phrase in a use case and call it a user story. Personally, I feel sorry for anyone who has to write “As a… I want… so that…” for 200 user stories. Kind of like being kept after school and having to write “I will not write silly user stories in class” 100 times
  • A use case pretty much by definition contains multiple stories. A use case is a collection of scenarios related to the primary actor’s goal – some scenarios show the actor interacting with the system and the system interacting with other systems so that they succeed with the goal, some show failure. That’s all in the nature of a use case. see Structuring use cases with goals (discussion: Re: Structuring use cases with goals) from 1995. A use case written for this will occupy between half a page for a shortish one to 2 pages for a long one. A user story is a nickname for a single scenario – it contains neither the information content of the scenario nor failure or alternate paths. A user story typically occupies 1/2 to one sentence no matter its size.
  • (p.s. Agile was supposed to reduce bureaucracy and overhead, not add to it. :) Alistair
Peter Van der Straaten

EAM-Initiative : ArchiMate® - 0 views

eam-initiative.org/...ArchiMate

ArchiMate architecture Enterprise architecture qbest togaf

shared by Peter Van der Straaten on 11 Apr 18 - No Cached
  • Advantages & Disadvantages of ArchiMate®
  • One advantage of ArchiMate® is that it enables the visualization of architectures on separate layers but also allows the depiction of cross-layer relationships
  • Additionally, ArchiMate® provides extensive list of enterprise architecture entities, a predefined meta-model, some simplified standard views and publicly available, comprehensive documentation. Also, tool support for modeling the enterprise architecture using this architecture description language is available
  • ...1 more annotation...
  • A downside of ArchiMate® is that there is a limited extensibility of the modeling language. Further, some concepts are ambiguous [BBL12] and modelers need training to apply the framework successfully. Finally, when implementing ArchiMate®, a terminology mapping assigning existing concepts to the ArchiMate concept needs to be conducted
Peter Van der Straaten

INCOSE - RM Tools Database - 2 views

www.incose.org/...rmsurvey.aspx

requirements engineering INCOSE tool requirements management review

shared by Peter Van der Straaten on 17 Mar 10 - Cached
  • INCOSE Requirements Management Tools Survey
  • The survey responses, including the rating of compliance with each question or feature, are provided by the tool vendors directly. However, the TDWG reserves the right to review and correct any "informational injustices" (i.e. exaggerated answers).
  • Requirements Management Tool Survey Responses
  • Peter Van der Straaten on 17 Mar 10
     
    Survey responses by tool vendors; Microfocus tools not available
1 - 15 of 15
Showing 20▼ items per page