quartz/content/notes/review-i201.md

title	aliases	tags
review-i201

soft dev methods

• sdlc
• tradition 9predictive vs agile flexible
• up (OO)
• scrun
• xp

requirements engineering

• bp re egineering
• requirments
  • properties of good ones
  • functional vs not
  • importance (moscow)
• elicitation
  • stakeholders techniques
  • outcome validation

business functions and use cases

• business functions - how to identify
• use cases - how to model
• uml use case diagrams
  • actors usecases
  • associations, dependencies

BPM

• business processes and how the are modelled
• BPMN vs (high level) UML activity

Data modelling

• erd concepts
  • subtypes
  • parrallel and reursive relationships
  • historical data
• normalisation
  • redundancy and anomalies
  • function and multivaly dependencies
  • normal forms

Modelling object structure

• oop concepts
  • state behaviiour encapsilation
  • class vs instance, object reference
• uml diagrams
  • steriotypes, visibility, multiplicity
  • specialsation/generalisation, navigability
  • erd vs class diagram

object behaviour

• inheritance
  • specialisation vs implementing an interface
  • separation of public private API (programming to interface)
• rich vs anaemic domaini models "processor objects"
• modelling behaviour with uml
  • sequnce diagrams
  • low level activity and state diagrams

round trip engineering

• foward engineering
  • erd -> SQL
  • uml class diagram -> e.g., java
  • correspondenc with use cases
• reverse engineering (code <- diagrams)

Data access

• data persistence file vs database
• da