System Analysis and Design Mind Map - Jonas Johann

Get Started. It's Free
or sign up with your email address
System Analysis and Design Mind Map - Jonas Johann by Mind Map: System Analysis and Design Mind Map - Jonas Johann

1. W1 - Development of Information Systems

1.1. Systems Development Life Cycle (SDLC)

1.2. System Analysis Skills

1.3. Problem Solving

1.4. System Vision Document

2. W2 - Approaches to Systems Development

2.1. SLDC

2.1.1. IPADIT

2.1.2. Waterfall

2.1.3. Adaptive

2.2. Models

2.2.1. Structured

2.2.1.1. Data Flow Diagram (DFD)

2.2.1.2. Entity Relationship Diagram (ERD)

2.2.2. Object-Oriented

2.2.2.1. Class Diagram

2.2.2.2. Tools and Techniques

3. W3 - Project Management

3.1. Initiation

3.1.1. Procedures

3.1.2. Charter

3.2. Planning

3.2.1. Risk and Feasibility

3.2.2. Work Breakdown Structure (WBS)

3.3. Execution

3.3.1. Executive Baseline

3.3.2. Monitor and Cope

3.4. Closedown

3.4.1. Reviews

3.4.2. Close Contract

4. W4 - Risk and Feasibility

4.1. Risk

4.1.1. Identify

4.1.2. Likelihood

4.1.3. Impact

4.1.4. Mitigation

4.2. Feasibility

4.2.1. Costs

4.2.2. Anticipated Benefits

4.2.3. Cost/Benefit Techniques

4.2.3.1. Return of Investment (ROI)

4.2.3.2. Net Present Value (NPV)

4.2.3.3. Payback Analysis

5. Assignment 1 is due

6. W5 - Fact Finding

6.1. What to find out?

6.1.1. Who?

6.1.2. What?

6.1.3. Where?

6.1.4. When?

6.1.5. How?

6.1.6. How Often?

6.1.7. Why?

6.2. Techniques

6.2.1. Interviews

6.2.2. Questionnaires

6.2.3. Documentation

6.2.4. Observation

6.2.5. Research

6.2.6. Comments and Suggestions

6.3. Activity Diagram

6.3.1. Users

6.3.2. Systems

6.3.3. Information Flow

7. W6 - Analysing Requirements

7.1. Use Cases

7.1.1. Traditional

7.1.1.1. Data Flow Diagram (DFD)

7.1.2. Object Oriented

7.1.2.1. Use Case Diagram (UCD)

7.1.3. User Goal

7.1.4. Verb+Noun

8. W7 - Study Break

9. W8 - Analysing Requirements

9.1. Attributes

9.2. Relationships

9.3. Associations

9.4. Cardinality

9.5. Notations

9.6. Aggregation

9.7. Entity Relationship Diagram (ERD)

9.8. Domain Model Class Diagram (DMCD)

9.9. Equivalent Domain Model Class Diagram

10. W9 - Modelling Approaches

10.1. Object-Oriented

10.1.1. Class Diagram

10.1.1.1. Use Case Diagram

10.1.1.2. Use Case Description

10.1.1.3. System Sequence Diagram (SSD)

10.1.1.3.1. Inputs

10.1.1.3.2. Outputs

10.1.1.3.3. Interaction

10.1.1.4. Activity Diagram

10.1.1.5. State Machine Diagram

10.2. Traditional

10.2.1. Entity Relationship Diagram (ERD)

10.2.1.1. Context Diagram

10.2.1.2. Data Flow Diagram (DFD)

10.2.1.2.1. Inputs

10.2.1.2.2. Outputs

10.2.1.2.3. Processes

10.2.1.2.4. Data Storage

10.2.1.3. Data Flow Definitions

10.2.1.4. Process Descriptions

10.2.1.5. Other Traditional Models

11. W10 - Alternatives for Implementation

11.1. What is to be included?

11.1.1. Mandatory / Needed

11.1.2. Important / Wanted

11.1.3. Desirable / Wishlist

11.1.4. General signed agreement

11.2. Types of application

11.2.1. Stand alone

11.2.2. Online

11.2.3. Distributed

11.2.4. Internet-based

11.2.5. Mobile optimised

11.3. Deployment

11.3.1. System Requirement Compatibility

11.3.2. Software and Hardware Compatibility

11.3.3. External Systems Interface

11.3.4. Cost and Schedule

11.3.5. Environment

11.3.5.1. Programming Language

11.3.5.2. CASE Tools

11.3.5.3. Other Softwares

11.4. Implementation

11.4.1. Outsource all IT Support

11.4.2. Package Softwares

11.4.3. Custom-built

11.4.4. In-house

11.4.5. Mix

12. W11 - System Implementation and Support

12.1. Testing

12.1.1. Top Down / Bottom Up

12.1.1.1. Input

12.1.1.2. Process

12.1.1.3. Output

12.1.2. Quality Assurance (QA)

12.1.3. Quality Control (QC)

12.1.4. Test Cases

12.1.5. Unit Test

12.1.6. Integration Test

12.1.7. Usability / Acceptance Test

12.1.8. System Stress Test

12.2. Deployment

12.2.1. Data Conversion

12.2.2. User Training

12.2.3. Configuring Environment

12.3. Installation

12.3.1. Direct

12.3.2. Parallel

12.3.3. Phased

12.3.4. Pilot

12.4. Maintenance

13. W12 - Current Trends in System Development

13.1. Adaptive / Agile Methodologies

13.1.1. Unified Process

13.1.1.1. Inception

13.1.1.2. Elaboration

13.1.1.3. Construction

13.1.1.4. Transition

13.1.2. Scrum

13.1.2.1. Sprints

13.1.2.2. Product Backlog

13.1.3. Extreme Programming and Scrum

13.2. Object Frameworks and Components

13.2.1. Set of Classes

13.2.1.1. Foundation

13.2.1.2. User Interface

13.2.1.3. Generic Data Structure

13.2.1.4. Relational Database Interface

13.2.1.5. Specific Application Type

13.2.2. Components

13.2.2.1. Software Modules

13.2.2.2. Well-defined interfaces

13.2.2.3. Standardised and interchangeable

13.2.2.4. Speeds up Completion

14. W13 - Assignment 2 is due