Objektorienterad mjukvaruutveckling Flashcards
Which of the following is an OO design principle?
- No answers correct
- SRK
- CMYK
- All answers are correct
- YDR
- LSP
- COP
LSP, Liskov Substitution Principle
Which is a reason for IT-project failure?
* Stable requirements
* Fast-changing technology
* Overuse of agile methods
* Underuse of the waterfall model
Fast-changing technology
What happens according to the triple contraint if you reduce cost(budget)?
* Increase cost and/or reduce scope
* Reduce time and/or cost
* Increase time and/or reduce scope
* Increase time and/or cost
* Reduce time and/or increase scope
Increase time and/or reduce scope
A Project is…
* A specific goal
* A long term goal
* A work environment
* A permanent endeavor
* A temporary endeavour
A temporary endeavour
Use cases are…
* Useless by today
* Used for requirements analysis
* Created during implemenation phase
* Evaluated by off-stage actors
* Used for testing
Used for requirements analysis
Which are the typical phases of a project management life cycle?
* Analysis, planning, inplementing, testing, closing
* Initiating, planning, implementing, testing, closing
* Initiating, planning, executing, testing, closing
* Initiating, planning, executing, closing
Initiating, planning, executing, closing
The difference between a Milestone and a Tollgate is that
* A tollgate is defined by the project manager, not so a Tollgate
* A tollgate hgas external dependencies, not so a Milestone
* A milestone is defined by the project manager, not so a tollgate
* A milestone is more important than a tollgate
* A milestone has external dependencies, not so a tollgate
A tollgate has external dependencies, not so a Milestone
The core of ‘agile’ is…
* The assumption that whatever the requirements are, the project will adapt to it
* The assumption that requirements needs to be fixed at the beginning
* The assumption that whatever the requirements might be at the beginning of a project, they won’t be the same at the end of a project
* The assumption that requirements do not matter that much, except when it comes to non-functional requirements
The assumption that whatever the requirements might be at the beginning of a project, they won’t be the same at the end of a project.
What is good design?
*Determined
*Beautiful
*Flexible
*Fixed
Flexible
A domain model does not contain…
* Associations
* Multiplicities
* Methods
* Attributes
Methods