Microservice Architecture platform

                                                             Fig1: Microservice architecture     source -www.docs/Microsoft.com

Microservice is a collection of small, independent, loosely coupled, and autonomous services. Here each service is self-contained and implements a single business capability. Its services can be deployed independently and can be updated on the existing service without re-building and re-deploying the entire application. The services in this architecture are responsible for persisting their data or external state. This approach is very different from the traditional model where there is a separate layer that handles the persistence.   Here services communicate with each other by using the well-defined API in the model. Here internal implementation details are hidden from the external users and they have displayed the necessary information required by them. Most importantly services are not required to share the same technologies such as technology stack, libraries, or framework. In this architecture, each component is responsible for placing the services on the nodes, identifying the failures, rebalancing the services across the platform. Along with this it also provides the facility of API gateways which help in forwarding the call to the appropriate services on the backend. With the help of this facility, it decouples the clients from the services. The services can be versioned and refactored without updating all clients. Further thus platform also supports the messaging protocols. Further, this architecture also supports authentication, logging, SSL termination, and load balancing.

Benefits of micro-service architecture

  • Microservices are deployed independently which supports agility.
  • The services can be versioned and refactored without updating all clients.
  • It supports the small and dedicated teams to process the services that support testing, updating, and maintaining the functions in well-versed form.
  • It has a small code base that provides the facility of updating the services more effortlessly.
  • It also provides the facility to its uses to select technology from various technologies provided in the platform or can use the combination of various technologies as per requirement.
  • Further, it also provides the facility of fault isolation as a single bug will not affect the entire application.
  • Its services can be scaled independently without scaling the subsystems. 
  • It provides an easier method of performing the schema update.  
  • This architecture is highly maintainable and is loosely coupled. It is independently deployable.

 

DevOPs and its application in Microservices

DevOps are a set of practices that combines software development and IT practices under one umbrella. The main objective of DevOps is to reduce the software development life cycle and provide continuous and high-quality service to its users. DevOps helps in breaking the wall between the operations and development for creating the rapid and automated process that helps in faster development of the applications. Here both the operation engineers and development engineers are jointly involved in the software development. The microservice architecture builds the complex architecture from its microservices and by using the DevOps the development of these services can be done in a better way. It helps in breaking down the complex processes in a smaller form and then performing the task of development. It helps in increasing the productivity and reliability of the services provided through this architecture. It further supports in creating the services on various servers in an easier way. Most importantly it supports the round-to-clock mode of service availability to its users. It provides improved agility that allows for quick results, rapid reiteration, and quicker time for deployment. As these services are loosely coupled the management of the entire application is easier. The management of the service is easier in comparison to other approaches. By implementing the DevOps in the microservices the application deployment and development becomes less time-consuming. It also supports fault tolerance and bug removal from the application. Here the deployment, testing, collaboration, and maintenance of the application can be done more easily. Along with this it also provides the facility of API gateways which help in forwarding the call to the appropriate services on the backend. With the help of this facility, it decouples the clients from the services. The services can be versioned and refactored without updating all clients.


What is Software Engineering



Software Engineering 

Software engineering is the application of engineering principles to the design, development, and maintenance of software systems. It is a discipline that involves the analysis, design, implementation, verification, and maintenance of software applications. It also involves the integration of existing software components into larger systems. Software engineering is an important part of modern technology and has been used in many industries such as banking, healthcare, retail, and transportation. By understanding the principles behind software engineering and its importance in our lives today, we can better understand how to create efficient applications that can help make our lives easier.

Description

Software engineering is an interdisciplinary field that involves the development, implementation, and maintenance of software solutions. It is a process-oriented approach to software design and development that focuses on creating systems that are reliable, efficient, secure, and maintainable. Software engineering also includes activities such as requirement gathering, system analysis and design, coding, testing and deployment. It is a highly specialized field of computer science that requires knowledge of programming languages such as Java or C++ as well as knowledge of database management systems such as Oracle or MySQL. With the right skillset and experience in software engineering, you can create robust applications for businesses across various industries.

SDLC

Software Development Life Cycle (SDLC) is an important process for software development. It provides a structured approach to ensure that the software developed meets the desired requirements and specifications. SDLC involves various stages such as planning, analysis, design, coding, testing and maintenance. Each stage has its own set of activities that must be completed in order to ensure a successful software development project. By following a systematic approach to software development, organizations can reduce risks and maximize the success of their projects.



