Technical Standards Overview Technical standards are important to ensure that all development staff utilize the same technologies for consistency, maintenance, and support. By ensuring that all...

1 answer below »

Technical Standards


Overview


Technical standards are important to ensure that all development staff utilize the same technologies for consistency, maintenance, and support. By ensuring that all individuals follow a specific set of standards, development processes can be efficiently completed by many different individuals rather than having the dependency on a few.


In this assignment you complete SDP Section 6, Technical Standards, which is intended to provide developers a high-level view of technologies to be used.


Preparation



  • Review the CapraTek Overview found in the assignment Resources as required.

  • Save a new version of your SDP document using this unit number and use it to complete the assignment.


Directions


Consider the CapraTek scenario and address the items below in Section 6 of the CapraTek SDP document:



  • Create a technology stack component diagram showing where each technical operation is performed.

  • Describe the following components and justify why each is important for solving the identified technical challenges:

    • Servers: Describe the various types of servers that are appropriate for integration with the identified applications.

    • Development Software:Identify four development and support tools needed for software development that both address identified technical challenges and that interoperate with Java and .NET operations. Justify your choices.






IT3345 – Software Architecture Directions: Follow the courseroom directions and use this template to complete your assignments. The areas that you are responsible for are highlighted using blued text designated as . Do not change the font color. Save the document as CapraTek SDP – Unit “X” CapraTek Software Development Plan Version 1.0 Prepared by IT-FP3345 – Software Architecture Contents 1.Introduction4 1.1Identification4 1.2Scope and Purpose4 1.3System Level Project Description4 1.4System Description4 1.5Document Organization4 2.Resources and Scheduling6 3.Organization and Staffing7 4.Technical Management and Control (Section 4 has been pre-completed)8 4.1Change Management8 5.Standard and Procedures9 5.1Deliverable Standard9 5.2Process Methodology Diagram9 5.3Process Methodology Explanation9 5.4Phase Description9 6.Technical Standards10 6.1Technology Stack Diagram10 6.2Cloud Environment10 6.3Programming Languages10 6.4Servers10 6.5Databases10 6.6Development Workstations10 6.7Development Software11 7.Software Phases12 7.1Phase 1: Software Requirements12 7.2Phase 2: Software Design12 7.3Phase 3: Software Construction12 7.4Phase 4: Software Testing12 8.Verification and Validation13 9.Maintenance Process14 9.1Maintenance Plan Diagram14 9.2Maintenance Plan14 10.Human Factors (Section 10 has been pre-completed)15 10.1Training15 Software Development Plan for CapraTek Page 1. Introduction 1.1 Identification This Software Development Plan (SDP) establishes the plans to be used for CapraTek in all the organization’s software development projects. 1.2 Scope and Purpose Scope This Project involves developing an environment of software development by a company named Capera Tech using agile methodology. The software development process will consist of analysis(requirement gathering & feedback), design & development, test, integration and deployment . This is anticipated to complete the development of the desired software within allotted time and cost with optimum use of resources. Purpose The purpose of this project to fulfill business needs by providing a new experience to stakeholders. Business Challenge To avoid time and cost overrun. Ensure developed solutions must fulfill business needs. 1.3 System Level Project Description This SDP describes the organization and procedures to be used by CapraTek in performing software development. This plan identifies the applicable policies, requirements and standards for software development. It defines schedules, organization, resources, and processes to be followed for all software activities necessary to accomplish the development. 1.4 System Description This document serves as a reference for all CapraTek employees who have a stake in its requirements gathering, design, implementation, testing, deployment, and ongoing support, including system architects, developers, test engineers, support engineers, Operations, and Legal. This document covers multiple facets of the software application. 1.5 Document Organization The SDP is organized as follows. · Section 1 describes the introduction of the software development plan. It also provides an overview of the scope and objectives of the software development plan. · Section 2 describes the resources and scheduling of CapraTek. · Section 3 describes the organization and staffing of CapraTek. · Section 4 describes the process for change management at CapraTek. · Section 5 describes the Standards and Procedures including the process methodology to be used in CapraTek. · Section 6 describes the technical standards that will be used at CapraTek. This section is to be updated based on CapraTek’s needs. · Section 7 describes the software phases involved for each software development project. Each phase will include an activity diagram outlining what processes are completed at each phase with an explanation of each phase. · Section 8 describes the verification and validation process to ensure that the software delivered meets the needs and requirements of the project and is developed correctly. · Section 9 describes the maintenance process for developed software at CapraTek. · Section 10 describes the human factors, including training, of the delivered software projects. 2. Resources and Scheduling Agile methods involve a series of small iterative completed steps leading up to the end. In agile we focus on product rather than execution of the project plan itself. Work broken down into iterations (sprints) and resources assigned to these sprints. We have shorter planning cycles that leads to reduced up front planning and more resource flexibility. Organization and Staffing Manpower planning: Based on the inputs of the required department, a draft of a manpower planning sheet will be made by the project leader. Recruitment strategy-In this scenario, lateral recruitment will be better than campus hiring. Selection-It can be done through in-house search avenues like linkedin, monster.com or can be outsourced to any consultancy. We can assign specific, measurable, attainable, relevant and time bound targets and keep a check on target completion. Performance appraisal will be based on target completion and performance. 3. Technical Management and Control (Section 4 has been pre-completed) 3.1 Change Management Changes to any specifications at CapraTek will be done by submitting a change report. The approval of the change must be made by the project manager. All risks will be reviewed by the technical committee each month and formal risk reports will be submitted to the management team on a quarterly basis. All changes must incorporate a cost reports to be given to the financial committee each week for review by the project sponsor. All issues will be reviewed at the project management meeting. Issues that delay the development schedules will be resolved by the technical committee. 4. Standard and Procedures 4.1 Deliverable Standard All design deliverables will be submitted using standard UML using Visio. Alternative tools may be used pending approval from the development lead. All deliverables will be reviewed by all stakeholders before the final signature by the project manager. 4.2 Process Methodology Diagram Chosen Agile methodology: Software development process using Agile methodology 4.3 Process Methodology Explanation We have chosen an agile methodology for the software development process. Today software development markets are changing at a faster pace than ever before and it requires more agility than retrenchment. How can we handle changes in a rapidly changing software development industry? WIth agile methodology we can easily cope with these changes. 4.4 Phase Description Phase 1 - Analysis Requirement gathering, elicitation of information from stakeholders and prior information about the project. Phase 2 – Design & development Preparing wireframe of solution and reviewing wirefame. Design and development of Actual solutions. Phase 3 - Test Testing of sprints(solution), if any discrepancy is found then go to phase 1. Phase 4 - Integration Integration of current sprints(Iterations) to the other sprints. Expanded Phase Details . . 5. Technical Standards 5.1 Technology Stack Diagram 5.2 Cloud Environment Amazon Web Services will be used for CapraTek’s cloud deployment. Existing applications are already deployed on Amazon Web Services and it is simpler to keep all the technology here rather than deployed to another cloud provider such as Microsoft Azure or Google Cloud. 5.3 Programming Languages C#: C# is the primary language used to develop the applications for CapraTek. Using Microsoft Xamarin, developers will be able to deploy applications to iOS and Android using C#. ASP.NET: For web applications at CapraTek, they will be developed using ASP.NET. This will be used in conjunction with HTML5, CSS3 and JavaScript. Java: There are some existing legacy applications that use Java and will continue to be supported with Java. There are also various projects that require Java to be used due to existing libraries and code base with third parties. 5.4 Servers . 5.5 Databases SQL Server 2016: Most of CapraTek’s databases will be using SQL Server 2016 as C# and ASP.NET are the primary programming languages at CapraTek. Oracle 12c: For the legacy CapraTek applications, there are some that requires Oracle 12c. There are no plans to continue to use Oracle 12c for future projects. Any plans to use Oracle 12c should be discussed with the project manager. 5.6 Development Workstations Development workstations must support Visual Studio 2017 and NetBeans. Development workstations should have the minimum hardware: · 2.4GHz CPU. · 8GB RAM. · 256GB SSD boot drive, 1TB HDD storage drive. · 2GB graphics card Development machines that are used for data analysis or video creation should have the minimum hardware: · 2.4GHz CPU. · 16GB RAM. · 256GB SSD boot drive, 512GB SSD storage. · 4GB graphics card. 5.7 Development Software . 6. Software Phases 6.1 Phase 1: Software Requirements · Gather requirements from clients by elicitation. · Gather information from our development team about resources and tools. · Discuss requirements from client and information from development team with project leader and executive. 6.2 Phase 2: Software Design · Break projects into sprints(Iterations). · Assign responsibilities to respective team members. 6.3 Phase 3: Software Construction The software construction phase will develop new code or modify existing code, unit test, integrate, and document software. While reused code will not be expected to conform to a single coding standard, changed source code must be supplemented with enough new comments and standard code headers to meet commenting provisions of the coding standard and to promote understandability. 6.4 Phase 4: Software Testing · · . · . 7. Verification and Validation Our developed software has met all the desired specifications and quality standards. If it’s met then we move forward to deployment. If it does not meet specifications(Intended outcomes) then we go to phase 1. 8. Maintenance Process 8.1 Maintenance Plan Diagram < maintenance="" plan="" activity="" diagram="">. 8.2 Maintenance Plan Refer to the software development UML diagram if there any anomaly occur in software development or a routine update. We will again gather information about anomalies or update. Implement and Integrate that in sprints. 9. Human Factors (Section 10 has been pre-completed) 9.1 Training All employees at CapraTek will need training, from computer literacy to the usage of each of the software applications developed. A culture change management plan will be needed to train those users involved of the new methods of conducting business and the technology to support these new approaches. ***End***
caprateksdpu1-clqyidbl.docx
Answered 2 days AfterJan 25, 2021

