Hyppää sisältöön
    • Suomeksi
    • På svenska
    • In English
  • Suomi
  • Svenska
  • English
  • Kirjaudu
Hakuohjeet
JavaScript is disabled for your browser. Some features of this site may not work without it.
Näytä viite 
  •   Ammattikorkeakoulut
  • Metropolia Ammattikorkeakoulu
  • Opinnäytetyöt
  • Näytä viite
  •   Ammattikorkeakoulut
  • Metropolia Ammattikorkeakoulu
  • Opinnäytetyöt
  • Näytä viite

Software Development Process in Small Enterprises : An insight into distributed development

Thapa Magar, Purushottam (2013)

 
Avaa tiedosto
Thapa_Magar_Purushottam.pdf (1.534Mt)
Lataukset: 


Thapa Magar, Purushottam
Metropolia Ammattikorkeakoulu
2013
All rights reserved
Näytä kaikki kuvailutiedot
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2013100215775
Tiivistelmä
The aim of this study is to analyse the overall work flow and processes that takes place in small enterprises during software development and give an insight into the distributed approach in software development.

There are thousands of small sized software companies all around the world. Naturally, small firms possess fewer resources and manpower than bigger companies like Microsoft and Oracle. However, the contributions made by these firms to the software industry are outstanding.

The world has turned into a global village. Information Technology is the father of this remarkable achievement of mankind. Hence, it is obvious that this field benefits the most from it. One of the advantages is that the software development can be distributed in various geographical locations, which is a huge leap from the traditional development methods. The possibility of distribution of development team has given a birth to a new kind of era, which is known as software outsourcing. Outsourcing is a very effective method to employ for rapid and creative development. In fact, it provides huge financial savings to businesses. Nevertheless, outsourcing also creates problems, which are irrelevant in centralized development. Those probable problems should be considered beforehand or it will jeopardize the entire project.
Kokoelmat
  • Opinnäytetyöt
Ammattikorkeakoulujen opinnäytetyöt ja julkaisut
Yhteydenotto | Tietoa käyttöoikeuksista | Tietosuojailmoitus | Saavutettavuusseloste
 

Selaa kokoelmaa

NimekkeetTekijätJulkaisuajatKoulutusalatAsiasanatUusimmatKokoelmat

Henkilökunnalle

Ammattikorkeakoulujen opinnäytetyöt ja julkaisut
Yhteydenotto | Tietoa käyttöoikeuksista | Tietosuojailmoitus | Saavutettavuusseloste