B. V. PATEL INSTITUTE OF COMPUTER SCIENCE, UKA TARSADIA UNIVERSITY 2019-2020

BCA – 3rd Semester Project Guideline

030010317: DSE4 Project Course Credit: 5 Total Hours: 9

Course Objective: To imbibe fundamentals of requirement analysis and system modelling skills.

Course Outcomes: Upon completion of the course, the student shall be able to CO1: Comprehend the need of a software system. CO2: Determine the functional and non-functional requirements for a software system. CO3: Model the functional requirements into system flow using UML. CO4: Design database schema and identify data validations. CO5: Determine and design user reports. CO6: Comprehend technical writing through preparation of Software Requirement Specifications.

Programme Outcomes:

PO1: Ability to understand the concepts of key areas in computer science. PO2: Ability to design and develop system, component or process as well as test and maintain it so as to provide promising solutions to industry and society. PO3: Effective communication and presentation skill. PO4: Ability to understand professional and ethical responsibility. PO5: Recognition of the need for life-long learning.

Programme Outcomes and Course Outcomes mapping:

Course Outcomes Programme Outcomes

PO1 PO2 PO3 PO4 PO5 CO1 Y Y Y CO2 Y Y CO3 Y Y CO4 Y Y CO5 Y Y Y Y CO6 Y Y Y Y

Project Guidelines:

Achievement of CO1 to CO4 shall be the responsibility of Course Teacher associated with the course Information Systems Analysis and Design.

Achievement of CO5 and CO6 shall be the responsibility of Course Teacher associated with the course Advanced Object-Oriented Programming.

It is must to implement a basic security feature. The Course Teacher of course Operating Systems is responsible to guide students in

determining Hardware/Software Specification for their project.

Team Formation and Guide Allocation:

A project shall be done in a team consists of minimum 3 and maximum 4 students. Team shall be formed by Project Committee during the first week of semester and shall be

displayed on the notice board after due approval of the Director. Guide shall be allocated to the teams by Project committee before start of the second week. Guide must get the project definition to be approved from Project Committee before

allocating it to the student team within six working days of guide allocation process.

Project Hours:

Following shall be the minimum hours to be spent by student for project work: Hours = No. of Contact hours X 12

Support and guidance team for Project: Support and Guidance Team is created so that student or guide can receive additional support

for respective project work.

Support and Guidance team System Analysis and Design KBL, BAD, KYP, TPR, JBU, PBG Database Design JRS, ADP System Testing JKT, PBG Web based Development PBN, JHT,VRF,RMP,KKB,MMS Mobile based Development DCP, ZMK, UJP Content Management over Web Application

UYS, KKB

Data Analytics BCP, JRS, JKT, CMT IoT based Development PRS, JAP Project Development Support Respective Guide

Project Execution:

Teams are expected to plan their project tasks well in advance and execute the same with punctuality.

Students must keep track of submissions by timely referring the mails and guidelines/circular related to project work published on our website

Project team must submit the timeline of [100 x total team members] schedule to the guide in the 3rd week of semester.

Time line must contains specific task to complete within specified duration. Project Timeline must be contain minimum 12 – 15 tasks related to the project execution and

duration of each task. Timeline will be evaluated twice during semester. Project Timeline must be submit in following format :

<<Institute Name>>

<<Course>> <<No.of Semester>> Semester

Course Name: DSE4 Project Course Code: 030010317

Project Team : <<No>> Project Title:

Project Timeline Project Timeline planning must list all the specific required tasks that are required achieve the functionalities described in system design. Tasks must be measurable.

Sr. No Project Task Estimated Start Date Estimated End Date

Total Days <NN>

Declaration:

I/We hereby declare that the timeline is prepared keeping in mind the complexity of each task and other aspects related to this project development. The duration planned is meant to be as close as the actual one.

The tasks and deadlines are approved.

Enrolment Number Name Signature

<<Guide Name>> <<Signature>>

Date:

Place:

Task Timeline:

Sr. No.

Task Conducted By Duration (in weeks)

Deliverables

1 System understanding, needs and objectives

Student 3

Initial Requirement

Document

2 Requirement analysis and scope description

Student 3

3 Determine System Functionalities and User roles

Student 4

4 Presentation regarding “How to document Project Requirement?”

Guide 4

5 UMLs and DFDs Student 5-6 System Design 6 Data Dictionary Student 7

7 Presentation regarding “How to document System modelling?”

Guide 7

7 Table Design Student 8 System Design

8 Identification of Reports Student 9

Reporting:

A project team shall maintain a log book. A student doing project at institute shall have to report about the project's progress to guide

on assign project time slot. Refer below given format for logbook.

1st Page:

Team No: Semester : Course:

Student Details :

Enrollment No Name

Project Title: Guide Name:

