Chapter 6:Systems Development
Steps, Tools, and Techniques
Management Information Systemsfor the Information Age
Chapter 6: Systems Development Slide 2
Visual Map of Chapter 6
KW & RolesKW & RolesIn SDLCIn SDLC
7 Phases7 PhasesOf SDLCOf SDLC
PrototypingPrototyping
SourcingSourcing- In- In- Self- Self- Out- Out
Why SystemsWhy SystemsFail ?Fail ?
PlanPlan AnalyzeAnalyze DesignDesign DevelopDevelop TestTest ImplementImplement MaintainMaintain
KW = Knowledge WorkersKW = Knowledge Workers SDLC = Systems Development Life CycleSDLC = Systems Development Life Cycle
SystemsSystemsDevelopmentDevelopment
Chapter 6: Systems Development Slide 3
Systems Development Life Cycle
The SDLC provides a structured step-by-step approach for creating information systems
Not all real-life development projects follow the SDLC and, as a result, experience high failure rates
Chapter 6: Systems Development Slide 4
SDLC: 1. Plan
ObjectiveObjectiveTo determine a solid and practical plan for developing a new information system
ActivitiesActivitiesDefine the system to be developed (CSFs)Set the project scope and boundariesDevelop the project plan including tasks, people, resources, and time frames
Treat as a living document (continually updated)Project manager sets and tracks milestone dates
Chapter 6: Systems Development Slide 5
SDLC: 2. Analysis
ObjectiveObjectiveTo comprehend the business problem or opportunity and to specify the business requirements for the proposed system
ActivitiesActivitiesGather the business requirements—detailed set of requests from knowledge workers and the actual users of the system
But no details generated on potential technologies or how the system will meet the requirements
Write a Functional Specification document
Chapter 6: Systems Development Slide 6
SDLC: 3. Design
ObjectiveObjectiveTo design a technical blueprint showing how the system will achieve the requirements outlined in the Functional Specifications document
ActivitiesActivitiesIdentify the technical architecture (hardware, software, and telecommunications equipment) required to support the proposed systemDesign system models (DFDs, ERDs, & GUIs) Write a Technical Specification document
Chapter 6: Systems Development Slide 7
SDLC: 4. Develop
ObjectiveObjectiveTo build the new information system (physical components) based on the functional and technical specifications (logical requirements)
ActivitiesActivitiesBuild the technical infrastructure, including sourcing and installing hardware systems and telecommunications equipmentCreate the database and programs, including coding and programming software systems
Chapter 6: Systems Development Slide 8
SDLC: 5. Test
ObjectiveObjectiveTo verify that the system successfully solves the problem, meets the opportunity, and/or achieves the business requirements specified
ActivitiesActivitiesWrite the test conditions
Document the detailed steps and expected results
Perform testing on the systemComponent (Unit), Interface (Integration), System (Whole Unit), User Acceptance (Requirements), Usability (GUI), and Release testing
Chapter 6: Systems Development Slide 9
SDLC: 6. Implement
ObjectiveObjectiveTo distribute the completed information system to all knowledge workers for everyday use
ActivitiesActivitiesProvide training for the system users
Instructor-led workshopsJust-in-time learning via Internet and CBT
Write detailed user documentationUses results from user and usability testingOften based on functional specifications document
Chapter 6: Systems Development Slide 10
SDLC: 7. Maintain
ObjectiveObjectiveTo monitor and support the information system to ensure that it continues to meet the business requirements of its knowledge workers
ActivitiesActivitiesBuild a help desk to support the users of the systemProvide an environment that supports system changes and adaptation
Chapter 6: Systems Development Slide 11
What Is Your Role in the SDLC?
Business Process ExpertYou know how the business works
Customer LiaisonYou know how to meet the customer’s needs
Quality Control AnalystYou need to keep the team focused and on track
ManagerYou need to ensure the system improves productivity for your team
Chapter 6: Systems Development Slide 12
How Are IS/IT Projects Unique?
People20:1 productivity difference in programmers
1 brilliant member worth more than 100 others2-guys-in-a-garage issue
Cost to change a line of code is up to 100x the cost to generate it in the first place
ProductivityTechnology changes every 12-18 months
TechnologyDoes all this technology pay for itself?More now means even more later
Chapter 6: Systems Development Slide 13
Why Do IS/IT Projects Fail?
Only 20% of IS projects are successfulReasons for Failure1. Incorrect, unclear, or missing
requirements2. Fast-tracking or skipping SDLC phases3. Failure to manage the scope
Scope Creep and Feature Creep
4. Failure to manage the projectProject plan is a living document that must be monitored, revised, and updated continuously
5. Changing technology architectures
Chapter 6: Systems Development Slide 14
What Do Errors Really Cost?
It’s far cheaper to find an error during the planning or analysis phase than it is to find the same error during the implementation or maintenance phase.
Chapter 6: Systems Development Slide 15
Project Management 101
Microsoft Project lets you define tasks, specify timeframes to completion, and assign resources. It then draws a structured GANTT chart, so you can map and track key milestone dates.
Chapter 6: Systems Development Slide 16
Who Is Going to Build It?
In-sourcingUsing IT specialists within your company
Self-sourcingUsing your own skills (or those of other knowledge workers and end-users)
Out-sourcingUsing external employees, from another company, or specialist contractors
Chapter 6: Systems Development Slide 17
Insourcing
AdvantagesAdvantagesTypically cheapest approachPersonnel is familiar with business processes, activities, and company structurePromotes “buy-in” if people who will use the system had a hand in creating it
DisadvantagesDisadvantagesCompany may not have the technical expertiseDifficult to fully commit resources to long-term projects; who handles the operational sideCan you ensure staff isn’t transient?
Chapter 6: Systems Development Slide 18
Selfsourcing
AdvantagesAdvantagesYou know what you need and want better than anyone elseSense of pride and ownership over the systemIterative model design moves quite quickly
DisadvantagesDisadvantagesTakes time away from you doing other tasks—the ones you have been hired to performYou may lack the technical expertiseOften users do not effectively test, document, or support their own creations
Chapter 6: Systems Development Slide 19
Outsourcing
AdvantagesAdvantagesYou can focus on your core competenciesExploit external intellect, expertise, and ITBetter predict timelines and reduce costs
DisadvantagesDisadvantagesLimits your technical know-how for making future enhancements and modificationsReduces your degree of control (dependency)You may need to turn over sensitive dataYou must create a detailed and binding RFP
Chapter 6: Systems Development Slide 20
Outsourcing Software Development
Chapter 6: Systems Development Slide 21
Prototyping
ObjectiveObjectiveTo build a model that demonstrates the features of a proposed product, service, or system
AdvantagesAdvantagesInvolves users and lets them see, touch, work with, and evaluate an inexpensive modelGood for gathering and refining requirementsProves that a plan is technically feasible
Proof-of-Concept prototype
Helps to sell the concept of a proposed systemSelling prototype
Chapter 6: Systems Development Slide 22
SDLC Summary