Answer To: Technical Standards Overview Technical standards are important to ensure that all development staff...

Deepti answered on Jan 27 2021
153 Votes
6. Software Phases
At Capratec, a software development project shall require to adapt to change. The projects shall emphasize on delivering results rather than establishing tools and processes. The company has adopted Agile methodology therefore customer needs are taken as highest priority instead of fixing development plans. End user satisfaction is of utmost importance and efficiency of development is taken care more than establishing processes, documenting the actions or following the plans. Agile development shall work in iterations foe the target company. A set of actions will be repeated in a fixed sequence till the desired condition is achieved. In Scrum Agile method. The iterations are implemented as Sprints. Each Sprint shall be aimed for 1-2 weeks. The workflow of each Sprint shall be managed by certain roles such as
· Product Owner- She will decide the scope of each Sprint and its goal. She will be responsible to complete the sprint, achieve the intended goals and remove the incomplete tasks. User stories are created, the product owner breaks them into tasks for Sprint stored in backlog. She is further responsible for meeting with development team as well as demonstrating the results of Sprint to customer.
· Development Team
6.1. Phase 1: Software Requirements
The product owner shall list the project requirements. She plans conversation with customer and elicits requirements. She plans strategic meeting with development team to discuss information about tools and resources required to fulfill the customer’s need. It is crucial for the stakeholders to decide the necessary features which are developed on priority and the secondary features which the team can build later. The initial requirements are simplified to the most lower level requirements to ensure that the product works well and fulfills the basic requirement of the customer wen deployed. Maximum details are captured to reduce rework and be clear and prepared.
The main elements of requirement gathering phase are
· Developing vision for high level details
· Brainstorming for requirement features
· Features broken down into user stories
· Defining detailed requirements
Key factor of this phase is to break down the scope of work. The work is divided into large chunks of work or Epics. Epics are further divided into smaller chunks of work called Stories. Stories are divided into Sprints. Requirement gathering document is prepared after collecting all requirement from customer and information on resources from team. All functionalities of end product are documented. Out of scope functionalities are also discussed and documented with final step of signing off from customer.
6.2. Phase 2: Software Design
Design phase is accomplished by dividing the work into design sprints. A design meeting is planned and held among designers, business owner and product owner. The design works and outcomes are presented in the meeting....
SOLUTION.PDF
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here
Have files?