Top Banner
Week 1 -Introduction IT2005 System Analysis & Design
16
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Week 1 -Introduction IT2005 System Analysis & Design.

Week 1 -Introduction

IT2005 System Analysis

& Design

Page 2: Week 1 -Introduction IT2005 System Analysis & Design.

2

Outline syllabus

1. Introduction to System Analysis and Design2. Software development lifecycles3. Requirement elicitation and business analysis4. System analysis and design tools5. Logical Data Design6. Interaction Design

Page 3: Week 1 -Introduction IT2005 System Analysis & Design.

3

objectives

• To provide an understanding of the role of systems analysis and design within various systems development lifecycles

• To develop an awareness of the different approaches that might be taken to systems analysis and design

• To understand the activities of the systems analyst and systems designer, and apply some current techniques

Page 4: Week 1 -Introduction IT2005 System Analysis & Design.

4

Week 1 –Information System

IT2005 System Analysis

& Design

Page 5: Week 1 -Introduction IT2005 System Analysis & Design.

5

Information system

• It is an arrangement of Computer Technology (Hardware & Software) and Telecommunication Technology(Data, image, voice) to support and Improve day to day operations, problem solving and decision making needs of management and users.

Page 6: Week 1 -Introduction IT2005 System Analysis & Design.

6

Main components of an Information SystemInformation systems consist of

four main components.They are, – Input (collects data)– Processing (process data) – Output (disseminates data)– Feedback

Page 7: Week 1 -Introduction IT2005 System Analysis & Design.

7

Computer Based Information Systems(CBIS)

• The resources of a CBIS include,– hardware – software – databases – telecommunications – people – procedures

Page 8: Week 1 -Introduction IT2005 System Analysis & Design.

8

System development environment• stakeholders

Is any person who has an interest in an information system and its outputs.

• Mainly, there are five types of stakeholders.1. Systems User 2. Systems Owner 3. Systems Builder 4. Systems Designer 5. Systems Analyst

Page 9: Week 1 -Introduction IT2005 System Analysis & Design.

9

Systems User• A “customer” who will use an information system by,

– capturing – validating – entering – responding to – storing – exchanging

• data and information on a regular basis. A common synonym is client.

• Systems users define the business requirements and performance expectations for the system to be built.

Page 10: Week 1 -Introduction IT2005 System Analysis & Design.

10

Systems Owner • Systems owner I an information system’s sponsor and

advocate and he owns the final system. • They pay for the system to be built and maintained .• They set the vision and the priorities for the system and

determine the policies for its use.• Responsible for funding the project of• Developing• Operating• Maintaining the information system.

Page 11: Week 1 -Introduction IT2005 System Analysis & Design.

11

System builder

• System builder are technical specialists involved with – Constructing– Testing– Delivering the system into operation

• They construct the information system components based on the design specifications from the system designers.

Page 12: Week 1 -Introduction IT2005 System Analysis & Design.

12

Systems Designer

• System designers are technical specialists • Translate systems users business requirements and

constrains into technical solutions• They design the system including– Databases– Inputs – Outputs– Screens – Network– Software to meet the users requirements

Page 13: Week 1 -Introduction IT2005 System Analysis & Design.

13

Systems Analyst

• System analysts are people who understand both business and computing

Page 14: Week 1 -Introduction IT2005 System Analysis & Design.

14

Roll of system analysis

1. Identify the problem2. Analyze and understand the problem3. Identify the solution requirements4. Identify alternative solutions5. Design and implement the best solution6. Evaluate the result

Page 15: Week 1 -Introduction IT2005 System Analysis & Design.

15

Legacy Systems

• Legacy system is an "antiquated" system.– potentially problematic – often run on obsolete hardware – spare parts for such computers become

increasingly difficult to obtain – hard to maintain, improve and expand – The designers of the system may have left the

organization, leaving no one left to explain how it works.

Page 16: Week 1 -Introduction IT2005 System Analysis & Design.

16

Upgrading a Legacy System

Many complex legacy systems are yet to be upgraded to new technologies because of – Cost – Skills – People required

Force to change – to reflect new or changing business requirements. – Year 2000 problem (Y2K) – Euro conversion