Class Notes (1,100,000)
CA (650,000)
UW (20,000)
AFM (1,000)
AFM341 (40)
Lecture 3

AFM341 Lecture 3: Intro to Systems Development


Department
Accounting & Financial Management
Course Code
AFM341
Professor
Alec Cram
Lecture
3

This preview shows pages 1-2. to view the full 6 pages of the document.
Class 3: Intro to Systems Development
1
Class Summary
● The SDLC provides a structured set of steps to aid companies in designing and building systems
● IT projects have a high failure rate, but managers can adopt strategies to mitigate the risks
● Waterfall and agile are two systems development methodologies that guide project teams
through the day-to-day activities of systems development
Managing IT Changes
● In order to guide employees though the design and implementation of IT systems, organizations
undertake a series of steps referred to as the systems development life cycle:
β—‹ Systems analysis: Gathering information, setting project goals, and determining system
requirements.
β—‹ Conceptual design: Describing the desired features and operations of the system
including screen layouts, business rules, and process diagrams.
β—‹ Physical design: Taking all of the detailed design documents and transforming (e.g.,
coding, testing) them into the actual system.
β—‹ Implementation and conversion: Placing the system into production so users can begin
to perform actual business operations with the system.
β—‹ Operations and maintenance: Performing changes, corrections, additions, and upgrades
to ensure the system continues to meet the business goals.
Who is Involved in the SDLC?
● Information Systems Steering Committee: Executive level, plans and oversees IS function;
facilitates coordination with integration of systems activities
● Project Development Team: Plan and monitor project progress
● Programmers: Write and test programs according to analysts specifications
● Systems Analysts: Determine information needs, prepare specifications for programmers
● Management: Get users involved in the process, provide support for development projects,
align projects to meet organizations strategic needs
● Users: Communicate needs to system developers, help design and test to ensure complete and
accurate processing of data
Systems Development Planning
● Proper planning provides for achieving goals and objectives
● Two types of plans are often used in systems development projects:
β—‹ Project Development Plan: Specific to a project and authored by the project team
identifies people, hardware, software, and financial resources needed
β—‹ Master Plan: Long-range and authored by steering committee outlining prioritized
projects and timetables

Only pages 1-2 are available for preview. Some parts have been intentionally blurred.

2
● A variety of tools can aid in the systems planning process, including:
β—‹ Program evaluation and review technique (PERT):
Diagram that depicts all project activities that
require time and resources with completion
estimates.
β—‹ Gantt chart: Bar chart that organizes activities on
the left hand side and project time scheduled with a
bar drawn to show the progress to date for that
particular activity.
Business Case (Feasibility Analysis)
● Economic - Do benefits of new system justify the costs (time and resources) to implement?
● Technical - Can we use existing technology?
● Legal - Does a new system comply with regulations, laws, and contractual obligations?
● Scheduling - Can the system be developed in the time allotted?
● Operational - Do we have the people to design and implement the system? Will people use the
new system?
Capital Budgeting
● Payback period - Calculate the number of years required for the net savings to equal the initial
cost of investment
● Net Present Value (NPV) - Estimate future cash flows with discounted rate for time value of
money
● Internal Rate of Return (IRR) - Calculates the interest rate that makes the present value of total
costs equal to the present value of total earnings
Managing IT Changes
● In 2018, about $3.65 trillion was spent on IT (Gartner), including devices, data center
equipment, enterprise software, and IT services.
● However, only about a third of such IT projects are seen to fully succeed.
The Triple Constraint
● Common reasons why IT projects fall behind schedule
Makes an IT Project Risky?
You're Reading a Preview

Unlock to view full version