Scribd
Upload
27 views

NU MCA - 4th - Project Guidelines

Uploaded by

bofolo7625
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
27 views

NU MCA - 4th - Project Guidelines

Uploaded by

bofolo7625
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

NOBLE UNIVERSITY - JUNAGADH

(Gujarat–India)

Master of Computer Application


(M. C. A.)

Semester – 4
Detailed Guidelines for
Subject code - MCA401
(Project)

Effective from Academic Year:


Dec–2023
NOBLE UNIVERSITY- JUNAGADH
Page No. 1
Noble University
Faculty of Computer Application Program : MCA
Semester : 4 Academic year: 2023-24
Teaching Hours
Subject Remarks
Subject name Theory Practical Tutorial Credits
Code If Any
MCA401 Project 00 30 00 15 –

Total 00 30 00 15 –

Prerequisites:

Software Engineering, Programming / Coding language, RDBMS

Guidelines for Internship:


1) It is advised that the team consist of two to three Students.
2) Project should be minimum 4 months of durations.
3) No plagiarism of any type should be included in the project.
4) Projects need to be assigned to internal guides, or the normal faculty members.
5) Within a maximum of five days following the commencement of the project, the project
plan and the assignment of tasks among teammates would have been established and
accepted.
6) Careful adherence to coding standards is required. The code should, at the very least, follow
a coherent naming convention, be modular, and include self-documentation.
7) Using object-oriented paradigm with code reuse, class reusability, etc., is recommended.
8) MIS reports, if any, have to be included in the output reports.
9) "Learning during Project Work," or "Experience of Journey," should be covered in a
chapter of the documentation.
10) "Experience of Journey during Project Duration"
11) Including data structure and database design in the report is highly advised. It is required to
provide at least some code, if not all of it. During the exam, the student can be required to
write the project's code.
12) The time allotted in accordance with the schedule must be used by internal guides, or the
regular faculty members, to assist the students with their projects. The time allotment will
follow the schedule for the 4th assigned semester project.
13) Project documents should be printed on both sides of paper; ideally, internal guides should
visit external guides to stay updated on the project.

Student accomplishments upon the completion of the course:

1) The student will gain extensive experience in creating major projects by completing the project.
This kind of experience will involve running into a variety of technical problems, looking for
solutions to the problems, and then figuring out how to address all of these problems properly.
2) Applying critical thinking, analysis, and synthesis to requirements and complex data in order to
Page No. 2
gain a thorough understanding of the solution technique that will be used.
3) Proficiency in writing and documentation.
4) Time management done right.
5) Collaborating with others and producing a significant amount of work.
6) It will get students ready for future work on big projects and industrial problem-solving and
programming.

Documentation:
1) The project must have comprehensive documentation in the form of a project report, which
should include source code, screenshots, data dictionaries, and design information spread across
at least 100 pages.
2) Format: Print with a single line spacing on both sides of the page. When writing standard text,
use Times New Roman in size 12.

TABLE OF CONTENTS
1. Introduction
1.1. Existing System
1.2. Need for the New System
1.3. Objective of the New System
1.4. Problem Definition
1.5. Core Components
1.6. Project Profile
1.7. Assumptions and Constraints
1.8. Advantages and Limitations of the Proposed System
2. Requirement Determination & Analysis
2.1. Requirement Determination
2.2. Targeted Users
3. System Design
3.1. Use Case Diagram
3.2. Class Diagram
3.3. Interaction Diagram
3.4. Activity Diagram
3.5. Data Dictionary
4. Development
4.1. Coding Standards
4.2. Screen Shots
5. Agile Documentation
5.1 Agile Project Charter
5.2 Agile Roadmap / Schedule
5.3 Agile Project Plan
5.4 Agile User Story (Minimum 3 Tasks)
5.5 Agile Release Plan
5.6 Agile Sprint Backlog
5.7 Agile Test Plan
5.8 Earned-value and burn charts
6. Proposed Enhancements

Page No. 3
7. Conclusion
8. Bibliography

Parameters for Evaluation:


1) The Institute's framework would be taken into consideration when evaluating the initiatives.
The students' ability to code would be the primary evaluation factor.
2) While the project and domain-specific knowledge would be evaluated, the students' capacity to
explain, edit, or change code would be the key factor in determining their grade.
3) Coding guidelines ought to have been used.
4) Even though the entire team will be assessed for the project, the examiner should highlight each
team member's contribution to the project's development.

Marking of Subject:

Total Marks (500 External + 200 Internal = 700 Marks)


For External Marks
Documentation (more especially, the relationship between the class diagram 100
and database structure, and the accuracy and completeness of UML
diagrams)
An explanation of design and analysis 100
Code Explanation (Testing the Capability to Describe How to Code a Few 200
Project Functionalities)
Presentation 100
Total Marks (External ) 500

For Internal Marks


Project preparation on a daily basis task submitted at a given period of time. 100
Continues evaluation.. 100
Total Marks (Internal ) 200

Page No. 4

You might also like