Software engineering — definition?
Systematic, disciplined, measurable approach to software.
Poor architecture — consequence?
Widespread failures and increased risk.
Model — purpose?
Abstract representation to reason about systems.
Engineering method — steps?
Formulate, analyze, search, decide, specify.
Knowledge acquisition — nonlinear?
New info can invalidate previous understanding.
Rationale — contains?
Context, reasons, and decision justifications.
Project — structure?
Activities and tasks organized to develop software.
Participant — role?
Person contributing to system development or use.
System — definition?
Interconnected parts working as a whole.
Work product — types?
Internal artifacts or client deliverables.
Notation — example?
UML for object-oriented modeling.
Method — purpose?
Repeatable technique for solving specific problems.
Development activities — sequence?
Elicitation, analysis, design, implementation, testing.
Testing — comparison models?
Unit: object design; Integration: system design; System: requirements.
Testez vos connaissances avec un QCM de 14 questions sur Introduction to Software Engineering.
1. What is the main purpose of safety-critical testing?
2. What best describes a methodology?
Révisez le cours complet dans la fiche de révision de Introduction to Software Engineering.
Voir la fiche →Intelligence Artificielle
Bases de données
Bases de données
Importe ton cours et l'IA génère des flashcards en 30 secondes.
Générateur de flashcards