Software engineering
Process models
Pavel Agejkin
Software engineering layers
Generic process framework activities
• Communication
• Planning
• Modeling
• Construction
• Deployment
Umbrella activities
• Software project tracking and control
• Risk management
• Software quality assurance
• Technical reviews
• Measurement
• Software configuration management
• Reusability management
• Work product preparation and production
General principles
• The Reason It All Exists
• KISS (Keep It Simple, Stupid!)
• Maintain the Vision
• What You Produce, Others Will Consume
• Be Open to the Future
• Plan Ahead for Reuse
• Think!
Generic process model
• Linear process flow
• Iterative process flow
• Evolutionary process flow
• Parallel process flow
Waterfall Model
Incremental Process Model
Evolutionary Process Models : Prototyping
Evolutionary Process Models : Spiral Model
Evolutionary Process Models : Spiral Model
Specialized Process Model
• Component-Based development
• Formal Methods Model
• Aspect-Oriented Software Development
Unified Process
Personal Software Process (PSP)
• Planning
• High-level design
• High-level design review
• Development
• Postmortem
Team Software Process (TSP)
• Project launch,
• High-level design
• Implementation
• Integration and test
• Postmortem
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
That is, while there is value in the items on the right, we value the
items on the left more.
Change cost vs time in development
Agility principles
• 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
• 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
• 4. Business people and developers must work together daily throughout the project.
• 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• 7. Working software is the primary measure of progress.
• 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace
indefinitely
• 9. Continuous attention to technical excellence and good design enhances agility.
• 10. Simplicity—the art of maximizing the amount of work not done—is essential.
• 11. The best architectures, requirements, and designs emerge from self– organizing teams.
• 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
Human factors
• Competence
• Common focus
• Collaboration
• Decision-making ability
• Fuzzy problem-solving ability
• Mutual trust and respect
• Self-organization
Extreme Programming (XP)
Values:
• Communication
• Simplicity
• Feedback
• Courage (discipline)
• Respect
Industrial XP ( IXP)
Feature Driven Develoment
Scrum
Kanban