DAR ES SALAAM INSTITUTE OF TECHNOLOGY
SOFTWARE ENGINEERING FUNDAMENTALS
COT (06111)
INDIVIDUAL ASSIGNMENT
NAME: ELIA FENIAS RUBEBE
REG. No: 2102202221141
1. Define software engineering and explain its significance in the development process
Software engineering refers to a structured approach to develop, design, implement
and maintaining software systems, by applying engineering principles and knowledge
of programming languages.
The significance of software engineering in the development process is its ability
to provide a structured and systematic approach to creating high quality software that
meets user requirements, is reliable, scalable and cost effective to develop and
maintain.
2. What is the Software Development Life Cycle (SDLC)? Briefly describe each phase.
Software Development Life Cycle refers to a structured process that enables the
production of high-quality, low-cost software in the shortest possible production time.
SDLC phases are as follows;
1. Planning and requirement analysis phase
Involves gathering, analyzing, and documenting user requirements for the
software. This phase aims to understand what the software needs to accomplish,
defining functionalities, constraints, and objectives.
2. Design
Translates the requirements gathered in the previous phase into a blueprint or plan
for the software system. It includes architectural design, database design, user
interface design, and other technical specifications.
3. Implementation(coding)
Actual coding or programming of the software based on the design specifications.
Developers write code in various programming languages, following best
practices and coding standards.
4. Testing
Involves verifying and validating the software to ensure it meets the specified
requirements. Testing includes various techniques like unit testing, integration
testing, system testing, and user acceptance testing to identify and rectify defects
or issues.
5. Deployment(installation)
In this phase, the software is released or deployed into the production
environment. It involves installation, configuration, and making the software
available for end-users.
6. Maintenance
After deployment, the software enters the maintenance phase, where it is regularly
monitored, updated, and enhanced to address issues, bugs, or to introduce new
features. Maintenance can include corrective, adaptive, perfective, or preventive
actions.
3. Differentiate between software development and software engineering.
Software development refers to a part of software engineering in which is focused
more on creating the software itself. WHILE Software engineering involves
applying engineering principles, methodologies and practices to ensure the creation of
high quality and reliable software systems
4. Explain the importance of requirements engineering in software development.
Its importance is that it helps to ensure that the software system being developed
meets the needs and expectation of the stakeholders and that it is developed on time
and with in budget and to the required quality.
5. What is version control, and how does it contribute to effective software
development?
Refers to software tools that help software teams to manage changes to source code
overtime.
It contributes to effective software development since it fosters collaboration
among developers, ensuring simultaneous work on code without conflicts while
maintaining a comprehensive history of changes for easy tracking and issue resolution
and it also acts as a safety net by serving as a backup system allowing retrieval of
earlier versions if needed.
6. Define the term "agile methodology" and provide an example of how it is applied in
software development.
Agile methodology refers to a flexible approach to software development,
emphasizing collaboration, adaptability and customer satisfaction in which it
prioritizes delivering a functional software in smaller increments allowing continuous
improvement.
Example of how agile methodology is applied in software development is that the
development team can be using agile framework such as scrum in which the team
works in short sprits, regularly interacting with the product owner to prioritize
features, deliver working software at the end of each sprint, gather feedback and adapt
to plans accordingly.
7. Explain the role of a software architect in the development process
The role of software architect in the development process is that he plays a vital role
in conceptualizing, designing, guiding and ensuring the successful implementation of
the system architecture, aligning technical decisions with business goals.
8. What are the key differences between waterfall and agile development
methodologies?
AGILE WATERFALL
PROJECT Changes are made well in advance with Performs well when the
SCOPE time and with in budget, it works well scope is well known in
even if the scope is not defined in advance with limited
advance changes
TEAM It consist of small sized dedicated Involves a large team,
teams with high coordination with decreased
coordination among
team members
CUSTOMERS Allows customers to be available Requires customers to
throughout the project be available only at the
milestones
9. Define the term "software testing" and discuss its importance in the development life
cycle.
Software testing refers to the process of evaluating and verifying that a software
product or application does what it is supposed to do.
The importance of software testing in SDLC is that it helps to identify and
eliminate defects or bugs with in the software after development in which they can
range from minor glitches to critical errors that may lead to system crash.
10. .Describe the concept of modularization in software design. Why is it essential?
Modularization refers to the process of breaking down a software system or
application into smaller, manageable, and independent modules or components.
Modularization is essential simply because it makes easy the manageability and
organization due to the break down of the software into smaller modules that are easy
to work with and understand also encourages re-usability simply because code are
separated into small parts hence can be used more that once, and finally it makes easy
debugging since one can know that the problem is found on certain piece of code.
11. Explain the difference between functional and non-functional requirements
Functional Requirements: These are the requirements that the end user specifically
demands as basic facilities that the system should offer. All these functionalities need
to be necessarily incorporated into the system as a part of the contract
Non-functional requirements: These are basically the quality constraints that the
system must satisfy according to the project contract. Example portability, security
and reliability
12. Discuss the importance of documentation in software engineering.
Documentation refers to a clear description of what a particular software does or shall
do.
Importance of documentation are as follows;
a) Makes easy communication. This is simply because it will be shared across team
members and stake holders hence each can understand what the system does.
b) Maintenance: Software development is an ongoing process and applications are
continually updated and modified over time. Documentation provides
a roadmap for developers who are updating or maintaining the software
c) Knowledge sharing: Documentation can also serve as a valuable resource for
knowledge sharing. When developers document their code, they are not only
helping future developers who may work on the same codebase,
13. What is the purpose of a UML (Unified Modeling Language) diagram in software
development?
Unified Modeling Language, is a visual modeling language that helps software
developers visualize and construct new systems.
The purpose on UML in software development is that it play a crucial role in
software development by providing a standardized and visual representation of the
system's structure, behavior, and interactions, facilitating effective communication
and guiding the development process from conception to implementation and
maintenance.
14. Describe the role of a project manager in a software development project.
Software project managers are in charge of the planning, scheduling, budgeting,
execution, and delivery of software and web projects. They ensure the successful
completion of all software projects and also oversee the people performing work on
the projects.
15. Explain the concept of "refactoring" in the context of software maintenance.
Refactoring in software maintenance refers to the process of restructuring existing
code or software systems without changing its external behavior. It involves making
modifications to the internal structure, design, or implementation of the code to
improve its readability, maintainability, performance, or extensibility, without altering
its observable functionality.
16. .What are the key challenges in software project management, and how can they be
mitigated?
a) Resource Allocation and Management: Challenges in allocating and managing
resources, including human resources, budget constraints, and availability of
skilled personnel.
Mitigation: Conduct thorough resource planning and allocation
b) Time and Schedule Management: Difficulties in meeting project deadlines and
managing project schedules due to unexpected delays or dependencies.
Mitigation: Develop realistic and achievable project timelines. Use project
management tools to track progress
c) Quality Assurance and Testing: Insufficient testing leading to quality issues,
bugs, or defects discovered late in the project lifecycle.
Mitigation: Incorporate testing and quality assurance activities throughout the
development process
d) Risk Management: Inadequate identification and management of project risks
that could impact project objectives.
Mitigation: Perform comprehensive risk assessments early in the project. Develop
risk mitigation strategies and contingency plans
17. Define the term "software quality assurance" and explain its role in the development
process
Software Quality Assurance (SQA) refers to a systematic and comprehensive
process within the software development lifecycle that ensures that the developed
software meets specified quality standards, adheres to defined requirements, and
satisfies customer expectations.
Software Quality Assurance is a crucial component of the software development
process that plays a crucial role on ensuring that the developed software meets
defined quality standards, adheres to requirements, functions reliably, and satisfies
customer needs. It encompasses a range of activities aimed at preventing defects,
improving processes, and delivering high-quality software products.
18. Discuss the significance of user involvement in the software development life cycle.
a) Understanding User Needs and Requirements: Users provide critical insights
into their needs, preferences, and challenges.
b) Improved Product Design and Usability: User involvement leads to better-
designed software with enhanced usability. Direct user feedback and involvement
aid in creating user-friendly interfaces, intuitive workflows
c) Validation and Feedback Loop: Regular involvement of users in testing and
validation phases provides immediate feedback on the software's functionality,
allowing for quick adjustments or improvements
d) Continuous Improvement: User involvement fosters a culture of continuous
improvement
19. What is the difference between verification and validation in software testing?
Verification Validation
Definition It is a process of checking if a It is a process of ensuring that the product
product is developed as per meets the needs and expectations of
the specifications. stakeholders.
What it It tests the requirements,
It tests the usability, functionalities, and
tests or architecture, design, and code
reliability of the end product.
checks for of the software product.
It emphasizes executing the code to test
Coding It does not require executing
the usability and functionality of the end
requirement the code.
product.
A few activities involved in
The commonly-used validation activities
verification testing are
Activities in software testing are usability testing,
requirements verification,
include performance testing, system testing,
design verification, and code
security testing, and functionality testing.
verification.
20. Reflect on the ethical considerations in software engineering and the responsibility of
software developers
Here are key ethical considerations and the responsibilities of software developers:
a) Data Privacy and Security: Developers should prioritize the protection of user data
and privacy. They should implement robust security measures, adhere to privacy
regulations, and be transparent about data collection and usage.
b) Bias and Fairness: Developers must strive to mitigate biases in algorithms and
software that could lead to discrimination. Fairness in AI systems, avoiding
reinforcement of social biases, and ensuring equal opportunities for all users are
essential.
c) Transparency and Accountability: Developers should be transparent about how
software functions, its limitations, and potential risks. They should be accountable for
the consequences of their code and decisions made within the software.
d) Accessibility: Creating software that is accessible to users with disabilities is
essential. Developers should consider inclusive design principles to ensure that their
products are usable by all individuals.
e) Environmental Impact: Software should be developed with considerations for
energy efficiency and reduced environmental impact
