Software Engineering ( DCOM ) 6th Sem

2078/2079
Question Paper Solution.
Compile by Arjun Chy

Website :- www.arjun00.com.np

1 a) Differentiate between following terms:

i) Program Vs software
Program Software
A program is a set of instructions that Software is a collection of programs,
perform a specific task or function. data, and instructions that tell a
computer what to do.
A program is usually a single executable Software can be composed of multiple
file or a set of files that are compiled or programs that work together to achieve
interpreted. a particular goal.
Programs are typically smaller in size Software is larger in size and provides a
and are designed to perform specific range of functions and capabilities.
tasks or functions.
Programs are created by programmers Software is created by software
or developers. development teams.
Programs require an operating system Software can run independently of an
to run. operating system or be dependent on
one.
Examples of programs include web Examples of software include operating
browsers, media players, and word systems, office suites, and graphics
processors. programs.

www.arjun00.com.np
 ii) Software process and software process model
Software process software process model
Refers to the set of activities and tasks Refers to a specific framework that
that are required to develop a software defines the various stages involved in
product. software development.

Includes all the steps involved in software It provides a structured approach to

development, from requirement software development that helps to
gathering to testing and maintenance. ensure that all necessary steps are
followed.
The software process can vary depending The software process model is a
on the project, organization, and standardized approach that is used to
industry. guide software development projects.
It is generally more flexible and adaptable It is more rigid and structured, and may
to changes. not allow for much flexibility.
The software process is focused on the The software process model is focused on
actual development of the software the process of software development
product. itself.
Examples of software processes include Examples of software process models
Agile, Waterfall, and Spiral. include the V-model, Iterative model, and
Incremental model.

b) What are the good characteristics of software? Explain.

➢ The good characteristics of software are:-
• Correctness: The software should perform the intended task accurately and
without errors. The output of the software should be consistent and reliable.
• Usability: The software should be user-friendly, easy to use, and have a clear
and intuitive user interface. Users should be able to easily navigate the
software and complete tasks efficiently.

www.arjun00.com.np
 • Efficiency: The software should be efficient in its use of system resources such
as memory, processing power, and network bandwidth. It should be optimized
for performance to ensure that it runs smoothly and quickly.
• Integrity: The software should maintain the integrity of data by ensuring that
it is protected from unauthorized access or modification. Data should be
securely stored and protected from corruption, loss, or theft.
• Adaptability: The software should be adaptable and flexible to changing
requirements or environments. It should be easily configurable to meet
changing needs without requiring a complete redesign or rewrite.
• Accuracy: The software should be accurate in its calculations and data
processing. It should be able to handle a wide range of input data and produce
reliable and accurate results.
• Maintainability: The software should be easy to maintain and update, with
clear documentation and modular design. It should be easy to modify, debug,
and enhance as needed.
• Portability: The software should be portable, meaning it can run on different
hardware and operating systems without requiring significant modifications. It
should be designed to work on a range of platforms and environments.

2. a) Describe spiral model with its advantages and disadvantage.

➢ The spiral model is a software development model that emphasizes on
risk analysis, which involves a continuous iteration of prototyping and
risk management activities. It is a combination of waterfall model and
iterative development model, with a strong emphasis on risk analysis
and customer feedback.

➢ The spiral model consists of four phases:

• Planning: This phase involves identifying the objectives, alternatives,
constraints, and risks associated with the project.
• Risk Analysis: This phase involves analyzing the risks associated with the
project, such as technical, cost, schedule, and personnel risks. www.arjun00.com.np
 • Engineering: This phase involves developing the software product, which
includes designing, coding, testing, and integration.
• Evaluation: This phase involves evaluating the results of the previous phase,
such as identifying any errors, reviewing the project's progress, and planning for
the next iteration.

➢ Advantages of Spiral Model:-

▪ Risk Analysis: The spiral model allows for risk analysis and mitigation, which can
help reduce project failure rates.
▪ Customer Feedback: The spiral model involves continuous customer feedback,
which helps in meeting the customer's requirements.
▪ Flexibility: The spiral model is flexible and can be adapted to the changing
requirements of the project.
▪ Early Detection of Defects: The spiral model involves continuous testing and
evaluation, which can help in early detection of defects and errors.

➢ Disadvantages of Spiral Model:-

▪ Complexity: The spiral model is more complex than other software development
models, which can make it difficult to manage.
▪ Costly: The spiral model can be more costly than other models because of the risk
analysis and continuous prototyping.
▪ Time-consuming: The spiral model is time-consuming due to the continuous
iteration of prototyping and risk analysis.
▪ Not Suitable for Small Projects: The spiral model is not suitable for small projects
because of its complexity and cost. It is more suitable for large and complex
projects.