2nd Page:

Date of Reporting Enrollment No. Task Assigned

Comment regarding

previous task General

Comment Student

Signature

Internal Guide

Signature

<enrollment1>

<enrollment2>

<enrollment3>

Project Progress and Evaluation

Project must be evaluated on continuous basis through following parameters: o Project timeliness o Usability of project o Project work related documentation o Project work related presentation

To determine the progress of the project work, following parameters must be considered :

Assessment Code

Assessment Type

Occurrence

Each Of

Marks

Weightage in CIE of marks(125)

Evaluated By Tentative Dates

A1 Timeline Status

Report 2 10 10x2=20

Guide 8/07/2019 16/08/2019

A2 Presentation 2 60 20X2=40 Panel decided by

the Project Committee

01/08/2019

16/09/2019

A3 Document

Report 2 30 20X2=40

Panel determined for Presentation

22/07/2019 21/09/2019

A4 Semester End Examination

(Presentation) 1 60 25X1=25

Panel decided by the Project Committee

01/10/2019

Each team will be given twenty minutes of project presentation followed by ten minutes of viva.

The guide must present the progress of each team after each Status Report submission during Interim Status Report Meeting.

A1: Timeline Status Report:

There shall be two timeline status report, which shall be evaluated by guide. In first timeline status report timeline and project definition must be submit to project

committee and evaluated by guide based on following criteria :

Timeline status report - 1 Parameter Marks (10)

Finalization of requirement 05 Preparation of timeline 02 Student Reporting 03

Timeline shall be evaluated by guide on daily basis and the status has to be marked by the

project guide on the day of estimated completion Date or actual end date, whichever comes first. The status can further be updated on the day of estimated completion date or actual end date whichever comes later. When the status is set to “Completed”, the mode must also be marked by the guide.

Sr.No Project Task Estimated Start Date

Estimated End Date

Actual Start Date

Actual End Date

Status (Completed /Pending) & Date

Mode (Intime /Early/Delayed) & Date

Timeline status report -2 must be submit on specified date with updated status and Mode by guide and photocopy of logbook to the project committee in following format and declaration :

Sr.No Project Task Estimated Start Date

Estimated End Date

Actual Start Date

Actual End Date

Status (Completed /Pending) & Date

Mode (Intime /Early/Delayed) & Date

Total Days <NN>

Declaration:

The estimated dates are as per the timeline planning submitted. The actual dates are mentioned as the tasks have started and/or ended.

The status is marked after appropriate verification.

Enrolment Number Name Signature

<<Guide Name>> <<Signature>>

Date:

Place:

Timeline status report – 2 is evaluated based on following parameters :

Timeline status report - 2 Parameter Marks (10)

Work Completion Percentage Work Completion Marks 07 Student Reporting 03 Remarks*(Reasons for project lagging and steps for coping up)

A2: Presentation: There shall be two presentations, which shall be evaluated by examiner panel. During presentation, a student has to bring log book, updated timeline and document. Student shall use presentation slides to explain the project work. No make-up work shall be accepted for missed or failed presentation. Presentation must be reviewed by internal guide. A review certificate must be submitted at

time of presentation. [Note: A review certificate format will be provide by Project Committee before time of Presentation.]

Presentation template, objective and marks weightage is as below :

Presentation template should include like:

Presentation 1 outline:

Project title, team member names, enrolment numbers, guide name System process flow Comparative study of existing system Common features Limitation Proposed System Definition, Objective , Scope , Requirement

Presentation 2 outline:

Project title, team member names, enrollment numbers, guide name (If students doing project at industry then also add company name , external guide name)

System process flow Comparative study of existing system Common features Limitation Proposed System Definition, Objective , Scope , Requirement System Design Reports

Objectives and marks weightage of presentation

Objective of Presentation 1: To verify, that the students are on right path of project execution. To assess the system analysis skills and presentation skills. To determine the process of system analysis. To provide an insight for modification, enhancement into the current work and

suggestions for improvement for better execution of succeeding work.

Parameter Marks (60) Study of existing ICT solutions 20 Problem definition and need identification

20

Expected Requirement 10 Presentation skill 10

Objectives of Presentation 2:

To verify that the students have fulfilled the requirements. To verify SRS, conceptual diagrams and data dictionary and reports. To verify that students have documented in their project work the

comments/suggestions of improvement given during presentation 1. To assess presentation skills, system analysis skills. To provide an insight for modification, enhancement into the current work and

suggestions for improvement for better execution of succeeding work.

Parameter Marks (60)

Conceptual diagrams 10 Data Dictionary 20 Reports 20 Implementation of suggestion given in Presentation 1 05 Presentation and communication skills 05

A3: Document Report:

There shall be 2 documentation reports submission during the semester. Student have to verify document and get it signed by guide and submit to project committee.

