Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword or section
Like this
9Activity

Table Of Contents

0 of .
Results for:
No results containing your search query
P. 1
Software Acquisition Management Guidelines

Software Acquisition Management Guidelines

Ratings: (0)|Views: 756 |Likes:
Published by daniel_svennberg
The thesis provides guidelines from the viewpoint of the customer for managing an acquisition project concerning an outsourced development of a software product customized for the specific needs of the customer. Current frameworks for software acquisition management such as SA-CMM, IEEE 1062, ISO 12207, etc. as well as literature, articles, and interviews has been used as a basis for formulating the guidelines.

The resulting guidelines include acquisition team roles descriptions, checklists for artifacts, customizable processes, and customization factors. The processes contain guidelines for the following issues: project steering, project management, planning and organizing, acquisition training, requirements management, risk management, contractor selection, contract management, product evaluation, transition to support, and post partum.

The guidelines can be used as a basis for planning an acquisition project or be read as an overview over the many issues that concern software acquisitions.
The thesis provides guidelines from the viewpoint of the customer for managing an acquisition project concerning an outsourced development of a software product customized for the specific needs of the customer. Current frameworks for software acquisition management such as SA-CMM, IEEE 1062, ISO 12207, etc. as well as literature, articles, and interviews has been used as a basis for formulating the guidelines.

The resulting guidelines include acquisition team roles descriptions, checklists for artifacts, customizable processes, and customization factors. The processes contain guidelines for the following issues: project steering, project management, planning and organizing, acquisition training, requirements management, risk management, contractor selection, contract management, product evaluation, transition to support, and post partum.

The guidelines can be used as a basis for planning an acquisition project or be read as an overview over the many issues that concern software acquisitions.

More info:

Published by: daniel_svennberg on Jan 01, 2010
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/23/2012

pdf

text

original

 
 
S
OFTWARE
A
CQUISITION
M
ANAGEMENT
G
UIDELINES
 
by
Daniel Svennberg 
A Thesissubmitted for the Degree ofMaster of Science
 
Linköping, Sweden, 2001The Department of Computer and Information ScienceLinköping UniversityLiTH-IDA-Ex-01/32
 
Lars Ljungberg, Mats RanAdvisors, Q-Labs ABKristian SandahlExaminer, Linköping University
 
 
Copyright 2001 Daniel SvennbergAll rights reserved. No part of this publication may be reproduced,stored in a retrieval system, or transmitted, in any form or by anymeans including, without limitation, photocopying, recording, or oth-erwise without the prior written permission of the author. Written per-mission is not needed if this publication is distributed for non-commercial purposes.
Linköpings Universitet,Institutionen för DatavetenskapQ-Labs, Linköping and MarylandFraunhofer, Maryland,Center for Experimental Software Engineering
Software Acquisition Management GuidelinesRiktlinjer för ledning av programvaruupphandlingLiTH-IDA-Ex-01/32
 
Linköping UniversityQ-Labs ABFraunhofer, Inc.
 
i
Abstract
The thesis provides guidelines from the viewpoint of the cus-tomer for managing an acquisition project concerning an out-sourced development of a software product customized for thespecific needs of the customer. Current frameworks for soft-ware acquisition management such as SA-CMM, IEEE 1062,ISO 12207, etc. as well as literature, articles, and interviews hasbeen used as a basis for formulating the guidelines.The resulting guidelines include acquisition team roles descrip-tions, checklists for artifacts, customizable processes, and cus-tomization factors. The processes contain guidelines for the fol-lowing issues: project steering, project management, planningand organizing, acquisition training, requirements manage-ment, risk management, contractor selection, contract manage-ment, product evaluation, transition to support, and post par-tum.The guidelines can be used as a basis for planning an acquisi-tion project or be read as an overview over the many issues thatconcern software acquisitions.

Activity (9)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
SamiRa liked this
Hermann Dario liked this
rajaramansuresh liked this
kalamsoftware liked this
dlwatson liked this
T_N_Ganesh333 liked this
tafe4cs liked this

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->