Scribd
Upload
40 views8 pages

SDLC Assignment Presentation

The document discusses software requirements traceability which tracks requirements from definition to implementation to ensure software meets user needs. The author traced requirements for a management data analytics module throughout development using a traceability matrix to identify gaps or changes needing implementation.

Uploaded by

Sameer Jung Pandey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
40 views8 pages

SDLC Assignment Presentation

The document discusses software requirements traceability which tracks requirements from definition to implementation to ensure software meets user needs. The author traced requirements for a management data analytics module throughout development using a traceability matrix to identify gaps or changes needing implementation.

Uploaded by

Sameer Jung Pandey
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Analysis of Software Requirements Traceability

Software requirements traceability is the ability to track a software


requirement from its initial definition to its final implementation. This is
important for ensuring that the software meets the needs of the users and
stakeholders.
I have traced the software requirements for the management data analytics
module throughout the entire software lifecycle, from requirements
gathering to implementation and testing. This has been done by using a
traceability matrix. The traceability matrix maps software requirements to
the artifacts that are used to implement them, such as use cases, design
documents, and code.
The traceability matrix has been used to identify any gaps or
inconsistencies in the software requirements. It has also been used to track
changes to the software requirements and to ensure that these changes
are reflected in the implementation.
Approaches to Improving Software
Quality
There are a number of approaches to improving software quality within a software
lifecycle. Two common approaches are:
• Top-down approach: The top-down approach to software quality focuses on the early
stages of the software development process. This includes activities such as
requirements gathering, design, and testing. The goal of the top-down approach is to
ensure that the software is well-designed and that it meets the needs of the users.
• Bottom-up approach: The bottom-up approach to software quality focuses on the
later stages of the software development process. This includes activities such as
coding, testing, and debugging. The goal of the bottom-up approach is to ensure that
the software is free of defects.
I have used a combination of the top-down and bottom-up approaches to improve the
software quality for the Gurkha-Finances project. For example, I have used the top-
down approach to ensure that the software requirements are well-defined and that
the design is sound. I have then used the bottom-up approach to ensure that the
software is implemented correctly and that it is free of defects.
Suitability of Software Behavioural Tools and Techniques

Behavioral design techniques improve software usability and


engagement. Examples include Cialdini's persuasion principles,
anchoring, scarcity, gamification, and UX design. In software, they can
encourage purchases, boost engagement, and enhance user-
friendliness.
Analysis of Software Behavioural Tools
and Techniques
I have used a number of software behavioral tools and techniques to
investigate the given problem. These tools and techniques have been
effective in helping me to collect and analyze data about user behavior.

For example, I have used a heatmap tool to identify the areas of the
software that are most used by users. I have also used a user session
recording tool to record how users interact with the software.
Justification of Data-Driven Software

Data-driven software can improve the reliability and effectiveness of


the software solution by providing insights into how users interact with
the software. This information can be used to identify and fix defects,
improve the user experience, and make the software more efficient.
For example, data-driven software can be used to identify users who
are struggling to complete certain tasks. This information can then be
used to provide the users with additional support or to redesign the
software to make it easier to use.
Impact on Improving Software Quality
The investigative process that I have undertaken on the Gurkha-Finances project will
affect improving the eventual quality of the implemented software application in a
number of ways:
• By ensuring that the software requirements are well-defined and that the design is
sound, the investigation process has helped to reduce the risk of defects in the
software.
• By understanding how users interact with the software and how they make decisions,
the investigation process has helped to identify potential usability problems and to
design the software to be more user-friendly.
• By collecting and analyzing data about user behavior, the investigation process has
helped to identify areas where the software can be improved to be more efficient and
effective.
Overall, the investigative process has helped to improve the quality of the Gurkha-
Finances project by reducing the risk of defects, improving the user experience, and
making the software more efficient and effective.
Examples from the Information Booklet

The information booklet for the Gurkha-Finances project states that the
management data analytics module should be "easy to use and navigate" and
that it should provide "clear and concise insights into the company's financial
performance.“

The investigative process that I have undertaken has helped to ensure that the
management data analytics module meets these requirements. For example, I
have used user interviews and task analysis to understand how users interact
with the software and to identify their pain points. I then used this information
to design the software to be more user-friendly and to provide clearer and
more concise insights into the company's financial performance.
Examples from Related Sectors and Projects

A study by Forrester Research found that companies that use data-driven


software are more likely to have higher customer satisfaction rates and lower
costs. The study also found that data-driven software can help companies to
improve their decision-making and to make better use of their resources.

Another study, by McKinsey & Company, found that companies that use data-
driven software are more likely to be successful in their digital transformations.
The study also found that data-driven software can help companies improve their
agility and responsiveness to change.

These examples from related sectors and projects show that data-driven software
can be used to improve the quality of software applications in a number of ways.

You might also like