Skip to main content

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

Rss Feed Group items tagged

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

SOLIM - software life cycle management - 0 views

Peter Van der Straaten

Requirements by Collaboration Book - Ellen Gottesdiener - 0 views

  •  
    Ellen has years of hands-on experience with Agile projects, with a focus on requirements. Key-note speaker on DREAM 2011; met her at evening workshop on 20110920.
Peter Van der Straaten

Use Cases for Business Analysts - The New School - 0 views

  • In my experience use cases are very powerful tools - their purpose is show the view from a *user's point of view*. The presented example is already very technical, and specifies a lot of details.
  • May I offer alternatives to the example in the article?A) A few brief classic requirements (for business) & a diagram (BPMN or UML activity diagram) (for the engineers)B) A use case with a lot less details (maybe 4-8 steps) & user interface design & a list of business rules (describing the essence of the details)C) No use case. One single sentence describing the goal & rationale ("As a user I want to have a recovery method when I forget the password because ....") & brief description of the important parts, business rules (no flow details!) & user interface design
  • May I offer other improvements to the "classic" use case in the example?- Instead of a summary, formulate it as a goal (remove redundancy)- Adding how frequently this is done ("Frequency: seldom, max. once per month ... once every few years")- Keep the main flow under 10 points- Remove pre-conditions and post-conditions. Keep it simple.- Integrate the alternative flows into the main flow (if possible, leave away details)
1 - 5 of 5
Showing 20 items per page