Intro It

Introduction to IT -
Common
www.scnsoft.com © ScienceSoft
Agenda
1. IT team structure
2. Outsourcing Models and Contracts
3. Life Cycle Models and Methodologies
Chapter 1: IT team structure
Basic team roles in IT are:

1. Frontend developer
2. Back-end Developer
3. UI Designer
4. UX Designer
5. Tester
6. QA Engineer
7. Team Lead
8. Business Analyst
9. DevOps Engineer
10.Project Manager
Frontend developer
creates the part of your application that the users see and directly interact with.
They make sure the experience is equally smooth and user-friendly to every
person who uses the app.
Back-end Developer
a programmer focused mainly on developing business logic and data layers. And
because elements are crucial to system functioning; its correctness depends on
the quality of back-end developer’s work.
UI Designer
The primary duty of the UI designer is to prepare, or design, the user interface.
This means transferring content, style, graphics connected with a client or product
to a system presentation layer.
UX Designer
Contrary to the UI designer, it’s a function characterised by a less ‘digital’ approach
to a user interface. The UX designer – whereby UX means User Experience – must
make sure that end users will have the best possible experience while using an
application.
Tester
a person who is responsible for quality control: finding and testing software
defects under controlled conditions and evaluating the results of its elimination.
QA Engineer
a person who improves the development processes to prevent the introduction of
defects making sure that any agreed-upon standards and procedures are followed.
Quality Assurance and Quality Control
Quality Assurance (QA) Analysis -> Architecture -> Development -> Testing -> Verification
is the planned and systematic set of activities to improve the development processes to prevent the introduction of defects.
Monitoring and improving the process
 making sure that any agreed-upon standards and procedures are followed
 ensuring that problems are found and dealt with
 It is oriented to problems prevention
Quality Control (QC) Analysis -> Architecture -> Development -> Testing -> Verification
includes activities that find and correct defects: operation of a system or application under controlled conditions and evaluating
the results. It is oriented to problems detection.
Team Lead
This person should have leadership qualities which allow for maintaining
communication between remote development teams and for example – clients.
Business Analyst
Most of the products fail, not because they were built poorly but because they
didn’t achieve the product-market fill they were expected to. A Business Analyst
helps you to avoid such a situation
DevOps
is a set of practices that combines software development (Dev) and IT operations
(Ops). It aims to shorten the systems development life cycle and provide
continuous delivery with high software quality.
Project Manager
Works on a higher level of abstraction and is responsible for a budget, risk,
schedule and contract management.
Support Engineer
A Technical Support Engineer, also known as an IT support engineer, helps in
resolving technical issues within different components of computer systems, such
as software, hardware, and other network-related IT related problems.
Technical Engineer Responsibilities

A technical support engineer should provide enterprise-level support to
customers. An ideal technical support engineer resume should address their
ability to research, diagnose, troubleshoot, and resolve the issues to the clients’
satisfaction.
What Is Level 1, Level 2, And Level 3 IT Support?

Breaking customer service into three tiers allows to apply the best member of the support
team.
Level 1 - involves simple customer requests that require limited IT support
Level 2 - escalates into more in-depth problems
Level 3 - utilizes subject matter experts that can figure out the toughest customer needs.
Chapter 2: Outsourcing
Models and Contracts
Chapter 2: Outsourcing Models and Contracts
Depending on the selected IT outsourcing models you can expect some

variations in the payment terms, work progress reporting, your ability to manage
the team directly, etc.
Types of IT outsourcing models:

• Time and material model
• Fixed-price contracts
• Dedicated development teams or resources
• Offshore development center
Time and material pricing method

One of the oldest and, probably, the most simple to explain and understand type
among IT outsourcing models. Time and material model is used when you have
the final goal. This objective might be pretty extensive, like “create and launch
software product”.
Types of outsourcing contracts: fixed-price

The fixed-price contract means that the payment does not depend on how much
time and resources vendor will spend to complete the project.
TEAM-BASED OUTSOURCING PRICING MODELS

The dedicated development team
The dedicated development team is among the ideal outsourcing pricing models
in IT for the technology companies and ISVs. It allows quickly extend their
development capabilities with the highly-qualified offshore developers and stay
in control of those engineers likewise the internal staff.
Dedicated teams are the best option for long-term support, maintenance and
gradual work on software products. The main reason for this is that with the
time the team is starting to become stakeholders of the product and functions
as internal staff. Potentially, this type of outsourcing contracts can last for
dozens of years.
Scalability and flexibility are what make the dedicated teams perfect choice
when the scope of work is hard to estimate.
Outsourcing pricing models in the dedicated development team services:

Cost per resource – the fixed-price that the client needs to pay to the outsourcing
company.
Management fee – the variation of the cost per resource model but more transparent.
The client is aware of the developer’s actual salary and pays a so-called “management fee”
on top.
Hourly rate – another way to go with the dedicated development team outsourcing
model. It helps to understand the cost of each working hour by the particular developer in
the team.
Types of outsourcing contracts: the dedicated development center

