Please enable JavaScript.
Coggle requires JavaScript to display documents.
01 Software Development Lifecycle (SDLC) (Roles and their relationship…
01
Software Development
Lifecycle (SDLC)
Roles and their
relationship to phases
Project management
Business analysis
Systems architecture
Programming
Testing
Config management and change control
Quality control and quality assurance
Service management
Activities / Deliverables
for each phase
Maintenance
How to guides
Completed tickets
Testing
Test plans
Tested system
Design
Technical specification
Logical and physical designs
Feasibility study
High level plan
Business case
project brief / charter / initiation / scope
Terms of reference
System scope / requirements
Requirements analysis
Requirements report
Threats and risks report
Recommendations
Development
Database
Developed system
Code / screens / reports
Interfaces
Implementation
Training procedure
Implemented system
User documentation
Support capabilities
Terminology
Systems Development
: business requirements -> structured stages -> operational IT system
Systems Development Lifecycle
: process to understand, plan, build, test and deploy an information system
Phases
Feasibility study
Depends on size / complexity of project
Benefits / likelihood of success
Funding
Resources / cost vs value
Business case
ROI
Requirements analysis
Manage requirements
Business needs
Elicit, analyse, document, validate requirements
Level of detail (SDLC)
Design
Possible solutions
Elaborate detail
Code development
Crate or buy components (hw / sw)
Follows design
AKA programming or build
Testing
Test components against design
Levels of testing
Unit testing
Integration testing
System testing
User acceptance testing
Deployment / implementation
Commission to live environment
Use test or staging environment first
Maintenance
Corrective (20%) and enhancement (80%)
Maintenance types
Corrective
Adaptive
Perfective
Preventative
Other elements
influencing the
approach used
within SDLC
Context
Requirements stable or changing?
Need for audit, quality or regulatory approval?
Big bang or phased release?
Team skills, expertise and preferred delivery style
Location of development teams and key stakeholders
New or existing technology?
Complexity of system?
Lifecycle
stages
Linear approach?
Evolutionary approach (agile)?
Processes
needed
Mandated by SDLC
Mix-and-match approach?
Roles needed
or available
Business (sponsor, business analyst, domain expert, end users)
Project (project manager, team leader, package manager)
Technical (technical architect, solution developer, tester)
Implementation support (release manager, DB admin, sys admin)
Deliverables
required
Requirements documents
Models (class, use case, process, state, sequence, components)
System components and working software
Test plans, test scripts
Implementation plans
Technique
influences
MoDAF for military
Rapid prototyping or test-driven development
Payment milestones, formal sign-off, review dates
Experience in UML
Formal standards or procedures for organisation
Diagram (c) 2018 Andrew Burgess
QA Apprenticeships