Summary

Functional requirements that describe system behavior must be completed with non-functional requirements that constrain system performance, scalability, availability, resilience, interoperability, usability, and security.Performance requirements come from response time and system load requirements. As a software architect, you should ensure you have the required performance at the minimum cost, building efficient algorithms and taking full advantage of the available hardware resources with multithreading.Scalability is the ability of a system to be adapted to an increasing load. Systems can be scaled vertically by providing more powerful hardware, or horizontally by replicating and load balancing the same hardware, which increases the availability. The cloud, in general, and Azure can help us implement strategies dynamically, with no need to stop your application.Tools such as .NET 8 that run on several platforms can ensure interoperability, that is, the capability of your software...

Questions

1. What are the two conceptual ways to scale a system?
2. Can you deploy your web app automatically from Visual Studio to Azure?
3. What is multithreading useful for?
4. What are the main advantages of the asynchronous pattern over other multithreading techniques?
5. Why is the order of input fields so important?
6. Why is the Path class so important for interoperability?
7. What is the advantage of a .NET standard class library?
8. List the most-used types of .NET Visual Studio projects.

Further reading

The following are some books and links you may consider reading to gather more information in relation to this chapter:

• https://www.packtpub.com/virtualization-and-cloud/hands-azure-developers
• https://docs.microsoft.com/en-us/azure/architecture/best-practices/auto-scaling
• https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/azure-apps/
• https://docs.microsoft.com/en-us/dotnet/standard/parallel-processing-and-concurrency
• https://docs.microsoft.com/en-us/dotnet/standard/parallel-programming/
• https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-5/
• https://docs.microsoft.com/en-us/dotnet/standard/security/
• https://docs.microsoft.com/en-us/aspnet/core/security/
• https://owasp.org/
• https://cheatsheetseries.owasp.org/cheatsheets/DotNet_Security_Cheat_Sheet.html
• https://docs.microsoft.com/en-us/aspnet/core/security/gdpr
• https://docs.microsoft.com/en-us/azure/architecture/patterns/category/resiliency
• https://docs.microsoft.com/en-us/azure/architecture/patterns...

Introducing GitHub projects

Considering all the benefits of Azure DevOps presented, you may now be asking why we need to explore another tool. The reason is simple: GitHub has become, over the years, the main tool for the open-source world. So, we will find many initiatives and projects there that have changed the way we deliver software.

The main objective of GitHub is to manage code and guarantee that its users can create solutions in a collaborative way. For this, the platform presents features like version control, pull requests, code reviews, issue tracking, and CI/CD.

However, it would be impossible to design great projects without a platform to support them. That is why we have GitHub projects as an initiative that delivers an adaptable, flexible tool for planning and tracking work on GitHub.

You can find more information about GitHub projects at https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.

...

Summary

This chapter covered how you can create an Azure DevOps or GitHub account for a software development project and how to start managing your projects with Azure DevOps or GitHub projects.

It also gave a short review of all of Azure DevOps’ functionalities, explaining how to access them through the Azure DevOps main menu.

To finish, it presented the GitHub project view options to plan and manage a project.

The chapter also described in more detail how to manage system requirements and how to organize the work necessary with various kinds of work items or issues, along with how to plan and organize sprints that will deliver epic solutions with many features.

The decision of whether to use Azure DevOps or GitHub in a project will vary according to the expertise of the team and the objective of the project itself. If you are designing an open-source solution, GitHub will definitely be a better option. On the other hand, if you are designing an enterprise...

Questions

1. Is Azure DevOps only available for .NET projects?
2. What kinds of test plans are available in Azure DevOps?
3. Can DevOps projects use private NuGet packages?
4. Why do we use work items?
5. What is the difference between Epic and Feature work items?
6. What kind of relationship exists between Task and Product Backlog items/User Story work items?
7. How can GitHub projects be useful?
8. Which is the better option: Azure DevOps or GitHub?

Learn more on Discord

To join the Discord community for this book – where you can share feedback, ask questions to the authors, and learn about new releases – follow the QR code below:

https://packt.link/SoftwareArchitectureCSharp12Dotnet8