What is Software Engineering?

Software engineering is the branch of computer science that deals with the design,
development, testing, and maintenance of software applications. Software engineers
apply engineering principles and knowledge of programming languages to build software
solutions for end users.
Software engineers design and develop computer games, business applications, operating
systems, network control systems, and middleware—to name just a few of the many career
paths available.

A career as a software engineer can be both fun and challenging with opportunities to work in
almost any industry, including large and small businesses, government agencies, nonprofit
organizations, healthcare facilities, and more. And as technology continues to evolve, the
need for software developers continues to grow. Many companies are also shifting towards
hiring software engineers who work from home, allowing for increased flexibility and more
opportunities to enter the field.

What Careers Are There in Software Engineering?

Career opportunities in software engineering are driven by new technologies in automobiles,

aviation, data management, telecommunications, factory control, robotics, defense, and
security. Software engineers may develop computer games, business applications, operating
systems, network control systems, and more. A bachelor's degree or higher is often required
to work as a software engineer.

Two common jobs within software engineering are applications developers and systems
developers.

Applications developers design computer applications, such as games, for consumers. They
may create custom software for a specific customer or commercial software to be sold to the
general public. Some applications developers create databases or programs for use internally
or online.
Systems developers create operating systems, either for the public or for an organization.
These operating systems keep computers functioning and control most of the consumer
electronics in use today, including those in cell phones and cars. Often, systems developers
also build the interface that allows users to interact with the computer.
Of course, applications and systems developer jobs are not the only two positions available in
the field of software engineering. Other common roles include mobile developers,
applications architects, quality assurance analysts, and database administrators.

Some common job titles for software engineers include:

 Applications Architect
 Applications Developer
 Computer Applications Engineer
 Database Administrator
 Mobile Developer
 Program Manager
 Programmer
  Project Leader
 Quality Assurance Analyst
 Software Engineer
 Software Quality Engineer
 Systems Analyst
 Systems Developer

What Tasks do Software Engineers do?

Successful software engineers use programming languages, platforms, and architectures to

develop everything from computer games to network control systems. In addition to building
their own systems, software engineers also test, improve, and maintain software built by other
engineers.

Day-to-day tasks for a software engineer might include:

 Designing and maintaining software systems or applications

 Evaluating and testing new software programs
 Optimizing software for speed and scalability
 Writing and testing code
 Ensuring platform compatibility
 Creating and enforcing IT standards within an infrastructure
 Maintaining documentation of IT systems
 Releasing software updates
 Collaborating with development teams, senior systems architects, and data science
professionals
 Consulting with clients, engineers, security specialists, and other stakeholders
 Recommending software upgrades for existing programs and systems
 Presenting new features to stakeholders and internal customers

Learning Outcome 01 PRODUCE SOFTWARE REQUIREMENTS

SPECIFICATION DOCUMENT (SRS)

Problem Statement
Defining Software

Software refers to a collection of data or computer instructions that tell the computer how to
work. This includes applications, programs, and the operating systems that control hardware
operations.

Importance of Software Engineering

Software engineering is crucial because it ensures the development of high-quality software

that is reliable, efficient, maintainable, and meets user needs. It involves systematic
application of engineering approaches to software development.

Attributes of Good Software

Good software should be:

 Functional: It should meet all specified requirements and perform all tasks
accurately.
 Reliable: It should perform consistently under specified conditions.
 Usable: It should be easy to use and understand.
 Maintainable: It should be easy to modify and extend.
 Efficient: It should use system resources judiciously.
 Portable: It should work across different environments.
 Secure: It should protect data and resist unauthorized access.

Key Challenges Facing Software Engineering

 Rapid technology change: Keeping up with the pace of technological advancements.

 Managing complexity: Handling the complexity of modern software systems.
 Quality assurance: Ensuring software is free of defects.
 Time and budget constraints: Delivering projects on time and within budget.
 User requirements: Understanding and meeting user needs.
 Security: Protecting against cyber threats.

Differentiating Software Engineering and Computer Science

 Software Engineering: Focuses on applying engineering principles to software

development. It emphasizes the software development lifecycle, from requirements
gathering to maintenance.
 Computer Science: Focuses on the theoretical foundations of computing, algorithms,
data structures, and the principles of software and hardware design.

Professional Ethics in Software Engineering

Professional ethics in software engineering involves adhering to standards of professional

conduct, such as ensuring software quality, respecting privacy and confidentiality, avoiding
harm, and maintaining integrity and honesty in professional practices.

