Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  System Specification Document -Customer
Previous Previous
 
Next Next
New Post 1/20/2010 11:44 AM
User is offline Mesh
2 posts
No Ranking


System Specification Document -Customer 
Hi All, I am analyzing a garment system for a customer, I produced Activity Diagram(Swim Lane) and Context Diagram for now, I am planing to produce Use cases, Use case specifications and after that the ERD and Table scheme. At the end I am planing to sketch the Screens of the project In addition to descriptions. But I have some questions and I hope you help me 1. Should I use DFDs 2. What should the document that will be presented to the client contains? Thank You All, Mesh
 
New Post 1/22/2010 7:21 PM
User is offline Jarett Hailes
155 posts
6th Level Poster




Re: System Specification Document -Customer 

Hi Mesh,

Good questions!  I am not very prescriptive when it comes to documentation - I think you need to determine what a) works for you and b) works for the people you interact with.  So I would ask myself the following questions:

  • What written documentation do I need to provide to my customer so that they can both understand:
    • How the system will support the business process(es) that the customer has
    • How the system interacts with people and other systems in those processes
    • What the system is expected to do
    • What considerations, limitations, etc. there are on the system
  • What written documentation do I need so that developers can actual create the solution that the customer expects based on the above?

Sometimes the documentation to accomplish these tasks can be the same, other times it needs to be different.  When it's different it needs to be clearly documented how the documents translate to one another.

I find that most customers do not understand a lot of the fancy diagrams and verbiage that we put in front of them, so Iusually  use simple yet effective diagrams and documentation (i.e. not use cases, state charts, DFDs, etc.).  Surprisingly my developers usually also like this documentation since it doesn't use artifacts that may misrepresent what the client really wants.  I'll rant on that another day...

Anyway, I would come up with a brief template/snippet of your total documentation and show it to the client to make sure they understand the information.  If they are comfortable with the presentation of the information then go to your developers and do the same.  If both can use the same set of documentation then you're good to go.  If the developers require additional information or a different format, then come up with a way that you'll be able to translate the details and also trace the translation.

 
New Post 1/23/2010 10:55 AM
User is offline Mesh
2 posts
No Ranking


Re: System Specification Document -Customer 
Hi Larimar,
Thank you for response, The documentation that I prepare will be used by the client's development team to implement the solution.
So could you list in titles the chapter that I could include in the documentation because this will be a great help.
 
New Post 1/25/2010 8:07 AM
User is offline Jarett Hailes
155 posts
6th Level Poster




Re: System Specification Document -Customer 

Hi Mesh,

Just to clarify - the client is both the end business user as well as the development team that will implement the solution?

If so, I would recommend sitting down with the development group and ask them what they're looking for.  The artifacts that you described before sound reasonable for a development group.  Just don't forget to ensure that the business side of the client also understands what will be built before moving ahead with development.

 
New Post 1/25/2010 11:51 AM
User is offline Mesh
2 posts
No Ranking


Re: System Specification Document -Customer 
Thx Larimar
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  System Specification Document -Customer

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...

 



Upcoming Live Webinars




 

Copyright 2006-2022 by Modern Analyst Media LLC