Please enable JavaScript.
Coggle requires JavaScript to display documents.
System development and system analysis - Coggle Diagram
System development and system analysis
Why need system development
Changes in business need
To gain competitive advantage
Changes in users needs
Availability of advanced technology with lower cost
Improved business processes
Productivity gains: automate clerical tasks, decrease task performance time, and provide employees with specialized knowledge.
Sys integration: Organizations with incompatible systems integrate them to remove incompatibilities and to consolidate databases
Sys age and need to be replaced
System development life cycle
System analysis
: First SDLC step where the information needed to purchase, develop, or modify a system is gathered.
Initial investigation: development requests are screened and prioritized
System survey: to identify strengths and weaknesses
Feasibility of the proposed project
Determine info needs & system requirements
Deliver sys requirements: that are used to select or develop a new system
-> Sys analysis report
Sys survey
: is an extensive study of the current AIS
Interview: answer to why Q
Questionare: used when the amount of info to be gathered is small and well defined
Observation: determine how the sys actually works, not how it should work
Sys documentation : identify the discrepancies between intended and actual sys operations
Documentation of sys analysis:
Physical models: illustrate how a system functions by describing document flow, computer processes performed, the people performing them, and the equipment used.
Logical model: focus on essential activities (what is being done) and the flow of information, not on the physical processes of transforming and storing data
Conceptual Design
: Second SDLC step where analysts decide how to meet user needs
Identify and evaluate design alternatives
Develop design specifications
Deliver conceptual design requirements
Physical Design
: translate the conceptual design requirements -> the detailed specifications used to code and test computer program
Design output and input documents
Design database and files
Develop procedures, programs
Design controls
Deliver developed sys
Implementation and conversion
: all of these come together
Develop and implementation and conversion plan
Install hardware and software
Train personnel
Test the sys
Complete documentation
Convert from old to new sys
Deliver operational sys
Operations and Maintenance
: new sys is periodically reviewed and modifications are made due to problems or new needs
Fine-tune and do post-implementation review
Operate sys
Modify sys
Do ongoing maintenance
Deliver improved sys
People involved
Management
Users
Info sys steering committee ISSC
Project development team
System analysts and programmers
External players
Planning
Project development plan
:
Prepared by project team
contains a cost–benefit analysis, developmental and operational requirements and a schedule of the activities required to develop and operate a
SPECIFIC PROJECT
Long-range Master Plan
:
-Prepared by ISSC
specifies what the system will consist of, how it will be developed, who will develop it, how needed resources will be acquired, and where the AIS is headed
Outline prioritized projects & timetables
Techniques
PERT: Program evaluation and review technique
Diagram
Depicts all project activities that require time and resources
with completion estimates
depicts precedent and subsequent relationships among activities
Critical path: if delayed, the whole project is delayed
Grantt chart
bar chart with
project activities on the left-hand side
units of time across the top
thus, defining the expected project completion time
(+): viualise
(-): doesnt show rela between activities
Feasibility analysis
: an investigation to determine whether it is practical to develop a new sys
Economic feasibility
Legal feasibility
Technology feasibility
Scheduling feasibility
Operation feasibility
Capital budgeting
Behavioral challenges
Why problems occur?
Fear
Top-management support
-Experience with prior change
Communication
Disruptive nature of change
Manner in which change is introduced
Biases and emotions
Personal characteristics and background
Resistance
Aggression
Projection
Avoidance
Prevention
Obtain management support
Meet user needs
Involve users
Allay fears, and stress new opportunities
Avoid emotionalism
Provide training
Reexamine performance evaluation
Keep communication lines open
Test the system
Keep the system simple, and humanize it
Control users’ expectations
