Vous êtes sur la page 1sur 11

preface

acknowledgement
certificate
introduction to project---------------------------
a.functional review
b.desc of technology.
system analysis
a.feasibility study
b.req. analysis
suiatble sdlc model

ieee SRS format for acc. to ur project

structured analysis
a.dfd
b.use case
c.transaction analysis
d.data object modelling
1. ER dig
2. Clasa dig
e.behavioural modelling
1.state transition dig
2.sequence dig

project design
a.highlevel design/system design
b.architechural design
c.data centered architechture

Data design
a.d/b tables
b.object design
interface design
low level design details

coding
testing
1.levels of testing
a.unit testing
b.integrated testing
c.system testing
2.approach of testing
a.functional
b.structural
project scheduling
future scope

this format is roughly noted in my copy so please confirm it by others


thankyou
ALL THE BEST

GUIDELINES FOR THE PREPARATION OF B.E./B. Tech. PROJECT REPORTS

¦Project reports should be typed neatly only on one side of the paper with 1.5 or
double line spacing on a A4 size bond paper (210 x 297 mm). The margins should b
e: Left - 1.25", Right - 1", Top and Bottom - 0.75".
¦The total number of reports to be prepared are
¦One copy to the department
¦One copy to the concerned guide(s)
¦Two copies to the sponsoring agency
¦One copy to the candidate.
3. Before taking the final printout, the approval of the concerned guide(s) is m
andatory and suggested corrections, if any, must be incorporated.
4. For making copies dry tone Xerox is suggested.
5.Every copy of the report must contain
¦Inner title page (White)
¦Outer title page with a plastic cover
¦Certificate in the format enclosed both from the college and the organization whe
re the project is carried out.
¦An abstract (synopsis) not exceeding 100 words, indicating salient features of th
e work. (NB: four copies of the abstract are to be submitted to the Department o
n the date of submission separately)

6.The organization of the report should be as follows

1.Inner title page


2.Abstract or Synopsis
3.Acknowledgments
4.Table of Contents
5.List of table & figures (optional)
Usually numbered in roman

¦Chapters (to be numbered in Arabic) containing Introduction-, which usually speci


fies the scope of work and its importance and relation to previous work and the
present developments, Main body of the report divided appropriately into chapter
s, sections and subsections.
¦The chapters, sections and subsections may be numbered in the decimal form for e.
g. Chapter 2, sections as 2.1, 2.2 etc., and subsections as 2.2.3, 2.5.1 etc.
¦The chapter must be left or right justified (font size 16). Followed by the titl
e of chapter centered (font size 18), section/subsection numbers along with thei
r headings must be left justified with section number and its heading in font si
ze 16 and subsection and its heading in font size 14. The body or the text of th
e report should have font size 12.
¦The figures and tables must be numbered chapter wise for e.g.: Fig. 2.1 Block dia
gram of a serial binary adder, Table 3.1 Primitive flow table, etc.
¦The last chapter should contain the summary of the work carried, contributions if
any, their utility along with the scope for further work.
Reference OR Bibliography: The references should be numbered serially in the ord
er of their occurrence in the text and their numbers should be indicated within
square brackets for e.g. [3]. The section on references should list them in ser
ial order in the following format.
1.For textbooks - A.V. Oppenheim and R.W. Schafer, Digital Signal Processing, En
glewood, N.J., Prentice Hall, 3 Edition, 1975.
2.For papers - Devid, Insulation design to combat pollution problem, Proc of IEE
E, PAS, Vol 71, Aug 1981, pp 1901-1907.
¦Only SI units are to be used in the report. Important equations must be numbered
in decimal form for e.g.
¦ V = IZ .......... (3
.2)
¦All equation numbers should be right justified.
¦The project report should be brief and include descriptions of work carried out b
y others only to the minimum extent necessary. Verbatim reproduction of materia
l available elsewhere should be strictly avoided. Where short excerpts from pub
lished work are desired to be included, they should be within quotation marks ap
propriately referenced.
¦Proper attention is to be paid not only to the technical contents but also to the
organization of the report and clarity of the expression. Due care should be t
aken to avoid spelling and typing errors. The student should note that report-w
rite-up forms the important component in the overall evaluation of the project
¦Hardware projects must include: the component layout, complete circuit with the c
omponent list containing the name of the component, numbers used, etc. and the m
ain component data sheets as Appendix. At the time of report submissions, the s
tudents must hand over a copy of these details to the project coordinator and se
e that they are entered in proper registers maintained in the department.
¦Software projects must include a virus free disc, containing the software develop
ed by them along with the read me file. Read me file should contain the details
of the variables used, salient features of the software and procedure of using
them: compiling procedure, details of the computer hardware/software requirement
s to run the same, etc. If the developed software uses any public domain softwa
re downloaded from some site, then the address of the site along with the module
name etc. must be included on a separate sheet. It must be properly acknowledg
ed in the acknowledgments.
¦Sponsored Projects must also satisfy the above requirements along with statement
of accounts, bills for the same dully attested by the concerned guides to proces
s further, They must also produce NOC from the concerned guide before taking the
internal viva examination.
¦The reports submitted to the department/guide(s) must be hard bounded, with a pla
stic covering.
¦Separator sheets, used if any, between chapters, should be of thin pape
NAME OF THE INSTITUTION
Address with pin code
Department of ..

CERTIFICATE
Certified that the project work entitled ... carried out by Mr./Ms.
d of Bachelor of Engineering / Bachelor of Technology in ... . of th
ity, Belgaum during the year ... It is certified that all corrections/suggestions i
ted for Internal Assessment have been incorporated in the Report deposited in th
e departmental library. The project report has been approved as it satisfies the
academic requirements in respect of Project work prescribed for the said Degree
.

