My lesson

 0    33 tarjetas    lid7
descargar mp3 imprimir jugar test de práctica
 
término definición
Programming
empezar lección
one activity in software engineering
Software
empezar lección
a computer program and it's documentation
Software testing
empezar lección
Execute the software using simulated test data
Activities in software engineering
empezar lección
Specification of requirements, Validation and Testing, Implementation or development
Diverse software engineering techniques
empezar lección
Waterfall model, Incremental model
Software process models
empezar lección
Rational Unified Process, V-model, Incremental, Spiral, Waterfall
Prototyping model
empezar lección
Not concerned with quality, ensures requirements are correct before using another process model
Waterfall model
empezar lección
Large systems, plan-based, difficult to change requirements
System to control antilock braking in a car
empezar lección
V-Model is best
Agile
empezar lección
working software is more valuable that comprehensive documentation
Agile requirements list
empezar lección
stored in the Product Backlog
Use case inherit from use case?
empezar lección
yes
Use case Association
empezar lección
represent an actor and a use case have interaction/communication
Actor inherit from another actor?
empezar lección
yes
Activity diagram rounded rectangles
empezar lección
Actions
Activity diagram diamonds
empezar lección
Decisions
Use state diagram when
empezar lección
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
empezar lección
Aggregation
Class diagram: solid line with empty white triangle at one end
empezar lección
Inheritance
Generalization
empezar lección
Two classes pointing at one third class with empty solid line white triangle
UML Use case diagrams are used to capture
empezar lección
Functional requirements
Software specification/requirement engineering
empezar lección
understanding and defining what services or functionalities are required and identifying the constraints on the system operation
Software design
empezar lección
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
empezar lección
Earlier delivery and deployment, easy customer feedback
Agile method advantages
empezar lección
team communication, requirements do not hold up progress, facilitates customer feedback, visibility of everything
Use cases capture requirements?
empezar lección
yes
Abstraction
empezar lección
reducing by focusing on the essential observable behavior
Encapsulation
empezar lección
hiding the details of the implementation
Polymorphism
empezar lección
a single name may denote objects of many different classes that are related by some common superclass
Pseudocode
empezar lección
"text-based" representation of an algorithm
Software Architecture
empezar lección
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
empezar lección
show that the program does as intended, discover program defects
Unit testing
empezar lección
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

Debes iniciar sesión para poder comentar.