Professional Documents
Culture Documents
1.0. ABSTRACT
2.1. Purpose
2.2 Scope
2.3 Goals/ Aim
2.4 Features of ur project ( Advantages)
3.3Overall description
3.4 Modules & Functionalities Description at Low Level – This is major part where we need to have in
the document. Almost 30% of the document should be this.
6.2 UML Design (Use case, Sequence, Class , state, activity, collaboration also)
6.4 DB Design (includes normalization theory, ER-diagram, Tables / Fields description) We have a
standard table for this.
Eg:
6.5) User Interfaces or Output Screens. [All screen shots include Validations screens]
EG:
User Screens:
Fig: 1
Description: User Registration form. Here We will collect the information about the
user. User has to fill the below fields
After entering all once he clicks on submit button All the fields are stored in RegTable
using stored Procedure <<Sp_InsertUser>>
EG:
a. Functionality Name:
Explanation: The below code prints 10 numbers
}
8.0. TESTING [Just include introduction for 5 pages) Write Test cases for all projects. Minimum of 30
Test cases should be there.
9 Deploying
11.0 BIBLIOGRAPHY
References:
EG:
H.E. Gruber & J. J. Vonèche [Eds.], The Essential Piaget, Basic Books, 1977
[2] Computing Curricula 2001, The Joint Task Force on Computing Curricula,
Final Report, IEEE Computer Society, Association for Computing Machinery,
[3] IEEE Std. 829-1998 IEEE Standard for Software Test Documentation
[4] IEEE Std. 830-1998 IEEE Recommended Practice for Software Requirements
Specifications
[5] IEEE Std. 1008-1997 IEEE Standard for Software Unit Testing
[6] IEEE Std. 1012-1998 IEEE Standard for Software Verification and Validation
[7] IEEE Std. 1016-1998 IEEE Recommended Practice for Software Design
Descriptions
[8] IEEE Std 1058-1998 IEEE Standard for Software Project Management Plans
[9] IEEE Std 1540-2001 IEEE Standard for Software Life Cycle Processes – Risk
Management
Education, 1951