Skip to main content

Requirements Engineering

I know I should read all those methods more in details.


I found this in the Poll Best Requirement Survey by Xebia.
So what is a requirements method? Since this is not a generally agreed-upon term from the dictionary, we need to define it. There are a few cases where a coherent set of ideas, written down in a book, can easily be seen as a 'method'. Two cases in point are "Volere" and "the Wiegers approach". They both cover almost the entire working area of requirements engineering in at least some detail. In other cases, an approach only covers one area of requirements engineering, such as elicitation techniques. Another possibility is a method that covers a larger area of software or business development, and includes part of requirements engineering. An example of the latter is RUP.
Methods
The methods covered in this survey are:

* Volere (Suzanne and James Robertson)
* Wiegers (Karl Wiegers)
* The Software Requirements Memory Jogger (Ellen Gottesdiener)

* Requirements by Collaboration (Ellen Gottesdiener)
* Just Enough Requirements Management (Alan M. Davis)
* Competitive Engineering (Tom Gilb)
* eRequirements (Stephen Robinson)

* RUP (Rational Software)
* Scrum (Sutherland, Schwaber et al.)

Terms and definitions

Requirements Engineering : All project life cycle activities associated with understanding a product's necessary capabilities and attributes.
Includes:

Requirements Management : Working with a defined set of product requirements throughout the product's development process and its operational life.
Includes: status tracking, tracing, change management, versioning

Requirements Development : The product of requirements development is a requirements baseline that defines the product to be built.

Elicitation : Identifying software or system requirements from various sources through various techniques.

Analysis : Classifying requirements information into various categories, evaluating requirements for desirable qualities, representing requirements in different forms, deriving detailed requirements from high-level requirements, negotiating priorities, etc.

Specification : Documenting a system's requirements in a structured, shareable, and manageable form.

Validation : Evaluating a work product to determine whether it satisfies the specifications and conditions imposed on it at the beginning of the development phase during which it was created.

Stakeholder Management : the activities a business enterprise initiates to manage the relationships with its stakeholders


I can't help to copy the whole thing since I am not sure about the longevity of this page.

Some points also in Wikipedia on Requirement.

Comments

Popular posts from this blog

VirtualBox, CentOS, Network and Template

I have been working with VirtualBox and CentOS recently, here are some notes about this experience.
I used VirtualBox 4.2 and CentOS 6.3, but most of this should work with other products too. I created the first headless, minimal CentOS via NetInstall.
I cover two points: create a template machine and configure the Network.
Configure the NetworkWe want Internet access and a LAN local to the host.
For background information read: Networking in VirtualBox by Fat Bloke on June 2012.
The easiest is to enable two Network Adapters: One will be "Host-only" and the second "Nat". In the "Preference" menu you can see the DHCP server range for the Host-only Network. So you may set fixed addresses outside this range.
Next: start the guest. There may be various results at first, depending on a lot of things. Some problem might be solved by rm -f /etc/udev/rules.d/70-persistent-net.rules and a reboot.
Anyway, configure the two interfaces (set your own IP and MAC addresses)…

One in six IT projects ends up ‘out of control’

http://www.ox.ac.uk/media/news_stories/2011/110822_1.html

A surprisingly high number of projects are 'ticking time bombs', according to researchers at the University of Oxford. They analysed 1,500 global projects that had revamped their information technology systems within the last 10 years. They discovered that one in six projects in the sample went over budget by an average of 200 per cent (in real terms) or over ran by an average of almost 70 per cent.

Their conclusion is similar to previous studies: http://brunovernay.blogspot.com/2009/10/excellent-studies-on-software-quality.html

TLS: Disabling legacy cipher suites

First: "cipher suite is a named combination of authentication, encryption, and message authentication code (MAC) algorithms".If you are using TLS (for HTTPS typicaly) you may want to remove some Cipher Suites.You maybe a little bit less compatible, but also a bit more secure. Things will be better when TLS1.2 is implemented everywhere.You can also claim to be FIPS 140 compliant: http://csrc.nist.gov/publications/nistpubs/800-52/SP800-52.pdf !How to do it:From the command line:  http://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/JSSERefGuide.html#CustomizationFrom code:  http://docs.oracle.com/javase/7/docs/api/javax/net/ssl/SSLSocket.html#setEnabledCipherSuites(java.lang.String%5B%5D)Jetty: http://wiki.eclipse.org/Jetty/Howto/CipherSuitesTomcat: Look at the "ciphers" attribute in  http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_SupportIf someone knows how to do it on the IBM J9 via configuration, I am interested.