TOPCIT Software | 02. Software Engineering

Summary

The video discusses the importance of software competitiveness, contrasting Apple and Samsung's 2012 financials to highlight Apple's advantage due to its software ecosystem. It emphasizes the growing role of software in business success, the challenges faced by software development teams, and the need for improved software quality and processes. The video explores various software development models, including waterfall, incremental, evolutionary, and spiral, and stresses the importance of adopting effective software engineering practices to meet the demands of an evolving market.

Takeaways

• 📊 Apple's financial performance in 2012 showed a significant lead over Samsung in terms of revenue and operating profit, highlighting the importance of software competitiveness in business success.
• 🌐 Apple's strategy of building a content ecosystem with various software applications contributed to its competitive advantage, overcoming the limitation of focusing only on hardware devices.
• 📈 The size and complexity of software are predicted to increase exponentially, necessitating improvements in software quality, including correctness and reliability.
• 🔍 The social and economic impact of software defects is often overlooked, and there is a need to reduce the damage caused by software faults and to improve IT convergence product competitiveness.
• 🏢 Challenges in the software industry include varying competency levels of new employees, low morale due to a hardware-centric environment, and knowledge leakage due to frequent staff turnover.
• 🛠️ Development issues such as ad hoc software development, lack of process improvement, and resistance to adopting new technologies due to perceived overhead are common in many organizations.
• 🛡️ Software configuration management (SCM) is crucial for managing source code, handling breaches, managing releases, and conducting check-ins and check-outs, but many companies lack proper training and awareness in this area.
• 📉 A local mid-sized company's evaluation revealed deficiencies in process, technology, and people aspects of SCM, indicating a need for policy development, improved tool features, and better workforce capabilities.
• 🤷‍♂️ Myths about software development, such as the belief that advanced tools are all that's needed or that adding more developers will make up for a delayed project, are prevalent among managers, customers, and developers.
• 🛑 The importance of software engineering is increasingly recognized, with a shift from a 'code first, fix later' approach to a more systematic and analytical process to ensure software quality and efficiency.
• 📚 The adoption of software process improvement models like CMMI or SPICE helps companies minimize development risks and identify opportunities for growth, emphasizing the need for continuous improvement in software processes.

Q & A

What was the main focus of the software engineering 2012 white paper by Napa?

The white paper focused on the competitiveness of software, highlighting the comparison between Apple and Samsung's financial performance and the importance of building software application-based content ecosystems.

How did Apple's financial performance compare to Samsung's in 2012?

In 2012, Apple, which focused on devices like the iPhone, had a revenue of $52 billion and an operating profit of $19 billion, which was ahead of Samsung's consolidated sales of $47 billion and operating profit of $5.2 billion.

Why was Apple's operating profit significantly higher than Samsung's despite Samsung's diverse product lineup?

Apple's higher operating profit was attributed to its focus on building various software application-based content ecosystems, overcoming the weakness of operating only on their platform with a range of services to customers.

What are the major challenges in software development that can impact social and economic costs?

Challenges include the need for improved software quality in terms of correctness and reliability, and the social and economic problems and costs caused by software defects, which are often overlooked.

What are some of the people-related development issues mentioned in the script?

Issues include varying competency levels of new employees, low morale of the software workforce due to a hardware-centric environment, and organizational knowledge leakage due to frequent staff turnover.

What are some common complaints from software developers regarding their work environment?

Developers often complain about the low position of software within the company, working style conflicts between generations, lack of career vision, and poor working environments with long working hours.

What are some of the development process issues that organizations face?

Organizations often develop software in an ad hoc manner or repeat development with rework, leading to insufficient introduction of new technology, lack of process improvement, and a general lack of understanding about the importance of process from managers.

What is the importance of software configuration management in a company?

Software configuration management is crucial for managing source code, handling breaches, managing releases, and performing check-ins and checkouts. It helps in establishing common rules and ensuring consistency in development practices.