Global Responsible leadership initiative

 

What is Global leadership

Globally responsible leadership begins with the guiding principles of justice, freedom, honesty, humanity, tolerance, openness, responsibility, solidarity, and sustainability. In order for a company to be successful and have good reputation, it must be both profitable and a decent corporate citizen at the same time. A new set of frameworks, laws, and business models are needed to keep up with global changes and fulfil financial commitments to provide both private and public advantages.

 

Model for Global responsible leadership

Short-term profitability, constant innovation, and long-term growth are the three pillars of value that today's corporate leaders must produce in order to succeed in today's economy.

q  When making choices, it's important to put own-self in the shoes of our stakeholders and create an inclusive workplace where everyone has a voice and feels like they belong.

q  Unlocking commitment and creativity through being authentically human and displaying compassion, humility, and openness via emotional and intuitive expressions such as empathy.

q  Our main goal is to help the company and its stakeholders see long-term success as a goal.

q  Innovating responsibly means using evolving technology to create new organizational and social benefits.

q  The goal of intelligence and insight is to find new and better ways to get things done by always learning and sharing information.

Communication

The art of leadership is to inspire, communicate, empower, and persuade others to embrace a new vision of sustainable development and the corresponding changes that are essential. Moral authority is the foundation of leadership. Credibility as a moral leader requires a combination of principles, character, and ability. Great leaders owe some of their influence to their personal traits, maybe more so than to their academic or technical abilities, as anybody who has taken part in action knows.

Example of Global responsible Leadership

          Roger McClendon, Green Sports Alliance

Since the beginning of this year, Rogre has served as the organization's executive director. After 14 years at Yum! Brands, he left to join the niche realm of green sports because, "My origins are in sports." Even during my time at Yum! I was aware that sports might play a significant part in sustainability. Corporations and sports organizations, according to him, naturally collaborate. They can both grow their businesses and instill the right values if they work together. Stadiums, have a lot of complicated procedures and food to deal with. When working with large corporations like Aramark, the Green Sports Alliance ensures that the food supplied is of high quality and sourced sustainably, as well as keeps tabs on the supply chain. In order to avoid waste, they must also keep costs down and his leadership is working for this objective.

Main competencies

 

q  Leadership: Executives in major businesses are required to develop their own self-awareness and emotional intelligence as part of their growth plans. While these intra-personal abilities are important, they are not enough for global leaders since they must also be able to adapt to novel circumstances and to cope with conflicting demands from numerous stakeholders.

q  Leaders need to develop their interpersonal, group, and social integration abilities as top-down, hierarchical management methods are being replaced by more bottom-up, globally dispersed management systems. The worldwide job of a leader necessitates that the leader learns how to function and establish authority in fluid, loosely organized, frequently leaderless task groups.

q  Cultural intelligence—the ability to grasp how various people think and feel and how society's cultures are founded on distinct philosophical, religious, and historical foundations—is also important. There has been a shift away from hierarchical divisions to cross-functional types of cooperation across nations and cultures in the workplace. To address this, we need leaders who are capable of strategizing and adopting a variety of perspectives.

 

                               About Author-Deepika Singh

 


  Academic and Technical writer with passion for technology . infovision.deepika@gmail.com

                                                     

                                                  DSDM Agile Framework 

DSDM Life cycle

 

The DSDM framework includes 3 sequential phases, specifically the pre-task, task life-cycle and post-task phases. The task segment of DSDM is the maximum complex of the 3 phases. The task life-cycle segment includes five ranges that shape an iterative step by step technique in growing an IS. 




1.    Pre-Project Phase

 

In the pre project discussions manifest at terrific control stage in which the commercial enterprise issues are identified, packages (to be built) are decided, those packages are prioritized, finances is allotted for the equal and crew formation is started. This segment guarantees the dedication a part of the venture. As ECC is planning to introduce a dedicated department Data Audit training associates(DATA) based on IOT technology . So ,this phase will help in taking the decision for the choice of technology and other required tools.

 

2.    Post -Project Phase

In post project  -phase  it's far demonstrated via way of means of the technical groups and the enterprise-operations groups that the system (product built) operates as in line with the enterprise expectations. Post challenge segment additionally contains of maintenance (or enhancements) and fixes segment. In those levels the challenge is improvised incrementally and hence non-stop product development (and hence incremental improvement) is achieved. By implementing this phase ECC will be able to asses the challenges the company can face post implementation of the project and can work to rectify those issues.

 