Name & Signature of the Guide Name Signature of the HOD


Signature of the Principal

External Viva

Name of the examiners


Signature w
ith date
1
2.
Certificate issued at the Organization where the project was carried out
(On a separate sheet, If applicable)
NAME OF THE INDUSTRY / ORGANIZATION
Address with pin code
CERTIFICATE

Certified that the project work entitled ... carried out


/ Bachelor of Technology in ... . of the Visveswaraiah Technolo
tified that, he/she has completed the project satisfactorily

Name & Signature of the Guide Name & Signat


ure of the Head of organization

COLOUR OF THE OUTER COVER/FRONT PAGE OF UG DISSERTATION / PROJECT REPORT

Sl. No.
UG course
Color of the outer cover/front page of the report
1
Electronics & Communication, Telecommunication, Bio-Medical, Medical Electronic
s, Electrical & Electronics and Instrumentation Technology (EC/TE/BM/ML/EE/IT)
PURPLE
2
Computer Science and Information Science and Engineering (CS/IS)
CREAM
3
Mechanical, Printing Technology, Mining, Industrial Production, Industrial Engi
neering & Management, Manufacturing Science and Engineering and Automobile (ME/P
T/MI/IP/IM/ MA /AU)
SKY BLUE
4
Civil, Transportation and Environmental Engineering (CV/TR/EV)
GREY
5
Chemical, Cement & Ceramics, Silk, Textile Technology and Polymer Science (CH/C
C/ST/TX/PM)
BROWN
DISTRIBUTION OF MARKS FOR B.E./B.TECH. DISSERTATION EVALUATION

Sl. No.
Particulars
Max. Marks
1
Relevance of the subject in the present context
10
2
Literature Survey
10
3
Problem formulation
10
4
Experimental observation / theoretical modeling
10
5
Results Presentation & Discussion
10
6
Conclusions and scope for future work
10
7
Overall presentation of the Thesis/Oral presentation
40
Preface
Acknowledgement
Certificate
1.0 Introduction to project
1.1 Functional review
1.2 Description of technology
2.0 System analysis
2.1 Feasibility study
2.2 Requirement analysis
3.0 Suitable SDLC model for project
4.0 IEEE SRS format according to the project
5.0 Structured analysis
5.1 Data Flow Diagram
5.2 Use Case Diagram
5.3 Transaction analysis
5.4 Data object modeling
5.4.1 Entity Relationship Diagram
5.4.2 Class Diagram
5.5 Behavioral modeling
5.5.1 State Transition Diagram
5.5.2 Sequence Diagram
6.0 Project design
6.1 High level design/System design
6.1.1 Architectural design
6.1.2 Data centered architecture
6.2 Data design
6.2.1 Database tables
6.2.2 Object design
6.3 Interface design
6.4 Low level design details
7.0 Coding
8.0 Testing
8.1 Levels of testing
8.1.1 Unit testing
8.1.2 Integrated testing
8.1.3 System testing
8.2 Approach of testing
8.2.1 Functional
8.2.2 Structural
9.0 Project scheduling
10.0 Future scope
1. Overview
2. Scope
3. References
4. Definitions
5. Considerations for producing a good SRS
5.1 Nature of the SRS
5.2 Environment of the SRS
5.3 Characteristics of a good SRS
5.3.1 Correct
5.3.2 Unambiguous
5.3.3 Complete
5.3.4 Consistent
5.3.5 Ranked for importance and/or stability
5.3.6 Verifiable
5.3.7 Modifiable
5.3.8 Traceable
5.4 Joint preparation of the SRS
5.5 SRS evolution
5.6 Prototyping
5.7 Embedding design in the SRS
5.7.1 Necessary design requirements
5.8 Embedding project requirements in the SRS
6. The parts of an SRS
6.1 Introduction (Section 1 of the SRS)
6.1.1 Purpose (1.1 of the SRS)
6.1.2 Scope (1.2 of the SRS)
6.1.3 Definitions, acronyms, and abbreviations (1.3 of the SRS)
6.1.4 References (1.4 of the SRS)
6.1.5 Overview (1.5 of the SRS)
6.2 Overall description (Section 2 of the SRS)
6.2.1 Product perspective (2.1 of the SRS)
6.2.2 Product functions (2.2 of the SRS)
6.2.3 User characteristics (2.3 of the SRS)
6.2.4 Constraints (2.4 of the SRS)
6.2.5 Assumptions and dependencies (2.5 of the SRS)
6.2.6 Apportioning of requirements (2.6 of the SRS)
6.3 Specific requirements (Section 3 of the SRS)
6.3.1 External interfaces
6.3.2 Functions
6.3.3 Performance requirements
6.3.4 Logical database requirements
6.3.5 Design constraints
6.3.6 Software system attributes
6.3.7 Organizing the specific requirements
6.3.8 Additional comments
6.4 Supporting information
6.4.1 Table of contents and index
6.4.2 Appendixes
Annex A SRS templates
Annex B Guidelines for compliance with IEEE/EIA 12207.1-1997
B.1 Overview
B.1.1 Scope and purpose
B.2 Correlation
B.2.1 Terminology correlation
B.2.2 Process correlation
B.2.3 Life cycle data correlation
B.3 Content mapping
B.3.1 Compliance with information requirements of IEEE/EIA 12207.0-1996
B.3.2 Compliance with generic content guidelines of IEEE/EIA 12207.1-1997
B.3.3 Compliance with specific content requirements of IEEE/EIA 12207.1-1997
B.3.4 Compliance with life cycle data objectives
B.4 Conclusion
http://forum.santabanta.com/showthread.htm?t=31419