What are some myths about software development that managers and customers often have?

Managers might think that developers have everything they need with advanced tools and standards, or that adding more developers can catch up a delayed project. Customers may believe that starting software development with just outlines is enough, and that changes to requirements are easy due to software's flexibility.

Why is the application of software engineering techniques important in addressing the complexity and challenges in software development?

Software engineering techniques provide systematic management and support for efficient work, addressing anticipated difficulties throughout the development process, from requirements analysis to maintenance, ensuring the successful development of increasingly complex software.

What are the three key success factors in software engineering mentioned in the script?

The three key success factors are the definition of systematic practices and workflows, organizing workforces with expertise, and balancing and harmonizing these factors to develop software in an engineering manner, which requires continuous improvement and investment.

Outlines

00:00

📈 Software Competitiveness and Market Performance

This paragraph discusses the significance of software competitiveness in the corporate world, using Apple and Samsung as case studies. It highlights how Apple, with a focus on a few devices like the iPhone, outperformed Samsung in terms of revenue and operating profit in 2012. The key to Apple's success is attributed to its robust software application-based ecosystems and services. The paragraph emphasizes the growing importance of software in business and the need for improved software quality to reduce social and economic damage caused by defects. It concludes by stressing the importance of securing global software quality competitiveness, especially for local enterprises competing in a small domestic market.

05:01

🛠️ Software Development Challenges and People Issues

The second paragraph delves into the challenges faced in software development, focusing on people-related issues. It outlines problems such as varying competency levels of new employees, low morale due to a hardware-centric environment, and knowledge leakage from frequent staff turnover. Additionally, it touches on the dissatisfaction among developers regarding the company's low regard for software, conflicts between generations, and poor working conditions. The paragraph also addresses development issues like ad hoc software development, lack of process improvement, and resistance to change due to a belief in the adequacy of current practices. It concludes with a discussion on the importance of configuration management and the need for better training and awareness.

10:02

🚀 The Evolution of Software Engineering Practices

This paragraph traces the history and evolution of software engineering, starting from the 1950s when it was adopted similar to hardware engineering. It discusses the software crisis of the 1960s due to a surge in demand and lack of experience, leading to the formal introduction of software engineering in the 1970s. The narrative continues with the shift from coding first and fixing later to more structured techniques like the waterfall model. The paragraph also covers the emergence of agile methodologies in the 2000s to address rapid market changes, emphasizing the importance of software engineering in defining and analyzing requirements for effective development.

15:04

📊 Assessing Software Engineering Capabilities in Korea

The fourth paragraph presents an assessment of software engineering capabilities in Korea based on 2012 data from Napa, which surveyed 220 companies and 255 projects. It reveals that local software engineering capabilities are underdeveloped, with low scores in workforce, technology, and overall software engineering, despite some improvement in processes. The paragraph underscores the need for continuous improvement in software process and adoption of models like CMMI or SPICE to minimize development risks and increase organizational maturity.

20:05

🔄 Software Life Cycle Models and Their Characteristics

This paragraph explores various software life cycle models, starting with the waterfall and V models, which are simple and sequential but require clearly defined requirements upfront. It then discusses the incremental model, suitable for environments where requirements may change over time, allowing for feature expansion through iterations. The evolutionary model is highlighted as similar to agile methodologies, focusing on continuous improvement and adaptation to changes. Lastly, the spiral model is introduced as a way to manage technological risks through prototyping and iterative development.

25:06

🌐 The Spiral Model and Managing Technological Risks

The final paragraph focuses on the spiral model, which is designed to reduce technological risks by developing multiple prototypes. This model evaluates the feasibility of technology at each stage and makes decisions on whether to proceed, cancel, or change project requirements. It emphasizes minimizing commitment in each phase to address technical uncertainties and adapt to changes, making it suitable for projects with stable system requirements and a need for detailed technical risk analysis.

Keywords

💡Software Engineering

