Just need this added to document attached. Basically finish it. Also added the
Assignment
For this assignment, you will develop 3 proposals for your development strategy, which include outsourcing (buy), insourcing (make), or a combination of both. You will present the pros and cons of each, along with a financial analysis. Finally, you will make a recommendation on which is the best proposal or strategy.
The project deliverables are as follows:
- Update the System Requirements, Design, and Implementation Specification title page with the new date.
- Update the previously completed sections based on the instructor’s feedback.
- Development Strategy
- Develop a proposal for each of these approaches: insourcing, outsourcing, and a combination of the two.
- Present the pros and cons or benefit analysis for each of the 3 proposals.
- Perform a financial analysis of the total costs for each proposal that includes ongoing support and maintenance.
- Recommend 1 of these proposals and your reason for selection of that proposal.
- Remember that this document should contain all of the sections from Weeks 1–4.
Instructions:
New content should include the following items:
Development Strategy
- A proposal with 3 approaches for development strategy: insource, outsource and a hybrid combination of the two.
- Present the pros and cons for each approach including a benefits analysis.
- A cost analysis for each of the 3 proposals.
- A summary with a recommendation for 1 of these proposals to be adopted for the student’s project.
- The development strategy document shows an example of the above proposals.
The report should be formatted according to APA guidelines.
Grammar, spelling, punctuation, and format should be correct and professional.
This should include updates based on feedback from the instructor and made during the peer review.
Part 2 should contain the work breakdown structure (WBS) for the 7 system development life cycle (SDLC) phases and activities under each phase, similar to some of the following:
- Preliminary Analysis or Systems Planning
- 1.1 Define mission, objectives, and purpose for system
- 1.2 Develop detailed problem statement
- 1.3 Describe current state
- 1.4 Identify benefits for new system
- 1.5 Identify scope, risks, and constraints
- 1.6 Feasibility study
- 1.7 Analyze formal system request
- 1.8 Receive approval to go to next phase
- System Analysis and Requirements Definition
- 2.1 Requirements gathering
- 2.2 Conduct interviews
- 2.3 Surveys
- 2.4 Document observations
- 2.5 Sampling
- 2.6 Review of artifacts
- 2.7 Build business, data, process, and object models
- 2.8 Conduct requirements reviews
- 2.9 Generate system requirements specification document
- System Design
- 3.1 Develop physical model
- 3.2 Design user interface
- 3.3 Identify inputs, outputs, and processes
- 3.4 Design internal and external controls
- 3.5 Design features and functions
- 3.6 Determine application architecture
- 3.7 Conduct design reviews
- 3.8 Develop final system design specification
- Development
- 4.1 Develop or code all components based on design
- 4.2 Prototype components
- 4.3 Conduct usability tests
- 4.4 Design test for all other types of testing
- 4.5 Unit test and fix errors
- Integration and Testing
- 5.1 Determine conversion activities
- 5.2 Determine training activities
- 5.3 Conduct testing activities
- 5.4 Fix any errors that occur during the test
- 5.5 Determine transition plan
- 5.6 Develop a back-out and recovery plan
- Acceptance, Installation, and Deployment
- 6.1 Install any required software and hardware for production environment
- 6.2 Validate that system is functioning correctly
- 6.3 Conduct stress or volume tests
- 6.4 Perform conversions and transitions
- 6.5 Receive approval for going live
- 6.6 Go live or perform back-out and recovery
- 6.7 Close out any contracts and end project
- 6.7 Conduct a post mortem or lessons learned
- Operation Support and Maintenance
- 7.1 Train all support personnel
- 7.2 Establish all information technology (IT) security infrastructure
- 7.3 Transition to operations and maintenance mode
- 7.4 Ensure that the system is meeting service level agreement (SLA) goals


0 comments