quartz/content/notes/review-i201.md

title	aliases	tags
review-i201

soft. dev. methods

• SDLC
• 1 traditional (predictive) vs 1 object oriented (flexible)
• UP (OO)
• scrum
• xp

requirements engineering

• business-process re engineering
• requirements
  • properties of good ones requirements-guidelines
  • functional vs not furps
  • importance (moscow)
• elicitation requirements-elicitation
  • stakeholders techniques stakeholders Stakeholders
  • outcome validation Validation of Requirements

business functions and use cases

• business functions - how to identify 1 Id business functions
• use cases - how to model 2 Use case
• uml use case diagrams use-case-diagrams
  • actors usecases 2 1 Actor 2 2 Use case
  • associations, dependencies 2 3 Association 2 5 Dependency

BPM

• business processes and how the are modelled business-process bsin
• BPMN vs (high level) UML activity business-process-model-and-notation activity-diagrams

Data modelling

• erd concepts ERD
  • subtypes subtypes
  • parrallel and reursive relationships parallel relationship recursive relationship
  • historical data dealing with data history
• normalisation normalisation
  • redundancy and anomalies redundancy-and-anomalies
  • function and multivaly dependencies dependencies
  • normal forms 2 Normal forms

Modelling object structure

• oop concepts 10-oop-concepts-and-uml
  • state behaviiour encapsilation
  • class vs instance, object reference
• uml diagrams what-are-uml-diagrams
  • steriotypes, visibility, multiplicity 1 Stereotypes 3 1 multuplicity
  • specialsation/generalisation, navigability 3 8 Specialisation generalisation 3 4 Navigability
  • erd vs class diagram 4 Domain class model vs 5 System class model

object behaviour

• inheritance 1 Inheritance
  • specialisation vs implementing an interface 1 1 Via Specialisation vs 1 2 Via Interface
  • separation of public private API (programming to interface) 1 3 Public vs Private
• rich vs anaemic domaini models "processor objects" 2 Behaviour
• modelling behaviour with uml modelling-behaviour
  • sequnce diagrams sequence-diagrams
  • low level activity and state diagrams activity-diagrams

round trip engineering

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

Data access

• data persistence file vs database Data Access
• database APIs (JDBC etc) JDBC
• DAOs DAO - oner per use case (not just per domain class) - often programming via DAO interface

Database transactions

• ACID ACID
• what and why Transactions
• commit vs rollback commit and rollback

SQL select

• select from where Select
• sorting grouping aggregation Aggregation and grouping
• view, inner and outer joins, subqueries Inline views Joins, Subqueries

data integrity

20-data-integrity

• nulls and their issues
• business rules, databas contrainsts, veification, validation Validation Verification Check constrainsts Primary and foreign key constraints
• in-database vs outside database
• in data base automation: sequence, triggers, stored procedures Automation

softare architectures, patterns, and templates

08-business-patterns

• monolithic vs client/server vs distributed (services) Monolithic architecture
• separation of reponsilbilities Separation of reponsibilities
• "standard patters" of design (recognise) s
• sysstem templates

performance and security

• performance requirements
  • how to quantify and measure
  • response time, workload, scalability
  • caching pooling
  • system reliability
• security and integrity requirements
  • consider throughout development
  • authentication and authorisation
  • principle of least privilege

cost benefit analysis

• project feasbility
  • need, funding, strong will
  • duration, priority, rick, uncertainty
  • should we, can we, is it worth it?
• economic feasibility:
  • costs vs benefits (tangigble/intangible)
  • payback time (break even), NPV, ROI