Research best practices for system integration approaches, such as the following
ID: 3715181 • Letter: R
Question
Research best practices for system integration approaches, such as the following approaches:
Systems development life cycle (SDLC) approach
Migration strategy and implementation approach
Acquisition utilizing requests for proposals
Others of your choice
Select 2 of the best practice approaches, and discuss how they support responding to professional and ethical issues potentially impacting your integration project.
Provide specific examples of how the application of best practices for system integration impact project success.
Explanation / Answer
1. Agile
The Agile model has been around for about a decade. But lately, it has become a major driving force behind software development in many organizations. Some businesses value the Agile methodology so much that they are now applying it to other types of projects, including non-tech initiatives.
In the Agile model, “fast failure” is a good thing. The approach produces ongoing release cycles, each featuring small, incremental changes from the previous release. At each iteration, the product is tested. The Agile model helps teams identify and address small issues on projects before they evolve into more significant problems, and engage business stakeholders and get their feedback throughout the development process.
As part of their embrace of this methodology, many teams are also applying an Agile framework known as Scrum to help structure more complex development projects. Scrum teams work in “sprints,” which usually last two to four weeks, to complete assigned tasks. Daily Scrum meetings help the whole team monitor progress throughout the project. And the ScrumMaster is tasked with keeping the team focused on its goal.
The agile software development emphasizes on four core values.
1. Individual and team interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan
There are 6 phases available in Agile XP method, and those are explained as follows:
Planning
1.Identification of stakeholders and sponsors
2.Infrastructure Requirements
3.Security related information and gathering
4.Service Level Agreements and its conditions
Analysis
1.Capturing of Stories in Parking lot
2.Prioritize stories in Parking lot
3.Scrubbing of stories for estimation
4.Define Iteration SPAN(Time)
5.Resource planning for both Development and QA teams
Design
1.Break down of tasks
2.Test Scenario preparation for each task
3.Regression Automation Framework
Execution
1.Coding
2.Unit Testing
3.Execution of Manual test scenarios
4.Defect Report generation
5.Conversion of Manual to Automation regression test cases
6.Mid Iteration review
7.End of Iteration review
Wrapping
1.Small Releases
2.Regression Testing
3.Demos and reviews
4.Develop new stories based on the need
5.Process Improvements based on end of iteration review comments
Closure
1.Pilot Launch
2.Training
3.Production Launch
4.SLA Guarantee assurance
5.Review SOA strategy
6.Production Support
2. Waterfall
Some experts argue that the Waterfall model was never meant to be a process model for real projects (check out the discussion on this topic on StackExchange). Regardless, the Waterfall model is widely considered the oldest of the structured SDLC methodologies. It’s also a very straightforward approach: finish one phase, then move on to the next. No going back. Each stage relies on information from the previous stage and has its own project plan.
The downside of Waterfall is its rigidity. Sure, it’s easy to understand and simple to manage. But early delays can throw off the entire project timeline. With little room for revisions once a stage is completed, problems can’t be fixed until you get to the maintenance stage. This model doesn’t work well if flexibility is needed or if the project is long term and ongoing.
Even more rigid is the related Verification and Validation model — or V-shaped model. This linear development methodology sprang from the Waterfall approach. It’s characterized by a corresponding testing phase for each development stage. Like Waterfall, each stage begins only after the previous one has ended. This SDLC model can be useful, provided your project has no unknown requirements.
Waterfall Model - Application
Every software developed is different and requires a suitable SDLC approach to be followed based on the internal and external factors. Some situations where the use of Waterfall model is most appropriate are ?
Requirements are very well documented, clear and fixed.
Product definition is stable.
Technology is understood and is not dynamic.
There are no ambiguous requirements.
Ample resources with required expertise are available to support the product.
The project is short.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.