In conclusion, the spiral model is an effective software development

model that emphasizes on risk analysis and customer feedback. However,
it may not be suitable for small projects and can be complex, costly, and
time-consuming.
www.arjun00.com.np
b) Explain RAD (Rapid application development) model.
➢ Rapid Application Development (RAD) is a software development model that
prioritizes rapid prototyping and quick feedback over lengthy planning and
development cycles. It was developed to address the need for faster software
development in response to changing business needs and technology trends.

➢ The RAD model has the following phases:

• Requirements Planning: This phase involves gathering business requirements,

defining the scope of the project, and identifying potential risks and
challenges.
• User Design: In this phase, users are involved in the design process, providing
feedback on prototypes and helping to refine the system.
• Construction: This phase involves building the software system, including
coding, testing, and integration.
• Cutover: In this final phase, the system is installed and implemented, and
training is provided to users.

➢ Advantages of RAD model:-

• Rapid development and delivery of software
• Improved communication and collaboration between developers
and users
• Flexibility and adaptability to changing requirements
• Reduced development time and cost
• Early detection and resolution of issues and defects

www.arjun00.com.np
 ➢ Disadvantages of RAD model:
• Requires highly skilled and experienced developers
• Reliance on customer involvement and feedback
• Can result in incomplete or insufficient documentation
• May not be suitable for large or complex projects
• Relies heavily on prototyping and may not always produce a final
product that meets all requirements.

3. a) Explain the detail task in a software configuration

management process with example.
➢ The detailed tasks involved in software configuration management
process along with examples:

• Configuration Identification: In this task, the software configuration

items (SCIs) are identified and labeled with unique identifiers. The
objective is to identify and track each item throughout the software
development life cycle. For example, the source code files, test cases,
documentation, and project plans can be identified as SCIs.

• Baseline: In this task, a baseline of the software is created and managed.

The baseline includes all the software configuration items that are frozen
and released for further development or testing. For example, when a
new version of the software is released, a baseline is created, and any
further changes are made to the new version, keeping the original
baseline unchanged.

www.arjun00.com.np
 • Change Control: In this task, changes to the software configuration items
are managed and controlled. The objective is to ensure that any changes
are properly reviewed, approved, and implemented. For example, if a
bug is found in the software, a change request is raised, and the change
is made only after it has been approved by the relevant stakeholders.

• Configuration Status Accounting: In this task, the status of each software

configuration item is tracked throughout the software development life
cycle. The objective is to ensure that the status of each item is known at
all times. For example, the status of each test case can be tracked to
determine whether it has passed or failed.

• Configuration Audits and Reviews: In this task, the software

configuration is audited and reviewed to ensure that it meets the
requirements and quality standards. The objective is to identify any
issues or defects in the software configuration and take corrective action.
For example, a code review can be conducted to ensure that the source
code meets the coding standards and is of high quality.

b) Define Risk. Explain the process of Risk management.

➢ Risk refers to the possibility of an event or situation that may
have negative consequences, such as financial loss, damage to
reputation, or failure to achieve a project goal. In software
development, risks can arise from various factors such as project
requirements, technology, resource availability, and external
factors.

www.arjun00.com.np
➢ Risk management is the process of identifying, analyzing, evaluating, and
mitigating risks that can affect a project's success. It involves identifying
potential risks and developing plans to address them in a timely and
effective manner. The following are the steps involved in the risk
management process:
• Risk Identification: In this step, potential risks are identified by
gathering information from stakeholders, analyzing historical data, and
using various techniques such as brainstorming, checklists, and
surveys. For example, a software project may identify risks related to
technology, requirements, and resource availability.
• Risk Analysis: In this step, the identified risks are analyzed to
understand the likelihood and impact of each risk. This helps to
prioritize risks and develop mitigation plans. For example, a risk
related to technology may be analyzed to determine the likelihood of
occurrence and its impact on the project's success.
• Risk Evaluation: In this step, the risks are evaluated to determine the
acceptable level of risk for the project. This involves considering the
impact of the risk on the project's goals and objectives, as well as the
cost and time required to mitigate the risk.
• Risk Mitigation: In this step, plans are developed to mitigate the
identified risks. This may involve avoiding the risk, transferring the risk
to another party, accepting the risk, or implementing risk reduction
measures. For example, a risk related to requirements may be
mitigated by involving the customer in the requirements gathering
process.
• Risk Monitoring: In this step, the risks are monitored throughout the
project to ensure that the mitigation plans are effective and to identify
new risks that may arise. This involves tracking the progress of
mitigation plans and updating the risk management plan as necessary.
www.arjun00.com.np
4. a) What do you mean by requirement elicitation? Write down various
methods of gathering requirement and explain them.
➢ Requirement elicitation is the process of identifying, gathering, and
defining the requirements for a software system. It involves communicating
with stakeholders to understand their needs, desires, and expectations for
the system. The main goal of requirement elicitation is to ensure that the
software system meets the needs of its users and stakeholders.

