Let’s begin the new chapter…

Nishchit
11 min readAug 28, 2022

--

Hello everyone,

Nishchit here from Udupi. I attended primary school in Perdoor, high school there, and PUC there. I recently graduated from the Mangalore Institute of Technology and Engineering with an Engineering degree in ISE (MITE). I currently hold the position of Trainee Software Engineer (TSE) at the IT company TietoEvry.

Campus to corporate:

Sharing my experience at TietoEvry, my first firm, makes me incredibly happy. I was quite eager to travel to Bangalore with my pals until the company informed me via email that we had an induction programme within the company itself. My companions and I boarded a bus, and we arrived in Bangalore.

On August 11th, 2022, I made my official debut in business. It was a good building, the Company. We received welcome kits from the HR staff on this particular day. They played some games as well. It was absolutely great fun for me. Moreover, they gave us lunch. They presented technical details for a few domains in the afternoon. I had a great time throughout the two-day induction training.
Campus to corporate sessions online began on August 16, 2022. Mrs. Vibha Mishra of the L&D team took the initiative and lead it. It was a fascinating session.

Industry transformation:
i)Industry 1.0:

The 18th century’s close marked the beginning of the first industrial revolution. Mechanization brought perhaps the biggest changes in the sectors. Mechanization explains why industry began to take agriculture’s role as the foundation of the economy. People at the time saw widespread coal mining and the important steam engine development, which produced a new kind of energy and eventually aided in accelerating the construction of railroads, so advancing the economy.
ii)Industry 2.0:
The second industrial revolution, which followed the first one, began at the end of the 19th century as a result of enormous technological developments in various industries that aided in the development of fresh energy sources like electricity, gas, oil, and so forth. The internal combustion engine was made possible by this revolution. Additionally, the demand for steel, chemical synthesis, and communication technologies like the telegraph and telephone all began to develop.
iii)Industry 3.0:
The invention of the vehicle, nuclear energy, and the aeroplane at the turn of the 20th century all began here in this revolution. The third industrial revolution saw the development of computers, electronics, and telecommunications. The world was involved in biotechnology and research. Programmable logic controllers (PLCs) and robots were two significant industrial innovations that contributed to the development of high-level automation.
iv)Industry 4.0:
At the beginning of the third millennium, Industry 4.0 began with the Internet, a tool that everyone utilises on a daily basis. The change from the first industrial revolution’s technological phase to Industry 4.0, which creates virtual reality worlds, is obvious to all. Around the world, initiatives are being launched that are aimed at assisting individuals. projects with the goal of involving the industrial sector in the transformation of digital skills that support industry technical advancements.

Industry Segments:
i)Banking sector:
The banking sector is the main sector in the industry where all the transaction of the money and all the money related queries will be maintained. Here the main thing is to give the very good customer experience. A financial activity to manage and secure one’s hard-earned money is referred to as banking. It benefits all parties involved — people, small businesses, and big businesses. Banks provide a variety of accounts and loans, as well as other financial management tools. Additionally, they offer simple access to money through resources like ATMs, debit cards, credit cards, etc.
ii)Healthcare sector:
In this sector all the hospital related queries and the data are maintained where all the details will be secured and the people will have the very good experience. The details of all will be stored and can retrieve the data whenever required.
iii)Transport sector
Companies in the transportation sector offer services to convey people or products, as well as infrastructure for transportation. Transportation technically belongs to the industrials sector as a subset. The transportation industry, which deals with the movement of people and goods, is a significant industrial sector in the economy. These companies comprise those that offer transportation infrastructure as well as those in the airline, trucking, rail, shipping, and logistics industries. Electric vehicles have made mobility easier for humans and have contributed to environmental preservation because they are emission- and noise-free.

Importance of Customer Experience:
The long-term success of every firm depends on providing outstanding customer service. Client loyalty is increased, customer retention is aided, and brand advocacy is prompted by a satisfying customer experience.

