1. Design Phase Deliverable - System Specification
2. HOW to build the new system
2.1. 1. Design Strategy
2.2. 2. Architecture Design
2.3. 3. User Interface Design
2.4. 4. Database and File specifications
2.5. 5. Program Design
3. Part 3: User Interface Design
3.1. Principles and considerations:
3.1.1. 1. Layout
3.1.1.1. ... visual metaphor
3.1.2. 2. Content Awareness
3.1.3. 3. Aesthetics
3.1.4. 4. User Experience
3.1.4.1. - trade-off .... Novice vs. Experts
3.1.5. 5. Consistency
3.1.6. 6. Minimize user effort
3.1.6.1. ... eg. designs with no more than 3 button clicks.
4. Part 5: Program Design
4.1. 1. Process modeling
4.1.1. usign dataflow diagrams DFD
4.2. 2. Logical process model
4.3. 3. Physical Process models
5. Things to consider that influence a system acquisition decision:
5.1. 1. Business need
5.2. 2. in-house experience
5.3. 3. Project Skills
5.4. 4. Project Management
5.5. 5. Time Frame
6. SYSTEM INTEGRATION
7. Objective: Decides how the new system will operate. - Analysis is all about what the business NEEDS ... Design says HOW to BUILD IT ... from the PROBLEM domain to the SOLUTION domain.
8. Selecting a Design Strategy: - Understand each acquisition startegy by the means of the following requests to a vendor ...
8.1. 1. Request for proposal RFP
8.2. 2. Request for Information RFI
8.3. 3. Request for Quote RFQ
9. Decision Making Tools:
9.1. 1. Alternative Matrix
10. Part 1: Design Strategy
10.1. Steps:
10.1.1. 1. Business Requirements are converted into System Requirements describing the Technical details of building the system.
10.1.1.1. System Requirements:
10.1.1.1.1. 1. Design Models
10.1.1.1.2. 2. Physical Models
10.1.1.1.3. 3. Data Models
10.1.2. 2. System Acquisition Strategies:
10.1.2.1. 1. Custom
10.1.2.2. 2. Packaged
10.1.2.3. 3. Outsourced
10.1.2.3.1. ASPs - Application Service Provider
10.1.2.3.2. SaaS - Software as a Service
10.2. Contract Types:
10.2.1. 1. Time arrangement
10.2.2. 2. Fixed-price
10.2.3. 3. Value added