Assignment Question [Part-1(10%)]

[You can submit before or on 13th Jan, 2025]

Attempt any TWO questions:
Instructions:
 Write your answer with minimum 600 words
 Use IEEE format or format specified by Faculty of Computing and Informatics, JiT, for
references.
 Require inline citations in the document.
 Try to answer that is free from plagiarism.
 Your assignment must follow these formatting requirements i.e.
 Be typed, 1.5 line spacing, using Times New Roman font (size 12), with
one-inch margins on all sides
 Include a cover page containing the name of the assignment, the student’s
name with id number, the teacher’s name, the course title, and the date.

1. Do you have any case studies or real-world examples that demonstrate the application of
software metrics? Also explain the distinction between size and complexity metrics, and
their respective roles in assessing software quality.
2. Choose a specific object-oriented programming language (e.g., Java, C++, C#) and identify
common tools or techniques used to collect object-oriented metrics within that language.
3. Define the concept of size metrics in software development and explain their significance.
Discuss two widely used size metrics for measuring the size of software products. Describe
each metric in detail, including its purpose, measurement technique and units of
measurement.
4. Provide an example scenario where Function Point Analysis (FPA) would be more suitable
as a size metric and another scenario where Lines of Code (LOC) would be more
appropriate. Justify your choices based on the characteristics of the software projects and
the information each metric provides.
5. Describe the steps involved in measuring software size using the Function Point Analysis
(FPA) technique. Discuss the advantages of using FPA as a size metric and any challenges
that may arise during its application.
6. Compare and contrast lines of code (LOC) and cyclomatic complexity as size metrics.
Discuss the strengths and limitation of each metric and explain when it is appropriate to use
one over the other.
7. Define the purpose of object-oriented metrics in software development. Explain the
different types of software reuse, including code reuse and component reuse. Describe each
type and provide examples to illustrate their application.
8. Describe three commonly used object-oriented metrics i.e. coupling, cohesion, and
inheritance metrics. For each metric, explain its purpose, measurement technique, and how
it reflects the characteristics of object-oriented design.
9. Explain the concept of depth of inheritance tree (DIT) as an object-oriented metric. Discuss
its significance in measuring the inheritance hierarchy and potential complexities
associated with excessive inheritance.
10. Research the application of object-oriented metrics in specific domains, such as embedded
systems, web development, or artificial intelligence. Discuss the unique challenges and
considerations in these contexts.
11. Imagine you are working on a software project that aims to improve maintainability.
Suggest two object-oriented metrics that can be used to measure maintainability, and
explain why they are suitable for this purpose.
 Project-based Question [Part-2 (10%)]
[You can submit before or on 13th Jan, 2025]
Attempt any TWO questions:
1. Consider a software project developed using an object-oriented programming language.
You have been assigned the task of assessing the quality and complexity of the project
using object-oriented metrics. In this context, answer the following questions:
a. Choose three object-oriented metrics and discuss their purpose and relevance in evaluating
software quality.
b. For each of the selected metrics, describe the measurement technique or formula used to
calculate the metric.
2. Imagine you have been assigned a software project to develop a web-based e-commerce
application. As part of the project, you are required to measure the size of the software
using appropriate size metrics. Design a plan to measure the size of the internal product
attributes for this e-commerce application. Your plan should include the following
components:
a. Measurement Technique: Describe in detail the measurement technique for each selected
size metric. Explain how you will collect the necessary data and calculate the size metric
values. Specify any tools or resources that will aid in the measurement process.
b. Reporting and Utilization: Describe how the measured size metrics will be reported and
utilized in the context of the software development project. Explain how the size metrics
can contribute to project planning, estimation, and quality assessment.
3. In software development, measuring the length of code, specification, and design
documents is essential for understanding and managing the complexity and maintainability
of a software product. Answer the following questions to demonstrate your understanding
of measuring the length of internal product attributes:
a. Describe three commonly used metrics for measuring the length of code, specification, and
design. For each metric, explain its purpose, measurement technique, and the units of
measurement used.
b. Suggest strategies or best practices for managing the length of code, specification, and
design to ensure maintainability and readability. Discuss how refactoring, modularization,
and documentation can contribute to managing the length effectively.
4. Imagine you are tasked with developing a software system for a library that tracks book
loans, memberships, and inventory. As part of the quality assurance process, you need to
measure internal product attributes related to size.
Scenario: The library software has three primary modules:
Membership Management: Handles registration, renewals, and member data.
Inventory Management: Tracks books, digital resources, and borrowing limits.
Loan Management: Logs borrowing and return activities.
Tasks:
a. Propose three metrics you could use to measure the size of the software’s internal
attributes during development.
b. Discuss how an unusually high size metric in one module might affect the
maintainability and performance of the software.
5. Imagine you're a software architect designing a system for an autonomous drone delivery
service. This system manages a fleet of drones, their flight paths, and package deliveries.
Question:
How would you use object-oriented metrics to evaluate the design of this drone delivery
system? Consider Method Complexity aspects:
Scenario: The "ObstacleAvoidance" method within the "Drone" class needs to analyze
sensor data, predict potential collisions, and calculate evasive maneuvers.
 Metric: How would you measure the complexity of this "ObstacleAvoidance" method?
What are the potential consequences of having highly complex methods in this safety-
critical system?
6. You are part of a team developing a healthcare management system for a hospital. The
system includes modules for patient records, appointment scheduling, billing, and
inventory management. The project must be delivered within a tight deadline, so the team
is encouraged to reuse existing components and libraries wherever possible.
Scenario: The project manager wants to evaluate the software size and the extent of reuse
to ensure efficiency and maintainability.
Tasks:
a. Propose three metrics that can be used to measure the size of the software while
accounting for reused components (e.g., reused lines of code, percentage of reused
modules).
b. Suggest best practices for balancing reuse with the development of new code to
ensure quality and maintainability in the healthcare system.
7. Imagine you're designing a software system for a futuristic smart home. This home is
controlled entirely by a network of interconnected devices and appliances, all
communicating through an object-oriented system.
Question: How would you use object-oriented metrics to evaluate the design of this smart
home system?
Consider Method Complexity aspects:
a. Scenario: The "Thermostat" class has a method called "adjust Temperature" that
considers factors like current temperature, desired temperature, time of day, and even
the presence of occupants in the house.
b. Metric: How would you measure the complexity of this method? What are the potential
consequences of having highly complex methods in this system?
8. Suppose you have been hired as a project manager for a startup developing a smart home
automation system. The system includes features for controlling lighting, temperature,
security cameras, and door locks through a mobile application. Each feature provides
various levels of functionality to cater to different user needs.
Scenario: The stakeholders want to measure the size of the software in terms of
functionality to better understand the scope and potential cost of the project.
Tasks:
a. Propose a methodology to measure the size of the software based on its
functionality (e.g., using Function Point Analysis or similar methods).
b. Imagine that the Security Camera module has significantly more functionality
than initially planned. Discuss how this could affect the overall project size and
timeline.
9. Write a case study on using software metrics to improve code quality in a mobile
Application development project.