BCA-V (M& E) Date: 23rd Aug, 2018

Minor Project Topic Summary

(VB.Net/Java/Andriod/PHP/ASP.Net)
Note: Texts in black are the headings and subheadings they are to be written as it is.
Texts in green are the descriptions are also to be written as it is. Texts in red are to be
written according to your system.

Synopsis:
1. Title of Project
2. Introduction of the Project
3. Objective
4. Scope
5. SRS Requirement
5.1 Functional Module
5.2 Non Functional Module
6. Tools/Platforms
7. Methodology
6.1 SDLC Model
6.2 Data Collection Methods
7. Future Scope

Chapter 1: Introduction

1. Description of Organization
1.1 Introduction -Existing System
1.2 History of Organization
1.3 Objective of Organization
1.4 Organizational Structure
1.5 Description of proposed information system – A brief description
of all processes & sub processes in narrative form
1.6 Functions (or modules)
1.7 Project Planning Activities
1.7.1 Team-Member wise work distribution table
1.7.2 Gantt Chart
1.8 Software Requirement Specifications

Note: Texts in black are the headings and subheadings they are to be written as it is.
Texts in green are the descriptions are also to be written as it is. Texts in red are to be
written according to your system.

1.8.1 Introduction – A single paragraph about SRS

The following subsections of Software Requirement Specifications

Document should facilitate in providing the entire overview of the
Information system “Title of your Project” under development.
This document aims at defining the overall software requirements
BCA-V (M& E) Date: 23rd Aug, 2018

for your end users. Efforts have been made to define the
requirements of the Information system exhaustively and
accurately.
1.8.2 Purpose
The main purpose of Software Requirement Specifications
Document is to describe in a precise manner all the capabilities
that will be provided by the Software Application “Your Title”. It
also states the various constraints which the system will be abide
to. This document further leads to clear vision of the software
requirements, specifications and capabilities. These are to be
exposed to the development, testing team and end users of the
software
1.8.3 Scope – scope of your proposed system
1.8.4 Definition, acronyms, abbreviations
1.8.5 References

1.8.6 Overview
The rest of this SRS document describes the various system
requirements, interfaces, features and functionality in detail.
Overall description of proposed system
1.8.7 Product Perspective
The application will be windows-based, self contained and
independent software product.

Front End Client

Application (with Backend
data entry / update Database
/delete /view and
reporting facility)

Fig. Interaction of Product with the environment

Assumptions and Dependencies – The application is developed on

the following assumptions. (List the assumptions specific to your
project)

1.8.8 System Interfaces

None
1.8.9 User Interfaces
The application will have a user friendly and menu based interface.
Following screens will be provided.
BCA-V (M& E) Date: 23rd Aug, 2018

(i) A Login Screen for entering username, password and role

(Administrator, operator) will be provided. Access to
different screens will be based upon the role of the user.
And so on.
The following reports will be generated:
(i) And so on.

1.8.9.1 Hardware Interfaces

None
1.8.9.2 Software Interfaces
<Describe the connections between this product and other
specific software components (name and version),
including databases, operating systems (Windows? Linux?
Etc…), tools, libraries, and integrated commercial
components.
1.8.9.3 Communication Interfaces
None

1.8.10 Memory Constraints

1.8.11 Operations
This product will not cover any automated housekeeping aspects of
database. The DBA at client site will be manually deleting old/ non
required data. Database backup and recovery will also have to be
handled by DBA.

1.8.12 Specific Requirements

This section contains the software requirements to a level of detail
sufficient to enable designers to design the system, and testers to
test the system.
1.8.13 User Characteristics
1. Educational Level: At least graduate and should be comfortable
with English language.
2. Technical Expertise: Should be a high or middle level employee
of the organization comfortable with using general purpose
applications on a computer
1.8.14 Product functions
The system will allow access only to authorized users with specific
roles (Administrator, Operator). Depending upon the user’s role,
he/she will be able to access only specific modules of the system.
A summary of the major functions that the software will perform:
(i) A Login facility for enabling only authorized access to the
system.
(ii) Users (with role operator) will add/update/delete the stored
information and so on
1.8.15 System Features
1.9.15.1 Module name
Description
One paragraph in brief about module
BCA-V (M& E) Date: 23rd Aug, 2018

Validity Checks
Sequencing Information
Error Handling / Response to abnormal situations
1.8.16 Performance Requirements
None
1.8.17 Logical Database Requirements
The proposed information system contains the following data
tables in its database collection.
Table name
1.8.19 Design Constraints
Standard Compliance
None
1.8.19 Software System Attributes
1.8.19.1 Reliability
This application is a reliable product that produces fast and
verified output of all its processes.
1.8.19.2 Availability
This application will be available to use for your end users
and help them to carry out their operations conveniently.
1.8.19.3 Security
The application will be password protected. User will have
to enter correct username, password and role in order to
access the application.
1.8.19.4 Maintainability
The application will be designed in a maintainable manner.
It will be easy to incorporate new requirements in the
individual modules.
1.8.19.5 Portability
The application will be easily portable on any windows-
based system that has oracle installed.
1.8.20 Other Requirements
None

Chapter 2: System Design

2.1. Physical Design- about your system

2.1.1. Block Diagram- about block diagram followed by properly labeled
diagram
2.1.2. Processes- All the processes along with their subprocessess
2.1.3. Input and Output of processes

No. Process Input Output

BCA-V (M& E) Date: 23rd Aug, 2018

2.1.4. Use case diagram

2.1.5. Data Flow Diagrams
2.1.6. Entity Relationship Diagram

2.2. Database Design

The information system of “your title” performs its function with
the help of the data store in certain repositories called Databases
of the system. Detailed descriptions of the various databases
included in the information systems are tabulated as follows:
2.2.1. Login database
2.2.2. Schema of each table properly labeled
2.3. Data Dictionary
2.3.1. A data dictionary is metadata repository or a centralized repository of
information about data such as meaning, relationships to other data, origin,
usage and format. The term may have one of several closely related meaning
pertaining to databases and database management systems (DBMS):
A document describing a database or collection of databases.
An integral component of DBMS that is required to determine its
structure.
A piece of middleware that extends or supplants the native data
dictionary of a DBMS.

TABLE COLUMN FIELD SIZ PRIMARY NULL DESCRIPTI

NAME NAME TYPE E KEY ON

2.4. Interface Design

The interface design consists of the input and output source layouts.
i.e. the input forms and screens and the report layouts that form as a
source of outcome and income in the design and implementation of the
information system under study

2.4.1. Input Design

The input specifications of the existing information system include
the illustration of the detailed characteristics of contents included in
each Input Screen and documents. The description for each graphical
user interface has been mentioned.
EXISTING SYSTEM DESIGN (Graphical User Interface)
1. Main Form
Snap shot of your main screen
Description and so on
2.4.2. Output Design
The output specifications of the existing information system
include the detailed characteristics of contents included in each
Report. The description for each Visual Basic Output Report has
been mentioned.
1. Report 1
Snap shot of your report properly labelled
BCA-V (M& E) Date: 23rd Aug, 2018

Description
File Linked to: name of the table and so on

Chapter-3: Systems Development &Implementation

3.1Programme Development (Coding)

Chapter-4: Testing &Implementation

4.1 Testing & Debugging(Types of testing(white box, black box, acceptance, alpha-beta
testing, Validation testing)
4.2 Include the test reports in the project to show the errors(i.e. screen shot), if any, and a
brief write-up on their rectification

Chapter-5 Scope of Improvement, Summary and Conclusions

5.1 Scope of Improvement
5.2 Summary
5.3 Conclusion

References