My lesson

Programming

one activity in software engineering

Software

a computer program and it's documentation

Software testing

Execute the software using simulated test data

Activities in software engineering

Specification of requirements, Validation and Testing, Implementation or development

Diverse software engineering techniques

Waterfall model, Incremental model

Software process models

Rational Unified Process, V-model, Incremental, Spiral, Waterfall

Prototyping model

Not concerned with quality, ensures requirements are correct before using another process model

Waterfall model

Large systems, plan-based, difficult to change requirements

System to control antilock braking in a car

V-Model is best

Agile

working software is more valuable that comprehensive documentation

Agile requirements list

stored in the Product Backlog

Use case inherit from use case?

yes

Use case Association

represent an actor and a use case have interaction/communication

Actor inherit from another actor?

yes

Activity diagram rounded rectangles

Actions

Activity diagram diamonds

Decisions

Use state diagram when

when a use case requires a list of different states of a system at a given time

Class diagram: solid line with empty white diamond at one end

Aggregation

Class diagram: solid line with empty white triangle at one end

Inheritance

Generalization

Two classes pointing at one third class with empty solid line white triangle

UML Use case diagrams are used to capture

Functional requirements

Software specification/requirement engineering

understanding and defining what services or functionalities are required and identifying the constraints on the system operation

Software design

the description of the structure of the software to be implemented. Responsible for the code level design, what each class is doing, its relationships, and scope

Incremental model

Earlier delivery and deployment, easy customer feedback

Agile method advantages

team communication, requirements do not hold up progress, facilitates customer feedback, visibility of everything

Use cases capture requirements?

yes

Abstraction

reducing by focusing on the essential observable behavior

Encapsulation

hiding the details of the implementation

Polymorphism

a single name may denote objects of many different classes that are related by some common superclass

Pseudocode

"text-based" representation of an algorithm

Software Architecture

responsible for the skeleton and the high-level organization of a software. Identifies the main structural modules/components in a system their relationships

Software testing goals

show that the program does as intended, discover program defects

Unit testing

testing method by which individual units of source code (which have associated control data, usage procedures, and operating procedures) are tested to determine whether they are fit for use