Pengantar Rekayasa Perangkat Lunak

Definisi Software (2)

Jenis Produk Software (1)
Karakteristik Software

Failure Curve for Hardware

Idealized and actual failure curves for software
Quality or Atribut Esensi Non-
Functional Software
Atribut Deskripsi
Maintainability Software should be written in such a way so that it can evolve to meet the
changing needs of customers. This is a critical attribute because software change is
an inevitable requirement of a changing business environment.
Dependability and Software dependability includes a range of characteristics including reliability,
security security, and safety. Dependable software should not cause physical or economic
damage in the event of system failure. Malicious users should not be able to access
or damage the system.
Efficiency Software should not make wasteful use of system resources such as memory and
processor cycles. Efficiency therefore includes responsiveness, processing time,
memory utilization, etc.
Acceptability Software must be acceptable to the type of users for which it is designed. This
means that it must be understandable, usable, and compatible with other systems
that they use.
Definisi Software Engineering
Pentingnya Software Engineering
Software Process
Mitos Pada Pengembangan Software
 Mitos
We already have a book that's full of standards
and procedures for building software, won't that
provide my people with everything they need to
know?
If we get behind schedule, we can add more
programmers and catch up (sometimes called the
Mongolian horde concept).
If I decide to outsource the software project to a
third party, I can just relax and let that firm build
it.
Realita
The book of standards may very well exist, but is it used? Are software
practitioners aware of its existence? Does it reflect modern software
engineering practice? Is it complete? Is it streamlined to improve time
to delivery while still maintaining a focus on quality? In many cases, the
answer to all of these questions is "no."
Software development is not a mechanistic process like
manufacturing. In the words of Brooks [BRO75]: "adding people to a
late software project makes it later." At first, this statement may seem
counterintuitive. However, as new people are added, people who were
working must spend time educating the newcomers, thereby reducing
the amount of time spent on productive development effort. People
can be added but only in a planned and well-coordinated manner.
If an organization does not understand how to manage and control
software projects internally, it will invariably struggle when it
outsources software projects.
 Mitos
A general statement of
objectives is sufficient to
begin writing programs
we can fill in the details
later.
Software requirements
continually change, but
change can be easily
accommodated because
software is flexible.
Realita
Although a comprehensive and stable statement of requirements
is not always possible, an ambiguous statement of objectives is a
recipe for disaster. Unambiguous requirements (usually derived
iteratively) are developed only through effective and continuous
communication between customer and developer.
It is true that software requirements change, but the impact of
change varies with the time at which it is introduced. When
requirements changes are requested early (before design or code
has been started), the cost impacts is relatively small. However, as
time passes, the cost impacts rapidly- resources have been
committed, a design framework has been established, and change
can cause upheaval that requires additional resources and major
design modification.
 Mitos
Once we write the program and get it to
work, our job is done.
Until I get the program "running" I have no
way of assessing its quality.
The only deliverable work product for a
successful project is the working program.
Software engineering will make us create
voluminous and unnecessary
documentation and will invariably slow us
down.
Realita
Someone once said that "the sooner you begin 'writing code', the longer
it'll take you to get done." Industry data indicate that between 60 and 80
percent of all effort expended on software will be expended after it is
delivered to the customer for the first time.
One of the most effective software quality assurance mechanisms can be
applied from the inception of a projectthe technical review. Software
reviews are a "quality filter" that have been found to be more effective
than testing for finding certain classes of software defects.
A working program is only one part of a software configuration that
includes many elements. A variety of work product (e.g., models,
documents, plans) provides a foundation for successful engineering and,
more important, guidance for software support.
Software engineering is not about creating documents. It is about creating
quality product. Better quality leads to reduced rework. And reduced
rework results in faster delivery times.