Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Writing BRS and FS for a vendor product
Previous Previous
 
Next Next
New Post 1/10/2015 4:19 AM
User is offline Jesse
1 posts
No Ranking


Writing BRS and FS for a vendor product 

Hi,

The project I am currently working on aims to replace an existing vendor system with an upgraded vendor system (same vendor) whereby the upgraded system is enhanced and richer in functionality than its predecessor. There are a number of reasons for the upgrade - support for existing system is ceasing soon, need to be compliant with legislative changes and the new system provides more functionality that could add value to the business.  The system does not have a UI. It is an engine that sits behind a loan origination system and is used to assess the customer's credit worthiness.

I have the following questions:

- In this situation what should the business requirements contain since we are not building anything from scratch? We are simply taking something off the shelf, may apply minimal customisation, and implementing it. Should it still contain requirements as if the system is being built from scratch eg. variabes that need to be assessed, frotend system having to be notified of the outcome of the decision made by the engine etc?

- Would a functional spec be required? If so, should it be written by us or the vendor?

- I would assume that a gap analysis will need to be performed to determine the gaps and impacts

- Are there any other BA activities that I have missed?

- Should use cases be used since their is no UI? Another system is the frontend.

We are constrained by an ambitious timeline also so need to consider what the quickest process is for the BA to convey the details as per the above.  

Would love people's thoughts. Thanks kindly.

 

 

 
New Post 1/11/2015 4:42 PM
User is offline NitWitNick
259 posts
5th Level Poster


Re: Writing BRS and FS for a vendor product 
Modified By NitWitNick  on 1/11/2015 7:46:46 PM)

I'd probably start first with the vendor and ask questions, this will give you a road-map to develop: Any tools they have for upgrading ... software, database, etc).  Is the O/S you have good for the new upgrade (do you need to upgrade to Win 8 from XP). If so, this is a FRESH install ... and would take time installing O/S, Software, Database Conversion ... etc.

If not, then get info on the database upgrade ... will it work as is or do you have to export, map and upload into the new one ? How about current software settings ... does the conversion keep them or do you have to reset everything.

At the Hardware level, ... do they meet the specifications for the new system (CPU, Memory, Video Cards, etc) ... Will it use your network, Routers, VPN's, etc. or is there an investment needed for upgrading.

How much different is the upgrade ... will the users be productive right away or do they have to be trained on the new software.

When will this upgrade take place ... night, weekend ... etc. 

Who is scheduled to be there. Systems people, network, users ... How long will it take.

Do you have some users scheduled for testing after the upgrade (make sure the database updated correctly, User Interfaces, etc.)

Do you have User Acceptance documents to be signed off.

How about a Roll-Back plan if it does not go as expected.


Remember to talk to the people who will do the conversion ... get estimated times from each one and system upgrade information so you can calculate time and costs to present to management / stakeholder.

-----

Start at the top (Vendor),  get the information and specs and work down ... talk to developers, DBA's ... anyone there who will do the conversion and create a document of what will be done ... including contact names just in-case.


If ALL FAILS ... do you have an Upgraded Resume ?

Just kidding


Have Fun


 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Writing BRS and FS for a vendor product

Community Blog - Latest Posts

Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

Requirements Life Cycle Management with Azure DevOps
Jul 05, 2020
0 Comments
Requirements management is a critical function for business analysis. Requirements management is focused on ensuring that the business users and stake...
Copyright 2006-2020 by Modern Analyst Media LLC