Problem frames and business strategy modelling

Babar, A; Zowghi, D; Cox, K; Tosic, V; Bleistein, S; Verner, J

Problem frames and business strategy modelling

Babar, A Zowghi, D

Cox, K Tosic, V Bleistein, S Verner, J

Permalink

Publication Type:: Conference Proceeding
Citation:: Proceedings - International Conference on Software Engineering, 2008, pp. 48 - 51
Issue Date:: 2008-12-08

Closed Access

	Filename	Description	Size
	2008001748OK.pdf		564.12 kB	Adobe PDF	View/Open

Copyright Clearance Process

Recently Added
In Progress
Closed Access

This item is closed access and not available.

Full metadata record

Field	Value	Language
dc.contributor.author	Babar, A	en_US
dc.contributor.author	Zowghi, D https://orcid.org/0000-0002-6051-0155	en_US
dc.contributor.author	Cox, K	en_US
dc.contributor.author	Tosic, V	en_US
dc.contributor.author	Bleistein, S	en_US
dc.contributor.author	Verner, J	en_US
dc.date.issued	2008-12-08	en_US
dc.identifier.citation	Proceedings - International Conference on Software Engineering, 2008, pp. 48 - 51	en_US
dc.identifier.isbn	9781605580203	en_US
dc.identifier.issn	0270-5257	en_US
dc.identifier.uri	http://hdl.handle.net/10453/11892
dc.description.abstract	Requirements engineering describes how an IT implementation will support business functions. Most IT systems are operational in nature and typical requirements engineering techniques and methods are usually adequate in capturing and documenting the requirements for such systems. Jackson's problem frames is a technique that is suitable for straightforward IT systems descriptions. However, when an organization deploys an IT system that must deliver upon its competitive business strategy, then an appropriate technique or method needs to be used to capture that business strategy in order to connect it to businesscritical IT requirements. Here we provide an overview of the use and adaptation of problem frames to connect requirements to business strategy. We found that a simplification of the problem frames notation was necessary and that to be really effective, we had to integrate problem fames with goal modelling and Map, a method that helps describe the evolution of IT over time. Copyright 2008 ACM.	en_US
dc.relation.ispartof	Proceedings - International Conference on Software Engineering	en_US
dc.relation.isbasedon	10.1145/1370811.1370821	en_US
dc.title	Problem frames and business strategy modelling	en_US
dc.type	Conference Proceeding
utslib.for	0803 Computer Software	en_US
dc.location.activity	Liepzig, Germany	en_US
pubs.embargo.period	Not known	en_US
pubs.organisational-group	/University of Technology Sydney
pubs.organisational-group	/University of Technology Sydney/DVC (Research)
pubs.organisational-group	/University of Technology Sydney/DVC (Research)/Graduate Research School
pubs.organisational-group	/University of Technology Sydney/Faculty of Engineering and Information Technology
pubs.organisational-group	/University of Technology Sydney/Strength - HCTD - Human Centred Technology Design
pubs.organisational-group	/University of Technology Sydney/Strength - STEM Education Futures
utslib.copyright.status	closed_access
pubs.publication-status	Published	en_US

Abstract:

Requirements engineering describes how an IT implementation will support business functions. Most IT systems are operational in nature and typical requirements engineering techniques and methods are usually adequate in capturing and documenting the requirements for such systems. Jackson's problem frames is a technique that is suitable for straightforward IT systems descriptions. However, when an organization deploys an IT system that must deliver upon its competitive business strategy, then an appropriate technique or method needs to be used to capture that business strategy in order to connect it to businesscritical IT requirements. Here we provide an overview of the use and adaptation of problem frames to connect requirements to business strategy. We found that a simplification of the problem frames notation was necessary and that to be really effective, we had to integrate problem fames with goal modelling and Map, a method that helps describe the evolution of IT over time. Copyright 2008 ACM.

Please use this identifier to cite or link to this item:

http://hdl.handle.net/10453/11892