➢ There are various methods of gathering requirements, including:

• Interviews: This method involves one-on-one discussions with
stakeholders to understand their needs and expectations. Interviews are
useful for collecting detailed information from stakeholders.
• Surveys and Questionnaires: These methods involve sending out questionnaires or
surveys to stakeholders to gather their requirements. Surveys and questionnaires
can be used to gather a large amount of data quickly and are useful when working
with a large number of stakeholders.
• Focus Groups: This method involves bringing together a group of stakeholders to
discuss their needs and expectations for the system. Focus groups can be useful for
generating new ideas and identifying common themes among stakeholders.
• Prototyping: This method involves creating a prototype or mockup of the software
system to gather feedback from stakeholders. Prototyping can help stakeholders
visualize the system and provide feedback on its functionality and usability.
• Observation: This method involves observing stakeholders in their work
environment to understand their needs and requirements. Observation can be
useful for identifying requirements that stakeholders may not be aware of or cannot
articulate.
• Document Analysis: This method involves reviewing existing documentation related
to the system, such as business plans, user manuals, and technical specifications.
Document analysis can help identify requirements and constraints that may have
been overlooked.
• Brainstorming: Brainstorming is a technique that can be used to generate ideas and
requirements from stakeholders. It involves bringing together a group of people and
encouraging them to generate as many ideas as possible in a short period of time.
There are no constraints on the ideas generated, and all ideas are accepted and
recorded for further analysis.
www.arjun00.com.np
b) Why do we use Use-case diagram in object-oriented
development? Draw a Use-case diagram for an Online course
registration system.
➢ We use Use-Case diagrams in object-oriented development to visually
depict the functional requirements of a system from a user's
perspective. It provides a high-level overview of the system's behavior
and helps in identifying the actors and use-cases.

➢ A Use-Case diagram for an Online course registration system can have

actors like student, instructor, and admin. The main use-cases can be
student registration, course enrollment, payment processing, grade
submission, and report generation.

➢ Here is a sample Use-Case diagram for an Online course registration system:

www.arjun00.com.np
5. a) Describe about the software design model and design strategies.
➢ Software design is the process of defining the architecture, components,
modules, interfaces, and data for a software system to satisfy specified
requirements. It involves a number of design models that capture
various aspects of the software design, such as the procedural design,
interface design, architectural design, and data design.
• Procedural design:
➢ Procedural design is the process of defining the sequence of operations or steps that a
software system must perform to accomplish a specific task or goal. This design model
defines the flow of control within the software system, including the input and output
data, the algorithms to be used, and the processing logic. It involves breaking down a
complex task into smaller, more manageable procedures that can be executed step-by-
step.
• Interface design:
➢ Interface design is the process of defining the external interfaces of the software system,
including the user interface and the system interface. This design model focuses on the
user experience and how users will interact with the system. It defines the layout and
functionality of the graphical user interface (GUI) and the methods for input and output
between the software system and other systems or devices.
• Architectural design:
➢ Architectural design is the process of defining the overall structure of the software
system, including the components, modules, and subsystems. This design model focuses
on the high-level view of the system and how the components interact with each other to
achieve the desired functionality. It involves choosing the appropriate architecture style,
such as client-server, peer-to-peer, or event-driven, and defining the relationships
between the components.

• Data design:
➢ Data Design: Data design is a software design model that focuses on defining the data
structures and data flow of the software system. This involves identifying the types of
data that the software system will handle, how the data will be stored and retrieved, and
how the data will be processed and transformed.

www.arjun00.com.np
➢ Software design strategies refer to a systematic approach to creating a software
design that meets user needs and requirements. These strategies help to plan,
organize and execute the software design process. Here are some common
software design strategies:

• Structured Design Strategy: This is a traditional approach that involves breaking down the
software design process into smaller, more manageable components. Each module or
component is designed independently before being combined with others to create the
final software design.

