Scribd
Upload
7 views6 pages

Mod 3

Open source development allows public access to source code for collaborative software creation, initiated by the Free Software Foundation. It has gained traction in business models focused on support rather than product sales, with various licensing options governing usage. Risk management in software development involves identifying, analyzing, and monitoring potential risks to ensure project success.

Uploaded by

Vansh negi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views6 pages

Mod 3

Open source development allows public access to source code for collaborative software creation, initiated by the Free Software Foundation. It has gained traction in business models focused on support rather than product sales, with various licensing options governing usage. Risk management in software development involves identifying, analyzing, and monitoring potential risks to ensure project success.

Uploaded by

Vansh negi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Open Source Development

Open source development is a way of creating software where the source code is made public, and
people are invited to contribute to its development.

This idea started with the Free Software Foundation (www.fsf.org), which believes that software
should not be restricted but should allow users to view and modify the code.

The internet has made it easier to involve a large number of volunteers, many of whom are also
users of the software.

A well-known example of open source software is the Linux operating system, widely used on
servers and now growing in popularity as a desktop system.

Other examples include Java, the Apache web server, and the MySQL database

Open Source Issues

1. Should the software being created use open source components?

2. Should an open source approach be used for the software’s development?

Open Source in Business

More and more product companies are using an open source approach to development.

Their business model is not based on selling a software product but on selling support for that
product.

They believe that involving the open source community will allow software to be developed more
cheaply, more quickly and will create a community of users for the software.

Open Source Licensing

The main idea of open-source development is that the source code is available for anyone to use,
but this doesn't mean it can be used however someone wants.

1. The creator of the code (whether a person or a company) still owns it and can set rules for how it
is used. These rules are included in the open-source license, which is legally binding.

2. Some developers believe that if their open-source code is used to create a new system, that new
system should also be open source.

3. Other developers are okay with their code being used in proprietary systems.

Types of Open Source Licenses

1. GNU General Public License (GPL):

o If you use GPL-licensed code, your software must also be open source.

2. GNU Lesser General Public License (LGPL):


o You can use open source components in your software without making your entire
software open source.

3. Berkley Standard Distribution (BSD) License:

o You can use and modify the code without sharing your changes. You can include it in
private software and sell it.

Managing Open Source Licenses

 Keep track of the open source components you use.

 Understand each component's license before using it.

 Know how components are updated and plan accordingly.

 Educate your team about open source rules.

 Have systems in place to check for proper use of open source components.

 Contribute to the open source community to stay informed and involved.


RISK MANAGEMENT

Risk management in software development is the process of identifying, assessing, and prioritizing
potential risks that could impact the project's success.

TYPES OF RISKS ARISED


Risk management process

An outline of the process of risk management is presented in Figure 22.2.

It involves several stages:

1. Risk identification :You should identify possible project, product, and business risks.

2. Risk analysis :You should assess the likelihood and consequences of these risks.

3. Risk planning: You should make plans to address the risk, either by avoiding it or by minimizing its
effects on the project.

4. Risk monitoring: You should regularly assess the risk and your plans for risk mitigation and revise
these plans when you learn more about the risk.

Risk Monitoring

Risk monitoring is the process of checking that your assumptions about the product, process, and
business risks have not changed.

To monitor risks effectively in software development, follow these steps:

1. Regularly Review Identified Risks:

o At each stage of the project, assess whether the risks you've identified are becoming
more or less likely to occur. This helps you stay aware of potential threats as they
evolve.

2. Evaluate Risk Probability and Impact:

o Continuously assess whether the probability of a risk occurring or its impact on the
project has increased or decreased. For example, track indicators such as
requirement change requests or performance issues that might signal growing risks.

3. Monitor Relevant Factors:

o Keep track of factors that could influence the likelihood or impact of specific risks,
such as:

 Estimation risks: Look for signs like missed deadlines or failure to resolve
defects.

 Organizational risks: Watch for signs of restructuring or financial difficulties.


 People risks: Monitor staff morale, turnover, and availability.

 Technology risks: Track technology issues like hardware delays or failures.

 Tools risks: Observe tool adoption and usage issues among team members.

4. Use Risk Indicators:

o Use specific indicators to assess risk, such as customer complaints, organizational


changes, or technology-related issues. These clues will help you decide whether a
risk is materializing or if its effects have worsened.

5. Conduct Regular Risk Reviews:

o Hold frequent management reviews to discuss key risks and evaluate their current
status. This allows you to adjust risk management strategies as needed.

6. Adjust Mitigation Plans:

o Based on your monitoring, update your risk mitigation plans. For example, if there
are concerns about recruitment, alert customers to potential delays or consider
bringing in external components to fill gaps.

PROJECT SCHEDULING PROCESS

SOFTWARE PRICING

A software pricing model is a strategy used by software developers or companies to decide how
much a customer will pay to use their software. It shows how the software will make money and how
the revenue will be earned.
FACTORS AFFECTING SOFTWARE PRICING

You might also like