Software Engineering PowerPoint.ppt

7/27/2019 Software Engineering PowerPoint.ppt

1/16

Software Engineering


2/16

Why Software Engineering?

As technology advanced, so did the need to build biggerand ever more complex programs. Softwaredevelopmentreached a point where it had to bedeveloped by teams.

There had to be:- requirements, plans, detailed designs, actual building,

testing, development of efficient, intuitive user interfaces,and integration into larger systems of computers,machines, and people.

The discipline to develop software in this manner isknown as software engineering, a complex process thatitself requires many sub-processes.


3/16

What is Software Engineering?

The application of a systematic,

disciplined, quantifiable approach

to the development, operation, andmaintenance of software; that is,

the application of engineering to

software.


4/16


Software engineering is also defined as the

field of computer science that deals with

the building of software systems which are

so large or so complex that they are built

by a team or teams of engineers.


5/16


Usually these software systems exist in

multiple versions and are used for many

years.

During their life-time, they undergo many

changesto fix defects, to enhance

existing features, to add new features, to

remove old features or to be adapted torun in the new environment.


6/16

Why a structured approach to the

software development process?

Increased dependence of many organizationson their computer systems

Crises in previous developments; for example:* increasing costs of softwaredevelopment

* dissatisfaction of users and management

with the quality and suitability of software* increasing length and complexity of thesoftware.


7/16

Why a structured approach to the

software development process?

Requirements for standard interfaces, both to

users and other software.

Need for tighter control and management ofprocess (visibility of the process, risk

management)

Importance of the need for the involvement of

end users and management.


8/16

Attributes of a well-engineered

software product

The attributesof a software product are thecharacteristics displayed by the product, once itis installed and put in use.

They are notthe services provided by theproduct.

Rather, they are concerned with the productsdynamic behavior and the use made of theproduct.


9/16


software product

maintainability

dependability

efficiency usability

portability

availability of appropriatedocumentation

f


10/16


maintainability

It should be possible to evolve software to

meet the changing needs of the customer.

A ib f ll i d


11/16


dependability

Software dependability includes a range of

characteristics including reliability, security

and safety. Dependable software should

not cause physical or economic damage inthe event of system failure.


12/16


efficiency

Software should not make wasteful use of

system resources such as memory and

processor cycle.


13/16


usability

Software should have an appropriate user

interface and documentation


14/16


portability

This refers to the ability to reuse the existing code

instead of creating new code when moving

software from one environment to another.

Software portability may be achieved on threedifferent levels:

Installed program files may be transferred to another computer.

The program may be reinstalled (from the distribution files) on

another computer.

The source filesmay be compiledfor another computer.
http://en.wikipedia.org/wiki/Source_filehttp://en.wikipedia.org/wiki/Compilehttp://en.wikipedia.org/wiki/Compilehttp://en.wikipedia.org/wiki/Source_file


15/16


availability of appropriate documentation

Computer Software that is accompanied with

written text on software documentationor

source code documentation. It either explainshow it operates or how to use it .

Types of documentation include: Requirements- Statements that identify attributes, capabilities,

characteristics, or qualities of a system. This is the

foundation for what shall be or has been implemented. Architecture/Design- Overview of software. Includes relations to an

environment and construction principles to be

used in design of software components.

Technical - Documentation of code, algorithms, interfaces, and APIs.

End User- Manuals for the end-user, system administrators and support staff.

Marketing- How to market the product and analysis of the market demand.


16/16


availability of appropriate documentation

Types of documentation include: Requirements- Statements that identify attributes, capabilities,

characteristics, or qualities of a system. This is the

foundation for what shall be or has been implemented.

Technical - Documentation of code, algorithms, interfaces, and APIs.

API Applications Programming Interface

End User- Manuals for the end-user, system administrators and

support staff.

Marketing- How to market the product and analysis of the market

demand.

Software Engineering PowerPoint.ppt

Documents

Transcript of Software Engineering PowerPoint.ppt