3.    Project Life Cycle Phase

 

The project  lifecycle segment as may be discovered from the above diagram contains of four fundamental degrees. The first one (Study) contains of key degrees of look at – the feasibility look at and the commercial enterprise look at. These take place sequentially and that they supplement every other. In those segment –

Feasibility Study:

As the term suggests, on this segment the opportunity (or feasibility) of constructing the software is studied and choices are made accordingly. It appears into the group to be had, the finances to be had the anticipated functionalities and the opportunity of constructing the functionalities withinside the sources to be had. The output as part of this look at contains of a model (or a prototype) and reviews that enlists how all of the feasibility standards are met. Business Study: In this a part of the look at, commercial enterprise specialists and the technical specialists are all known as upon and discussions take place wherein in all of the important commercial enterprise troubles are indexed and studied. It is then not noted into if the technical abilities to be had are enough to fulfil the commercial enterprise necessities. A prioritization is then made upon the necessities and software & infrastructure diagrams are finalized.

Functional model iteration:

The requirements are finalized and prioritized in the sooner research are then constructed in a practical prototype in which a version of 1 requirement after some other is constructed in incrementally. The prototypes are then studied for its high-satisfactory and development opportunity with the aid of using practical experts (and additionally a few instances with the aid of using stop customers) in order that it could be in addition stepped forward upon. This degree may be in addition sub divided into smaller sub-stages: Identify practical prototype: Based at the prioritized necessities, pick out the important thing functionalities to be constructed withinside the prototype Accept plan and agenda: Form a plan and agenda to construct the functionalities are finalized. Identify crew members, allocate obligations and finalize time limits on this sub degree. Create a practical prototype: The builders then loop in and create the prototype primarily based totally at the practical necessities. They additionally in addition take a look at the functionalities themselves (unit testing) and in addition enhance the product on this sub degree Review the practical prototype: End customers are then introduced into the picture. These then have a examine the functionalities after which take a look at those. The remarks are then considered and in addition development regions are identified.

Design and build integration: This segment first starts off evolved with making sure that the functionalities as constructed meet the person’s expectancies and might feature nicely withinside the realistic and operational surroundings. Most critical attention motel this segment, the man or woman units (or functionalities) as constructed in the sooner level are included into one device. Since in DSDM, there may be no clean difference among layout & construct, each of those levels are clubbed collectively and those levels concurrently hold collectively. This level additionally contains of 4 sub-stages:

Identify layout prototype: Once the necessities are modelled into the prototype, those that want to be withinside the very last device are diagnosed and prioritized.

Accept plan and schedule: The prioritized ones are then deliberate and scheduled to be constructed. Team pals are diagnosed and the responsibilities are allocated.

Create a layout prototype: A layout prototype is created with the aid of using the builders after which it's far furnished to the testers and quit customers for trying out. The  customers then look at the app and offer remarks on how it may be advanced in addition.

 Review the layout prototype: Further trying out is completed at the device and its correctness and closeness to the deliberate one is diagnosed.

Implementation: As part of this level the examined utility is placed up in stay surroundings and is made to be had to the quit customers. Training to quit customers is likewise furnished. Also, well timed evaluate and comments is collated from the quit person to make sure that the commercial enterprise needs are met and proper answer is furnished to the quit customers and their desires are all catered too. Implementation is in addition grouped down into four sub-parts:

 User approval & guidelines Train customers Implement Review commercial enterprise: Above 3 factors are self-explanatory. In this sub level, the effect of the utility at the commercial enterprise is judged, climate the app meets the commercial enterprise desires is diagnosed and any new capability which can have in addition commercial enterprise effect is diagnosed and looped in for in addition development (or enhancement)

   DSDM Principles


Principle 1 - Focus on the Business Need

·       Every selection taken at some stage in a mission need to be considered withinside the mild of the overriding mission goal - to supply what the commercial enterprise desires to be delivered, whilst it desires to be delivered.

·       It is critical to keep in mind that a mission is a method to an end, now no longer a result in itself.

·        In order to fulfil this principle, DSDM groups will: Understand the proper commercial enterprise priorities Establish a legitimate commercial enterprise case Ensure non-stop commercial enterprise sponsorship and commitment.

Principle 2 - Deliver on Time

