Please enable JavaScript.
Coggle requires JavaScript to display documents.
IT Systems in an Organization - Coggle Diagram
IT Systems in an Organization
SDLC/Project Methodologies
PMBoK
Can be used to virtually manage any project not only software
Knowledge areas
Project Risk Management
Project Quality Management
Project Scope Management
Project Integration Management
Project Human Resources Management
Project Time Management
Project Cost Management
Project Procurement Management
Project Communications Management
Stages
Stage 3 - Launch or execution
Stage 1 - Conception and initialization
Stage 5 - Project close
Stage 2 - Definition and planning
Stage 4 - Performance and control
Waterfall
Highly time bound
Flows from analysis to initialization stage for the entire software on whole
Ensures that problems are found in analysis stage
Highly sturctured :
Due to being time bound its requirements are prone to changes by the time it has been finished
Lacks adaptability
Allows for long term planning
PRINCE2
Includes Project initiation document which contains the result of the analysis tasks
Stages
Starting up
Levels
Managing
Delivering
Directing
Delivering
Levels
Directing
Delivering
Managing
Final delivery
Levels
Delivering
Managing
Directing
Initiating
Levels
Delivering
Managing
Directing
Starts with an evaluation of benefits and challenges
Planning, Organization and Risk management are key features of this approach
Agile
Same stages as waterfall but it applies only to a small part of the software at a certain time.
Due to lack of order in progress causes difficulty in maintaining a project in long term.
Requires short period of time
Requires analyzation of a part of the problem and developing a solution. Making rapid production of working code.
Lacks initial goal and design for whole project, this causes less efficient designs
Easier to make changes
SSADM
Primary focus on Analysis and Design stages
Stages
Stage 7 - Physical design : Translation of design work into physical hardware and software specifications
Stage 2 - Investigation of the current environment : Creation of DFD and ERD diagrams of the current system and documentation of problems and inadequacies of current system in detail.
Stage 6 - Logical design : Identifying, modelling and documenting required data for the new system. Analogous to design stage in Waterfall method.
Stage 1 - Feasibility study : Examination of feasibility of project and possible solutions for the problem
Stage 3 - Business system options : Presentation of different options for business and cost/ benefit analysis of proposed systems
Stage 4 - Requirements Specification : Generation of detailed list of requirements. Representation of new systems via DFD and ERD diagrams with the help of investigation of old systems and definition of user roles.
Stage 5 - Technical system options : Consideration of hardware, software, network and personnel required for the proposed system
Software
Types of software
Off the shelf software - Used for general purposes sold by a vendor
Bespoke/ Custom software - Tailored according to the needs of the Organization
Changeover
Process of introducing a new system while retiring an old system
Direct changeover - New system is put in place immediately
Phased changeover - Gradual migration to the newer system
Parallel changeover - Introducing the new system while running the old system side by side
Virtual Machine
Creates a virtual computer
Independent of the host computer
Runs its own operating system and software
Emulator
Recreates entire system hardware
There may be performance issues
Legacy Systems
Run on older hardware or operating system
Replacement is not easily available
Manufacturer stopped support
Receive no updates and security fixes
No longer available for purchase
Is costly and hard to convert all the data into the newer systems
GANTT
PERT
ERD
DFD