Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  What do you call this document?
Previous Previous
 
Next Next
New Post 2/23/2011 5:58 PM
Resolved
User is offline EJK
4 posts
No Ranking


What do you call this document? 

 A potential client of mine sells a Distribution Management System.  When they sell and implement it for a company they take the base product and customise it as required. They are tasking me with writing a document that covers all the base functionality of the product.   It will contain details such as navigation, screenshots, field length, field type, field options, validation, use cases etc.    This document will be used as the base doc which their analysts wil then use when writing up the actual functional spec for acustomised implementation.  The modified doc will be one that the customer needs to sign off on, prior to actual development and implementation, and will also be used by developers to do the build.

Would you call this base document a functional specification or is there another name?

 
New Post 2/23/2011 9:53 PM
User is offline Adrian M.
764 posts
3rd Level Poster




Re: What do you call this document? 

I definitely sounds like a functional specification document as it doesn not include the requirements (why) but the functionality of the system (what & how).

You can call it the "Base Functional Specification" document.

It sounds like your company's process is to take the new customer requirements and analyze them in the contex of the "Base Functional Specification"  the end result will be a modified system which will be based on the new Functional Specification which was created from the base specs.

Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 2/24/2011 12:44 AM
User is offline EJK
4 posts
No Ranking


Re: What do you call this document? 

 Thanks Adrian.

 
New Post 2/25/2011 11:01 AM
User is offline htbaBA
7 posts
10th Level Poster


Re: What do you call this document? 
Modified By Adrian M.  on 2/27/2011 2:16:05 AM)

 adrian wrote

I definitely sounds like a functional specification document as it doesn not include the requirements (why) but the functionality of the system (what & how).

You can call it the "Base Functional Specification" document.

It sounds like your company's process is to take the new customer requirements and analyze them in the contex of the "Base Functional Specification"  the end result will be a modified system which will be based on the new Functional Specification which was created from the base specs.

Adrian

 

A agree with Adrian.  You can also call it something like "Base Document - [insert system name]"

-htbaBA

 
New Post 3/20/2011 8:45 PM
User is offline EJK
4 posts
No Ranking


Re: What do you call this document? 

Thanks!

The document my customer currently uses is a specification that is structured completely around the user interface (modules, tabs, button functions, field display, field validation etc).  My customer really likes this structure cause it gives their customers a nice understanding of the interface and makes testing or checking of the interface easy.  BUT, it really lacks any view of the processes of the application.  This lack of process in the document makes it very difficult for the customer to see where the gaps exist between their own processes and the processes supported by the application. 

My gut feel is that the doc should be structured around process and should reference the user interface where this is useful.... Is this correct?

Does anyone have a good example of a specification that is structured around the user interface, but still neatly, concisely references process too (or vice versa)?

Thanks

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  What do you call this document?

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC