The Simplicity in User Manual

User manual is still needed. However, it should as simple as possible. The real question is, what the content of user manual that can be as simple as possible and provide simplicity guide for the user. This article will guide it for you. If you are Scrum or XP user, this agile user manual is for you. This is the improvement of my previous post Creating Agile User Manual ( What you Put in Your Manual Technically not everything on the DevOps work item. You can put the essential information such as Product vision, mission, and success criteria Product version and history Product actor. Who will use the product? Product feature. List of features Product user story Product guide how to use the user story. User story limitation and rules medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

MLOps a DevOps Culture for Machine Learning

What is MLOps and Why You Should Care? MLOps is a DevOps in Machine Learning Project. Just imagine you have a project to build an AI 'empowered' software. You need to build the AI feature through machine learning approach. You should build model, test the model, and implement it into your software. There are extra steps you should fulfill and implement the MLOps means you can make sure that the machine learning activity can be well integrated with your DevOps. MLOps = DevOps + ML Project What is the key difference between MLOps and DevOps? MLOps is an extra step in the DevOps. Therefore, some additional activity will be happened in MLOps. Here are the key deference's MLOps is an iteration of experiment. MLOps provides additional iteration to experiment the model. You can put the experiment before the scrum sprint or includes it in the Scrum. MLOps needs to be monitored. When building the model, you need to understand that the model itself need to be monitored carefully. Imagine you have a DGX1 to play with the dataset, you need to monitor the DGX 1 status with Azure Monitor. MLOps needs automation before the model is built. Imagine you have dataset; you might need to pre-processing first. This extra step is part of MLOps MLOps needs to handle model validation. MLOps doesn't use acceptance test, unit test, or code coverage. It uses different approaches. You might need validation set to validate your model. Doing some statistics measurement for error rate or something like that MLOps needs a special member. MLOps might need more than software engine. Data Engineer, Data Science, or AI engineer can be part of MLOps medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299"; How do I get started with MLOps? To get started in MLOps you should learn You should learn how to build machine learning models. You can learn here for free You should learn how to scale your AI solution and ML model. You can learn here for free. You can see the implementation of MLOps here Any Quick Reference for MLOps? We have it for you, you can click to download the PDF file. Case study about MLOps – Download Here MLOps infographic – Download Here MLOps how to implement it – Download Here In the next post, we will learn MLOps in step-by-step. medianet_width = "600"; medianet_height = "250"; medianet_crid = "858385152"; medianet_versionId = "3111299";

Beginner Guide for Azure Pipeline

So today, I want to show you how to use Azure Pipeline for Continuous Integration and Continuous Delivery through the Visual Studio 2019. In order to finish this guide you should have Visual Studio 2019 any version Azure DevOps Azure Subscription The services can be used for free. Just create an account and you ready to go. Beginner Guide Scenario On this guide, I will create a website with ASP.NET MVC template. After that, we will setup the Continuous Delivery and Continuous Integration directly in Visual Studio 2019. Finally, we will check and validate the setup in the Azure Subscription. This guide will be displayed as step by step scenario. Step by Step Scenario #1 Build Your Website We assumed that you already know how to store your codes to the Azure Repos. If you don't know how to upload your codes to the Team Foundation Control or GIT. There will be a guide namely Beginner Guide for Azure Repos. After you connect to the report, you can build your codes and do the first commit. We expect you can do that and already to do that. #2 Creating Azure Services. You should have azure services. You can create an Azure Website by following this tutorial You can create the Azure Portal, Azure CLI, or through Visual Studio. #3 Publish your Codes to the Azure Website After creating an initial website, you can publish the website through the visual studio by right clicking and click publish. In the publishing scheme, you can choose severalways by hosting to the cloud, VM, on-premise, and local folder. We will choose the Azure Web App and select the existing one. When you click the ok button it will connect your deployment model to the cloud. #4 Configure the Continuous Delivery After configuring the cloud, we can configure the continuous delivery as shown below. Please beware that you should have the same App Services with similar App Services. #5 Configure the Azure Pipelines The previous step provides a basic way to do CI and CD. The result of the previous step created an azure pipeline configuration for release and for the build. Visual Studio 2017 hosted will compile your codes, build and test when necessary and then pass away the result to the Release (CD). A developer can modify the release script and the developer script in the Configuring Build Pipeline In the Azure Pipeline, select the edit menu You will see the build steps for the project, you can change it when necessary. For example, you want to do additional tasks, you can click the add button to compress, add some file, put some additional SDK, do some unit test, and many more.   Configure Release Pipeline On this step, you can configure the release activity. Release activity provides some additional action to distribute the solution to the staging or production. On order to do that, you can visit the release menu on the Azure Pipeline features and click edit on the list of release created by visual studio.   That is the basic of the Azure Pipeline with Visual Studio. On the next part, I will create a short video to guide you further on Azure Pipeline. //

Software Testing Tips for Your Software

Building a software is good but testing a software will be great. Today we will discuss what kind of basic testing that you need when you built a software. This article will discuss three fundamental testing that can be done with minimal effort to improve the quality of your software. Unit testing Actor: Developer Unit testing is fundamental test to understand the functionality of the software. The idea of unit testing is to test the method / procedure through a testing framework. Visual Studio 2017 or Visual Studio 2019 helps you through specific features such as: // Unit Test Framework. Visual Studio provides template to create unit test project with MSTest or other compatible framework. It will help you to create skeleton of the unit testing. Live unit test. After you build unit test, you can make visual studio run unit test automatically when codes changed. IntelliTest. IntelliTest help you to create unit test automatically based on several input and output. Although the unit test codes are not created, visual studio provides mechanism to save the tests and reuse later. Please visit further information in Unit Testing Scenario Acceptance Test Actor: Tester, Customer Acceptance test can be used to test the user story or usage scenario of the software. Acceptance test can be helped by the Azure DevOps test plan. You can use test manager to test your software based on usage scenario. You can read further information about Acceptance test through test suite, test plan, and test case. You can learn more at Azure DevOps lab by using Azure Test Performance and Load Test Actor: Tester Staring in Visual Studio 2015, you can do performance and load test by using your local machine or cloud test. You can record your web activity through coded ui test/test recording and then use performance test to simulate the usage of your web application. You can read how to do that here Are you have any other test that you will use to make sure your software great, drop it in a comment   //

Topics Highlights

About @ridife

This blog will be dedicated to integrate a knowledge between academic and industry need in the Software Engineering, DevOps, Cloud Computing and Microsoft 365 platform. Enjoy this blog and let's get in touch in any social media.


Month List