Please enable JavaScript.
Coggle requires JavaScript to display documents.
SYSTEMS DEVELOPMENT AND SYSTEMS PRACTICE (SYSTEM ANALYSIS AND SYSTEM…
SYSTEMS DEVELOPMENT AND SYSTEMS PRACTICE
SYSTEM DEVELOPEMENT PROCESS
Solving
problems
Recognize & define a problem or opportunity using systems thinking
Develop & evaluate alternative system solution
Select the system solution that best meets your requirements
Design the selected system solution
Implement & evaluate the success of the designed system
Development
Approaches
Approaches to solving problems in systems
(SSADM)
System Engineering
Systems
Thinking
Thinking in big picture
• Looking into real world
• Modeling problem from different viewpoints
• Define root definition of relevant systems
SYSTEM ANALYSIS AND SYSTEM ENGINEERING
SSADM
systems approach to the analysis and design of information systems
It follows a waterfall model It
is built on top of different schools of structured analysis and development methods such as Peter Checkland’s Soft Systems Methodology, Larry Constantine's structured design, Edward Yourdon's Yourdon Structured Method, Michael A. Jackson's Jackson Structured Programming, and Tom DeMarco's structured analysis
“Structured” in two aspects:
a default structure of steps and tasks which the project team should consider
set of techniques to be applied in each step that provide (largely diagrammatic) structured definition of user requirements and system components.
framework
holistic thinking
evaluation system
Systems Engineering
V models
Information System Engineering
METHODOLOGY AND SYSTEM PRACTICE
General Objectives
Methodology Benefits
Scope of Methodology
Sources
purchasable product, licence product subset of CASE or 4GL
Costs
purchasable product, licence product subset of CASE or 4GL
Success not guaranteed
Repeatability is acid test of a methodology
Systems Practice
Custom
Subset of some standard
Packaged methodology
Manuals, training, CASE support, forms, templates
None (Most companies do not use any methodology)
Issues in System Practices
Initial effort on tangible ‘hard’ aspects such as program code and data structures but omitting the resources (people, money and equipment
Miscomunication between individuals, team, customers, and organization during development phase
Resolving application backlog
Management attitude towards application of methodology
