Skip to main content

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

Rss Feed Group items tagged

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

ISO/IEC 42010:2007 architectural description of software-intensive systems - 0 views

www.iso.org/...catalogue_detail.htm

shared by Peter Van der Straaten on 01 Mar 10 - Cached
  • Systems and software engineering -- Recommended practice for architectural description of software-intensive systems
  • Peter Van der Straaten on 01 Mar 10
     
    Systems and software engineering -- Recommended practice for architectural description of software-intensive systems
Peter Van der Straaten

Requirements Engineering: A Roadmap - 0 views

www.doc.ic.ac.uk/...sotar.re.pdf

requirements engineering paper 2000-2010

shared by Peter Van der Straaten on 17 Mar 10 - Cached
  • Peter Van der Straaten on 17 Mar 10
     
    This paper presents an overview of the field of software systems requirements engineering (RE). It describes the main areas of RE practice, and highlights some key open research issues for the future.
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

IREB - Mission - 0 views

www.certified-re.de/mission.html

requirements engineering certification

shared by Peter Van der Straaten on 12 Mar 10 - Cached
  • Requirements Engineering ist eine Schlüsseldisziplin
  • jährliche Bericht der Standish Group “The Scope of Software Development Project Failures”
  • Rund die Hälfte der in dem Bericht untersuchten Projekte erreicht die angestrebten Ziele nicht aufgrund von Fehlern im Requirements Engineering.
Peter Van der Straaten

IREB -Mission - 0 views

www.certified-re.de/...mission.html

ireb requirements engineering certification

shared by Peter Van der Straaten on 12 Mar 10 - Cached
  • Requirements Engineering is a key discipline
  • the annual report of the Standish Group, “The Scope of Software Development Project Failures”. About half of all projects examined in the report fail to achieve their set goals because of a lack of requirements engineering.
Peter Van der Straaten

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

www.blueprintsys.com/...ion-and-management-for-dummies

BARE ---- ebook requirements engineering requirements management

shared by Peter Van der Straaten on 14 Jul 14 - No Cached
  • 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
      Peter Van der Straaten on 14 Jul 14
       
      Content quite superficial; It's somewhat usefull for RE, RM and BA newbies. Mostly advertises the blueprint tool
  • Peter Van der Straaten on 14 Jul 14
     
    VALT TEGEN: Relatief oppervlakkig, en meer een vehikel om eigen tool aan de man te brengen.
Peter Van der Straaten

SearchSoftwareQuality - Software Requirements researched and organized - 0 views

searchsoftwarequality.techtarget.com/...295493,sid92_tax306103,00.html

requirements engineering

shared by Peter Van der Straaten on 17 Mar 10 - Cached
  • Requirements Software requirements resources to help development teams create quality software.
Peter Van der Straaten

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

en.wikipedia.org/MKS_Inc.

wikipedia requirements engineering review tool requirements management 2000-2010

shared by Peter Van der Straaten on 10 May 11 - No Cached
  • 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

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

www.abelia.com/122_016.pdf

j-std-016 ieee iso iso12207 ieee12207 rws waterportaal requirements engineering MIL-STD-498

shared by Peter Van der Straaten on 02 Dec 11 - No Cached
  • Peter Van der Straaten on 02 Dec 11
     
    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

agile - How to use BPMN and use case and other diagrams together - Software Engineering... - 0 views

softwareengineering.stackexchange.com/...se-and-other-diagrams-together

use case business analysis requirements engineering BPMN

shared by Peter Van der Straaten on 22 Jul 21 - No Cached
  • The only use cases that should be left over should be cases that describe situations that are not fully covered by the BPMN.
Peter Van der Straaten

IT Job Market, Processes & Methodologies Category - 0 views

www.itjobswatch.co.uk/default.aspx

Agile RE process methodologies job market agile requirements engineering

shared by Peter Van der Straaten on 04 May 12 - No Cached
  • Agile Software Development21+4£45,000-10114 (8.23 %)
  • Scrum35+10£47,500-6778 (5.51 %)
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

Requirements.net: - The industry consortium for business analysis. - 0 views

www.requirements.net

requirements engineering

shared by Peter Van der Straaten on 12 Mar 10 - Cached
  • Requirements.net is home of the industry consortium for business analysis. Through focus on requirements definition, visualization, and management, the companies behind Requirements.net are driven to share and sponsor best practices and technologies to improve industry requirements practices
  • Peter Van der Straaten on 12 Mar 10
     
    Consortium consists of HP Software, Blueprint, RQNG, Orasi, Sky IT, and CorTechs
Peter Van der Straaten

SOLIM - software life cycle management - 0 views

www.solim.nl

requirements engineering requirements management

shared by Peter Van der Straaten on 10 Mar 10 - Cached
Peter Van der Straaten

Software Quality Requirements and Evaluation, the ISO 25000 Series - 0 views

www.ic.unicamp.br/...iso_25000_SEI_2004.pdf

SQuaRE ISO25000 measurement sei requirements engineering non-functional

shared by Peter Van der Straaten on 20 Apr 12 - Cached
  • Peter Van der Straaten on 20 Apr 12
     
    Measurement focus
Peter Van der Straaten

Automating Requirements Management - K.E. Wiegers - 0 views

www.processimpact.com/...rm_tools.html

requirements engineering tool review paper

shared by Peter Van der Straaten on 17 Mar 10 - Cached
  • Automating Requirements Management
  • Software Development, July 1999
Peter Van der Straaten

Use-Case 2.0 ebook - 0 views

www.ivarjacobson.com/use_case2.0_ebook

ebook book requirements engineering use case cockburn ++++ Use case 2.0 debate

shared by Peter Van der Straaten on 25 May 12 - No Cached
  • re-focuses on the essentials and offers a slimmed down, leaner way of working, for software teams seeking the benefits of iterative, incremental development at an enterprise level
  • Author: Ivar Jacobson, Ian Spence, Kurt Bittner
  • Based on several years of work with many of our customers around the world, we have revamped use cases to provide a scalable approach to managing requirements for agile projects and programs.
  • Peter Van der Straaten on 25 May 12
     
    Free e-book (after registration)
1 - 20 of 20
Showing 20▼ items per page