Software Engineering is a systematic approach to the development, operation, and maintenance of software. It is the application of engineering principles to software, which includes processes, methods, and tools to ensure the production of high-quality software. In the video's context, it is emphasized as a key to address the challenges faced by companies in the competitive tech industry, as it helps in building robust software ecosystems and improving the competitiveness of IT convergence products.

💡Competitiveness

Competitiveness refers to the ability of a company to compete effectively in the market. It is often associated with factors such as innovation, quality, and efficiency. In the script, the competitiveness of software is highlighted through the comparison of Apple and Samsung's financial performance, showing how software plays a significant role in a company's market position.

💡Operating Profit

Operating profit, also known as operating income or EBIT, is the profit from a company's core business operations, excluding any income from non-operational activities such as investments or interest. The script mentions Apple's operating profit to illustrate the financial success achieved through their focus on software and hardware integration.

💡Ecosystems

In the context of the video, ecosystems refer to a set of interconnected components or services that work together to deliver value. Apple's strategy of building application-based content ecosystems is mentioned to show how they overcome platform limitations and provide various services to customers, enhancing their market presence.

💡Software Quality

Software quality encompasses the performance, reliability, and overall effectiveness of software. The script discusses the importance of improving software quality to reduce social and economic damage caused by software defects, emphasizing the need for correctness and reliability in software development.

💡Configuration Management

Configuration management is the process of tracking and controlling changes in software during its development life cycle. The script points out the lack of proper configuration management policies and practices in a local company as a key issue, which can lead to inconsistent execution and poor integration of tools and best practices.

💡Agile Methodologies

Agile methodologies are a group of project management and product development approaches that emphasize flexibility, collaboration, and customer feedback. The script mentions the introduction of agile methodologies in the 2000s as a response to the rapidly changing market environment, allowing companies to effectively respond to changes and increase productivity.

💡Software Process Improvement

Software process improvement refers to the ongoing efforts to enhance the processes used in software development to increase efficiency, reduce errors, and improve product quality. The video discusses the adoption of various models like CMMI or SPICE to facilitate continuous improvement in software processes.

💡Waterfall Model

The Waterfall Model is a traditional software development approach where progress is seen as flowing steadily downwards (like a waterfall) through phases in a strict sequence: requirements, design, implementation, testing, deployment, and maintenance. The script contrasts this model with Agile methodologies, highlighting its limitations in a fast-paced, changing environment.

💡Incremental Model

The Incremental Model is a software development approach where the software is built and delivered in increments, allowing for early delivery of core features and subsequent additions. The script describes this model as useful for reducing system development time and accommodating changes or improvements over time.

💡Evolutionary Model

The Evolutionary Model is a software development approach that involves iterative development of the entire system, with each iteration providing the user with all features. The script describes this model as similar to Agile methodologies, allowing for continuous product improvement and reflection of changes and feedback into the system.

💡Spiral Model

The Spiral Model is a risk-driven software development model that emphasizes iterative development through a series of prototypes. The script mentions this model as a way to reduce technological risks by evaluating and proving the feasibility of technology at each phase, making decisions based on the outcomes.

Highlights

Apple's revenue and operating profit significantly outperformed Samsung's in 2012, highlighting the impact of software competitiveness.

Apple's success is attributed to its ecosystem of software applications, overcoming the limitation of operating on a single platform.

The importance of software's role in the market is growing, with its size and complexity expected to increase exponentially.

There is a recognized need for improved software quality, including correctness and reliability, to address social and economic issues caused by defects.

Local software enterprises face challenges competing in a small domestic market against global corporations.

New software employees have varying competency levels, impacting the development process.

Low morale among the software workforce is attributed to a hardware-centric environment.

Organizational knowledge loss due to frequent staff turnover is a significant issue in software development.

Software developers face challenges such as low recognition within companies and inter-generational working style conflicts.

Most organizations develop software in an ad hoc manner with insufficient introduction of new technologies.

