Content management in software development transition - Case Tellabs

 |  Login

Show simple item record

dc.contributor Aalto University en
dc.contributor Aalto-yliopisto fi
dc.contributor.author Koskinen, Jani
dc.date.accessioned 2012-05-26T01:30:39Z
dc.date.available 2012-05-26T01:30:39Z
dc.date.issued 2012
dc.identifier.uri https://aaltodoc.aalto.fi/handle/123456789/3528
dc.description.abstract Objectives of the Study The objective of the study was to create a new model for managing content during and after software development transition. The goal was to find out, how the new software development model differs from the old one and what new requirements it creates for content management, as well as study how the content was earlier managed and how the old model should be changed. Academic background and methodology Theory of the content management and especially requirements management and elicitation was studied through during the academic background. Additionally, productization and new product development process execution were examined, as well as different software development models and techniques, like traditional and agile models, and their differences. The study used action case as the research methodology, where a new content management model was created on the basis of theory and master code line software development model. The new content management model was implemented and necessary modifications were executed for better suitable. Moreover, the execution and experiences of the transition of the new software development model, and especially content management model, were gathered and studied. Findings and conclusions A new content management model was created and implement. We learnt that the transition can be very complex and time consuming, because the change affects all functionalities in the organization. The biggest challenge is the burden of old processes: already ongoing projects were very hard to change to follow the new model. However, we noticed that necessary training as well as open and sufficient communication was the key for engaging the organization for the transition. We also noticed that the change is actually continuous: the organization should learn from their experiences and should continuously try to improve their procedures. en
dc.format.extent 75
dc.language.iso en en
dc.title Content management in software development transition - Case Tellabs en
dc.type G2 Pro gradu, diplomityö fi
dc.contributor.school Kauppakorkeakoulu fi
dc.contributor.school School of Economics en
dc.contributor.department Department of Information and Service Economy en
dc.contributor.department Tieto- ja palvelutalouden laitos fi
dc.subject.keyword agile methodology
dc.subject.keyword content management
dc.subject.keyword master code line
dc.subject.keyword new product development
dc.subject.keyword product process
dc.subject.keyword requirements elicitation
dc.subject.keyword requirements management
dc.subject.keyword scrum
dc.subject.keyword software development model
dc.subject.keyword software development transition
dc.identifier.urn URN:NBN:fi:aalto-201205271730
dc.type.dcmitype text en
dc.programme.major Information Systems Science en
dc.programme.major Tietojärjestelmätiede fi
dc.type.ontasot Master's thesis en
dc.type.ontasot Pro gradu tutkielma fi
dc.subject.helecon tietojärjestelmät
dc.subject.helecon information systems
dc.subject.helecon ohjelmistot
dc.subject.helecon software
dc.subject.helecon kehitys
dc.subject.helecon development
dc.subject.helecon muutos
dc.subject.helecon change
dc.subject.helecon mallit
dc.subject.helecon models
dc.subject.helecon tuotekehitys
dc.subject.helecon product development
dc.subject.helecon uudet tuotteet
dc.subject.helecon new products
dc.ethesisid 12804
dc.date.dateaccepted 2012-05-11
dc.location P1 I


Files in this item

Files Size Format View

There are no files associated with this item.

This item appears in the following Collection(s)

Show simple item record

Search archive


Advanced Search

article-iconSubmit a publication

Browse

My Account