My lesson

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

You must sign in to write a comment