Why are software projects different

Kód výsledku v IS VaVaI

<a href="https://www.isvavai.cz/riv?ss=detail&h=RIV%2F68407700%3A21230%2F17%3A00315481" target="_blank" >RIV/68407700:21230/17:00315481 - isvavai.cz</a>

Výsledek na webu

<a href="http://icatse.org/icitcs2017/invited-speakers/" target="_blank" >http://icatse.org/icitcs2017/invited-speakers/</a>

DOI - Digital Object Identifier

—

Jazyk výsledku

angličtina

Název v původním jazyce

Why are software projects different

Popis výsledku v původním jazyce

Software engineering is the subject of software project development. Many techniques of general project management are applicable to software projects. Software projects are more often than other project unsuccessful. We consider the project as a successful if it is realized in time, in the required quality and in budget. On average, 50% of large SW projects last longer than estimated, three quarters of major projects have operating errors and one quarter of large projects is canceled. What are the software projects specific? Substantial influence on the management of software projects has 3P: 1. Peoples must be organizing into efficient teams. 2. Problem must be well-specified in the customer’s communication with the developer. 3. Processes must be tailored to People and the Problem, and a suitable model for project implementation must be chosen. Software development is specific to complexity and frequent changes. Specifics of software projects include: 1. Product invisibility – The product is intangible and progress in development is not immediately visible. It is easy to say that the software project is 90% complete even though there are no visible results. 2. Complexity of the problem – IT systems can project developmnetbe very simple, but they are often very complex. An IT project often turns out to be more complex than we expected. 3. Flexibility – The ease of changing software is usually considered to be one of its strengths, but the reality is different. 4. Uniqueness – We pool teams and technologies in a way that have not been done before. 5. Risks – Risk management is crucial for IT projects. 6. System Requirements Specifications – Very difficult and often impossible communication between the customer and the developer. 7. Technology is changing very quickly. In the lecture we will discuss these and other differences of software projects and possible improvement in IT projects development.

Název v anglickém jazyce

Why are software projects different

Popis výsledku anglicky

Software engineering is the subject of software project development. Many techniques of general project management are applicable to software projects. Software projects are more often than other project unsuccessful. We consider the project as a successful if it is realized in time, in the required quality and in budget. On average, 50% of large SW projects last longer than estimated, three quarters of major projects have operating errors and one quarter of large projects is canceled. What are the software projects specific? Substantial influence on the management of software projects has 3P: 1. Peoples must be organizing into efficient teams. 2. Problem must be well-specified in the customer’s communication with the developer. 3. Processes must be tailored to People and the Problem, and a suitable model for project implementation must be chosen. Software development is specific to complexity and frequent changes. Specifics of software projects include: 1. Product invisibility – The product is intangible and progress in development is not immediately visible. It is easy to say that the software project is 90% complete even though there are no visible results. 2. Complexity of the problem – IT systems can project developmnetbe very simple, but they are often very complex. An IT project often turns out to be more complex than we expected. 3. Flexibility – The ease of changing software is usually considered to be one of its strengths, but the reality is different. 4. Uniqueness – We pool teams and technologies in a way that have not been done before. 5. Risks – Risk management is crucial for IT projects. 6. System Requirements Specifications – Very difficult and often impossible communication between the customer and the developer. 7. Technology is changing very quickly. In the lecture we will discuss these and other differences of software projects and possible improvement in IT projects development.

Druh

D - Stať ve sborníku

CEP obor

—

OECD FORD obor

10201 - Computer sciences, information science, bioinformathics (hardware development to be 2.2, social aspect to be 5.8)

Projekt

—

Návaznosti

I - Institucionalni podpora na dlouhodoby koncepcni rozvoj vyzkumne organizace

Rok uplatnění

2017

Kód důvěrnosti údajů

S - Úplné a pravdivé údaje o projektu nepodléhají ochraně podle zvláštních právních předpisů

Název statě ve sborníku

It Convergence and Security

ISBN

978-981-10-6450-0

ISSN

1876-1100

e-ISSN

—

Počet stran výsledku

350

Strana od-do

1-350

Název nakladatele

Springer Nature Singapore Pte Ltd.

Místo vydání

—

Místo konání akce

Seoul

Datum konání akce

25. 9. 2017

Typ akce podle státní příslušnosti

WRD - Celosvětová akce

Kód UT WoS článku

—