chapter 11
DESCRIPTION
CHAPTER 11. Systems Development and Project Managmenet. Introduction to the Systems Approach. It’s methodology for problem solving The more time spent planning, the better the outcome Note the process is typically iterative Systems approach masters Ed Yourdon Grady Booch The GOF - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/1.jpg)
CHAPTER 11
Systems Development and Project Managmenet
![Page 2: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/2.jpg)
Introduction to the Systems Approach
It’s methodology for problem solving The more time spent planning, the better
the outcome Note the process is typically iterative Systems approach masters
Ed Yourdon Grady Booch The GOF
Gamma, Helm, Johnson, Vlissides
![Page 3: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/3.jpg)
The Systems Approach (Steps)
Problem identification (planning) Systems analysis Systems design Systems development Systems testing Systems deployment
(implementation) Systems maintenance
![Page 4: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/4.jpg)
The Systems Approach (Problem Identification)
An existing system does not meet a need or expectation
Conduct feasibility studies If a project seems feasible, assemble a
project management plan and team
![Page 5: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/5.jpg)
The Systems Approach (Feasibility Domains)
Organizational Do we have the human resources Do we have the organizational resources
Technical Does the hardware / software exist
Economic Cost / benefit analysis Accounting ROI Present value analysis
Operational
![Page 6: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/6.jpg)
The Systems Approach (Systems Analysis)
Analyze information needs of constituents
Develop a system’s functional requirements
Analysis tools Brainstorming Lateral thinking
![Page 7: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/7.jpg)
The Systems Approach (Systems Analysis)
Develop a list of functional requirements User interface requirements Processing requirements Storage Controls
Input validationEvent notificationHuman controls
![Page 8: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/8.jpg)
The Systems Approach (Systems Design)
We need to completely understand the existing system If it’s not broke, don’t fix it Understand how users use the existing
system Interviews
Know what users want out of the new system
At times, users don’t know what they want
![Page 9: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/9.jpg)
The Systems Approach (Systems Design)
Logical design Design how the system will work Design workflow and information flow Design the user interface
Screen diagramsNavigation diagramsAppropriate use of color
Data designEntity relationship diagrams
![Page 10: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/10.jpg)
The Systems Approach (Systems Design)
Process design Tools
Flowcharts IP charts UML use-case diagrams UML activity diagrams UML Statechart diagrams
![Page 11: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/11.jpg)
The Systems Approach (Systems Design)
Physical design Select physical hardware and software Note that there may be site preparation
requirements
![Page 12: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/12.jpg)
The Systems Approach (Development)
Hardware and software acquisition Use RFPs and RFQs to evaluate alternatives Hardware and software benchmarking
Decisions Make vs. buy Lease vs. buy Internal implementation or outsourcing
Documentation For users For IS staff
Preserve organizational memory
![Page 13: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/13.jpg)
End User Development
Positives Users get what they want
Negatives Users don’t know what they want Users may have a narrow minded vision of the
system They may not see how a system contributes
to the organizational mission Loss of centralized control Users are not experienced in system design
methodologies
![Page 14: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/14.jpg)
Testing
My rule is, you cannot ever test too much or be too thorough
http://video.google.com/videoplay?docid=2889527841583480458&q=pwnz
![Page 15: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/15.jpg)
The Systems Approach (Deployment)
User training Data conversion Systems testing
Parallel (run 2 systems at once) Pilot study (deploy in limited sited) Phased (deploy functionality in stages) Plunge (only fools rush in)
Systems deployment
![Page 16: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/16.jpg)
The Systems Approach (Maintenance)
Perform a postimplementation audit to determine whether goals were met
Revise system as necessary
![Page 17: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/17.jpg)
Development Methodologies (1)
Waterfall The systems lifecycle operates as a
sequence of states Sequential development
![Page 18: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/18.jpg)
Development Methodologies (2)
Agile processes and iterative development Break a large project into several small
projects Deliver results in small stages
![Page 19: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/19.jpg)
Development Methodologies (3)
Extreme programming It’s an agile methodology at its best Relies on close communication between
users and developers Relies on experienced developers Uses small incremental deliverables
![Page 20: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/20.jpg)
Development Methodologies (4)
Scrum delivers small software pieces every 30 days The term derives from the game of
rugby The development effort is monitored
and controlled daily Some organizations use a
combination of these methodologies
![Page 21: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/21.jpg)
Waterfall (Illustration)
![Page 22: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/22.jpg)
Scrum (Illustration)
![Page 23: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/23.jpg)
Successful Software Development Metrics
Control costs – Don’t keep throwing money at a bad project
Avoid scope creep and feature creep
Test and deliver Involve all constituents
![Page 24: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/24.jpg)
Project Management (Introduction)
We spend about $1 trillion on IT projects 3 out of 10 project fail One in four does not following business
rules and requirements
![Page 25: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/25.jpg)
Why Projects Fail
![Page 26: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/26.jpg)
Roles in Project Management
![Page 27: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/27.jpg)
Choosing Strategic Projects
Projects should match organizational goals
Projects should be prioritized Perform financial analysis to
determine the best projects
![Page 28: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/28.jpg)
Project Planning
Create a project charter which clearly lists Scope Objectives Constraints Assumptions
Create a project plan and timeline Pert and Gantt charts
![Page 29: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/29.jpg)
Project Outsourcing
We outsource to Tap into outside expertise Focus on core business goals rather
than develop extensive IT infrastructure Reduce head count and expenses Minimize technology investment Reduce cost
![Page 30: CHAPTER 11](https://reader030.vdocument.in/reader030/viewer/2022032806/5681349f550346895d9b961b/html5/thumbnails/30.jpg)
Types of Outsoucring
Onshore Nearshore Offshore