Fluent Essays

This course focuses on the foundation of software architecture and software development planning. A software development plan (SDP) establishes the standards and procedures to use for all software development phases within an organization. During course assessments, you create an SDP for a fictional company that uses Agile for software development. The SDP defines the process methodology, resources, staffing, organization, scheduling, technical standards, software development phases, and maintenance, as well as verification and validation plans.     Syllabus  This course focuses on the foundation of software architecture and software development planning. A software development plan (SDP) establishes the standards and procedures to use for all software development phases within an organization. During course assessments, you create an SDP for a fictional company that uses Agile for software development. The SDP defines the process methodology, resources, staffing, organization, scheduling, technical standards, software development phases, and maintenance, as well as verification and validation plans.  5 Assessments Course Resource/CapraTek Overview.docx IT3345 – Software Architecture ` CapraTek Software Project Overview Imagine that you are a software architect that has been hired by CapraTek to create an IEEE Standard 1058-based Software Development Plan for all their future in-house development projects. The document below has been sent to you by CapraTek’s CIO. Hi, I am excited to have you on board to help us in defining our future software develop practices! I just want to share relevant information about our company. It is not a complete picture, but it is enough to get you started. Please feel free to make and state any assumptions you might need to make in areas that I have not provided sufficient information. We can talk about those when we refine our plan. For now, I need a polished first draft to share with our stakeholders by the end of next month. We are a longtime leader in computer server technology but are now shifting our effort to focus on Alfred!, an integrated wireless smart-home hub that seamlessly connects household electronics, appliances, and devices. While we have traditionally outsourced our software development to third party companies, we have now decided to bring all development in-house with the hope that it will decrease design and development time and improve software quality. Many existing projects have either failed, or gone over time and budget, while much of the current software has become stale, due to poorly maintained code, and needs a proper plan. One of our biggest challenges is changing the way we produce our product. We are interested in introducing Agile for software development, but many of our personnel are more familiar with traditional project management. Many have a basic understanding of Agile and a keen interest to adopt it, but they need a blueprint from which to work. We understand that there are several Agile methodologies and are looking for guidance on selecting the one that fits best. We hope you can help! Our Team of Developers We currently have 10 in-house developers that have experience with a mixed set of programming languages. Based on previously outsourced work, we are planning to increase this to 20–25 developers, but are not sure of what non-developer resources will be required by Agile. The organization is willing to hire additional non-development support staff (that is, PMs, QA, testers, administrators, etc.) based on Agile requirements. Projects We have three large software development projects planned for next year that are each similar in scope. We need to extend our Alfred! Web application and build both iOS and Android apps for users to control the hub. Using traditional project management techniques, we were able to build our original Alfred! Web application with 6 software developers and one project manager in 12 months. Our plans are to rewrite the entire application to improve the current hub’s performance. There will be few added features in the first iteration. The mobile apps will have similar functionality and will be relegated to phones for the first release, although we will be incorporating responsive design that should increase its reach to other devices. Technology We currently use the following technology and plan to continue to do so: · Microsoft Xamarin for cross-platform development. · C# applications using Visual Studio. · ASP.NET Web applications using Visual Studio. · Legacy Java applications using NetBeans. · Amazon Web Services (AWS). · Red Hat Linux. · Microsoft Server 2016. · Oracle 12c and SQL Server 2016 databases. Here are some of the requirements and technical challenges facing projects that we would like addressed: · Servers: Dedicated servers need to be used for each process including databases and Web applications. · Bug Tracking: Most of the issues have been dealt with through e-mails or word of mouth. It is important that issues and bugs are tracked in a single application. · Version Control: Existing applications, when updated, do not have a trail of code being updated. There needs to be more accountability for developers and ensuring that all changes are being tracked against bug tickets. · Asset creation: Any images, videos, or other multimedia needs to be developed in a common tool that can be edited by any other individual. Common standard file formats should be used for any images and videos that are created. I look forward to seeing your plan! Sincerely Yours, Robert Craft Chief Information Officer CapraTek Corporation 1 2 Course Resource/Course Overview.docx This course focuses on the foundation of software architecture and software development planning. A software development plan (SDP) establishes the standards and procedures to use for all software development phases within an organization. During course assessments, you create an SDP for a fictional company that uses Agile for software development. The SDP defines the process methodology, resources, staffing, organization, scheduling, technical standards, software development phases, and maintenance, as well as verification and validation plans. Software Preparation and Technology Access In this course, you will be using software and technology that is needed to complete designated assessments. There is no additional cost for this software and technology. Some software packages will be made available to you at no additional cost through Capellas subscription with Microsoft, while other software packages are available for free download through open-source licensing. Capella University requires learners to meet certain minimum  computer requirements . Please note that some software required for a course may exceed these minimum requirements. Check the requirements for the software you may need to download and install to make sure it will work on your device. Most software will require a Windows PC. If you use a Mac, refer to Installing a Virtual Environment and Windows on a Mac . The software and technologies in this course are strongly recommended to support you in completing the course objectives. If you have access to other tools that you believe may still meet the requirements of this course, please discuss your selected alternatives with faculty. If you use assistive technology or any alternative communication methods to access course content, please contact  [email protected]  with any access-related questions or to request accommodations. Course Resource/Software Development Plan Template - SDP.docx 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 <Enter here>. Do not change the font color. Save the document as CapraTek SDP – Assessment “X” CapraTek Software Development Plan Version 1.0 Prepared by <name> <Date> IT-FP3345 – Software Architecture Contents 1. Introduction 4 1.1 Identification 4 1.2 Scope and Purpose 4 1.3 System Level Project Description 4 1.4 System Description 4 1.5 Document Organization 4 2. Resources and Scheduling 6 3. Organization and Staffing 7 4. Technical Management and Control (Section 4 has been pre-completed) 8 4.1 Change Management 8 5. Standard and Procedures 9 5.1 Deliverable Standard 9 5.2 Process Methodology Diagram 9 5.3 Process Methodology Explanation 9 5.4 Phase Description 9 6. Technical Standards 10 6.1 Technology Stack Diagram 10 6.2 Cloud Environment 10 6.3 Programming Languages 10 6.4 Servers 10 6.5 Databases 10 6.6 Development Workstations 10 6.7 Development Software 11 7. Software Phases 12 7.1 Phase 1: Software Requirements 12 7.2 Phase 2: Software Design 12 7.3 Phase 3: Software Construction 12 7.4 Phase 4: Software Testing 12 8. Verification and Validation 13 9. Maintenance Process 14 9.1 Maintenance Plan Diagram 14 9.2 Maintenance Plan 14 10. Human Factors (Section 10 has been pre-completed) 15 10.1 Training 15 Software Development Plan for CapraTek Page iii 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 <Enter here>. Purpose <Enter here>. Business Challenge <Enter here>. 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. Resources and Scheduling <Enter here>. Organization and Staffing <Enter here>. Technical Management and Control (Section 4 has been pre-completed) 1.6 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. Standard and Procedures 1.7 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. 1.8 Process Methodology Diagram Chosen Agile methodology: <Enter here>. <Enter UML activity diagram here>. 1.9 Process Methodology Explanation < Enter here including justification for its adoption>. 1.10 Phase Description Phase X - <Enter here>. Phase X - <Enter here>. Phase X - <Enter here>. Phase X - <Enter here>. Phase X - <Enter here>. Add as necessary… Expanded Phase Details <Enter Phase “X” Details here>. <Enter Phase “X” Details here>. Technical Standards 1.11 Technology Stack Diagram <Enter Technology Stack diagram>. 1.12 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. 1.13 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. 1.14 Servers <Enter here>. 1.15 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. 1.16 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. 1.17 Development Software <Enter here>. Software Phases 1.18 Phase 1: Software Requirements · <Add the activity diagram here>. · <Enter high-level steps here>. · <Enter process flow effect here>. 1.19 Phase 2: Software Design · <Add the activity diagram here>. · <Enter high-level steps here>. · <Enter process flow effect here>. 1.20 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. 1.21 Phase 4: Software Testing · <Add the activity diagram here>. · <Enter high-level steps here>. · <Enter process flow effect here>. Verification and Validation <Enter here>. Maintenance Process 1.22 Maintenance Plan Diagram < Maintenance Plan Activity Diagram>. 1.23 Maintenance Plan <Enter here>. Human Factors (Section 10 has been pre-completed) 1.24 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*** 4 15 Course Resource/Syllabus.docx  This course focuses on the foundation of software architecture and software development planning. A software development plan (SDP) establishes the standards and procedures to use for all software development phases within an organization. During course assessments, you create an SDP for a fictional company that uses Agile for software development. The SDP defines the process methodology, resources, staffing, organization, scheduling, technical standards, software development phases, and maintenance, as well as verification and validation plans. Software Preparation and Technology Access In this course, you will be using software and technology that is needed to complete designated assessments. There is no additional cost for this software and technology. Some software packages will be made available to you at no additional cost through Capellas subscription with Microsoft, while other software packages are available for free download through open-source licensing. Capella University requires learners to meet certain minimum  computer requirements . Please note that some software required for a course may exceed these minimum requirements. Check the requirements for the software you may need to download and install to make sure it will work on your device. Most software will require a Windows PC. If you use a Mac, refer to Installing a Virtual Environment and Windows on a Mac . The software and technologies in this course are strongly recommended to support you in completing the course objectives. If you have access to other tools that you believe may still meet the requirements of this course, please discuss your selected alternatives with faculty. If you use assistive technology or any alternative communication methods to access course content, please contact  [email protected]  with any access-related questions or to request accommodations.  Toggle Drawer Course Competencies To successfully complete this course, you will be expected to: 1. Define business problems that can be solved using software architecture concepts and standards. 2. Explain fundamental concepts and principles of software architecture. 3. Create a Software Development Plan for an organization. 4. Apply software process model strategies within the software architecture process. 5. Communicate effectively. Assessment 1.docx Overview Complete the Software Development Plan, Section 5: Standards and Procedures. As a software architect, you will be exposed to different software development processes. Currently, Agile software development is the most widely used software development process. Show Less By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria: · Competency 1: Define business problems that can be solved using software architecture concepts and standards. · Justify why an Agile methodology is appropriate for CapraTek. · Competency 2: Explain fundamental concepts and principles of software architecture. · Explain each activity or phase depicted on a UML diagram and how they relate to the software development process. · Competency 3: Create a Software Development Plan for an organization. · Describe how Agile phases might manifest themselves in a business scenario. · Competency 4: Apply software process model strategies within the software architecture process. · Create an activity diagram that properly illustrates an Agile life cycle methodology. · Competency 5: Communicate effectively. · Integrate visual elements with writing that generally clarify or highlight key points. Required Resources The following resources are required to complete the assessment: · CapraTek Overview [DOCX]. · Software Development Plan Template [DOCX]. Suggested Resources The following suggested resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom. Agile Methodology · Tsui, F., Karam, O., & Bernal, B. (2018). Essentials of software engineering (4th ed.). Burlington, MA: Jones & Bartlett Learning. Available from the bookstore . · Read Chapter 4, Software Process Models, pages 57–79. · Read Chapter 5, New and Emerging Process Methodologies, pages 83–101. · Manifesto for Agile software development. (n.d.). Retrieved from http://Agilemanifesto.org/ · This resource describes the original tenets of the Agile philosophy. · Agile Alliance (n.d.). Agile glossary. Retrieved from https://www.agilealliance.org/agile101/agile-glossary/ · This resource Agile terms and definitions. · Scrum Case Studies.com. (n.d.). Scrum case studies. Retrieved from http://www.scrumcasestudies.com/ · This resource contains various case studies for projects that use Scrum. Skillsoft Resources Complete the following from the Capella University Library: · Pender, T. (2003).  UML bible . Indianapolis, Indiana: Wiley Publishing, Inc. · Read Chapter 13: Modeling Behavior Using an Activity Diagram. · Keenan, C. (2014).  OOD: UML activity diagram [Video]. Skillsoft, Ireland. · This video demonstrates how to create a UML activity diagram. · Saleh, H. (2015).  Agile project management fundamentals: Moving to Agile [Video]. Skillsoft, Ireland. · This video walks you through various considerations about moving to Agile.  · Calnan, C. (n.d.).  Introduction to agile software development [Tutorial]. Skillsoft. · This tutorial gives you an introduction into Agile Software Development with considerations about all the organizational requirements to move to Agile. · Skillsoft. (n.d).  Adopting an agile approach to project management [Tutorial]. · This tutorial walks you through the conversion from traditional projects to Agile and discusses strategies that can be used to adopt Agile practices. · Girvan, L., & Paul, D. (2017).  Agile and business analysis: Practical guidance for IT professionals . Swindon, UK: BCS Learning & Development Ltd. · Read Chapter 2, Agile Philosophy and Principles, which covers some of the origins of Agile and the Agile manifesto. It also covers some of the various Agile approaches. · Read Chapter 5, Understanding Agile Methods and Frameworks, which provides you with a foundation about many of the popular Agile methods and approaches, including XP, Scrum, RAD, Lean, and Kanban. Microsoft Software For this course, follow the instructions provided through the links below to download and install software or register for an account: · If you have a Capella MS Imagine account, go to Step 2. Otherwise, see the instructions for registering an account at MS Imagine–Registration. · Log into the Capella Microsoft Imagine WebStore. · Identify the version of MS Visio that is compatible with your operating system. · Download and install. If you encounter any difficulties in the download and installation process, post a detailed question in the Ask Your Faculty Discussion in the menu dropdown when you click the image of your faculty. Note: As a Capella learner, you have access to IT online resources through Capellas Skillsoft subscription, where you can find helpful materials.  Note: As a Capella learner, you have access to IT online resources through Capellas Skillsoft subscription, where you can find helpful materials.  Assessment Instructions Overview In this assessment you focus on the process methodology of Section 5, Standards and Procedures, of your Software Development Plan (SDP)—choosing, diagramming, explaining and finally applying your choice of Agile development methodology to CapraTek. The choices that you make here drive the rest of the SDP, so it is an appropriate starting point. Note: Complete the assessments in this course in the order in which they are presented. Preparation Use the assessment Resources to complete the following: · View the CapraTek scenario. · Download the Software Development Plan Template. Save it as CapraTek_SDP_A1 and use it to complete and submit your assessment for this course. Directions  Consider the CapraTek scenario and address the items below in Section 5 of the CapraTek SDP document. · Select an Agile methodology and briefly justify why your chosen Agile methodology is appropriate for CapraTek. · Create a Unified Modeling Language (UML) activity diagram that illustrates the process methodology life cycle. · Describe each of the phases depicted in the process methodology diagram with relation to the software development process. Keep your descriptions generic—the point is to explain the processes involved in each phase to illustrate the concept. · Partial Example: Scrum Initial Requirements Steps: During the initial requirements steps, the product owner examines the product backlog and gets feedback from the customer and other stakeholders. The product owner then informs the development team of the items from the product backlog . . . · Select two of the phases and describe how each would manifest itself in the context of CapraTek. Consider CapraTeks requirements, resources, time constraints, et cetera.  Save and submit your SDP. Note: Microsoft Visio is provided for your use via MS Imagine. See the Microsoft Software section in the Assessment 1 Resources for more information. Agile Methodology Scoring Guide - 1.pdf Agile Methodology Scoring Guide CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED Justify why an Agile methodology is appropriate for CapraTek. Does not justify why an Agile methodology is appropriate for CapraTek. Justifies a choice of Agile methodology that is ill-suited for CapraTek or provides a justification that unclear, disorganized, or unconvincing. Justifies why an Agile methodology is appropriate for CapraTek. Justifies why an Agile methodology is appropriate for CapraTek by using specific examples to support it. Create an activity diagram that properly illustrates an Agile life cycle methodology. Does not create an activity diagram. Creates an activity diagram that poorly illustrates an Agile life cycle methodology. Creates an activity diagram that properly illustrates an Agile life cycle methodology. Creates an activity diagram that effectively illustrates an Agile life cycle methodology using UML conventions and symbols. Explain each activity or phase depicted on a UML diagram and how they relate to the software development process. Does not explain each activity or phase depicted on a UML diagram and how they relate to the software development process. Explains each activity or phase depicted on a UML diagram incompletely or does not explain how they relate to the software development process. Explains each activity or phase depicted on a UML diagram and how they relate to the software development process. Explains each activity or phase depicted on a UML diagram and how they relate to the software development process in great detail that demonstrates superior understanding of Agile development methodologies. Describe how Agile activities or phases might manifest themselves in a business scenario. Does not describe how Agile activities or phases might manifest themselves in a business scenario. Describes how Agile activities or phases might manifest themselves in a business scenario in an inaccurate or confusing manner. Describes how Agile activities or phases might manifest themselves in a business scenario. Describes how Agile activities or phases might manifest themselves in a business scenario in great detail that includes specific references to the business scenario. Integrate visual elements with writing that generally clarify or highlight key points. Integrates visual elements with writing that do not clarify or highlight key points. Integrates visual elements with writing that somewhat clarify or highlight key points. Integrates visual elements with writing that generally clarify or highlight key points. Integrates visual elements with writing that clearly and directly clarify or highlight key points. Agile Methodology Scoring Guide https://courserooma.capella.edu/bbcswebdav/institution/IT-FP/IT-FP334... 1 of 1 10/13/2021, 12:20 AM Assessment 3.docx Overview Complete the software development plan, Section 6: Standards and Procedures. By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria: · Competency 1: Define business problems that can be solved using software architecture concepts and standards. · Create a technology stack component diagram that accurately reflects CapraTeks needs. · Competency 2: Explain fundamental concepts and principles of software architecture. · Justify the employment of specific development and support tools that address CapraTeks technical challenges. · Competency 3: Create a software development plan for an organization. · Identify servers that are appropriate for business and technical conditions. · Competency 5: Communicate effectively. · Write clearly with few spelling or grammatical errors.  Resources Required Resources The following resource is required to complete the assessment: · CapraTek Overview [DOCX]. Suggested Resources The following suggested resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom. Resource for SDP Section 6 · Tsui, F., Karam, O., & Bernal, B. (2018). Essentials of software engineering (4th ed.). Burlington, MA: Jones & Bartlett Learning.  Available from the bookstore . · Read Chapter 3, Engineering of Software, pages 41–49. Skillsoft Resources Complete the following from the Capella University Library: · Castillo, D. (n.d.).  Getting started with Amazon Web Services [Tutorial]. Skillsoft. · This tutorial introduces the basics about getting started with Amazon Web Services (AWS). CapraTek will use this resource. · Mueller, J. P. (2017).  AWS for developers for dummies . Hoboken, NJ: John Wiley & Sons. · Read Chapter 1, Starting Your AWS Adventure, which explores the AWS cloud and understanding when, why, and how to use AWS. · Read Chapter 3, Choosing the Right Services, which explores an overview of the features in AWS and matching those services to our organizations needs. · Skillsoft (n.d.).  Advanced architecting on Amazon Web Services: Data storage architecture [Tutorial]. · This tutorial looks at the storage architecture required on Amazon Web Services used for software architecture on the cloud. · Girvan, L., & Paul, D. (2017).  Agile and business analysis: Practical guidance for IT professionals . Swindon, UK: BCS Learning & Development Ltd. · Read Chapter 4: Adopting an Agile Mindset. · This chapter relates many of the Agile principles to business analysis. · Read Chapter 7: Working with Stakeholders and Roles.  · This chapter introduces the various types of stakeholders and customers.  Assessment Instructions 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 assessment you complete SDP Section 6, Standards and Procedures, which is intended to provide developers a high-level view of technologies to be used. Preparation · Review the CapraTek Overview found in the assessment Resources. · Save a new version of your SDP document using this assessment number and use it to complete the assessment. Directions Consider the CapraTek scenario and address the items below in Section 6 of the CapraTek SDP document: 1. Create a technology stack component diagram showing where each technical operation is performed. 2. 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 interoperate with Java and .NET operations. Justify your choices. Save and submit your SDP. Note: Microsoft Visio is provided for your use via MS Imagine. See the Microsoft Software section in the Assessment 1 Resources for more information. Technical Standards Scoring Guide - 3.pdf Technical Standards Scoring Guide CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED Create a technology stack component diagram that accurately reflects CapraTeks needs. Does not create a technology stack component diagram. Creates a technology stack component diagram that does not accurately reflect CapraTeks needs. Creates a technology stack component diagram that accurately reflects CapraTeks needs. Creates a technology stack component diagram that accurately reflects CapraTeks needs and shows a deep understanding of the interdependence of the technologies that are required and uses UML diagramming conventions. Identify servers that are appropriate for business and technical conditions. Does not identify servers. Identifies servers that are inappropriate or inadequate for business and technical conditions. Identifies servers that are appropriate for business and technical conditions. Identifies required servers that are very well-suited for business and technical conditions. Justify the employment of specific development and support tools that address CapraTeks technical challenges. Does not attempt to justify the employment of specific development and support tools that address CapraTeks technical challenges. Justifies the employment of specific development and support tools that inadequately address CapraTeks technical challenges. Justifies the employment of specific development and support tools that address CapraTeks technical challenges. Justifies the employment of specific development and support tools that effectively address CapraTeks technical challenges in an efficient manner using compelling rationale. Write clearly with few spelling or grammatical errors. Writes unclearly with many spelling or grammatical errors. Writes somewhat unclearly with some spelling or grammatical errors. Writes clearly with few spelling or grammatical errors. Writes clearly with no spelling or grammatical errors. Technical Standards Scoring Guide https://courserooma.capella.edu/bbcswebdav/institution/IT-FP/IT-FP334... 1 of 1 10/13/2021, 12:43 AM Assessment 2.docx Toggle Drawer Overview Complete Sections 1–3 of the software development plan. By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria: Show Less · Competency 1: Define business problems that can be solved using software architecture concepts and standards. · Define the SDP scope and purpose to accurately reflect business needs. · Prioritize relevant business challenges in order of importance. · Competency 3: Create a software development plan for an organization. · Specify an appropriate software development organization and scheduling that satisfy business conditions while adhering to an Agile process methodology. · Competency 4: Apply software process model strategies within the software architecture process. · Specify software development team roles and responsibilities that satisfies business conditions while adhering to an Agile process methodology. · Competency 5: Communicate effectively. · Write clearly with few spelling or grammatical errors. Required Resources The following resource is required to complete the assessment: · CapraTek Overview [DOCX]. Show Less Suggested Resources The following suggested resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom. Resource for SDP Sections 1–3: · Tsui, F., Karam, O., & Bernal, B. (2018). Essentials of software engineering (4th ed.). Burlington, MA: Jones & Bartlett Learning.  Available from the bookstore . · Read Chapter 1, Creating a Program, pages 7–20. · Read Chapter 2, “Building a Program, pages 23–38. · Read Chapter 13, Software Project Management, pages 267–293. Skillsoft Resources Complete the following from the Capella University Library: · Skillsoft. (n.d.)  Software practices (SCRUM): SCRUM roles [Tutorial]. · This tutorial walks you through the SCRUM roles involved in an Agile Scrum project. · Walters, B. (n.d).  Agile stakeholder engagement and team development [Tutorial]. Skillsoft, Ireland. · This tutorial walks you through how to engage the stakeholders and build the team within an Agile project. · Skillsoft. (n.d).  Engaging Agile stakeholders and leading Agile teams [Tutorial].  · This tutorial discusses Agile teams and team development. · Girvan, L., & Paul, D. (2017).  Agile and business analysis: Practical guidance for IT professionals . Swindon, UK: BCS Learning & Development Ltd. · Read Chapter 3: Analyzing the Enterprise. · This chapter provides a business analysis perspective of how we can apply the Agile methodology for the organization. · Skillsoft. (n.d.)  Agile planning: Project initiating and requirements gathering [Tutorial]. · This tutorial provides information on project scoping.  Assessment Instructions Overview A proper SDP document must consider the organizations capabilities and constraints. This assessment focuses on the first three sections of the SDP: · Section 1: Introduction: Scope, Purpose and Business Challenges. · Section 2: Resources and Scheduling. · Section 3: Organization and Staffing. Considering the following questions may help guide you in this assessment: · Why is there a need for the software development plan? · What are CapraTeks motivations to create the new architecture? · What are the consequences of not adopting a new architecture? · What business problem will the new architecture solve? · What resources and scheduling would be required for each development project? · What roles need to be filled within the Agile methodology that you have selected? Preparation · Review the CapraTek scenario available from the assessment Resources. · Save a new version of your SDP document using this assessment number and use it to complete the assessment. Directions Consider the CapraTek scenario and address the items below in Sections 1–3 of the CapraTek SDP document: · In the Introduction (SDP Section 1), complete the following sections: · Scope. · Purpose. · Business challenges: Identify and prioritize the challenges facing CapraTek. · In Resources and Scheduling (SDP Section 2), specify the project roles and responsibilities based on your Agile process methodology. Assume three concurrent and similarly scoped projects. · In Organization and Staffing (SDP Section 3), specify the project allocation breakdown based on the required resources for anticipated projects. Since CapraTek does plan to run three software development projects simultaneously, resources may need to be shared between projects. Note: You will need to make, and state, general assumptions regarding and based on the approximate size of each project. Save and submit your SDP. Resources, Scheduling, Organization, and Staffing Scoring Guide - 2.pdf Resources, Scheduling, Organization, and Staffing Scoring Guide CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED Define the SDP scope and purpose to accurately reflect business needs. Does not define the SDP scope and purpose. Defines the SDP scope and purpose in a way that does not accurately reflect business needs. Defines the SDP scope and purpose to accurately reflect business needs. Defines the SDP scope and purpose to clearly and succinctly to accurately reflect business needs and the content within the SDP. Prioritize relevant business challenges in order of importance. Does not prioritize relevant business challenges in order of importance. Identifies unimportant business challenges or prioritizes them poorly. Prioritizes relevant business challenges in order of importance. Prioritizes relevant business challenges in order of importance and cites clear and appropriate reasons for their ranking. Specify software development team roles and responsibilities that satisfy business conditions while adhering to an Agile process methodology. Does not specify software development team roles and responsibilities. Specifies software development team roles and responsibilities that do not satisfy business conditions or do not adhere to a predefined Agile process methodology. Specifies software development team roles and responsibilities that satisfy business conditions while adhering to an Agile process methodology. Specifies software development team roles and responsibilities that satisfy business conditions that show a deep understanding of business needs and an Agile process methodology. Specify appropriate software development organization and scheduling that satisfies business conditions while adhering to an Agile process methodology. Does not specify software development organization and scheduling that satisfies business conditions. Specifies inappropriate software development organization and scheduling that does little to satisfy business conditions or adhere to an Agile process methodology. Specifies appropriate software development organization and scheduling that satisfies business conditions while adhering to an Agile process methodology. Specifies appropriate software development organization and scheduling that satisfies business conditions that shows a deep understanding of business needs and an Agile process methodology. Write clearly with few spelling or grammatical errors. Writes unclearly with many spelling or grammatical errors. Writes somewhat unclearly with some spelling or grammatical errors. Writes clearly with few spelling or grammatical errors. Writes very clearly with no spelling or grammatical errors. Resources, Scheduling, Organization, and Staffing Scoring Guide https://courserooma.capella.edu/bbcswebdav/institution/IT-FP/IT-FP334... 1 of 1 10/13/2021, 12:30 AM Assessment 4.docx Overview Complete the software development plan Section 7: Software Phases. By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria: Show Less · Competency 2: Explain fundamental concepts and principles of software architecture. · Describe the high-level steps involved with software development phases. · Explain how an Agile methodology affects the process flow of each software development phase. · Competency 3: Create a software development plan for an organization. · Create software development phase activity diagrams that accurately depict their top-level steps. · Competency 5: Communicate effectively. · Write clearly with few spelling or grammatical errors.  Use this online tool to track your performance and progress through your course.  Resources Required Resources The following resource is required to complete the assessment: · CapraTek Overview [DOCX] . Suggested Resources The following suggested resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom. Software Phases · Tsui, F., Karam, O., & Bernal, B. (2018). Essentials of software engineering (4th ed.). Burlington, MA: Jones & Bartlett Learning.  Available from the bookstore . · Read Chapter 6, Requirements Engineering, pages 105–129. · Read Chapter 7, Design: Architecture and Methodology, pages 130–167. · Read Chapter 9, Implementation, pages 191-207. · Read Chapter 10, Testing and Quality Assurance, pages 208–235. Requirements Analysis · Doig, C. (2015).  The benefits of doing a detailed enterprise software requirements analysis.  Retrieved from http://www.cio.com/article/2923225/enterprise-software/the-benefits-of-doing-a-detailed-requirements-analysis-before-selecting-enterprise-software.html · This article explains why it is beneficial to complete a detailed enterprise software requirements analysis. Skillsoft Resources Complete the following from the Capella University Library: · Skillsoft. (n.d).  IT project management essentials: Introduction to IT project management [Tutorial] . · This tutorial focuses on project phases. · Abran, A. (2004).  Guide to the software engineering body of knowledge: 2004 Edition: SWEBOK . Skillsoft, Ireland. · Read Chapter 2: Software Requirements. · Read Chapter 3: Software Design. · Read Chapter 4: Software Construction. · Read Chapter 5: Software Testing.  Assessment Instructions Overview By adhering to the key software development phases defined in the SWEBOK, CapraTek has signaled its commitment to creating consistent software projects. In this assessment you complete SDP Section 7, Software Phases. Preparation · Review the CapraTek Overview found in the assessment Resources. · Save a new version of your SDP document using this assessment number and use it to complete the assessment. Suggested Resources · You may refer to the SWEBOK V3 found in the assessment Resources.  Directions Consider the CapraTek scenario and address the items below in Section 7 of the CapraTek SDP document: 1. Create activity diagrams depicting the steps involved in each of the following software development phases. · Phase 1: Software Requirements. · Phase 2: Software Design. · Phase 3: Software Construction. · Phase 4: Software Testing. 2. Describe the high-level steps involved with each phase. Note: Phase 3 has already been completed as an example. 3. Explain how your chosen Agile methodology affects the process flow of each software development phase. Save and submit your SDP. Note: Microsoft Visio is provided for your use via MS Imagine. See the Microsoft Software section in the Assessment 1 Resources for more information. Software Phases Scoring Guide - 4.pdf Software Phases Scoring Guide CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED Create software development phase activity diagrams that accurately depict their top-level steps. Does not create software development phase activity diagrams. Creates software development phase activity diagrams that do not accurately depict their top-level steps. Creates software development phase activity diagrams that accurately depict their top-level steps. Creates detailed and clear software development phase activity diagrams that accurately depict their top-level steps using UML conventions. Describe the high- level steps involved with software development phases. Does not identify the high-level steps involved with software development phases. Identifies the high-level steps involved with software development phases in a way that is incomplete, unclear, or confusing. Describes the high-level steps involved with software development phases. Describes in detail the high-level steps involved with software development phases using examples that are relevant to CapraTek. Explain how an Agile methodology affects the process flow of each software development phase Does not explain how an Agile methodology affects the process flow of each software development phase. Explains how an Agile methodology affects the process flow of some of software development phases or offers an explanation that has significant errors or omissions. Explains how an Agile methodology affects the process flow of each software development phase. Explains in detail how an Agile methodology affects the process flow of each software development phase in a way that clearly depicts important nuances of the process that are relevant to CapraTek. Write clearly with few spelling or grammatical errors. Writes unclearly with many spelling or grammatical errors. Writes somewhat unclearly with some spelling or grammatical errors. Writes clearly with few spelling or grammatical errors. Writes very clearly with no spelling or grammatical errors. Software Phases Scoring Guide https://courserooma.capella.edu/bbcswebdav/institution/IT-FP/IT-FP334... 1 of 1 10/13/2021, 12:46 AM Assessment 5.docx Overview Complete the Software Development Plan Sections 8 and 9. By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria: Show Less · Competency 2: Explain fundamental concepts and principles of software architecture. · Create an activity diagram that effectively illustrates a software maintenance program. · Competency 4: Apply software process model strategies within the software architecture process. · Create an effective plan for independent verification and validation of the software based on an Agile methodology. · Create a maintenance plan that details effective ways to evolve and maintain deployed software. · Competency 5: Communicate effectively. · Write clearly with few spelling or grammatical errors. Resources Required Resources The following resource is required to complete the assessment: · CapraTek Overview [DOCX]. The following suggested resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom. Support and Maintenance · Tsui, F., Karam, O., & Bernal, B. (2018). Essentials of software engineering (4th ed.). Burlington, MA: Jones & Bartlett Learning.  Available from the bookstore . · Read Chapter 12, Software Support and Maintenance, pages 254–267. Skillsoft Resources Complete the following from the Capella University Library: · Tripathy, P., & Naik, K. (2014).  Software evolution and maintenance: A practitioner’s approach . Hoboken, NJ: John Wiley & Sons. · Read Chapter 2, Taxonomy of Software Maintenance and Evolution, which considers common approaches for software maintenance in the long term. · Read Chapter 3, Evolution and Maintenance Models, which considers some of the standard maintenance models that can be applied to your project. · Laporte, C. Y., & Alain, A. (2018).  Software quality assurance . Hoboken, NJ: John Wiley & Sons. · Read Chapter 7, Verification and Validation, which covers the verification and validation process and understand how verification and validation fits into the software quality assurance process.  Assessment Instructions Overview Once a software development project is completed at CapraTek, it is also important that there is a plan in place to have the system verified and validated to assure it is the right system and is developed correctly. The SDP needs to spell out how independent verification and validation is to be conducted. Software is rarely completely done at the end of a project. There may be bugs that are uncovered or additional criteria that must be implemented. Planning out a process for the maintenance of the software is crucial. A large part of the software maintenance is to preserve its integrity as changes are made. Any changes are needed to be logged and tracked. There needs to also be criteria put in place when certain software needs to be retired or migrated. In this assessment you will complete SDP Section 8, Validation and Verification, and Section 9, Maintenance Process. Preparation · Review the CapraTek Overview found in the assessment Resources as needed. · Save a new version of your SDP document using this assessment number and use it to complete the assessment. Directions Consider the CapraTek scenario and address the items below in Section 8 and Section 9 of the CapraTek SDP document: · Create a plan for the independent verification and validation of software based upon your chosen Agile methodology per SWEBOK standards (should be one page or less). (SDP Section 8). · Create an activity diagram demonstrating the software maintenance process. (SDP Section 9). · Create a maintenance plan that specifies of how to maintain deployed software per SWEBOK standards (should be one page or less). (SDP Section 9). Save and submit your SDP. Note: Microsoft Visio is provided for your use via MS Imagine. See the Microsoft Software section in the Assessment 1 Resources for more information. Verification, Validation, and Maintenance Scoring Guide - 5.pdf Verification, Validation, and Maintenance Scoring Guide CRITERIA NON-PERFORMANCE BASIC PROFICIENT DISTINGUISHED Create an effective plan for independent verification and validation of the software based on an Agile methodology. Does not create a plan for independent verification and validation of the software. Creates a plan for independent verification and validation that is inadequate or inappropriate or is not based on an Agile methodology. Creates an effective plan for independent verification and validation of the software based on an Agile methodology. Creates a detailed and effective plan for independent verification and validation of the software based on an Agile methodology that demonstrates superior understanding of the business needs and requirements. Create an activity diagram that effectively illustrates a software maintenance program. Does not create an activity diagram that effectively illustrates a software maintenance program. Creates an activity diagram that ineffectively illustrates a software maintenance program or contains significant errors or omissions. Creates an activity diagram that effectively illustrates a software maintenance program. Creates an activity diagram that effectively illustrates a software maintenance program using appropriate UML conventions, symbols, and terms. Create a maintenance plan that details effective ways to evolve and maintain deployed software. Does not create a maintenance plan. Creates a maintenance plan that details ineffective ways to evolve and maintain deployed software or has significant errors or omissions. Creates a maintenance plan that details effective ways to evolve and maintain deployed software. Creates a detailed maintenance plan that identifies effective and efficient ways to evolve and maintain deployed and future CapraTek software. Write clearly with few spelling or grammatical errors. Writes unclearly with many spelling or grammatical errors. Writes somewhat unclearly with some spelling or grammatical errors. Writes clearly with few spelling or grammatical errors. Writes very clearly with no spelling or grammatical errors Verification, Validation, and Maintenance Scoring Guide https://courserooma.capella.edu/bbcswebdav/institution/IT-FP/IT-FP334... 1 of 1 10/13/2021, 12:53 AM