What is Software?

"Software is a set of programs (sequence of instructions) that allows the users to perform a
well-defined function or some specified task."

Software is responsible for directing all computer-related devices and instructing them regarding what
and how the task is to be performed. However, the software is made up of binary language (composed of
ones and zeros), and for a programmer writing the binary code would be a slow.

Therefore, software programmers write the software program in various human-readable languages such
as Java, Python, C#, etc. and later use the source code.

Types of Software
Software's are broadly classified into two types, i.e., System Software and Application
Software.

1. System Software
System software is a computer program that helps the user to run computer hardware or
software and manages the interaction between them. it is software that constantly runs in
the computer background, maintaining the computer hardware and computer's basic
functionalities, including the operating system, utility software, and interface. In simple
terms, you can say that the system acts as a middle man that checks and facilitates the operations
flowing between the user and the computer hardware.

The further classifications of system software are as follows:

1. Operating System
 It is a group of software that handles the execution of programs and offers general services
for the application that runs over the computer. 

Some of the commonly used examples of operating systems are given below.

o Microsoft Windows
o Apple's iOS
o Apple's MacOS
o Android
2. Device Drivers
In computing, the device driver is a type of software that operates or controls some specific
hardware devices linked to your system.

o Display Drivers
o Printer Drivers

2. Application Software
Application programs or software applications are end-user computer programs developed
primarily to provide specific functionality to the user. The applications programs assist the
user in accomplishing numerous tasks such as doing online research, completing notes,
designing graphics, managing the finances, watching a movie, writing documents, playing
games, and many more.

a. Word Processors
Word processor applications are globally used for documentation, making notes, and typing
data. It also helps the end-users store and format data. They also enable the users to print their
documents.

Some examples of Word Processor software's are as follows:

o MS Word (Microsoft)
o iWork-Pages (Apple)
o Corel WordPerfect
o Google Docs

b. Database Software
Database software is used to create, manage, modify and organize a massive amount of data
quickly retrieved. Another name for database software is Database Management System
(DBMS). Such software helps companies in their data organization. Common examples of
Database Software's are:

o Oracle
o MS Access
o SQLite
o Microsoft SQL Server
 o FileMaker
o dBase
o MariaDB
o MySQL

c. Multimedia Software
This software enables the users to play, create or record images, music, and video
files. Different graphic designing companies widely use multimedia software to make animation,
images, posts, packaging, marketing creative, gif, or even video editing. Due to their popularity
and increasing demand, every software product development corporation has massive avenues in
creating and upgrading them.

Common examples of Database Software's are given below:

o Adobe Photoshop
o Windows Movie Maker
o Adobe Illustrator
o Picasa
o Windows Media Player
o Corel Draw

d. Web Browsers
These are a type of software that is globally used to browse the Internet. Web browsers help the
users in positioning as well as fetching data across the web. Common examples of web
browsers are given below:

o Chrome
o Mozilla Firefox
o Microsoft Internet Explorer
o Opera

Information gathering
A Process of Collecting the user needs to solve a problem or issues and achieve an objective.

Business Requirement: A series of needs that must be fulfilled to achieve a high-level objective.
Clear business requirements help ensure that the end result of a project fulfills the stakeholders'
needs.

1. One-on-one interviews:-The most common technique for gathering requirements is to sit

down with the clients and ask them what they need.

There are many good ways to plan the interview, but generally you want to ask open-ended
questions to get the interviewee to start talking and then ask probing questions to uncover
requirements.

Open-ended interview questions allow interviewees to respond how they wish, and to what
length they wish, appropriate when the analyst is interested in breadth and depth of reply

2. Group interviews:-Simply, Group interviews are similar to the one-on-one interview,

except that more than one person is being interviewed. These interviews work well when
everyone is at the same level or has the same role. Group interviews require more preparation
and more formality to get the information you want from all the participants.

3. Joint application development (JAD):-Is a technique that allows the analyst to

accomplish requirements analysis and design the user interface with the users in a group setting.

In another meaning, JAD sessions are similar to general facilitated sessions. However, the group
typically stays in the session until the session objectives are completed. For a requirements JAD
session, the participants stay in session until a complete set of requirements is documented and
agreed to.

4. Questionnaires:-Questionnaires are much more informal, and they are good tools to
gather requirements from stakeholders in remote locations or those who will have only minor
input into the overall requirements. Questionnaires can also be used when you have to gather
input from dozens, hundreds, or thousands of people.

Questionnaires are useful in gathering information from key organization members about:

1. Attitudes – what people in the organization say they want.

2. Beliefs – what people think is actually true.

3. Behavior – what organizational members do.

4. Characteristics – properties of people or things.

5. Prototyping:-Prototyping is a relatively modern technique for gathering requirements. In

this approach, you gather preliminary requirements that you use to build an initial version of the
solution — a prototype. You show this to the client, who then gives you additional requirements.
You change the application and cycle around with the client again. This repetitive process
continues until the product meets the critical mass of business needs or for an agreed number of
iterations.

6. Use cases:-Use cases are basically stories that describe how discrete processes work. The
stories include people (actors) and describe how the solution works from a user perspective. Use
cases may be easier for the users to articulate, although the use cases may need to be distilled
later into the more specific detailed requirements.

7. Following people around:-This technique is especially helpful when gathering

information on current processes. You may find, for instance, that some people have their work
routine down to such a habit that they have a hard time explaining what they do or why. You
may need to watch them perform their job before you can understand the entire picture. In some
cases, you might also want to participate in the actual work process to get a hands-on feel for
how the business function works today.

8. Request for proposals (RFPs):-If you are a vendor, you may receive requirements
through an RFP. This list of requirements is there for you to compare against your own
capabilities to determine how close a match you are to the client's needs.

9. Brainstorming:-On some projects, the requirements are not "uncovered" as much as they
are "discovered." In other words, the solution is brand new and needs to be created as a set of
ideas that people can agree to. In this type of project, simple brainstorming may be the starting
point. The appropriate subject matter experts get into a room and start creatively brainstorming
what the solution might look like. After all the ideas are generated, the participants prioritize the
ones they think are the best for this solution. The resulting consensus of best ideas is used for the
initial requirements.

10. Demo Screens:-This technique is especially helpful when gathering information from a
client how is totally not related to Information technology field or the client does not know
exactly what he needs. By providing basic screens “Not necessary to be active” and explaining
the concept of the estimated system, the client will understand more and start to give the analyst
the information and the requirements.
Data Flow Diagrams:-
A Data Flow Diagram (DFD) is a traditional visual representation of the information flows
within a system. A neat and clear DFD can depict the right amount of the system requirement
graphically. It can be manual, automated, or a combination of both.

It shows how data enters and leaves the system, what changes the information, and where data is
stored.

The objective of a DFD is to show the scope and boundaries of a system as a whole. It may be
used as a communication tool between a system analyst and any person who plays a part in the
order that acts as a starting point for redesigning a system. The DFD is also called as a data flow
graph or bubble chart.

Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A data store
indicates that the data is stored which can be used at a later stage or by the other processes in a
different order. The data store can have an element or group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system inputs or sink
of system outputs.