This document outlines a student micro-project proposal to create a Software Requirements Specification. A team of 4 students - Advait Kamthekar, Shivani Bodke, Pragya Pal, and Dhruv Nandgaonkar - will work to understand SRS concepts and documentation. They will collect information, draft the SRS format over 5 days from April 7-12, with tasks divided among team members. The goal is to learn how to specify software requirements for a customer in a structured document.
This document outlines a student micro-project proposal to create a Software Requirements Specification. A team of 4 students - Advait Kamthekar, Shivani Bodke, Pragya Pal, and Dhruv Nandgaonkar - will work to understand SRS concepts and documentation. They will collect information, draft the SRS format over 5 days from April 7-12, with tasks divided among team members. The goal is to learn how to specify software requirements for a customer in a structured document.
This document outlines a student micro-project proposal to create a Software Requirements Specification. A team of 4 students - Advait Kamthekar, Shivani Bodke, Pragya Pal, and Dhruv Nandgaonkar - will work to understand SRS concepts and documentation. They will collect information, draft the SRS format over 5 days from April 7-12, with tasks divided among team members. The goal is to learn how to specify software requirements for a customer in a structured document.
This document outlines a student micro-project proposal to create a Software Requirements Specification. A team of 4 students - Advait Kamthekar, Shivani Bodke, Pragya Pal, and Dhruv Nandgaonkar - will work to understand SRS concepts and documentation. They will collect information, draft the SRS format over 5 days from April 7-12, with tasks divided among team members. The goal is to learn how to specify software requirements for a customer in a structured document.
TOPIC : Software Requirement Specification (SRS) Format TEAM MEMBERS:-
61. Advait Kamthekar
62. Shivani Bodke 63. Pragya Pal 64. Dhruv Nandgaonkar
1.0 Aim of the micro-project:
• To learn different concepts of Software Requirement Specification (SRS)
• To understand why this type of document is necessary in software engineering. • It is easy to partition the work in a project based on objects. • To develop self –learning skills. • To collect the knowledge beyond the syllabus related to the topic. 2.0 Course outcomes: • Understand overall working and main objective of document and what value it will provide to customer. • Description and overall review of product will be explained in the document. • Understanding how software system performs desired functions under specific conditions.
3.0 Proposed methodology:
We started by understanding the topic and then all of the group members started with the work assigned to them. On 8thth April we understood the topic and from 9th April onwards group members Advait and Shivani started to collect the required information. On 10th April, the understanding and the drafting of the microproject was done by Shivani and Advait. On 11th April the listing down of the points was done by Pragya and Dhruv, the drafting of Annexure 1 was done by Shivani and then finally the drafting of Annexure 2 was worked on by everyone.
4.0 Action plan:
SR. NO DETAILS OF START FINISH TEAM
ACTIVITY DATE DATE MEMBERS 1 Understanding 7 /4/22 8/4/22 Everyone the topic 2 Collecting the 9/4/22 9/4/22 Advait and Information Shivani 3 Understanding 10/4/22 11/4/22 Shivani and the Advait microproject 4 Listing down 11/4/22 11/4/22 Pragya and the points Dhruv 5 Drafting of 12/4/22 12/4/22 Shivani and Annexure 1 Advait 6 Drafting of 12/4/22 12/4/22 Everyone . Annexure 2 5.0 Resource Required:- SR NAME OF SPECIFICATIONS QTY REMARKS NO RESOURCES MATERIAL 1 Desktop PC 1TB, Ryzen 5 4600H, GTX 1 1660ti 3 Class notes - 1 (Reference )