Managers often lack understanding of the importance of process improvement in software development.

Software engineering techniques and methods are underutilized in practice, with insufficient use of case tools and global standards.

Leading companies periodically evaluate their software development maturity and prioritize improvement activities.

Software configuration management is crucial for managing source code, handling breaches, and controlling releases.

Common myths among managers, customers, and developers about software development are debunked.

The application of software engineering is emphasized for successfully developing increasingly complex software.

Three key success factors in software engineering are defined: systematic practices, skilled workforce organization, and process integration.

Software engineering should be a continuous effort, supported by top management for desired results.

The history of software engineering is traced back to the 1950s, with the waterfall model developed to address the software crisis in the 1970s.

Agile methodologies emerged in the 2000s to respond to rapid market changes, emphasizing concurrent engineering.

Software development capabilities are key to a company's success in the digital age, with 69% of companies leveraging it for competitive advantage.

Statistics from Napa in 2012 show that local software engineering capabilities in Korea are still poor, with low scores in workforce and technology.

Software process improvement and adoption are emphasized for effective software development with minimal investment.

Various software process improvement models like CMMI or SPICE are adopted to minimize development risk and increase organizational maturity.

The software life cycle is crucial as it dictates the direction of a software project, with different models like waterfall, V model, incremental, evolutionary, and spiral having distinct characteristics and applications.

The evolutionary model is particularly suitable for environments with continuous demands for product improvement and unclear system specifications.

The spiral model is used to reduce technological risks by developing multiple prototypes and evaluating feasibility at each phase.

Transcripts

[Music]

[Music]

[Applause]

[Music]

[Music]

ah

let's take a look at the software

challenges in your company if you you

see a software engineering 2012 white

paper issued by Napa we can see the

importance of the competitiveness of the

software through comparison of Apple and

Samsung Apple has achieved a $52 billion

Revenue operating profit of 19 billion

from fiscal year 2012 quarter 1

performance Samsung Electronics in

fourth quarter announced Consolidated

sales of $47 billion operating profit of

5.2 bill milon Dollar in

2012 it can be seen that Apple which is

only focusing in it devices such as the

iPhone was ahead of Samsung sales with a

full lineup in the semiconductor LCD

mobile phones home

appliances in particular we can see

apple is much ahead even in the

operating profit four times higher than

Samsung so you can see that apple is

ahead of Samsung both in terms of grow

sales and substance

what major causes to make such a

difference the answer is that Apple has

been building various software

application-based content

ecosystems Apple overcomes their

weakness which they operate only in

their platform with various services to

customers as we see the data we can

realize that how important software

competitiveness of Enterprises are in

recent

days recently software significantly

takes important role and increase their

size and predict that in the future the

size and complexity of software

increases

exponentially as the dependency to

software get increased in parallel there

are needs that software quality should

be improved such as correctness and

reliability but we actually Overlook for

the Social and economic problems and

costs caused by quality problems such as

software

defects therefore it's now time to

reduce the social and economic damage

caused by the fault of the software and

prepare a plan or approach to improve

the competitiveness of the it

convergence products in particular we

have the situation where it is required

to put more our interests and efforts to

secure Global software quality

competitiveness given the reality of

local software Enterprises in the small

domestic Market struggling to compete

with global

corporations

let's continue the people processes

Technologies aspects of issues related

to software

development the development issues

related to people is firstly new

employees have different competency

levels from the past secondly morale of

software Workforce is low due to

Hardware Centric environment and thirdly

organizational knowledge is leaked due

to frequent staff

turnover and also other problems which

is is the common concern of software

developers are included in development

issues they are complaining about the

low position of software in company and

the working style conflict between

senior and juniors due to different

generation concerning on lack of career

vision for example we have no vision and

raise a problem in poor work

environments that require work until

9:00 p.m. at 900

a.m. take a look at the following issues

in the development process point of view

most organizations have developed

software with ad hoc manner or repeat

development with

rework therefore the effect on the

