ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

How to Avoid Problems When Creating Software Requirements

Updated on January 9, 2018
tamarawilhite profile image

Tamara Wilhite is a technical writer, industrial engineer, mother of two, and a published sci-fi and horror author.

Introduction

Software requirements gathering may be a hurried list of "must haves" or a long laundry list of everything the customer wants, needs and would like to have if money were no object.

How can you avoid problems when gathering and defining software requirements?

Handling Meetings to Gather Software Requirements

Do not let the person most familiar with the requirements mapping notation or requirements documentation software dominate the actual generation of requirements. Their job should be that of a secretary in an organizational meeting, collecting all inputs for group or management review, not acting as a gatekeeper as well as a court recorder.


Gather requirements from all stakeholders, such as software application support and view-only users, not just IT security, managers who use the tool for reports and task delegation and super-users.

Not every complaint will have a solution. Nor does every frustration someone have with the current software version need to become a software requirement for the next build. However, documenting all complaints and concerns reduces the resistance to the project in the future.

Determine if problems can be resolved by changing report settings or improving data imports before rewriting your app.
Determine if problems can be resolved by changing report settings or improving data imports before rewriting your app. | Source

Gathering Software Requirements

Ask context-free questions at the start of the software requirements process to gather global requirements, instead of diving into the weeds up front. Global requirements more easily flow down into detailed ones than pushing the discussion back up to a higher level.


Identify potentially conflicting software requirements up front. Resolve conflicting requirements before going past the requirements phase.

Label whether a software requirement is a "need" or a "want" when it is recorded.

Do not forget to add bug-fixes from the current software version into the requirements to be part of the next software build, unless the bug was fixed in an intermediate patch.

Requirements Management

Pay attention to the assumptions behind your software requirements. If the assumptions change, such as the definition of your user community, some of the software requirements will change as well.

When developing requirements, do not necessarily mandate how the requirement is met. For example, creating a web-based version of a client-server application may be a requirement to move to a cloud based application. However, it does not necessarily have to be built with a specified software suite or run on a particular platform.


Remember the power of inertia. Making changes for the sake of changes or "looking new" alienates users. Only change the appearance of a tool and how one performs basic functions if it makes someone's job easier, whether it is simplifying the number of steps to complete a transaction in that one tool or standardizing the tool set. Software should not follow fashions like cars and clothing, changing interfaces to look like something new, cool or hot on the market today.

Track your software requirements and make sure none of them are redundant or conflicting before you start coding.

Source

Steps to Take Before You Start Writing Code

Gain consensus on requirements before moving forward with coding. However, it is important to realize that it may not be possible to satisfy everyone.

Determine if reported problems are technical in nature, a matter of perception or a need for user training before planning to write code. Requirements for software do not always necessitate rewriting the software, and other options should be explored before altering the software application.

Formally document all software requirements in applications like DOORS. Make the software requirements document a contractually required document to which customers must agree before you start coding. This ensures that customers have signed off on the project requirements before you start work. You gain a legal defense against an expanding scope and new requirements mid-stream, as well as protection against customers rejecting the project because it isn't what they wanted. If the software meets the requirements, they are contractually obligated to accept it.

How to Avoid Problems During Software Development

If a software requirement is found to be too complex to implement as planned, determine if there are other ways to perform the task within the tool, use other available software tools to perform the same task or another way to complete the objective.


Bug-free should be a goal of all software projects. Strive to resolve all major software bugs and as many minor ones as possible during software development, coding and testing.


If mistake-proofing is built into a software application, such as the use of "masks" to enforce a particular data entry format, also include the ability to alter theses masks. For example, a data field format built to enforce American style phone number entries may fail if users try to enter international phone numbers. Ensure that the mistake-proofing is alterable in case it no longer fits the situation.

Review the requirements as new features or functionality are added. Ensure that the new functionality doesn't interfere with existing requirements or alter them, just as the new functions are tested to ensure that they do not interfere with other functions.

Comments

Submit a Comment

No comments yet.

working

This website uses cookies

As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

Show Details
Necessary
HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
LoginThis is necessary to sign in to the HubPages Service.
Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
AkismetThis is used to detect comment spam. (Privacy Policy)
HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
Features
Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
MavenThis supports the Maven widget and search functionality. (Privacy Policy)
Marketing
Google AdSenseThis is an ad network. (Privacy Policy)
Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
Index ExchangeThis is an ad network. (Privacy Policy)
SovrnThis is an ad network. (Privacy Policy)
Facebook AdsThis is an ad network. (Privacy Policy)
Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
AppNexusThis is an ad network. (Privacy Policy)
OpenxThis is an ad network. (Privacy Policy)
Rubicon ProjectThis is an ad network. (Privacy Policy)
TripleLiftThis is an ad network. (Privacy Policy)
Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
Statistics
Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)