Software Engineering - Lecture 1

developed or engineered

Software is _________, it is not manufactured in the classical sense.

wear out

Software doesn't _______

custom-built

Although the industry is moving toward component-based construction, most software continues to be ______

adapted

Software must be _____ to meet the needs of new computing environments or technology.

enhanced

Software must be _________ to implement new business requirements.

extended

Software must be _______ to make it interoperable with other more modern systems or databases.

re-architected

Software must be ______ to make it viable within a network environment.

design

________ becomes a pivotal activity in software engineering

high quality

software should exhibit _____

maintainable

software should be ________

The seminal definition

Software engineering is the establishment and use of sound engineering principles in order to obtain economically software that is reliable and works efficiently on real machines.

The IEEE definition

The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software that is, the application of engineering to software.

tools
methods
process models
a quality focus

A layered technology

professional software engineering

developing complex software in a professional environment

objective of professional software engineering

On-time delivery of high-quality software that satisfies customers

role assignment

shares the critical responsibilities among team members

Roles

________ can be used to leverage capabilities, create experts in each area

Work allocation

___ need not be totally tied to roles

responsibility of project manager

Plans and oversees software development projects

responsibility of project manager

Manages budget, scope, and timelines

responsibility of project manager

Coordinates between stakeholders and team members

key skill of project manager

Leadership, communication, risk management

goal of project manager

Deliver the project on time, within scope and budget

responsibility of system analyst

Gathers and analyses user requirements

responsibility of system analyst

Translates business needs into technical specifications

responsibility of system analyst

Bridges the gap between business and development teams

key skill of project manager

Analytical thinking, problem-solving, documentation

goal of project manager

Ensure the system meets business goals and user expectations

responsibility of developer

Write, test, and maintain code

responsibility of developer

Implement features based on design and requirements

responsibility of developer

Collaborate with other team members for code integration

key skill of developer

Programming, debugging, version control (e.g., Git)

goal of developer

Build efficient and functional software

responsibility of tester

Design and execute test plans

responsibility of tester

Identify bugs and ensure software quality

responsibility of tester

Work closely with developers to resolve issues

key skill of tester

Attention to detail, knowledge of testing tools, analytical thinking

goal of tester

Deliver a bug-free, reliable product

Polya suggests:

1. Understand the problem (communication and analysis)
2. Plan a solution (modeling and software design)
3. Carry out the plan (code generation)
4. Examine the result for accuracy (testing and quality assurance)

Essence of practice