introduction of new technology is

generally

insufficient an organization that

generates a lot of benefits does not

really care about the process

Improvement because they think they are

the best and there is no reason to do

additional work to get better in the

case of managers a lack of under

understanding about the importance of

process because they think the most

important is sales and revenue for

developers they have a sense that the

process makes additional overhead so

that they have a lack of the motivation

to participate in the process

Improvement finally having the issues of

the technology aspect there are problems

in that to apply software engineering

techniques and methods in practice also

using case tools applying global

standard s and a systematic reuse

practices is

insufficient leading companies recognize

that software development is very

important these companies evaluate their

software development maturity

periodically and looking for improvement

opportunities and prioritize Improvement

activities and Carry Out execution plans

to

move this is the summary data related to

software configuration management which

carried out in a local midsized company

in the past when evaluating any

company's capabilities it usually

diagnoses three

perspectives the first is process the

second technology and the third is

person for each of the three

aspects regarding process issues found

we saw this company had a lack of

configuration management policies and

process definition and there was

inconsistent execution in their real

practices regarding technology issues

tools and best practices for

configuration management were not well

integrated for people issues there were

a lack of knowledge and competency

development for developers these

problems are not just limited to this

company process is not defined process

was poor even if there was a defined

process tools are in place but we can

frequent quently see developer skills

understanding and deployment are

generally

poor look at the developer side

importance of configuration management

how should configuration management does

how to manage the source code how to

manage breaches how to manage releases

and how to do check-in and checkout are

not well

established these should be done with

General common rules but as there are

insufficient training or awareness they

are not well integrated and each

separately so companies are looking to

find the problems and derive the

implications of the problem for example

this company needed policy and process

Concepts and definition and improve CM

support tool features and performance

Improvement to be able to operate in

automaking workflow based CM

processes from people aspect there

should be a need to set up the CM

dedicated team to Foster the developer

configuration man management

capabilities and knowledge to maintain

CM

systems this company found the

implications and prioritize based on

impacts and importance developed the

action plans and finally executed an

action plan to improve the configuration

management

process now shall we look at some things

that are related to myths that manager

and customers and software developers

have managers think developers have

everything they need to develop software

if they have advanced case tools

standards and

procedures and they think developers

don't need standards and tools because

developers work hard and put their best

when project behind schedule they think

they can catch up to the schedule if

they add more developers to the project

they think good managers can also manage

the project well as the software is not

visible they think it should be enough

to check the start and end

for customers they think that it's

enough to start software development

once we get the outlines it's okay that

the detail can be developed later they

have myths that changes to requirements

and are easy as software itself is

flexible and developers make decisions

themselves than execute

project for developers they have myths

that their job is complete the program

and developed and run they think that

there is no way to assess the quality

until a program is run working programs

are only project deliverables and case

tool solves their

[Music]

problem now what would be the answers to

address these problems complexity and

our challenges we are seeking to find

the answers from software engineering to

successfully develop the software which

is increasing the sizes and functional

alities the application of software

engineering is more important than

others as systemic management software

engineering techniques to provide a

technique techniques that support the

efficient work performed address

anticipated difficulties throughout the

process up to the maintenance from the

requirements

analysis the companies realize and need

the importance of software

engineering in the past from the way of

coding first and fixing later now the

companies get more recognition on that

it is important to Define and analyze

requirements in order to effectively

apply software engineering techniques

three key success factors which are the

definition of systematic practices and

workflows that integrate into processes

organizing the workforces with expertise

and infrastructure to operate to find

workflows and workforces efficiently

should be balanced and harmonized then

we can develop software that we want in

engineering manner also these three

factors are required to be steadily

improved and invested with many efforts

During the period in which the company

operates software engineering is not a

onetime event but should proceed as

planned and continuous efforts through

strong commitment and sponsorship of top

management then you can finally achieve

the desired

results this this is how the birth of

software engineering and explain what is

