1. Identify and select the system for development.
2. Assess project feasibility.
3. Develop the project plan. the most critical phase
1. Gather business requirements.
2. Create process diagrams.
3. Perform a buy versus build analysis.
1. Design the IT infrastructure.
2. Design system models. creating blueprints
1. Develop the IT infrastructure.
2. Develop the database and programs.
1. Write the test conditions.
2. Perform the system testing.
1. Write detailed user documentation.
2. Determine implementation method.
3. Provide training for the system users.
involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet the business goals most expensive and long phase 1. Build a help desk to support the systemusers. 2. Perform system maintenance.
3. Provide an environment to support system changes.
cost of system failure
increase/decrease revenue, repair or damage reputation, prevent or incur liabilities, increase/decrease productivity
reliable, good timing - benchmark for system success
keep costs and development times low - benchmark for system success
needs to be able to expand - benchmark for system success
sequential, activity based process in which each phase of SDLC is performed sequentially
rapid application development (rad)
emphasizes user involvement / creating a prototype, involve system users, accelerated collection of business requirements
extreme programming (XP)
breaks project into tiny, sequential phases / each phase gets user feedback (like a jigsaw puzzle)
(form of XP) gets user feedback/customer satisfaction. less focus on team coding and more on limited project scope - fast, efficient, small, low cost, fewer features, shorter projects
information technology infrastructure library
a framework of best practice approaches intended to facilitate the delivery of high quality IT services (management procedures)
-slash the budget - if it doesn't work, kill it - keep requirements to a minimum - test and deliver frequently - assign non IT executives to software projects
time cost scope
three factors that affect the quality of a project - people use software to help manage their projects because it is so important
feasibility - financial benefits and costs
feasibility - examines all potential legal and contractual ramifications of the proposed system
feasibility - examines the likelihood that the project will attain its desired objectives
feasibility - assesses the likelihood that all potential time frames and completion dates will be met
feasibility - determines the organizations ability to build and integrate the proposed system
two ways to train users
discard old system and use new system
introduce the new system in phases
small group uses the new system and then everyone else uses it afterward
use both old and new systems until the new one works
choosing strategic projects
focus on organizational goals - categorize projects - perform financial analysis
set project scope
define the work that must be done to deliver the product with the specified features and functions
easy to read/understand, communicated, appropriate to objectives, prepared by a team - use PERT or GNATT charts
a set of techniques that aid in evolution, composition and policy management of the design and implementation of a system - change management control board
process of proactive and ongoing identification, analysis, and response to risk factors
promote leadership skills, learn form experience, share knowledge, create a project management culture