Tecnia Institute of Advanced Studies, New Delhi

Academic Circular 1/2012

P!"#CT $!% &#T'!D!(!)*
+! &CA S#&ST# ,I ST-D#NTS
!./ective
1. Students of Semester VI are to carry out a software project as part of curriculum of MCA.
At the end of the semester the students are to submit a written project report to be forwarded to
GGSIP ni!ersity. "he objecti!e of this "eachin# $ote is to standardise the format of
submission of the project report and to lay #uidelines to conduct the project.
-niversit0 Scheme for Pro/ect
%. As per the syllabi of MCA &Paper $o MCA'()% * MCA'()+,- students of Semester VI
are to write a dissertation.project report comprisin# of %/ credits. "he dissertation.project report
has three components- !i0.
&a, 12ternal 3 Dissertation &/) Mar4s,- where a written report is to be
submitted. It in!ol!es e2ternal Vi!a and presentation.
&b, Internal 3 Dissertation &+) Mar4s,.
&c, Paper MCA'()+, 3 S0no1sis 2 Presentations &1)) Mar4s, It in!ol!es
submission of synopsis- presentations * Vi!a at the
Institute.

Sco1e of the Dissertation
(. It is partly responsibility of the student to find a rele!ant topic for his.her term
dissertation. If you are in!ol!ed in research or de!elopment in this area- your dissertation can
relate to your wor4 as lon# as your wor4 can be public. "he dissertation is to study the selected
problem and 5uality * shortcomin#s of a!ailable solutions. In the report- you must also include
any new solution you can thin4 of and #eneral comments on why the problem is important.
+. "he dissertation wor4 could be based on literature sur!ey- simulation study- or
implementation. 6ou are allowed to perform ori#inal wor4- if you so desire.
Pro1osal
7. "he project proposal should be about one.two pa#e lon# and must be submitted in writin#
to your respecti!e #uide. "he format of the synopsis is attached as A11endi3 4A5. All students
are re6uired to su.mit the s0no1sis .0 7
rd
, &arch 2012 .
+inal e1ort
/. "he format of the project report is attached as A11endi3 485. "he Guidelines for
methodolo#y to be adopted for conductin# the project is attached as A11endi3 4C5. The last
date of su.mission of the com1leted and .ounded re1ort is to .e su.mitted as 1er the
schedule 9iven .elow.
Im1ortant Dates
8. 9ollowin# Schedule is to be adhered to by all the students3
To 8e com1leted 80 the Date Pro9ress/Activit0
Saturday- March )(- %)1% Submission of Project Proposal to the respecti!e #uides
Saturday- March 1)- %)1% Submission of 9irst Pro#ress :eport
Saturday- March 18- %)1% Submission of Second Pro#ress :eport
Saturday- March %+- %)1% Submission of "hird Pro#ress :eport
Saturday- March (1- %)1% Internal :e!iew for Industrial Project by Committee
Saturday- April )8- %)1% Submission of fourth Pro#ress :eport
Saturday- April 1+- %)1% Submission ;f <raft Copy of Project :eport for appro!al
Saturday- April %1- %)1% <iscussion on appro!ed draft copy with concern faculty #uide
Saturday- April %=- %)1% 9inal Project :eport Submission - Internal Presentation and Vi!a
to the committee
May %- %)11 to May 1)- %)1% Vi!a >y 12ternal 12aminer
A11endi3 4A5
&:efer para 7,
+!&AT !+ T'# P!"#CT P!P!SA(
1. Title of the Pro/ect
%. !r9anisation3 Mention the name of or#anisation where you intend doin# your project.
>riefly e2plain the nature of the or#anisation and its business.
(. Pro.lem Definition3 If an old information system is the topic of dissertation- what are
the problems with the e2istin# system? In what ways your proposed system will impro!e
the e2istin# system? If a new system is bein# proposed- how will it fulfil the user
re5uirements? 12plain the objecti!es of the Project.
+. &ethodolo903 12plain which methodolo#y you will adopt for analysis and desi#n- e.#.-
Classical S<@C Method- ;bject ;riented Analysis * <esi#n Method- Structured
Analysis * <e!elopment Method or Prototype Method.
7. Tools3 12plain the software tools and platform that you propose to use in the project.
/. Nature of esearch3 If you are writin# the dissertation based on literature sur!ey- #i!e
details of literature to be sur!eyed. 12plain whether the nature of research is e2ploratory
or ori#inal thou#ht process is bein# pursued.
A11endi3 485
&:efer para /,
+!&AT !+ T'# P!"#CT #P!T
+ormat
1. "he final report should be written in the followin# the format3
&a, "itle Pa#e
&b, Certificate &s,
&c, Ac4nowled#ements
&d, Synopsis.12ecuti!e Summary
&e, Contents
&f, @ist of "ables
&#, @ist of 9i#ures
&h, @ist of Symbols
&j, >ody of the Project :eport
&4, Summary and Conclusions
&l, :eferences
&m, Appendices
Title Pa9e
%. "he format of the title pa#e is attached as Anne3ure:I.
Certificate
(. "he format of the certificate is attached as Anne3ure:II. A certificate of the or#anisation
where the student has conducted the project may also be attached.
Ac;nowled9ements
+. In the AAc4nowled#ementsB pa#e- the writer reco#nises his indebtedness for #uidance
and assistance of the thesis ad!iser and other members of the faculty. Courtesy demands that he
also reco#nise specific contributions by other persons or institutions such as libraries and
research foundations. Ac4nowled#ements should be e2pressed simply- tastefully- and tactfully
dul0 sin9ed a.ove the name<
S0no1sis/#3ecutive Summar0
7. A synopsis is a brief or condensed summary of the project for hi#her'le!el mana#ement
positions. It should be about ('+ pa#es in len#th. It should comprise problem definition-
objecti!es of the project- methodolo#y and tools used- findin#s- limitations- directions for future
de!elopment- if any.
Contents 2 (ist of Ta.les/+i9ures/S0m.ols
/. "he format of Contents and list of "ables.9i#ures.Symbols is attached as Anne3ure:III.
A publication is a research paper published.communicated durin# the current research wor4.
8od0 of the Pro/ect e1ort = )uidelines for Pro/ect e1ort/Dissertation $ritin9
8. "he #uidelines for >ody of the Project :eport &methodolo#y, are detailed in A11endi3
4C5. 9ollowin# aspects must be adhere to3
&a, Pa9e Si>e3 Good 5uality white A+ si0e e2ecuti!e bond paper should be used for
typin# and duplication.
&b, Cha1ter/Para Num.erin93 "he chapters are to be numbered as Chapter'1-
Chapter'% etc. "he headin#.title of the chapter is to appear below the chapter number in
uppercase. Para#raphs are to be numbered as 1-%-( etc in e!ery chapter separately. Sub'
paras are to be numbered as 1.1- 1.%- 1.(''''- %.1- %.%- %.('''''etc. Sub'sub paras are to be
numbered as 1.11- 1.1%- 1.1(- %.11- %.1%- %.1( etc.
&c, Pa9e S1ecifications=
&i, @eft Mar#in 3 1.%7 inch
&ii, :i#ht Mar#in 3 1.%7 inch
&iii, "op Mar#in 3 1 inch
&i!, >ottom Mar#in 3 1 inch
&d, Pa9e Num.ers= All te2t pa#es startin# from >ody of the Project :eport as well
as pro#ram source code listin#s should be numbered at the .ottom center of the pa#es.
&e, Normal 8od0 Te3t=
&i, +ont Si>e= 1%- "imes $ew :oman- <ouble Spacin#- Sin#le Side Critin#.
&ii, Para9ra1hs 'eadin9 +ont Si>e= 1%- "imes $ew :oman- nderlined
&iii, Pa9e/Title +ont Si>e3 1+
&f, Ta.le and +i9ure Num.er3 "able and fi#ure numbers are to be written at the
bottom of the table. fi#ure as #i!en below3

&i, Ta.le No:1= Num.er of #m1lo0ees in !r9anisation A8C
&ii, +i9ure No:1= Data +low Dia9ram
&#, 8indin9 2 Color Code of the e1ort=
&i, Dard >ound :eport
&ii, >ac4#round of the co!er pa#e ' $a!y >lue
&iii, @etters in Sil!er Chite
Summar0 2 Conclusions
=. "his section of the report.dissertation should co!er findin#s of the wor4- whether the
stated objecti!es of the wor4 is achie!ed with full justification- recommendations- limitations-
directions for future de!elopment.
eferences/8i.lio9ra1h0
E. 12amples are #i!en below3
1. <.@. Carney- F.I. Cochran- A"he 71SS Switchin# System3 Architectural ;!er!iew-B
AT&T Technical Journal- !ol. ?@, no. ?, Fuly'Au#ust 1E=7- pp. 1((E'1(7/.
%. A. Ste!ens- C++ Database Development- MIS Press- $ew 6or4- 1EE%- p. (+.
(. F. Martin- Computer Database Organization- Prentice'Dall- 1n#lewood Cliffs- $F-
1E88- p. 7(.
+. www.ibm.com.in
7. www.intel.com.india
A11endices
1). "he appendices are to be attached at the end of the report.dissertation and to be numbered
as Appendi2'A- Appendi2'> etc. ri#ht justified at the top of the pa#e. >elow the world
Appendi2 write in parenthesis A:efer Para $oGGB. "he para number is to be the number in the
body of te2t where the reference of appendi2 is #i!en. An appendi2 may ha!e anne2ure &s,. If
there are anne2ure- there are to be attached immediately after the said appendi2. "he anne2ures
are to be numbered as Anne2ure'I- Anne2ure'II etc.
Anne3ure:I
Title of The Pro/ect e1ort
&9ont si0e H 1=,
Submitted in partial fulfillment of the requirements
for the aard of the degree of

&aster of Com1uter A11lication A&CAB
"o
Guru Gobind Sin#h Indraprastha ni!ersity- <elhi
Guide&s,3 Submitted by3
&Guide $ame, &Student name,
:oll $o.3
Tecnia Institute of Advanced Studies, New Delhi
New Delhi C 1100 DE
8atch A200F:2012B
@o#o of the
Institute
Anne3ure:II
Certificate
I- Mr..Ms.GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG- :oll $o. GGGGGGGGGGGGGGGG certify that
the Project :eport.<issertation &MCA'()%, entitled
AGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGB is done by me and it is an authentic wor4 carried
out by me at GGGGGGGGGGGGGGGGGGGGGGGGGGG &$ame of the or#anisation or of the Institute,.
"he matter embodied in this project wor4 has not been submitted earlier for the award of any
de#ree or diploma to the best of my 4nowled#e and belief.
Si#nature of the Student
<ate3
Certified that the Project :eport.<issertation &MCA'()%, entitled AGGGGGGGGGGGGGGGGGGB
<one by Mr..Ms.GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG- :oll $o. GGGGGGGGGGGGGGGG- is
completed under my #uidance.
Si#nature of the Guide
<ate3
$ame of the Guide3
Countersi#ned <esi#nation3
Address3
"ecnia Institute of Ad!anced Studies-
$ew <elhi'11))=7
<irector.D;<
Anne3ure:III
+!&AT +! C!NT#NTS 2 (IST !+ TA8(#S/+I)-#S/ S*&8!(S
C!NT#NTS
S No To1ic Pa9e No
1 Certificate &s, '
% Ac4nowled#ements '
( Synopsis.12ecuti!e Summary '
+ @ist of "ables '
7 @ist of 9i#ures '
/ @ist of Symbols '
8 Chapter'13 Introduction.Problem <efinition
= Chapter'%3 Systems Analysis of 12istin# System
E Chapter'(3 :e5uirements Analysis
1) Summary and Conclusions
11 :eferences
1% Appendices
(IST !+ TA8(#S/(IST !+ +I)-#S
Similar tables &as shown abo!e for Contents, are to be drawn for @ist of "ables and @ist
of 9i#ures on separate pa#es.
(IST !+ S*&8!(S
Symbols that are used in the body of the te2t are to be listed in tabular form as #i!en
below3
S No S0m.ol Nomenclature 2 &eanin9
1 Si#ma &Summation,
% %.1s Iilo bits per second
A11endi3 4C5
&#*'!D!(!)* +! P!"#CT $!%/DISS#TATI!N
Cha1ter:1= Introduction/Pro.lem Definition
1. 9ollowin# aspects need to be co!ered in the first chapter3
&a, 8rief Descri1tion of the !r9anisation3 If the project wor4 is bein# done outside
the Institute- describe the or#anisation- its nature of business- products- turno!er- mar4et
position etc.
&b, )eneral Descri1tion of the S0stem under Stud03 >riefly e2plain how the
e2istin# information system achie!in# the tas4- which is under study.
&c, -ser e6uirements3 12plain in non'technical terms- why the e2istin#
information system is not able to meet the current tas4s a#ainst the
objecti!es.standards.benchmar4s of the or#anisation. Problems faced by the e2istin#
system.
&d, #sta.lish the Need of the New S0stem3
Gi!e justification- Dow * Chy without the new system user re5uirements
cannot be fulfilled.
Dow will the proposed solution enhance the efficiency- effecti!eness- better
control- security and achie!ement of objecti!es.standards.benchmar4s?
&e, !./ectives of the Pro/ect3 Ieepin# in !iew the user re5uirements and needs-
a!ailable time and e2pertise- lay down the objecti!es of the project. Clearly spell out
what is proposed to be done in the project.
&f, &ethodolo903 S<@C- Structured Analysis * <esi#n- ;bject ;riented <esi#n
method or Prototype method. 6ou may follow a mi2ed methodolo#y and toolsJ howe!er-
you should clearly mention the steps and tools and techni5ues that you are #oin# to
follow in the current project with brief justification.
&#, Data e6uired 2 Data Collection &ethod3 6ou should establish re5uirement
of data and methodolo#y.techni5ue of data collection- e.#.- inter!iew- 5uestionnaire-
document analysis. If 5uestionnaire is de!eloped- attach a copy of the 5uestionnaire as
appendi2.
Cha1ter:2= S0stems e6uirement Anal0sis
%. In this chapter students are re5uired to establish the user re5uirements by doin# the
systems analysis of the e2istin# system in !o#ue and by interactin# with the mana#ement.staff of
the or#anisation. In e!ery or#anisation a system does e2ist in some rudimentary or manual form-
if not computerised. "he acti!ities that are re5uired to be carried out and to be described in the
project are3
&a, Identify the process &es,.
&b, Identify the Input to and ;utput of each process- e.#.- for :ail :eser!ation System
input is the form and output is a tic4et.
&c, Identify the data elements &fields, in each input and output.
&d, Identify the procedures.rules.mathematical relationships used for con!ertin# input
into output.
&e, Identify the controls &for I.; * access,- security needs- !alidation rules and codes
used for data elements.
&f, Identify deficiencies in e2istin# system.
(. Da!in# collected the data on the abo!e aspects- analyse it and interact with the
mana#ement for any chan#es in process &es,- input- output- procedures- access and control ri#hts-
security needs and your su##estions for remo!in# the deficiencies.
Cha1ter:7= S0stems Desi9n
+. Ph0sical Desi9n3 12plain relationship between !arious components &processes- input-
output * entities, of the system. <raw <9<s and other dia#rams.
7. #31lain Processin9 (o9ic3 sin# Pro#ramme 9low Charts- Al#orithm- <ecision
"able."ree or Pseudo codes.
/. Interface Desi9n3
&a, !ut1ut Desi9n3 Screen * Print layouts- i.e.- the format and contents &fields, to be
included K alon# with the file to which it is lin4ed.
&b, In1ut A+orm or ScreenB Desi9n3 9or 4eyin#'in data. Gi!e fields- format- codes to be
used- !alidation &error detection, re5uirements * the file to which it is lin4ed.
8. Data.ase 2 +ile Desi9n3
&a, Data.ase +iles/Ta.les Desi9n3 <ependin# on the <>MS.:<>MS pac4a#e
used- #i!e contents of each file includin# 9ield $ame- "ype- Si0e * <escription.
&b, Pro9ramme +iles or Guer0 Desi9n3 Gi!e purpose and detailed wor4in# of each
pro#ramme file or a Luery and lin4 it to the processin# lo#ic and Process.Input.;utput.
&c, Com1ose Data #lement Dictionar03 @ist all the fields in all the files in
alphabetical order in a tabular form and serially numbered them.
Cha1ter:@= S0stems Develo1ment
=. Pur1ose3 "o carry out the acti!ities of writin# actual pro#rammes- their debu##in#-
testin# and !alidation. 9ollowin# acti!ities are to be carried out3
&a, Pro9ramme Develo1ment3 12plain the lan#ua#e or pac4a#e used for de!elopin#
the pro#rammes &both bac4'end and front'end,.
&b, Testin9 2 De.u99in93 se !ast Data to chec4 whether the pro#rammes wor4 as
intended by
&i, &odule Testin93 Indi!idual pro#ramme testin#.
&ii, S0stem Testin93 Inte#rated module "estin# for the entire system.
&6ou may li4e to include the test reports in the project to show the errors- if any- and a
write'up on their rectification,.
&c, ,alidation3 Chec4 the system with "eal#time Data for input- output-
computational processin# * controls.
E. Attach pro#ramme codes- input and output desi#ns and outputs usin# the real data in this
chapter. Codes may be attached as appendi2.
Cha1ter:E= S0stems Im1lementation
1). 9ollowin# acti!ities are re5uired to be conducted3
&a, Ac6uisition3 Cor4out the memory re5uirement- dis4 space re5uired for
pro#ramme &s, and database &s,. @ist out DC- SC and people resources re5uired and
indicate the cost of the system.
P!C#SS
NA&#/No
+I(#
NA&#/No
+I#(D
D#SCI
PTI!N
T*P#2
SIH#
+I#(D
NA&#
Data
#lement
S No
P!C#SS
NA&#/No
+I(#
NA&#/No
+I#(D
D#SCI
PTI!N
T*P#2
SIH#
+I#(D
NA&#
Data
#lement
S No
&b, Conversion3 Su##est chan#e o!er procedures &Parallel- <irect or Partial Chan#e
o!er, with justification.
&c, Trainin9 Needs3 1stablish the trainin# needs of operatin# personnel- clerical.non'
clerical staff- super!isors- and senior staff.
&d, Documentation3
&i, Include ;peration Manual &instructions for runnin# pro#rammes,.
&ii, ser Manual'Gi!in# instructions * procedures for end'users &for data
entry- output- help etc,.