Please enable JavaScript.
Coggle requires JavaScript to display documents.
SYSTEM DEVELOPMENT AND PROGRAM CHANGE ACTIVITIES (SDLC 7 Phases (Phase l -…
SYSTEM DEVELOPMENT AND PROGRAM CHANGE ACTIVITIES
SDLC 7 Phases
Phase l - System Planning
Strategic System Planning- Involve allocation of system resource at macro level
Project Planning - allocate scarce resource to individual within the stragic plan framework
The steering committee should done the system planning
Responsibilities
Reviewing project and assign priorities
Budgeting fund for system development
Resolving conflict arise from system
Review the under development project's status
Determine to continue or terminate project throughout SDLC
Planning Technique
Gantt chart
Program evaluation and review technique (PERT)
Phase ll
System Analysis Report
Analyze
Gathering facts
Personal interviews
Reviewing key documents
Task participation
Observation
Do the survey
Phase lV
System Evaluation and Selection
Feasibility
Technical
Operational
Legal
Operational
Schedule
Perform Cost- Benefit Analysis
Identify Costs
Identify Benefits
Tangible
Increased Revenues
Increased sales within existing markets
Expansion into other markets
Cost redudtion
Labour reduction
Operating cost reduction
Reduced inventories
Less expansive equipment
Reduced equipment maintainance
Intangible
increased customer satisfaction
Improved employee satisfaction
More current information
Improved decision making
Faster response to competitor actions
More efficient operations
Better internal and external communications
Improved planning
Operational flexibility
Improved control environment
Compare cost and benefits
Prepare system selection report
Phase V
Detailed Design
Perform a System Design Walkthrough
Review System Documentation
Phase Vl
Application Programming and Testing
Program the application software
Select program language
Test the Application Software
Test Methodology
Testing Offline Before Deploying Online
Test Data
Phase Vll
System Implementation
Testing the Entire System
Documenting the System
Designer and Programmer Documentation
Operator Documentation
User Documentation
User Handbook
Tutorials and Help Features
Converting the Database
Converting to the New System
Cold Turkey Cutover
Phased Cutover
Parallel Operational Cutover
Postimplementation Review
Examples
Systems design adequacy
Accuracy of time, cost, and benefit estimates
Phase Vlll
System Maintenance
Formal process to accomodate changes to user needs
Maintenance can be extensive
Should be treated the same as new development
Phase lll
Two approaches of system design
The structured design approach
The objected oriented approach
The Role of Accountants
Provide Technical Expertise
Detailed design
Procedures
Rules
Convention
Failure to comply
Legal exposure for the firm
Comply
GAAP
GAAS
SEC regulations
IRS codes
Specify Documentation
Adequately documented
Verify Control Adequacy
Programmed or manual procedures
Control
Daily Operation
Special action
Precede, follow, or oversee routine processing
Project management Tools
Project milestone
Project deadline
Project schedule
Critical path
Resist to change
poor communication
disruption
bad prior experiences
manner changes
Lack of top management support
biases and emotion
Fear
personal character and background
Introduction
Reason to change or develop new IS?
Productivity gains
Competitive advantage
Growth
Downsizing
Improved business processes
Systems integration
Technological changes
Systems age and need to be replaced
Changes in user or business needs
Stories of LEGO Denmark
Current IS cannot keep up with rapid changes
Hold 8000 employees in 130 countries
Upgrade or new siystem?
IBM system
Qualitative value
Quicker responses
Better control
Quantitative value
Invest= 45 million , Benefit =150 million
Initiating systems development. Problem or benefit?
Desire to make more effective use of information
Organizational growth
Increasing competition
Merger or acquisition
Desire to exploit new opportunities
Change in market and external environment
Problems with existing system
New laws or regulations
Project Failure
Statistic
70% delivered late
54% over budget
75% not being used as it should be
66% unsuccessful
Causes
Expensive
Time consuming task
Difficult
Omit some steps in developing IS
The Systems Development Process
Activities=Interest to accountants and auditors
Formal and well controlled processes
Free from internal control weaknesses
A set of activities by which organizations obtains IT based IS
Participant in System Development
End Users
Stakeholders
Systems Professional
Parties Involved in SDLC
Project Development Team
Programmers
Information Systems Steering Committee
System Analysts
Management
Users
Information System Acquisition
Commercial Systems
Growth Factors
Growing demand from small business who can't afford in-house system
emergence of vendors who targeting their software use for particular types of business
Low cost compared to customized
trend of downsizing organizational units
moving toward distributed data processing
Types of Commercial System
Backbone Systems
basic system which are meant for further build
Vendor-Supported Systems
develop by vendors for client organisation
Turnkey Systems
System that are ready for implementation
Advantage
cost
cost spread across many users, hence lower cost com[ared to in-house
Realiability
less likely to have error as it is tested thoroughly befor release to customer
Implementation Time
can be implement immediately, users does not have to wait
Disadvatage
The Need for Customized Systems
in-house can produce application to exact specification of business
Maintenance
difficult to modify commercial software when the users need change in their system
Independece
firm dependent on the vendor for maintenance
risk of vendor will cease to support the system
Systems Development Life Cycle
involve problem solving process
alternative solution
understand what need to be done
select best solution
implement solution
identify problem
software development process
system maintenance began one 7 phases completed and system fully implemented