Project Document -1 will be partial document and Project Document -2 will be full spiral bound copy of document.

In case, if a student failed to meet the deadlines, he/she shall receive zero marks in particular parameter.

As Project Document- 2, student shall have to submit spiral bounded copy of project document compulsorily in the prescribed format along with soft copy in CD before the Semester End Presentation with approval of internal guide as well as signed certificates from institute and endorsed by Program co-ordinator.

Marks weightage of Documentations are as given below : Parameter for Document - 1 Marks(30) Topics for partial

submission from project report

Document flow & Formatting 10

Chapter 1, 2 as format discussed below.

Requirement gathering 10

Reporting 05 Viva 05

Parameter for Document - 2 Marks(30) Topics for submission from project report

System Design 10

Full Document as format discussed below.

Reports 10 Incorporation of Suggestion given in 1st project document progress report

02

Reporting 03 Viva 05

Project Document Report Format: Document of project shall be create using following format.

i. Title Page ii. Project Certification Form(From Institute)

[The Institute certificate should be signed by internal project guide and endorsed by program coordinator.]

iii. Declaration certificate [A self-declaration regarding work originality and non-plagiarism. Declaration certificate format is given below.]

iv. Acknowledgement [All persons (e.g. guide technician, friends, and relatives) and organization/authorities who/which have helped in the understanding of the project shall be acknowledged.]

v. Table of Contents with page numbering vi. List of Tables, Figures, schemes

1. System 1.1 Introduction [Description in general that must include physical process and data

flow] 1.2 Existing System Study (at least three system solutions that are ICT enabled)

1.2.1. System 1 [Citations mandatory] 1.2.2. System 2 [Citations mandatory] 1.2.3. System n [Citations mandatory] 1.2.4. Comparative Study

1.2.4.1. Common features 1.2.4.2. Distinct features [Can be add after the completion of chapter 5 of Information system] 1.2.4.3. Limitations 1.2.4.4. Features adopted for proposed system

2. Proposed System 2.1 Definition 2.2 Objectives 2.3 Scope 2.4 Requirements 2.4.1 Expected 2.4.2 Exciting 2.5 Acronyms and Abbreviation 2.6 Proposed technologies (to be used with justification)

3. System Design 3.1 Use cases

3.1.1 Actors and Roles 3.1.2 Scenario description of each Use-Case 3.1.3 Use-Case Diagrams

3.2. E-R Diagram 3.3. Data Flow Diagrams 3.4. Data Dictionary with Constraints 3.5. User Interface Design

3.5.1. UI Specifications with technical justifications (fonts, elements and its measurements, appearance, alignment etc.) 3.5.2. Validations

3.5.3. Navigations 3.5.4. Screenshots

3.6. Reports 3.6.1. TPS

3.6.1.1. Inputs-Process-Outputs [detailed explanation for each report] 3.6.1.2. Layouts 3.6.1.3. Report usage

3.6.2. MIS 3.6.2.1. Inputs-Process-Outputs [detailed explanation for each report] 3.6.2.2. Layouts 3.6.2.3. Report usage

4. References 4.1. Books 4.2. Web references 4.3. Additional references (technical white papers, magazines, technical manuals etc.)

Guideline for Report Formatting: Use A4 size page with 1" margin all sides. Header should include Project tile and footer should contain page number and

enrollment numbers. Chapter Name should be of Cambria font, 20 points, Bold. Main Heading should be of Cambria font, 16 points, Bold. Sub Heading should be of Cambria font, 12 points, Bold. Sub Heading of sub heading should be of Cambria font, 12 points, Bold, Italic. Paragraph should be of Cambria font, 12 points. Line spacing - 1.5 lines, before - 0, after - 0. No chapter number for references. Before chapter 1, give page number in roman letter (Title Page, Project Certification

Form, Acknowledgements, Table of Contents/Index with page numbering, List of Tables, Figures, Schemes and Summary/abstract of the project work).

Front Page Format: Each project document must have front page as follows:

PROJECT

<<TITLE IN CAPITAL LETTERS>>

Submitted By,

<<Student’s Name (Enrollment Number)>>,

<<Student’s Name (Enrollment Number)>>

Guided By,

<<Internal Guide Name>>

for partial fulfillment of the requirements

for the Degree of Bachelor of Computer Applications

B.V.Patel Institute of Computer Science,

Uka Tarsadia University.

December, 2019.

Declaration Certificate: Each project document must have declaration certificate page

as follows:

DECLARATION

We hereby declare that the project titled “<<Project Title>>“is fully implemented by us. It is neither paid nor copied. Even though, later on, in case of any infringement found for this project work, we are solely responsible for the same and understand that as per UGC norms, the University can revoke the degree conferred to us.

Student Name and Signature Guide Name & Signature