currently the hottest and trendy look at

the history of software engineering

1950s software engineering Concepts was

adopted to software development projects

which was similar to Hardware

engineering as the demand for software

surged in the 1960s it caused a software

crisis due to the lack of experience and

ability numerical shortage of manpower

to implement it so then software

engineering earnestly got

introduced starting in the 1970s as high

demand for software occurred it become

lack of

Manpower there were a situation where

put a large number of non- Majors to

resolve the problem these people

typically coded first then fixed the

problems later leveraging the

characteristics of software which can be

easily modified when they developed the

software this approach would make

company realize that the Gap exist in

reality a fast changing World

requirements were becoming increasingly

apparent and development teams defined

their own requirements themselves as

coding first and fixing later approach

made many defects found and they caused

the side effects structured or formal

techniques had

revealed thus the waterfall model was

developed to proceed in order with the

analysis design implementation and so on

but formal techniques had difficulties

in use for the general software

developers the waterfall model required

requirements to be clearly defined at

front and start the analysis development

testing which such defined requirement

but in reality there were a lot of

changes in the middle of development

occurred because the development

typically started with undefined

requirements these impacted the progress

slowed down due to high rework and cost

overrun so in 1980s where try to address

these problems there were many

researches on finding ways to increase

software productivity to develop

software effectively to increase the

reusability in 1990 it happened to be a

need to shorten the time to Market of

products for a competitive advantage in

the market this impacted more research

on software development productivity

used the model that focused on

concurrent engineering to conduct a

requirements design and implementation

at the same time in waterfall

model in 2000s which began to rapidly

changing Market environment surrounding

the software agile methodologies have

been introduced in order to effectively

respond to these rapid changes and you

can see many modern companies have been

adopting and institutionalizing these

agile

methods software development

capabilities is recognized as the key

success of companies in the digital age

the companies which understand and

prepare the major technology Trends get

tangible benefits to bridge the

execution Gap in fact 69% of companies

that leverage software development to

reap the competitive Advantage is better

performance than any other company in

terms of

profitability therefore companies should

increase software development

capabilities in order to enhance the

competitiveness of products and services

however as software development gets

more difficulties due to software

increases in size software features

Diversified and changes to software

operating environment such as user

interface software engineering is

required and at the same time the need

for efforts to increase the execution

and quality is also

necessary let's summarize the software

statistics in Korea via the 2012 data of

Napa this Statistics was made by Napa

based on results of targeted 255

projects of total 220 companies in

conclusion we look to see local software

engineering capabilities are still very

poor if you look at this chart it shows

69 point for process 57 points for

Workforce 59 points for technology and

62 points for overall score out of 100

points in software

engineering in this case we can see all

aspect except for process are very poor

which points to the lowest

grade looking at the data compared to

2010 to understand how much get improved

we can see process aspect is somewhat

improved but the quality technology and

Workforce are very little relatively

improved what common phenomenon appears

in Korea software engineering capability

scores between 2009 and

2011 the processes are usually defined

as internal policies in many companies

but we can see that they have relatively

insufficient quality workforces to

efficiently operate and manage processes

and their technology aspect is

considerably very

[Music]

poor recently many companies strive to

adopt and improve effective processes

for software development in order to

improve software quality and keep it

consistent the reason to emphasize on

software process Improvement and

adoption in the companies is that it can

perform effectively in software

development with less investment and can

independently proceed with people and

Technology even if outstanding people or

technology exists it is difficult to

maximize these capabilities without

appropriate processes or

understanding software process is

consisted of a series of steps carried

out activities tasks and deliverables as

seen on the

screen this will ensure that there is

visibility as roles and responsibilities

are clearly defined in addition this

makes easy to plan and track the project

and reduce unnecessary work the starting

point for process Improvement to enable

continuous process Improvement in your

company to enable them to continuously

improve their software process in the

company they're adopting a various

software process Improvement models such

as cmmi or spice which helps minimize