Good and bad customer experience:
Good customer service is about understanding your customer’s feelings, desires, and needs in every situation whereas bad customer service can be defined as when a business fails to meet customer expectations in terms of service quality, response time, or overall customer experience.
Near my house there is one temple and infront of that there is one shop where all the things will be there which is taken to the temple. The shopkeeper guides everyone and tells the speciality of the place whoever visits his shop . By this way he is have a very good number of customers. This is my good experience
Recently i ordered a classmate book for my brother. I received the order in 2 days but the material which i ordered was not that. It was of poor quality too. Not classmate for sure. This was very bad experience because it didnt meet my expectation.

Basics of Computer and it’s architecture:
A computer system is essentially a device that automates challenging operations. It should increase efficiency while lowering expenses and electricity usage. The many parts of the computer system architecture include the control unit, storage unit, arithmetic logic unit, input unit, and output unit.

There are five primary parts that make up computer architecture: input, control unit, ALU, memory unit, and output.
i)Input: Entering data and programmes into a computer system .
ii)Control Unit (CU): A component known as “The Control Unit” is in charge of overseeing the input, output, processing, and storage processes. It chooses when and where to begin and stop receiving data, as well as where to keep it. It handles the meticulous processing of each and every computer function.
iii)Memory Unit: Information and instructions are kept in the computer’s memory unit. 4. Arithmetic Logic Unit (ALU): The ALU performs addition, subtraction, multiplication, division, logic, and comparison as its main operations.
iv)Output: This is the process of generating information-rich results from the data.

The evolution of standalone to cloud architecture/platform:

Evolution of standalone to cloud architecture/platform

Google Cloud :
The Google Cloud Platform is a collection of cloud computing services that Google offers. It employs the same internal architecture as Google does for its consumer products, including Google Search, Gmail, Drive, and YouTube.

To save any kind of data that is highly vital to me, I personally utilise Google Cloud. You can upload or download a file, delete a file, see a list of files, or find out the size of a particular file using Google Cloud Storage.

Software Engineering:
The process of evaluating user needs and then designing, developing, and testing software applications that will meet those requirements is known as software engineering.

Software Development Life Cycle:
The Software Development Life Cycle (SDLC) is a structured process that enables the production of high-quality, low-cost software, in the shortest possible production time. The goal of the SDLC is to produce superior software that meets and exceeds all customer expectations and demands.

Waterfall Model
The waterfall is a universally accepted SDLC model. In this method, the whole process of software development is divided into various phases.

RAD Model
RAD or Rapid Application Development process is an adoption of the waterfall model; it targets developing software in a short period.

Spiral Model
The spiral model is a risk-driven process model. This SDLC model helps the group to adopt elements of one or more process models like a waterfall, incremental, waterfall, etc.

V Model
In this type of SDLC model testing and the development, the step is planned in parallel. So, there are verification phases on the side and the validation phase on the other side.

Incremental Model
The incremental model is not a separate model. It is necessarily a series of waterfall cycles. The requirements are divided into groups at the start of the project.

Agile Model
Agile methodology is a practice which promotes continues interaction of development and testing during the SDLC process of any project.

Requirement Gathering Process, Techniques, Types of requirements:
No matter how big or small the project, gathering requirements is an essential step. Understanding and meeting the demands of the consumer are both crucial.
In the process of gathering requirements, customers, users, stakeholders, etc. must be identified and their requirements for the project must be documented. Solutions in the shape of goods, services, software, etc. will be created using this knowledge.
Techniques like interviewing, mind-mapping, focus groups, questionnaires, etc., may be used to collect this data.

Requirements types

  • User Requirements
  • Business Requirements
  • System Requirements

Use case diagram:
Use-case diagrams describe the high-level functions and scope of a system. These diagrams also identify the interactions between the system and its actors.

Steps to draw Use Case Diagram,

  1. Identify the system users or actors and categorize them
    by the level of access to the system.
  2. Assign roles to every category of users as relevant to the
    system.
  3. Define the steps the users should undertake to achieve
    given goals on the system.
  4. Identify the goals and create a use case for each.
  5. Structure all the use cases.
  6. Review and validate the system actors.

Use case and user story:
Use cases are very specific in relation to user stories. User story is a simplified form of many users interacting with a software.

