Systems Development Life Cycle: Feasibility Study and SWOT Analysis, Assignments of Software Engineering

An overview of the Systems Development Life Cycle (SDLC), focusing on the feasibility study phase and SWOT analysis. The feasibility study evaluates operational, technical, economic, and schedule feasibility of a systems request. The SWOT analysis identifies the strengths, weaknesses, opportunities, and threats of a company, in this case, FedEx, using external and internal factor analysis.

Typology: Assignments

2019/2020

Uploaded on 08/23/2020

akaasi-i
akaasi-i 🇵🇰

1 document

1 / 50

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
SDLC – SYSTEM
DEVELOPMENT
LIFE CYCLE
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32

Partial preview of the text

Download Systems Development Life Cycle: Feasibility Study and SWOT Analysis and more Assignments Software Engineering in PDF only on Docsity!

SDLC – SYSTEM

DEVELOPMENT

LIFE CYCLE

TOPICS COVERED

 SDLC

 Business Information Systems

 Preliminary Investigations

 SWOT Analysis

SYSTEMS DEVELOPMENT LIFE CYCLE

 Systems planning

Systems analysis

 Systems design

 Systems implementation

 Systems operation and support

 Waterfall model

 Interactive model

SYSTEMS DEVELOPMENT LIFE CYCLE

 Systems planning

 (^) Purpose – identify problem’s nature/scope  (^) Systems request – begins the process & describes desired changes/improvements  (^) Systems planning – includes preliminary investigation or feasibility study  (^) End product – preliminary investigation report SYSTEMS DEVELOPMENT LIFE CYCLE

 Systems analysis

 (^) Purpose is to learn exactly how the current system operates  (^) Fact-finding or requirements determination is used to define all functions of the current system SYSTEMS DEVELOPMENT LIFE CYCLE

 Systems design

 (^) Purpose is to satisfy all documented requirements  (^) Identify all outputs, inputs, files, manual procedures, & application programs  (^) Avoid misunderstanding through manager and user involvement  (^) End product is system design specification SYSTEMS DEVELOPMENT LIFE CYCLE

 Systems implementation

 (^) Construct/deliver information system  (^) Prepares functioning, documented system  (^) Write, test, document application programs  (^) User and manager approval obtained  (^) File conversion occurs  (^) Users, managers, IS staff trained to operate and support the system  (^) Post-implementation evaluation performed SYSTEMS DEVELOPMENT LIFE CYCLE

SDLC -

SYSTEMS

PLANNING

OBJECTIVES  (^) Describe the initial review of systems requests and the role of the systems review committee  (^) Describe the internal and external factors that affect information systems projects  (^) Define operational feasibility, technical feasibility, schedule feasibility and economic feasibility  (^) Describe the steps and end product of a preliminary investigation

INFORMATION SYSTEMS PROJECTS

 Starting point is a systems request

 (^) Main Reasons for Systems Projects  (^) Systems request  (^) Improved service  (^) Support for new products and services  (^) Better performance  (^) More information

INFORMATION SYSTEMS

PROJECTS

INFORMATION SYSTEMS

PROJECTS

 (^) Internal Factors  (^) Strategic plan  (^) Top managers  (^) User requests  (^) Information technology department  (^) Existing systems

INFORMATION SYSTEMS

PROJECTS

 (^) External Factors  (^) Technology  (^) Suppliers  (^) Customers  (^) Customer Relationship Management (CRM)  (^) Competitors  (^) Economy  (^) Government