Roles in Software Engineering

 Project Manager: Oversees the project and ensures it meets deadlines and budgets.
 Software Developer: Writes and maintains code.
 Systems Analyst: Analyzes and designs information systems.
 Quality Assurance Engineer: Tests software to ensure it is free of defects.
 UI/UX Designer: Designs user interfaces and experiences.
 DevOps Engineer: Manages software deployment and infrastructure.

Defining a Problem Statement

A problem statement clearly describes an issue that needs to be addressed. It sets the direction
for finding solutions and is essential for any project.

Importance of a Problem Statement

A problem statement is important because it:

 Defines the scope of the project.

 Provides focus and direction.
 Facilitates understanding among stakeholders.
 Sets the foundation for developing solutions.

Procedure for Writing a Problem Statement

1. Identify the problem: Clearly define the issue.

2. Explain the impact: Describe how the problem affects stakeholders.
3. Specify the objectives: Outline what needs to be achieved.
4. Provide context: Give background information.
5. Justify the need: Explain why solving the problem is important.

Problem Solving Process

1. Define the problem: Clearly articulate the issue.

2. Gather information: Collect relevant data and insights.
3. Generate solutions: Brainstorm potential solutions.
4. Evaluate solutions: Assess the feasibility and impact of each solution.
5. Choose a solution: Select the most effective solution.
6. Implement the solution: Put the chosen solution into action.
7. Review the results: Evaluate the outcome and make necessary adjustments.

Problem Addressed by the Software Product

The software product addresses the issue of inefficient project management by providing
tools for task tracking, resource allocation, and collaboration.

Evaluating Alternative Solutions

 Manual methods: Using spreadsheets and documents.

 Generic project management software: Adopting off-the-shelf solutions.
 Custom software development: Building a tailored solution.

Bottom-Up vs. Top-Down Approaches in Software Engineering

 Bottom-Up: Starts with designing and coding individual components, then integrating
them into a complete system.
 Top-Down: Starts with designing the overall system architecture, then breaking it
down into smaller components.

Software Requirements Gathering

 System Requirements: Define the functionalities and capabilities the system must
have.
o Functional Requirements: Specify what the system should do.
 o Non-Functional Requirements: Specify how the system should perform,
including performance, usability, and reliability.

Differentiating User Requirements and System Requirements

 User Requirements: Descriptions of what the users need from the system, often
written in a natural language.
 System Requirements: Detailed specifications of system behavior and
functionalities.

Justifying User Involvement in Software Engineering

User involvement is crucial to ensure the software meets user needs, increases user
satisfaction, and reduces the risk of project failure.

Fact-Finding Techniques

 Interviews: Gathering information through direct conversations.

 Surveys/Questionnaires: Collecting data from a large group of users.
 Observation: Watching users interact with the current system.
 Document Analysis: Reviewing existing documentation and records.

Fact Recording Tools

 Diagrams: Flowcharts, use case diagrams, and data flow diagrams.

 Documents: Requirement specifications, user stories, and meeting notes.

Feasibility Study

A feasibility study assesses the practicality and viability of a proposed project.

Importance of Feasibility Study

A feasibility study helps determine whether a project is worth pursuing by evaluating

technical, economic, legal, and operational factors.

Types of Feasibility

 Technical Feasibility: Assessing if the technology needed is available.

 Economic Feasibility: Evaluating the cost-effectiveness of the project.
 Legal Feasibility: Checking if the project complies with legal requirements.
 Operational Feasibility: Determining if the project can be operationally
implemented.

Analyzing Software Requirements

 Importance of Requirements Validation: Ensures the requirements accurately

reflect user needs and are feasible to implement.
  Requirements Engineering Process: Involves elicitation, analysis, specification,
validation, and management of requirements.
 Requirements Elicitation and Analysis: Gathering and refining requirements from
stakeholders.
 Requirements Management: Tracking and maintaining requirements throughout the
project lifecycle.

Components of an SRS Document

 Introduction: Overview of the document and the project.

 Product Description: Detailed description of the product.
 Software Requirements: List of functional and non-functional requirements.
 External Interface Requirements: Specifications for interactions with other
systems.
 Non-Functional Requirements: Performance, usability, reliability, and security
requirements.

Benefits of an SRS Document to Developers

 Provides a clear and detailed understanding of the project.

 Serves as a reference throughout the development process.
 Helps in managing changes and maintaining consistency.
 Facilitates communication among stakeholders.

Writing an SRS Document

For a given scenario, an SRS document should be written to include all components listed
above, ensuring clarity and completeness to guide the development process.