1.0 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN

Get Started. It's Free
or sign up with your email address
Rocket clouds
1.0 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN by Mind Map: 1.0 INTRODUCTION TO SYSTEM ANALYSIS AND DESIGN

1. 1.2.4 Identify appropriate life cycle models based on given scenario

2. 1.2.5 Describe project management activities:

2.1. a. planning

2.1.1. Identifying all project tasks and estimating the completion time and cost of each.

2.2. b. scheduling

2.2.1. Involves the creation of a specific timetable, usually in the form of charts that show tasks, task dependencies, and critical tasks that might delay the project

2.3. c. monitoring

2.3.1. Requires guiding, supervising, and coordinating the project team’s workload.

2.4. d. reporting

2.4.1. Includes regular progress reports to management, users, and the project team itself.

3. 1.1 Discuss Information System.

3.1. 1.1.1 Define information and information system.

3.1.1. Information : Is data that has been transformed into output that is valuable to users.

3.1.2. Information system : -Combines information technology, people and data to support business requirements. -Information System have 5 components which are hardware, software, data, processes and people.

3.2. 1.1.2 Describe information system components

3.2.1. Hardware

3.2.1.1. Is the physical layer of the information system

3.2.2. Software

3.2.2.1. System software

3.2.2.2. Application software

3.2.2.3. Enterprise applications

3.2.3. Data

3.2.3.1. Tables store data

3.2.3.2. Linked tables work together to supply data

3.2.4. Processes

3.2.4.1. Describe the tasks and business functions that users, managers, and IT staff members perform to achieve specific results

3.2.5. People

3.2.5.1. Stakeholders

3.2.5.2. Users, or end users

3.3. 1.1.3 Identify various types of information system.

3.3.1. Executives

3.3.1.1. Executive Information Systems

3.3.2. Senior Managers

3.3.2.1. Decision Support Systems

3.3.3. Middle Managers

3.3.3.1. Management Information Systems

3.3.4. Workers

3.3.4.1. Transaction Processing Systems

4. 1.2 Discuss system development approach.

4.1. 1.2.1 Explain system development method:

4.1.1. a. Structured Analysis

4.1.1.1. Is a traditional systems development technique that is time tested and easy to understand.

4.1.1.2. Uses a series of phases to plan, analyze, design, implement and support an IS.

4.1.2. b. Object Oriented Analysis

4.1.2.1. is a popular technical approach for analyzing, designing an application, system,

4.1.2.2. business by applying the object-oriented paradigm and visual modeling throughout the development life cycles to foster better stakeholder communication and product quality.

4.1.3. c. Agile/Adaptive Method

4.1.3.1. aim to provide new product or service development in a highly flexible and interactive manner.

4.2. 1.2.2 Explain System Development Life Cycle (SDLC) activities:

4.2.1. a. Planning

4.2.1.1. The purpose of this step is to find out the scope of the problem and determine solutions.

4.2.2. b. Analyze

4.2.2.1. Where businesses will work on the source of their problem or the need for a change.

4.2.3. c. Design

4.2.3.1. This is the step for end users to discuss and determine their specific business information needs for the proposed system.

4.2.4. d. Development

4.2.4.1. This work includes using a flow chart to ensure that the process of the system is properly organized.

4.2.5. e. Testing

4.2.5.1. Involves systems integration and system testing.

4.2.6. f. Implementation

4.2.6.1. This phase involves the actual installation of the newly-developed system.

4.2.7. g. Maintenance

4.2.7.1. Final phase involves maintenance and regular required updates.

4.3. 1.2.3 Describe various types of life cycle models such as:

4.3.1. a. Waterfall model

4.3.1.1. Represents the system in terms of data and the processes that objects that act upon that data.

4.3.2. b. Spiral Model

4.3.2.1. Stated that each iteration, or phase, of the model must have a specific goal that is accepted, rejected, or changed by the user, or client.

4.3.3. c. Iterative and incremental development

4.3.3.1. Allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system

4.3.4. d. Agile Model

4.3.4.1. Methods attempt to develop a system incrementally, by building a series of prototypes and constantly adjusting them to user requirements

4.3.5. e. Prototyping model

4.3.5.1. Prototyping tests system concepts and provides an opportunity to examine input, output, and user interfaces before final decision are made.

4.3.6. f. Rapid Application Development (RAD)

4.3.6.1. Process allows users to examine a working model as early as possible, determine if it meets their need, and suggest necessary changes.

4.3.7. g. Joint Application Development (JAD)

4.3.7.1. Is a popular fact-finding technique that brings users into the development process as active participants.

5. 1.3 Understand Project Management

5.1. 1.3.1 Explain project planning, scheduling, monitoring, and reporting.

5.2. 1.3.2 Explain steps in project planning.

5.2.1. Step 1: Project Goals

5.2.2. Step 2: Project Deliverables

5.2.3. Step 3: Project Schedule

5.2.4. Step 4: Supporting Plans

5.3. 1.3.3 Describe work breakdown structures, task patterns, and critical path analysis.

5.3.1. A work breakdown structure must clearly identify each task and include an estimated duration.

5.3.2. Tasks in a work breakdown structure must be arranged in a logical sequence called a task pattern.

5.3.3. Is a series of tasks which, if delayed, would affect the completion date of the overall project

5.4. 1.3.4 Create a work breakdown structure.

5.5. 1.3.5 Explain techniques for estimating task completion times and costs.

5.6. 1.3.6 Explain leadership and project manager.

5.6.1. Good leadership is essential in building up an information system project.

5.6.2. In a systems project, the project manager, or project leader, usually is a senior systems analyst or an IT department manager if the project is large.