Get Free Shipping on orders over $79
Requirements Engineering : Practitioner Series - Elizabeth Hull

Requirements Engineering

By: Elizabeth Hull, Ken Jackson, Jeremy Dick

eText | 17 April 2013

At a Glance

eText


$129.00

or 4 interest-free payments of $32.25 with

 or 

Instant online reading in your Booktopia eTextbook Library *

Why choose an eTextbook?

Instant Access *

Purchase and read your book immediately

Read Aloud

Listen and follow along as Bookshelf reads to you

Study Tools

Built-in study tools like highlights and more

* eTextbooks are not downloadable to your eReader or an app and can be accessed via web browsers only. You must be connected to the internet and have no technical issues with your device or browser that could prevent the eTextbook from operating.

We live in a commercial world where much of our work is undertaken through a project -oriented approach. This has the advantage of determining the cost and time of the project to be undertaken, which in their turn are based on the knowledge of what the project is to deliver. Computing is no different in this regard, and so in order to organize our activities, we need to know what it is that is to be delivered. Hence Requirements Engineering, an organized approach to determining what is required in the project/ system that is being undertaken. There are some problems with the idea of Requirements Engineering, which I have on previous occasions encapsulated in a single sentence called 'The Mock Theorem of Information Systems' which states 'There exists some point in time when everyone involved in the system knows what they want and agrees with everyone else' Clearly nonsense (how would you know what everyone is agreeing to for example?). But in order to build a system on a project basis, this sentence has to be assumed to be true (either explicitly, or even worse, implicitly). Then Requirements Engineering can be made to work, and the correct prod uct/ system delivered by the project. However, we do not have an established alternative to the project approach, and the business world is used to projects. So Requirements Engineering is necessary, but it needs tempering to allow for the desired certainty actually being unknown.

on
Desktop
Tablet
Mobile

Other Editions and Formats

PDF

Published: 23rd August 2017

Instant online reading in your Booktopia eTextbook Library *

More in Software Engineering

The End of Leadership - Barbara Kellerman

eBOOK

The Debugging Handbook - Johannes Kuhlmann

eBOOK

RRP $67.77

$54.99

19%
OFF
API Management with Bruno - Lyria Tharax

eBOOK

Essential n8n Playbook - Leandro Calado

eBOOK