Design information System

Get Started. It's Free
or sign up with your email address
Design information System by Mind Map: Design information System

1. Analysing Requirements Entities

1.1. Modelling Requirements:Things

1.1.1. Brainstorming technique

1.1.1.1. Identify a user and a set of use cases.

1.1.1.2. Brainstorm with the user to identify things about which information should be captured by the system.

1.1.1.3. Use the types of things (categories) to systematically ask questions about potential things

1.1.1.4. Continue to work with all types of users and stakeholders to expand the brainstorming list

1.1.1.5. Merge the results, eliminate any duplicates, and compile an initial list.

1.1.2. Noun technique

1.1.2.1. Identify all nouns using the use cases, actors, and other information including inputs and outputs.

1.1.2.2. Use other information from existing systems including procedures, reports, forms, items or categories of information.

1.1.2.3. Refine the list of nouns.

1.1.2.4. Create a master list of all nouns identified and then note whether each one should be included, excluded, or researched further.

1.1.2.5. Review the list with users, stakeholders, and team members and then refine the list of things in the problem domain.

1.2. Characteristics of things

1.2.1. Attributes

1.2.1.1. Specific information about a thing

1.2.1.2. Identifier or key attributes

1.2.2. Relationship

1.2.2.1. Optional relationship

1.2.2.2. Mandatory relationship

1.2.2.3. Generalisation/specialisation relationship

1.2.2.4. Whole/part relationships

1.2.3. Domain Model Class Diagrams

1.2.3.1. Class

1.2.3.2. Class diagram

1.2.3.3. Domain model class diagram

1.2.3.4. camelback notation or camelCase notation

2. Development Approaches

2.1. Traditional Approach

2.1.1. Data Flow Diagram

2.1.1.1. Context Diagram

2.1.1.2. Expanding into sub-processes

2.1.1.3. Next level of DFDs

2.1.2. Data flow definitions

2.1.3. Process descriptions

2.1.4. Other traditional models

2.2. Object-Oriented Approach

2.2.1. Use case diagrams

2.2.2. Use case descriptions

2.2.3. System sequence diagrams

2.2.4. Activity diagrams

2.2.5. State machine diagrams

3. Systems Implementation and Support

3.1. Implementation activities

3.1.1. Program the software

3.1.2. Unit test the software

3.1.3. Identify and build test cases

3.1.4. Integrate and test components.

3.1.5. Usability test

3.1.6. System and stress test

3.2. Deployment activities

3.2.1. Data conversion

3.2.2. Training users

3.2.3. Configuring the production environment

3.2.4. Source code control system

3.2.5. Version control systems

3.2.6. Installation

3.2.6.1. Direct installation

3.2.6.2. Parallel installation

3.2.6.3. Phased installation

3.2.6.4. Pilot installation

3.2.7. maintenance

4. Systems Design

4.1. Design Environment

4.1.1. Network Specialists-based on strategic plan

4.2. Design and integrate network

4.3. Design Application Architecture & Software

4.3.1. Specify how use cases are carried out

4.3.2. Start with system architecture

4.3.3. move to detailed models

4.4. Design Databases

4.4.1. ERDs

4.4.2. Decide on structure

4.4.3. Security and Encryption

4.5. Design user Interface

4.5.1. Critical part of the system

4.5.2. user interface

4.5.3. HCI(human computer interaction)

4.5.3.1. Affordance

4.5.3.2. Consistency

4.5.3.3. Discoverability

4.5.3.4. Closure

4.5.3.5. Readability and Navigatiion

4.5.3.6. Usability and Efficiency

4.6. Design system Control

4.6.1. ensure that the system and data are secured and protected

4.6.2. need controls for

4.6.2.1. user interface

4.6.2.2. system interface

4.6.2.3. application architecture

4.6.2.4. database

4.6.2.5. network design

4.6.3. More information in control,Audit&Security unit

5. Alternatives for Implementation

5.1. Prioritise requirements

5.1.1. define the scope of the project precisely

5.2. Prioritising Requirements

5.2.1. Predictive approach

5.2.2. Adaptive approach

5.2.3. Determining the level of automation

5.2.3.1. Low

5.2.3.2. Medium

5.2.3.3. High

5.3. Alternatives

5.3.1. in-house

5.3.1.1. Satisfy unique business requirements

5.3.1.2. Minimise changes in business procedures and policies

5.3.1.3. Meet constraints of the existing system

5.3.1.4. Meet constraints of the existing technology

5.3.1.5. Develop internal resources and capabilities

5.3.2. out-source

5.3.2.1. Lower costs or to control the costs

5.3.2.2. Deal with rapid changes in software / hardware technology

5.3.2.3. Less time to implement

5.3.2.4. Proven reliability and performance benchmarks

5.3.2.5. Less technical development staff

5.3.2.6. Future upgrades provided by vendor

5.3.2.7. Obtain input from other companies

5.4. Selecting an alternative

5.4.1. General requirements

5.4.2. Technical requirements

5.4.3. Functional requirements

6. Modelling Approaches

6.1. Modelling Requirements

6.1.1. Use case descriptions and diagrams

6.1.2. Activity diagrams

6.1.3. Domain Model Class Diagrams / Entity Relationship Diagrams