Delivering an answer on time is a completely applicable final results for a mission and is pretty frequently the unmarried maximum critical fulfilment factor. Late shipping can frequently undermine the very intent for a mission, specifically in which marketplace possibilities or prison time limits are involved. Even for tasks with-out a want for a hard and fast stop date, on time shipping of intermediate or contributing merchandise remains the pleasant manner to illustrate manipulate over evolution of the solution. In order to fulfil this principle, DSDM groups want to: Timebox the work Focus on commercial enterprise priorities Always hit time limits Build self -assurance via predictable shipping.

 

Principle 3 – Collaborate

 

Teams that work in a spirit of energetic cooperation and dedication will usually outperform agencies of people running simplest in unfastened association. Collaboration encourages improved understanding, extra velocity and shared ownership, which permit groups to carry out at a degree that exceeds the sum in their parts. In order to fulfil this principle, DSDM groups want to: Involve the proper stakeholders, on the proper time, all through the project Encourage pro-energetic involvement from the enterprise representatives Ensure that each one contributors of the crew are empowered to take selections on behalf of these they represent Build a one-crew culture.

 

Principle 4 - Never Compromise Quality

 A solution has to be ‘true enough’. If the commercial enterprise is of the same opinion that the functions withinside the Minimum Usable Subset meet the agreed popularity criteria, then the answer must be ‘true enough’ to apply effectively. In order to fulfil this principle, DSDM groups want to: Agree the extent of nice from the outset, earlier than improvement starts Ensure that nice does now no longer emerge as a variable Test early, check constantly and check to the precise level Build in nice with the aid of using steady review Design and file appropriately

 

 

Principle 5 -Build Incrementally through firm foundation

Just like different agile strategies which includes the Scrum method, DSDM makes a speciality of turning in price early and constructing at the development made at every step. Though cautiously figuring out the scope of the undertaking and undertaking desires on the begin of the undertaking guarantees all of us has a not un-usual place vision, liberating new functions early lets in to test the undertaking is usually headed withinside the proper course without losing time on details.

 

                               About Author-Deepika Singh




Academic and Technical writer with passion for technology . infovision.deepika@gmail.com

                                      IOT Design System

Deepika Singh 
Academic and Technical Writer
For assignment help-infovision.deepika@gmail.com




1   Custom IoT  development  methodology for the Health care system

 

          IOT technology is one of the most revolutionized technology that has shaped the design of modern software-based services in the more adoptable way with advance features. To enable the IOT services , the IoT Platform plays a pivotal role that is a group of technologies that provides the building block for development of the IoT platform for the purposed product. Here in this report the IoT platform development methodologies will be presented. The Evolution framework to be followed for this design process is as follows-



-Defining meta-features

   The purposed platform will provide the support to the health care system that enables the individuals to exploit the on-body both portable and connected sensors for frequently monitoring the health signals originated from the human body. These signals will be related to the body temperature , pulse rate, blood pressure etc., and will be captured through sensors deployed in human body and will be communicated to the heath care analytics server. This is very critical service as it aims to provide life support to the patients. It aims to exploit the sensor-based data for analysing , profiling and managing the connected and smart heath care system( Imreh, Robert & Raisinghani, Mahesh. 2021).

Step-2 Derivation of the feature set

In this phase complete lifecycle coverage with the help of proposed IOT platform is set. In this step the various processes are broken down in following steps-

Initialization- In this step the core objective of the project , schedule , responsibilities and other necessary information for development of the IOT platform is set as well documented. Along with this majorly the feasibility of the proposed application is estimated.

Analysis – In this step the analysis of the requirement for the proposed application is set . As mentioned that the  purposed platform will provide the support to the health care system that enables the individuals to exploit the on-body both portable and connected sensors for frequently monitoring the health signals originated from the human body. So, it is analysed for which apparatuses for supporting the health care system the sensors are required to develop. Along with this the features for security and interoperability is also considered.

Design – In this phase firstly the architecture and technologies for proposed sensors are designed. The networking architecture for the proposed IOT platform is designed . According to the research study conducted the various technologies proposed for supporting the health care system are as follows-

 

Along with this technology for supporting the front end and backend design is also set. We are suggesting Arduino platform as it is widely used and is easily available. Secondly it is compatible with modern technologies. Along with this monitoring system with appropriate log files are also required to develop. To support the services data centre is also required to develop.

Implementation

Here in this phase the design and logic develop is converted in the actual working application with the help of appropriate programming language and platform.

Testing

In this phase the developed application is tested both for the functionality features and working  given as well for the given functionalities in the application.

Deployment

