Need SRS Document

I'm a Bsc degree holder in computer science. I have worked on many papers in report writing, research.I have read and understood your requirement and I know you will never regret, thank you.

Hi, We have done similar work in past. The pdf attached has the modules and specification, so do you want a detailed version of same doc or you want this type of content for your software? Please message us so that we can share our past work which we had done for a few portals like Jewellery eCommerce and multiple seller eCommerce.

A proposal has not yet been provided

Hi, I've over 9+ years of experience in this field and I'm very good in requirements gathering and preparing various documentation. I already did this kind of work and completed it successfully. I'm ready to start your project immediately. I also looked into the attached document for your Smart Inventory project and I'm very confident of creating SRS document for the same. Looking forward your reply... Regards, Chitra

I always make sure to understand what my client needs to bring value to their articles, I respect deadlines, I’m very responsible and serious about my freelancer job. I can deliver you excellent quality work on your topic

Have worked as a business Analyst. I have a strong understanding the inventory processes and have worked on ERP projects for the last 30 years.

I'm new to Freelancer, but have been a technical writer for over 20 years, and have worked on SRS & FS docs in the past. 'Happy to discuss more when we speak. I like to approach SRS documents from a process-design perspective, listing out the following, ideally, in order. 1. The application's objectives, its context, and target audience profile 2. Key terms and reference documents associated with the application and industry 3. Functional and technical constraints that may impact the application's functionality 4. The modules that make up the application and the interaction between them (flows & text) 5. The user roles that will access these module, and their access & responsibilities in each module 6. The tasks that users can perform in each module 7. Use cases and cross-references associated with each task 8. Detailed logical data model (drawn from tasks and use cases) 9. Security requirements 10. Any additional specifications 11. Features identified but planned for future releases I hope this approach works for you. Personally, I have found the process-driven approach the most effective for SRS / feature specifications documentation. This approach allows one to drill down across levels much more effortlessly, helps create documentation that is more interconnected, and creates a more systemic image of the end product in the team's mind. I look forward to discussing this in more detail when we speak.

I am ERP \ BI expert with more than 10 years of consulting career, I can draft your SRS within no time and can also share already created document for an idea to start with.