Synopsis of a project shall contain the following items

1. Title of the project
2. Objectives of the project
3. Project Category
4. Tools to be used
5. Structure of the project
• Requirement Analysis
• Data flows Diagram, Flow charts etc.
• Module description
• Implementation procedure
• Testing Plan
6. Any other relevant information
• Limitation of the project
• Future scope and further enhancement of the project

Example showing the Synopsis of a student Project

1. Title of the project
Payroll System of Techpro Systems Inc.
2. Objectives of the Project
• To computerize the existing manual system of preparing the payroll of the employees
• To speed up the process of preparing the payroll
• To efficiently manage the payroll system with lesser number of people
• To remove the errors in preparing the payroll. Thus benefit will be both to the Employer and to the employee
3. Project Category

It is an user application with an user interface as front end to feed in and to retrieve the data. A database as back end to store the data.

4. Tools to be used
• Requirement analysis tools:
• Questionnaire to the Employer
• Questionnaire to the user
• Programming tools:
• Back end: My SQL
• Front end: VB.Net
• Kind of Hardware needed for the project
• Testing tools:
• Manual testing with set of real time data
5. Structure of the project
• Requirement Analysis

Problem analysis: In this the need of the client and users will be understood. It will be done by providing the questionnaire to the client to understand what exactly he want? How he want the new pay roll system to work. Whether he want any control over the system. If so what kind of control. Any constraint in the new system? How much investment the management is willing to invest in the new system? What or how much part of the system to be computerized? As it may involve in investing in new h/w systems like computers, scanners, web cams, printers etc.

Discussions will also held with the users. Questionnaire will also be provided to them to know the present working of the system. What part of the system be computerized. The different reports they wanted. The input they provide to the present system and how the input is processed to get the correct output. What part of the manual system still they want to maintain.

Even different methods like presentation, interaction, brain storming session will be conducted with the client and users to understand the present system and to provide them with specification document of the product. At the end of all these SRS of Payroll system will be generated.

Software Requirement: SRS of Payroll system
• Details of the existing/new employees will be scanned and stored
• Provision to use web camera to get the photograph of the employee for records
• Weekly timesheets will be scanned to calculate the pay
• Details of the employee to find the pay rate will be taken from the stored details of the employee
• Pay slip for each employee will be generated and will be printed.

Format of the pay slip is Employee Id, Employee Name, Weekly hours, pay, Overtime hours, pay, tax deducted, net pay All these information has to be updated in the employees records

• Following Reports will be generated:
1. Weekly, monthly, yearly net payments made to individual employee
2. Tax deducted for individual employee on Weekly, monthly, yearly basis
3. Overtime payment made for individual employee on Weekly, monthly, yearly basis
4. The above details are to be generated for all the employees
• Data Flow Diagram, Flow Chart

Data flow diagram are used during the problem analysis. A DFD shows the flow of data through a system.

DFD for Employee Payment System




• Module Description
Different Modules used in the Software are:
• Scanning module:
To scan the details of existing employees or new ones and to store the details
• Module to get the details the employees from the stored records
• Module to scan the time sheets and store
• Module to use the Web Cam
• Module to calculate the pay, generate pay slip and update the records
• Module to generate different reports
• Implementation Procedure
• The way in which you are going to implement different modules
• Give the algorithm or details by which you are going to achieve the target
• Even the schedule can also be given
• Testing Plan
• Top Down Testing or Bottom up testing
• White box (Functional) and Black box (structural) testing

Each of the individual modules like scanning module, Employee Details, Time sheet etc. are tested first to check whether they work according to the needs of requirement (functional testing) and these modules then linked and final testing is done with real time data.

Each of these modules will undergo structural testing with different set of data.

6. Any other relavent information about the project
• Limitations:
• Employees can not login and check their payment status
• All the documents which are needed to be scanned should not be in the hand written format
• Future Scope:
• Employees may be given access to login and check their payment status
• A cloud based module can be implemented so that a remote user can access it
• All the documents which are needed to be scanned need not be in a specific format