• Object-Oriented Design Strategy: This approach is based on designing software based on

objects or entities. It helps to create modular and reusable code that can be easily
maintained and updated. Object-oriented design strategy uses the concepts of
encapsulation, inheritance, and polymorphism to design software.

• Agile Design Strategy: This is an iterative approach that involves creating software in small
increments or sprints. It helps to deliver software quickly and efficiently while allowing for
flexibility and adaptability in the design process. Agile design strategy emphasizes
collaboration between the development team and stakeholders.

• User-Centered Design Strategy: This strategy focuses on designing software with the user
in mind. It involves gathering user feedback and incorporating it into the design process to
create software that meets their needs and expectations.

• Domain-Driven Design Strategy: This strategy is based on designing software that reflects
the real-world domain it is intended to serve. It involves defining the domain model and
designing software that implements it.

The functions of software design strategies include identifying user needs and
requirements, defining the software design goals and objectives, planning the
software design process, creating a design that meets user needs and
requirements, and testing and validating the software design.

www.arjun00.com.np
b) What is software metrics? Explain it with examples.
➢ Software metrics refers to the measurement and analysis of software systems or
projects in order to evaluate their quality, efficiency, and effectiveness. These
metrics help software developers and project managers make informed decisions
about software development and maintenance.

➢ There are various types of software metrics, such as product metrics, process
metrics, and project metrics. Here are some examples:

• Product Metrics: These metrics measure the quality and characteristics of the
software product itself. Some examples are:
▪ Lines of code: measures the size of the software codebase
▪ Cyclomatic complexity: measures the complexity of the code and identifies
potential trouble spots
▪ Code coverage: measures the percentage of code that is executed by
automated tests

• Process Metrics: These metrics measure the efficiency and effectiveness of the
software development process. Some examples are:
▪ Defect density: measures the number of defects found per unit of code
▪ Lead time: measures the time it takes from starting a task to its completion
▪ Code review comments: measures the number of comments made during
code reviews

• Project Metrics: These metrics measure the progress and success of the software
development project. Some examples are:
▪ Schedule variance: measures the difference between planned and actual
project timelines
▪ Cost variance: measures the difference between planned and actual project
costs
▪ Customer satisfaction: measures the satisfaction level of the end-users or
customers of the software product.
www.arjun00.com.np
6. a) What is software quality? Discuss about software reliability
model.
➢Software quality refers to the degree to which a software product meets its
requirements and is free from defects or errors. High-quality software is reliable,
efficient, maintainable, and meets the expectations of its users.

➢ Software reliability model is a mathematical model that helps to estimate the

reliability of a software system. Software reliability models are used to predict and
analyze the behavior of a software system under specific conditions and to
identify potential risks and vulnerabilities. The goal of software reliability models
is to provide an estimate of the probability of failure of a software system over a
specific period of time.

➢ There are several ways to categorize software reliability models based on their
nature or characteristics. Here are some commonly used categories:

• Execution-based models: These models are based on observed failures during

software execution, such as the time between failures (TBF) and failure intensity (FIT)
models.
• Failure-based models: These models are based on observed failures and the
development of a failure distribution function, such as the Weibull distribution,
exponential distribution, and lognormal distribution models.
• Fault-based models: These models are based on the number of faults or defects in the
software, such as static and dynamic fault-based models.
• Statistical models: These models are based on statistical analysis of data collected
during testing, such as non-parametric and parametric models.
• Markov models: These models are based on Markov processes to model the reliability
of complex and interdependent software systems.
• Bayesian models: These models are based on Bayesian statistics to assess the
reliability of software systems in situations with limited or highly variable data.
• Hybrid models: These models are combinations of two or more of the above models to
provide a more comprehensive assessment of software system reliability.

It's important to note that these categories are not mutually exclusive, and some models
can fall into multiple categories depending on how they are designed and used.
www.arjun00.com.np
b) List and explain different types of software testing.
➢ Testing is the process of evaluating a software product to determine whether it
meets its specified requirements and to identify any defects or errors that need to
be addressed. The goal of testing is to ensure that the software product is of high
quality and performs as expected.

➢ There are several types of software testing that can be performed to ensure the
quality of a software product. Some of the most common types of software testing
include:

• Unit Testing: This is the testing of individual software components or modules to

ensure that they function correctly and meet their specifications. Unit testing is
usually performed by developers themselves as part of the development process.

• Integration Testing: Integration testing is the process of testing how different

