Requirements analysis:
(1) business model à concept model-> design model
Business model: from requirements
Business Use case:
What’s use case, not a step:
(1) meaningful for user
(2) from actor
(3) It’s an abstraction from reality
There are 3 relationships between use cases: implement, include, extend
There are some diagrams for requirements analysis:
Activity diagram:
Sequence diagram:
Collaboration digram:
Concept model: what it should be
Concept use case:
Design model: how to do it
Mapping to implementation: languages, communication protocol,
Logical, development view, deployment view,
What impressed me most?
(1) boundary
(2) Analysis mode: entity, control, boundary
(3) Architecture: business architecture, technical architecture, architecture patterns( MVC, layered, micro kennel)
System thinking vs structural thinking to build a system