the development risk and identify

Improvement opportunities that help a

company to increase maturity of

organizational

development let's see the

characteristics in the software life

cycle as said in the beginning the

software life cycle serves as the

backbone in the software project

compared to the human since it takes the

backbone role depending on which model

is selected the software project tracks

right direction or in Failure we should

consider it take a very important role

to dictate

it in the waterfall model or V model

there are a typical model of the most

most widely used in the field the reason

is that it is typically the easiest as

analysis design implementation and

testing phase progress sequentially

project managers or developers stand to

think of something simple and not

complicated progress in a series of

activities so waterfall or V model

clearly shows that what process should

be performed by project manager or

developer and is fairly easy to

understand customers who does not know

software development well but when you

see the shortcomings this is a model

that can be applied in the most ideal

when user system software requirements

are clearly identified in advanced

details but in reality it is almost

impossible therefore agile is recently

one of the hottest Trends as it is more

appropriate than waterfall because we

can see that agile is most suitable to

recent changing development

environment in addition the waterfall

model is a model that emphasizes the

verification validation and testing so

according to the characteristics of our

development environment as we always

emphasize the testing processes on the

other hand the company considers the

waterfall or V model is the most

suitable let's look at the incremental

model in case of the incremental model

it is a useful model when there is a

need to reduce the system development

time after core features are developed

and operated first the rest of the

features are implemented and

added this results in the system

development via the function expansion

through several

iterations therefore firstly let the

base system version operate with limited

features and then complete the future

system version with add-on features on

top of Base features of previous

versions

so requirements are already determined

but this is the most useful model in the

case that there are possibility of

changes or Improvement for defined

requirements over

time now let's look at the evolutionary

model The evolutionary model is a useful

model when there is a need to reduce the

system development time unlike the

incremental model we discussed it is the

model to repeat several times to develop

the entire systems it's also a model

that each system provides the user with

all the features

finally so a system was developed and

operated and changes are derived these

changes are inputs and feedbacks to

develop the next system so this model is

fairly similar model to Agile and

interactive development which is one of

Agile development

methodologies because it has similar

properties current many companies are

are using the evolutionary model

aot it is a model that changes including

changes to the functions and changes to

the user interface and changes to

nonfunctional requirements such as

reliability and performance Improvement

are implemented and reflected to the

system as it

evolves in case where system

specification is unclear as a whole it

is also the most appropriate model where

there are continuous demands for product

Improvement

there are many cases where mix of

incremental and evolutionary models are

both adopted in the

field by closing look at the field

several models in hybrid forms are

applied not just only one model The

evolutionary model has the

characteristics where software

development progresses by adding new

features and improving existing features

at the same time for new system version

therefore such model has the following

characteristics for The evolutionary

model even if the system does not have

the full functionality early training

for the system can be delivered it can

also provide initial training for system

users also allow users to become

familiar with the system elicit

necessary changes and reflect those

feedbacks into future

Evolution so due to the shortening of

the development cycle can be more

competitive as the early use of the

system

because the system is developing several

times it is a good model that can

address the issues problems and risks

early also it can be developed by

splitting it with professional

breakdown for example this model can be

used that if the project transforms the

text-based user interface into Graphics

based a user interface development team

first develops certain Improvement on

user interface and the other development

teams then to proceed and improve

improve the next

pieces lastly let's talk about a spiral

model while previous models are to

reduce managerial risks spiral model is

to develop many prototypes to reduce the

number of technological

risks with this prototype this model

evaluates the technology is really

reasonable can prove the feasibility or

if not then decide whether it should be

disposed or develop another prototype

it would make a decision on whether we

changes to project requirements cancel

or proceed after each of the prototypes

has been

developed it is also the model that

minimizes the commitment in each phase

to find a solution of the technical

risks the spiral model is adequate when

there are a dependency on stable system

requirements and detail analysis of

technical

risks

[Music]

[Music]

[Music]

[Music]

[Music]