Agile Methodology:
Agile is an iterative approach to project management and software development that helps teams deliver value to their customers faster and with fewer headaches.

Agile as a methodology began with the release of the Agile Manifesto in 2001. Since then, a number of agile frameworks, including scrum and extreme programming, have evolved (XP). Each in its own way exemplifies the fundamental ideas of frequent iteration, continuous learning, and high quality. Software development teams choose Scrum and XP, while service-oriented teams like IT or human resources prefer Kanban.
Many agile teams now blend techniques from a few different frameworks, flavoured with techniques particular to the team. Teams may follow some agile rituals (such as frequent stand-ups, retros, backlogs, etc.), while others may develop their own agile approach.
Future agile teams will place a higher priority on their own effectiveness than on following rules. Companies that want to draw in the greatest talent and make the most of them are starting to treat openness, trust, and autonomy as cultural assets. These businesses have already demonstrated that, as long as teams are directed by the appropriate principles, practices can differ.

Roles involved in the execution:
The Scrum team is primarily made up of the three positions of the Product Owner, Development Team, and Scrum Master.
Nobody besides the core team has any direct power over the Team. Each of these Scrum roles has a fairly defined set of duties, which we will go over in more detail later on in this lesson. Let’s concentrate on the qualities of the Scrum Team as a whole and the optimal team size under this part.

Standup meeting:
Stand-up meetings are regular events, usually every day, where team members report on their progress. In order to ensure a quick check-in rather than a drawn-out conversation, they are frequently held while participants are standing.

Scrum:
Scrum is a framework that helps teams work together. It is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
Scrum requires a Scrum Master to foster an environment where:

  1. A Product Owner orders the work for a complex problem into a Product Backlog.
  2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
  3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
  4. Repeat

Scrum is simple. The Scrum framework defines the parts required to implement Scrum theory. Scrum is built upon the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.

Standup meetings in scrum:
One of the core components of agile development is stand-ups. The objective is to review significant tasks that have been completed, are currently being worked on, or are about to be initiated. Although they are particularly common in software development teams, they are also becoming more and more common in a wide range of other professions, including marketing, project management, product development, and many others. This is due to the fact that organising a quick stand-up meeting offers a novel and, above all, efficient alternative to the common round-table meetings, which a huge section of the present workforce despises.

Sprints in scrum:
A scrum team strives to finish a specific amount of work during a brief, time-boxed sprint. Agile teams may provide better software with fewer headaches if sprints are done correctly because they are the foundation of scrum and agile approaches. The scrum’s first activity is sprint planning, which begins the sprint. Sprint planning’s goal is to specify what can be completed in a sprint and how it will be done. The entire scrum team collaborates on sprint planning. The sprint planning meeting establishes the focus and agenda for the sprint. If done well, it also produces a setting in which the team is inspired, challenged, and capable of success. Bad sprint plans can derail the team by setting unrealistic expectations

DevOps:
DevOps is the combination of practices, and tools that increase an organization’s ability to deliver applications and services at high speed. It is helping in evolving and improving products at a faster rate than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market.

Retrospective meeting:
After a project is completed, teams hold retrospective sessions to reflect on how they may perform better in the future. It’s a secure environment for assessing the project’s accomplishments, spotting chances for process improvement, and resolving any potential problems.

Task planning:
Project task planning is an organised and integrated management process that concentrates on the tasks necessary for the project’s effective completion. It avoids project roadblocks including alterations in projects or organisational goals, a lack of resources, and other issues.

Estimation process:
Finding an estimate, or approximation, that may be used for a purpose even though the input data may be partial, imprecise, or unstable, is the process of estimation. Estimation establishes how much money, time, effort, and other resources will be required to create a particular system or product. Estimation is supported by Past Information, Past Experience, Documents at Hand, and Knowledge Assumptions. Recognized Risks.
The four fundamental stages of software project estimation are as follows:
i) Calculate the development product’s size.
ii) Decide on a person-month or person-hour estimate for the endeavour.
iii) Calculate the timetable in months.
iv) Calculate the project’s expense in the chosen currency.

--

--