| |
SSADM Philosophy, Principles and Concepts
- An overview of the history of the method, including why a method is needed and how SSADM meets that need
- Need for a good systems development method
- Scope and limitations in the project life cycle
- Separation of concerns in the System Development Template and 3-Schema Specification Architecture
- Place of all major SSADM products in the SDT
- User involvement throughout
- Architecture of SSADM4+ (SSADM Reference Manual, User Guide, System Development library volumes)
- The need for a structural model
- Product driven approach
The Business Context
- Business Activity Modelling
- Business Activity Model
- What business activities are done
- When the business activities are done
- How the business activities are done
- Why the business activities are done
- Requirements Definition
- Focusing analysis on requirements for the future system,
- What is a requirement, types of requirement (functional and non-functional and the categories within each of these)
- Identifying requirements to meet the needs of the business
- Service level requirements
- Usability requirements
- Requirements Catalogue
Modelling Data
- Logical Data Modelling
- Entity (master, detail)
- Relationships (cardinality, optionality, exclusivity, recursion)
- Attributes
- Keys (simple, compound, hierarchic, foreign)
- Sub types, super types
- Logical Data Model
- Data Catalogue
- Relational Data Analysis
Modelling from the user's perspective
- Data Flow Modelling
- Function Definition
- Purpose of Functions, definition of Functions, online and offline Functions
- Function Description
- Function Navigation Model (online)
- I/O Structures (offline)
- User Object Modelling
- Purpose of User Object Model, user objects, types of user object, Attributes and actions, associations
- User Object Model
- User Interface Design
- Purpose of User Interface Design
- Dialogues
- Style guides
- Navigation models
|
Modelling from the system's perspective
- Entity Behaviour Modelling
- Purpose of Entity Life Histories
- Event and enquiry identification
- Business and conceptual model events
- Effects,
- Valid sequence of events in an entity's life:
- Birth
- Death
- Main life changes
- Entity Access Matrix
- Entity Life Histories
- Conceptual Process Modelling
- Purpose of conceptual process models
- Representing access paths
- Entry points
- Sequence
- Selection iteration
- Use of Entity Access Matrix
- Operations
- Conditions
- Validating the Logical Data Model
- Enquiry Access Paths
- Effect Correspondence Diagrams
- Event and Enquiry Catalogue
Human Factors
- Work Practice Modelling
- Where business activities are to be carried out
- Who will carry out business activities
- Work Practice Modelling
- Prototyping
- Purpose of prototyping
- Properties of prototype
- Prototyping and evaluation
- The process of prototyping
- Types of prototype
Formulating Options
- Business Systems Options
- Development of each BSO, including inputs to the technique and personnel involved
- Documenting the option
- Reducing the number of options
- Selection of the BSO
- Constraints
- Technical Systems Options
- Development of each Technical System Option including skills required
- Technical Systems Architecture
- System Description
- Impact Analysis
- Outline Development Plan
- Cost Benefit Analysis
- Constraints
- identifying candidate technologies for the three areas of the 3-SSA
Physical Design
- Physical Design Strategy
- PDI
- Mapping logical products onto the Technical System Architecture
- Physical Data Design
- Physical Process Specification
- FCIM
|