In this phase the proposed application is deployed at the actual working place . Here the proposed application will be deployed with complete training and user manuals. Along with this the features are synchronized according to the deployment site requirement.

Tasks or processes

To develop the IOT product for supporting the processes that were conducted as also explained in above section too are to define the context of the processes , life cycle of the product development, Roles of different human entities and  modelling for data products and modelling languages( Fergus, Kristin. 2012).

Roles

Role

Responsibilities

Project manager

Will perform the responsibility of initiating , planning , executing , monitoring and controlling the IOT product

IOT Architect

Will develop the IOT architecture for the product that meets the stakeholder requirements

IOT Programmer

Will perform the responsibility of implementing the IOT API for providing the interoperability , coding , configuring the smart object at the machine level. 

Third party Programmer

Will perform the responsibility of the implementing and supporting of the third-party services

Data/Analyst

Will perform the responsibility of designing and implementing the data models for the data level architecture

Non-relational data storage specialist

Will perform the responsibility of implementing and managing the non-relational SQL technologies

Infrastructure Administrator

Will perform the responsibility of procuring , managing and monitoring the physical platform infrastructure.

Security Specialist

Will perform the responsibility of implementing the mechanism for ensuring the platform’s privacy, security and integrity.

Integrator

Will perform the responsibility of identifying the integration points and implementing the integration layers for addressing the interoperability issues

Medical Staff

Sharing data

 Models /Work Products

Functionalities

Particular constraints

Possible technologies and algorithms

For hospital building

Floor level accuracy

Atmospheric pressure, RFID/Wi-Fi , finger prints , Bluetooth, UWB

For activity recognition

Validity >90%

Accelerometer , RFID , Wi-Fi, decision trees , genetic algorithms , neural network and thresholding

For Vital Sign monitoring such as heart rate

non-invasive method

Electrocardiogram, infrared and acoustic

Classification of the behaviour

High validity required

Neural network, decision tree , k-nearest neighbourhood, genetic algorithms etc. 

For control

Fast responsiveness

Inter-integrated circuit and serial peripheral  interface

 

Modelling language

To implement the application with the help of software’s the programming language such as C, C++, Python and Java will be  used. Along with this machine language such as C and Assembly programming language will be used. Proper communication protocols and smart object layer will be developed.

 

Map Table

Method Fragment

Selected/Not Selected

Justification

Lifecycle Phases

yes

It helps in defining the various stages in the chronological sequence for development.

Tasks/processes

yes

it helps in defining the work scope of each process

Roles

yes

Defines the responsibilities of developing team

Modelling language

yes

It helps in defining the programming language required for developing the working application

Model/work product

yes

Helps in defining possible technologies for product development

 

 

 

 

 

 

IOT Methodology Diagram

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


2. Strength /Advantages and weaknesses of the IOT methodology selected

            Strengths –

The proposed methodology has defined all the phases in the most acceptable form similar to the traditional software life cycles. The proposed methodology is capable for developing the implementable application. It has provided the features for security too. In the IOT health care applications one of the most important requirement is the localization of the patient or equipment. It is very important for localizing the equipment’s and patients for collecting the signals through the sensors. Along with this each sensor has its own features and complexity as here the signals of equipment’s used for the  purposed platform will provide the support to the health care system that enables the individuals to exploit the on-body both portable and connected sensors for frequently monitoring the health signals originated from the human body. These signals will be related to the body temperature , pulse rate, blood pressure etc., and will be captured through sensors deployed in human body and will be communicated to the heath care analytics server. This is very critical service as it aims to provide life support to the patients (Kumar, Gaurav & Bhatia, Pradeep. 2012). Therefore, to design this system a very systematic approach has been utilized. To achieve the optimal result the problem formulation and product development is performed. The algorithms are also specified  according to the requirement of the health care system. Each stage defined above in the methodology is self-explanatory and helps in providing the support to the development of IOT platform for the health care system. In the above section the purpose of each phase and significance in the development life cycle. Here  in this project mainly sensors are required for collecting the data through various apparatuses attached to the patients and storing the information in the backend server . This methodology  is flexible and provides complete scope for the testing and debugging the errors and faults in the convenient manner. Along with this it is providing complete support for connecting with the IOT system devices and support for IOT

Weakness –

·       Though this methodology has provided a great support for the development of IOT platform for the health care system but the methodology is weak in respect to providing the security mechanism.

·       Along with this architecture system for error and exceptional handling is also not specified.