Please enable JavaScript.
Coggle requires JavaScript to display documents.
1 - Introducing Systems Development Controls - Coggle Diagram
1 - Introducing Systems Development Controls
Systems Development Life Cycle
Design review
Coding
Control specifications development
Add security requirements
Code review walkthrough
Functional requirements determination
List the specific system requirements: input, behavior, output
System test review
Conceptual definition
Very high-level statement of purpose
Stakeholders: developers, customers and management
Maintenance and change management
SDLC models
Waterfall model
It allows the developers to step back only one phase in the process
Spiral model
Use the waterfall model for each iteration leading to a new prototype
Agile software development
Emphasis on the needs of the customer
Methodologies
Scrum
Kanban
Lean
Rapid Application Development (RAD)
Agile Unified Process (AUP)
Dynamic Systems Development Model (DSDM)
Extreme Programming (XP)
Scaled Agile Framework (SAFe)
Essential SAFe
Teams work in Agile Release Trains with increments of 8-12 weeks
Large Solution SAFe
For vast systems requiring multiple ARTs
Portfolio SAFe
Configuration where strategic direction is translated into actionable items
Full SAFe
Combines the 3 above
Maturity models
Capability Maturity Model (SW-CMM, CMM, SCMM)
Level 3: Defined
Developers operate according to a set of formal, documented software development processes
Key processes
Organization Process Focus
Organization Process Definition
Training Program
Integrated Software Management
Software Product Engineering
Intergroup Coordination
Peer reviews
Level 4: Managed
Quantitative measures are used to gain a detailed understanding of the development process
Key processes
Quantitative Process Management
Software Quality Management
Level 2: Repeatable
Basic life cycle management process
Reuse of code in an organized fashion
Key processes
Requirements Management
Software Project Planning
Software Project Tracking and Oversight
Software Subcontract Management
Software Quality Assurance
Software Configuration Management
Level 5: Optimizing
A process of continuous improvement occurs
Key processes
Defect prevention
Technology change management
Process Change Management
Level 1: Initial
Hardworking people charging ahead in a disorganized fashion.
Little or no defined software development process
Software Assurance Maturity Model (SAMM)
Governance
Design
Implementation
Verification
Operations
IDEAL model
Establishing
Organization takes the general recommendations from the diagnosing phase and develops a specific plan of action that helps achieve those changes
Acting
Develop solutions and then tests, refines, and implements them
Diagnosing
Analyze the current state of the organization and make general recommendations for change
Learning
Continuously analyse efforts to determine whether it has achieved the desired goals.
Initiating
Outline the business reason behind the change
Build support for the initiative
Appropriate infrastructure is put in place