MSD
FHNW - Medical Software Development
FHNW - Medical Software Development
Fichier Détails
| Cartes-fiches | 16 |
|---|---|
| Langue | English |
| Catégorie | Informatique |
| Niveau | Université |
| Crée / Actualisé | 13.06.2021 / 14.06.2021 |
| Lien de web |
https://card2brain.ch/box/20210613_msd
|
| Intégrer |
<iframe src="https://card2brain.ch/box/20210613_msd/embed" width="780" height="150" scrolling="no" frameborder="0"></iframe>
|
Créer ou copier des fichiers d'apprentissage
Avec un upgrade tu peux créer ou copier des fichiers d'apprentissage sans limite et utiliser de nombreuses fonctions supplémentaires.
Connecte-toi pour voir toutes les cartes.
Top Risk for failure in SW Development
- Schedule (e.g. Time estimation)
- Budget (e.g. Cost overrun)
- Operational and Management (e.g. Resource planning)
- Technical (e.g. Change of requirements)
- External (e.g. Government rule change)
What are the SW Engineering knowledge areas? List 15 areas!
- SW Requirements
- SW Design
- SW construction
- SW Testing
- SW Maintenance
- SW Config Managment
- SW Engineering Management
- SW Engineering Process
- SW Engineering Methods
- SW Quality
- Common Practise
- Economics
- Computing, Mathematical and Engineering Foundations
Define Software Requirements
elicitation,negotiation, analysis, specification, andvalidation
Define SW Design
definition of the architecture, components, interfaces,
SW construction
detailed design, coding, unit testing, integration testing, debugging, verification and tools,
SW Testing
fundamentals of software testing; testing techniques; humancomputer user interface testing and evaluation; test-related measures
Software Maintenance
reverse engineering, refactoring, software retirement; disaste recovery techniques, tools,
Software Configuration Management
identification, control, status accounting, auditing; software release management and
delivery, tools
Software Engineering Management
process planning, estimation of effort, cost,
and schedule, resource allocation, risk analysis,
planning for quality; product acceptance;
review and analysis of project performance;
project closure; tools
Software Engineering Process:
software life cycle models, process assessment, tools
Software Engineering Methods
modeling, analysis
Software quality
verification, validation, reviews, audits, tools
Software Engineering Professional Practice:
standards, codes of ethics; group
dynamics (working in teams, cognitive problem
complexity, interacting with stakeholders,
dealing with uncertainty and ambiguity,
dealing with multicultural environments);
communication skills
Software Engineering Economics
costbenefit analysis, optimization, risk analysis,
estimation, decision making
Computing, Mathematical and Engineering Foundations
Computing Foundations: operation systems,
networking, algorithms, parallel an
distributed computing
Mathematical Foundations: sets, relations,
and functions; basic propositional and
predicate logic; proof techniques; graphs
and trees; discrete probability; grammars
and finite state machines; and number theory.
Engineering Foundations: statistical
analysis; measurements and metrics; engineering
design; simulation and modeling
Give a short model of the whole process in this discipline!
Split into 2 main categories and give 3 subcategories for each of them.
Software Development
- Requirements : elicitation, negotiation, analysis, specification, and validation,
- Design : architecture, components, interfaces,
- Construction : coding, unit & integration testing, documentation
Project Management
- Configuration Management : change control, release management
- Process Life Cycle : planning, resource allocation, risk analysis
- Quality Management : verification, validation, reviews
-
- 1 / 16
-
