Software Process Models 2 Eng 29
Software Process Models 2 Eng 29
Software Process Models 2 Eng 29
co
1 | Page
www.gradeup.co
Software Process Models 2:
Content :-
1. Project Management
3. Extreme Programming
8. Scrum
9. Web engineering
1: Project Initiation
The start of the project, and the goal of project is to define the project at
a broad level. This phase usually begins with a business case. This is when you
will research whether the project is feasible and undertaken.
2 | Page
www.gradeup.co
2: Project Planning
This phase is key to successful project management and focuses on developing
a roadmap that each will follow. This phase typically begins with setting goals.
3: Project Execution
The phase where deliverable are developed and completed. This feels like the
meat of the project since a more is happening during a time, like status reports
and meetings, development updates, and performance reports.
4: Project Performance/Monitoring
This is all about measuring project progression and performance and ensuring
that everything happening aligns with the project management plan. Project
managers will use key performance indicators to determine if the project is on
track.
5: Project Closure
This phase represents the completed project. Contractors hired to work
specifically on the project are terminated at this time. Valuable team members
are recognized.
It considers that code scattering and tangling are the symptoms of crosscutting
concerns.
3 | Page
www.gradeup.co
Extreme Programming:It is a software development methodology which is
intended to improve software quality and responsiveness to changing customer
requirements. It takes its name from the idea that the beneficial elements of
traditional software practices are taken to "extreme" levels.
• Planning
• Requirements Analysis
• Design
• Coding
• Unit Testing and
• Acceptance Testing.
Agile model believes that every project needs to be handled differently and the existing
methods need to be tailored to best suit the project requirements. In Agile, the tasks are
divied to time boxes (small time frames) to deliver specific features for a release.Iterative
approach is taken and working software build is delivered after each iteration. Each build
is incremental in terms of features; the final build holds all the features required by the
customer.
4 | Page
www.gradeup.co
The Agile thought process had started early in the software development and started
becoming popular with time due to its flexibility and adaptability.
Advantages are:
Disadvantages are:
5 | Page
www.gradeup.co
1. Requirements gathering: In this, user must define the requirements. User should explain
business opportunities and plan time and effort needed to build the project. Depend on this
2. Design the requirements: When you have identified the project, work with stakeholders to
define requirements.
3. Construction/ iteration: When the team defines the requirements, the work begins. Designers
and developers start working on their project, which goals to deploy a working product. The
product will undergo some stages of improvement, it includes simple, minimal functionality.
4. Testing: In this phase, the Quality Assurance team examines the product's performance
5. Deployment: The team issues a product for the user's work environment.
6. Feedback: After producing the product, the last step is feedback, the team receives feedback
6 | Page
www.gradeup.co
It replaced the waterfall cycle with a repeating series of speculate,
collaborate, and learn cycles. Cycle provides for continuous learning and
adaptation to the emergent state of the project.
The focus of this is in the computer code. Instead of planning the program
out before hand, developers have a basic idea in their heads and they go to
work. If software needs a patch, somebody just makes it.
• Transparency
• Inspection
• Adaptation
Principles:
• Control over the empirical process. Transparency, checking, and adaptation carry
the whole its methodology.
• Self-organization.
• Collaboration.
7 | Page
www.gradeup.co
• Value-based prioritization.
• Timeboxing.
• Iterative development.
8 | Page
www.gradeup.co
Web Engineering: It is the application of systematic, disciplined and quantifiable
approaches to development, operation, and maintenance of Web-based
applications. Both pro-active approach and a growing collection of theoretical and
research in Web application development.
It is basically all about designing and promoting web based systems. “The
project of systematic and quantity approaches to cost-effective analysis, design,
implementation, testing, and maintenance of high-quality Web applications.
It is concerned with the developed and use of sound scientific, engineering, and
management principles and disciplined and systematic approaches to the
successful development, deployment, and maintenance of high quality Web-based
systems and applications.
9 | Page
www.gradeup.co
10 | P a g e