Enterprises use this model in case they don’t have an internal IT department
capable of the full cycle of software development. In opposite to the dedicated
team model, where external specialists are used rather as an augmentation to
the in-house IT team, dedicated centers are used to outsource the whole IT
processes on the service provider’s premise.
Chapter 3: Life Cycle Models
and Methodologies
Chapter 3: Life Cycle Models and Methodologies
Software development life cycle (SDLC) is a series of phases that provide a

common understanding of how the software will be realized and developed from
the business understanding and requirements elicitation phase to convert these
business ideas and requirements into functions and features until its usage and
operation to achieve the business needs.
Waterfall Model
• any phase in the development process begins only if the previous phase is
complete.
• does not define the process to go back to the previous phase to handle changes
in requirement.
Advantages Disadvantages
• Easy to explain to the users. • Assumes that the requirements of a
system can be frozen.
• Structures approach.
• Very difficult to go back to any stage
• Stages and activities are well defined. after it finished.
• Helps to plan and schedule the project. • A little flexibility and adjusting scope is
difficult and expensive.
• Verification at each stage ensures early
detection of errors/misunderstanding. • Costly and required more time, in
addition to the detailed plan.
• Each phase has specific deliverables.
V-Shaped Model
Instead of moving down in a linear way, the process steps are bent upwards after
the implementation and coding phase, to form the typical V shape.
• Simple and easy to use • Very inflexible, like the waterfall model.
• Each phase has specific deliverables. • Adjusting scope is difficult and

expensive.
• Higher chance of success over the
waterfall model due to the development • The software is developed during the
of test plans early on during the life cycle. implementation phase, so no early
prototypes of the software are produced.
• Works well for where requirements are
easily understood. • The model doesn’t provide a clear path
for problems found during testing
• Verification and validation of the phases.
product in the early stages of product
development. • Costly and required more time, in
addition to a detailed plan.
Prototyping Model
• the activity of creating prototypes of software applications, used to visualize some component of the
software to limit the gap of misunderstanding the customer requirements by the development team.
Types of Prototyping Model

• Throwaway prototyping:
• Evolutionary prototyping:
• Incremental prototyping:
• Reduced time and costs, but this can be • Insufficient analysis. User confusion of
a disadvantage if the developer loses prototype and finished system.
time in developing the prototypes.
• Developer misunderstanding of user
• Improved and increased user objectives.
involvement.
• Excessive development time of the
prototype.
• It is costly to implement the prototypes
Spiral Model (SDM)

• is favored for large, expensive, and complicated projects. The usage
• is used in the large applications and systems which built-in small phases or
segments.
• Estimates (i.e. budget, schedule, etc.) • High cost and time to reach the final
become more realistic as work product.
progressed because important issues are
discovered earlier. • Needs special skills to evaluate the risks
and assumptions.
• Early involvement of developers.
• Highly customized limiting re-usability
• Manages risks and develops the system
into phases.
Iterative and Incremental Model

• starts with an initial planning and ends with deployment with the cyclic
interactions in between.
• is used in shrink-wrap application and large system which built-in small phases or
segments.
• Produces business value early in the • Requires heavy documentation.
development lifecycle.
• Follows a defined set of processes.
• Better use of scarce resources through
proper increment definition. • Defines increments based on function and
feature dependencies.
• Can accommodate some change requests
between increments. • Requires more customer involvement
than the linear approaches.
• More focused on customer value than the
linear approaches. • Partitioning the functions and features
might be problematic.
• We can detect project issues and changes
earlier. • Integration between the iterations can be
an issue if it is not considered during the
development and project planning.
Agile Model
• based on iterative and incremental development, where requirements and
solutions evolve through collaboration between cross-functional teams.
• Decrease the time required to avail • Scalability.

some system features.
• The ability and collaboration of the
• Face to face communication and customer to express user needs.
continuous inputs from customer
representative leaves no space for • Documentation is done at later stages.
guesswork.
• Reduce the usability of components.
• The end result is the high-quality
software in the least possible time • Needs special skills for the team.
duration and satisfied customer.
CONCLUSION
CONCLUSION
After reading the above contents, do you
have a brief understanding of what IT is?
If not, or if you have some questions,
please feel free to write them down and
ask your mentor. Hope you have learned
today something new. Good bye

Intro It

Uploaded by

Copyright:

Available Formats

You might also like

Intro It

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Intro It

Uploaded by

Copyright:

Available Formats

Introduction to IT -

Basic team roles in IT are:

Technical Engineer Responsibilities

What Is Level 1, Level 2, And Level 3 IT Support?

Depending on the selected IT outsourcing models you can expect some

Types of IT outsourcing models:

Time and material pricing method

Types of outsourcing contracts: fixed-price

TEAM-BASED OUTSOURCING PRICING MODELS

Outsourcing pricing models in the dedicated development team services:

Types of outsourcing contracts: the dedicated development center

Software development life cycle (SDLC) is a series of phases that provide a

• Each phase has specific deliverables. • Adjusting scope is difficult and

Types of Prototyping Model

• It is costly to implement the prototypes

Spiral Model (SDM)

Iterative and Incremental Model

• Decrease the time required to avail • Scalability.

You might also like