Please enable JavaScript.
Coggle requires JavaScript to display documents.
2 .Software Development process (Umbrella Activities (support activities),…
2 .Software Development process
Software Development Process
Component
Milestones
Measure progress
decision
achievement
Start/end of an activity
Artifacts/work product
Stakeholders
Core activities
Model/framework
Core Activities
Planning/Scope
Specification
Design
Implementation
Validation
Maintenance / Evolution
Umbrella Activities (support activities)
Project tracking and management
Risk Management
Quality Assurance/Management
Formal technical reviews
Measurement and reporting
Configuration management
Change management
Models/Frameworks
Sequential / Linear
Waterfall problems
Assumes that the requirements are well known before construction
Difficult to accommodate change
Doesn't really reflect how actual software development is done
Derived from a manufacturing mind-set
Limited customer insight
What if there are problems with the project?
Steps
s
Requirements definition
Implementation and unit testing
Integration and system testing
Operation and maintenacne
System and Software design
V Model
Incremental
Build software in pieces to achieve the final solution
each incremental is a subset of functionality
Each increment is fully tested and releable
Additional increments add more functionality towards the final solution
Delivers value early
Benefits:
cost of changing requirements is reduced
easier to get customer feedback on the development work that has been done
More rapid delivery and development of useful software to the customer is possible
Incremental development problems
The process is not visible
Software structure tends to degrade as new increments are added
Steps
Communication
planning
modeling (analysis and design)
Construction (code, test)
Deployment( delivery, feedback)
Iterative
Successive refinement
initial iteraction is incomplete
subsequent iterations add more detail
Start simple, expect change
good approach to find the right solution >> fail fast
Agile (is both incremental and iterative)
Scrum (30 days)
Focus on iterative development rather than specific agile practices
three phases
initial phase >> an outline planning phase
a series of sprint cycles, where each cycle develops an increment of the system
Sprint process
Meetings: Daily standup/ planning/ review/ retrospective
Self Organized
Timeboxed
Must be committed and focused to sprint goal
The project closure phase wraps up the project. completes required documentation
Roles
Product Owner
Scrum Master
Development team
benefit:
chunk
unstable requirements do not hold up progress
progress are visible
gain feedback / customers can see on time delivery
trust between customers and developers
XP
Customer is part of the team
Prototyping
Can be used in
Requirements
Designs
Testing
Process
Coomunication
Quick plan
Modeling quick design
Construction of prototype
Deployment delivery and feedback
Rational Unified Process
PSP/TSP