2.0

(see 1.6 Data Life Cycle)
- Software Ecosystem (distinct roles and processes) <- emerging complexity <- from scale up initiatives
- some P theory (Cohen) freedom/autonomy -> development, expression, movement (transportation, voting, gov info)

2.1

P in a software ecosystem (P effects different Software Dev models / roles )

(see 1.6 Data Life Cycle - consider for each role )
LAW monitor P legislation regulation trust => dev must align
MKT w/ customers <- privacy -> requirements
PM ensure communication / resources through SDLC
REQ Engineers (Analysts) collect analyze manage
DESIGNERS architect trace CIA(anonymity) through
DEV best practices standards frameworks
QA validate confirm requirements AND misuse abuse -> violate P
OPS operational assumptions of arch are implemented
Users informed aware given control

2.2

P risk management -> +/- investment in P

P Techniques for all stages...

2.3

Requirements engineering for P

2.4

High level design

2.5

Low level design and implementation

2.6

Testing, validation, and verification