software components work together as a whole. This is done to ensure that the
system is functioning as intended and that all the components are working
together seamlessly.

• System Testing: This is the testing of the complete software system as a whole.
System testing checks if the software meets its functional and non-functional
requirements and if it meets the user's needs. This testing is typically performed by
a dedicated testing team.

• Acceptance Testing: Acceptance testing is performed to ensure that the software

product meets the customer's requirements and that it is ready for deployment.
This testing is usually performed by the customer or end-users of the software.

• Regression Testing: Regression testing is performed to ensure that changes made

to the software system do not adversely affect the existing functionality of the
system. It is done after any change to the software to make sure that everything
still works as expected.
www.arjun00.com.np
 • Performance Testing: Performance testing is performed to test the speed, scalability,
and stability of the software system under different conditions, such as different user
loads or network speeds.

• Security Testing: Security testing is performed to identify and mitigate potential

security risks and vulnerabilities in the software system. It is done to ensure that the
system is secure and protected from external threats.

• Usability Testing: Usability testing is performed to evaluate the software's user

interface and overall user experience. It is done to ensure that the software is user-
friendly and easy to use.

Each type of testing has its own goals and objectives, and they are all necessary for
ensuring the quality of the software product.

7. Write short notes on: (Any Two)

i) COCOMO model
➢ COCOMO (Constructive Cost Model) is a software cost estimation model developed
by Barry Boehm in the late 1970s. It is a well-known model used for estimating the
cost, effort, and time required for developing a software system.
COCOMO is a top-down model that estimates the software development effort
based on the size of the software project, the complexity of the software, and other
factors such as the team's experience, project constraints, and development
environment.The model takes into account three different levels of software
development:
▪ Basic COCOMO
▪ Intermediate COCOMO:
▪ Detailed COCOMO.

COCOMO has been widely used in the software industry for several decades, and it remains a
popular method for estimating software development costs and efforts. However, it has been
criticized for not taking into account the complexity of modern software systems, which often
involve multiple technologies and platforms. Therefore, it is important to use COCOMO in
combination with other estimation techniques to get a more accurate estimate of software
development costs and effort. www.arjun00.com.np
ii) Quality assurance
➢ Quality assurance (QA) is a process of ensuring that a product or service meets the
required standards and customer expectations. It is a proactive approach that
focuses on preventing defects and ensuring that the product or service meets the
required quality standards.

➢ The primary goal of quality assurance is to ensure that the product or service meets
customer requirements and is of high quality. This is achieved through a range of
activities, including:
▪ Defining and implementing quality standards: Quality standards are defined
to ensure that the product or service meets customer expectations. These
standards are used as a benchmark to measure the quality of the product or
service.
▪ Quality planning: Quality planning involves developing a plan to ensure that
the product or service meets the required quality standards. This includes
identifying the quality objectives, defining the quality requirements, and
developing a plan to achieve those objectives.
▪ Quality control: Quality control involves monitoring and testing the product or
service to ensure that it meets the required quality standards. This includes
conducting inspections, audits, and tests to identify any defects or issues.
▪ Continuous improvement: Continuous improvement involves identifying areas
for improvement and implementing changes to improve the quality of the
product or service. This includes collecting feedback from customers, analyzing
data, and making improvements based on that feedback.

In summary, quality assurance is a process of ensuring that a product or service

meets the required quality standards and customer expectations. It involves defining
and implementing quality standards, quality planning, quality control, and
continuous improvement. By implementing a quality assurance process,
organizations can improve customer satisfaction, reduce costs, and improve the
overall quality of their products or services.

www.arjun00.com.np
iii) Verification Vs validation
➢
Verification Validation

• Process of evaluating a product, • Process of evaluating a product,

system, or component to system, or component to
determine whether it meets its determine whether it meets the
specified requirements customer's needs and
expectations
• Involves checking whether the • Involves checking whether the
product or system has been built product or system meets the
according to the specifications user's requirements and
and design expectations

• Focuses on the process of • Focuses on the end result of the

building the product or system product or system
• Can be done through reviews, • Can be done through user
walkthroughs, and inspections acceptance testing, usability
testing, and performance testing
• Done by developers or testers • Done by customers or end-users
• Examples include verifying that • Examples include validating that
the software code matches the the software meets the user's
design specification, or that the needs, or that it performs its
requirements have been intended functions
implemented correctly

• Helps to ensure that the product • Helps to ensure that the product
or system is built correctly or system is useful and meets
the customer's expectations

www.arjun00.com.np