MAJOR INTERNSHIP (45 WORKING DAYS) (Practical)

Paper Code: 
24MCA 424
Objective: 

This course enables the students to

  1. Provide exposure of industrial atmosphere and subsequent placement in industries across the country.
  2. Identify project goals, constraints, deliverables, performance criteria, control needs, and resource requirements in consultation with stakeholders.
  3. Understanding different methods of project delivery and the roles and responsibilities of all constituencies involved in the design and construction process
  4. Implement project management knowledge, processes, lifecycle and the embodied concepts, tools and techniques in order to achieve project success.
  5. Build skills in giving professional presentations, applying research to develop project outcomes, report writing and reflecting on the development of employability skills.


 

 

Course Outcomes: 

Course

Learning Outcome (at course level)

 

Learning and teaching strategies

Assessment Strategies

Course Code

Course

Title

24MCA 424

Major Internship

(Practical)

  1. Build skills and capabilities that intersect effectively with the needs of industry.
  2. Apply and practice good communication skills in the workplace setting.
  3. Create project for organization's strategic plans and business justification throughout its lifecycle.
  4. Utilize technology tools for communication, collaboration, information management, and decision support
  5. Adapt, Reflect and Evaluate on  project management skills to meet the needs of stakeholders from multiple sectors of the economy (i.e. consulting, government, arts, media, and charity organizations).
  6. Contribute effectively in course-specific interaction

Approach in Teaching:

Software Designing using Modular Approach, Form Design, Database Design, Presentation, Creating Technical Report

 

Learning activities for the students:

Self-Learning Assignments, Converting specifications to Code, Innovative Solutions

CA Assessment

  • Synopsis / Report
  • Software Requirement & Design Specification
  • Presentation
  • Viva Voce

 

SEE Assessment:

  • Execution of Software
  • Presentation
  • Report
  • Adherence to Specifications
  • System Knowledge and Understanding
  • Innovation and Originality
  • Viva-voce

 

Contents

Project Report Formulation:

The project report should contain the following:

  • Original copy of the Approved Performa and Project Proposal.
  • Bio-data of the guide with her/his signature and date.
  • Certificate of Originality (Format given).
  • Project documentation.
  • A CD consisting of the executable file(s) of the complete project should be attached on the last page of the project report. In no case, it should be sent separately. The student needs to retain the identical copy of the CD that should be carried while appearing for the viva-voce along with the project report.

Project Documentation:

  • Project documentation may be about 100 to 125 pages (excluding coding).
  • The project documentation details should not be too generic in nature.
  • Appropriate project report documentation should be done, like, how you have done the analysis, design, coding, use of testing techniques/strategies, etc., in respect of your project.
  • The project report should normally be printed with single line spacing on A4 paper (one side only). All the pages, tables and figures must be numbered. Tables and figures should contain titles.
  • Two copies of the original project report in the bound form along with the CD (containing the executable file(s) of the project should be enclosed in the last page) is to be prepared at the time of final viva.  One copy of the same Project Report and the CD containing the executable file(s) shall be retained by the student, which should be produced before the examiner at the time of viva-voce

MANUAL FOR PREPARATION OF MCA Project (Prescribed Format and Specification)

Essential Components of Project Report

  1. Title Page
  2. Certificate from Company
  3. Certificate from Guide
  4. Acknowledgement
  5. Index with printed Page Numbers

CHAPTER 1 : INTRODUCTION

1.1 Company/Educational Institute Profile  

1.2 Existing System and Need for System

1.3 Scope of Work

1.4 Operating Environment – Hardware and Software

CHAPTER 2: PROPOSED SYSTEM

2.1 Proposed System

2.2 Objectives of System

2.3 User Requirements

CHAPTER 3: ANALYSIS & DESIGN

3.1 Entity Relationship Diagram (ERD)                                                                                                                 3.2System Architecture

3.3 Database Requirements & User Interfaces

3.4 Data Flow Diagram (DFD)

3.5 Data Dictionary

3.6 Table Design

3.7 Code Design

3.8 Menu Screens

3.9 Input Screens

3.10 Report Formats

3.11 Test Procedures and Implementation

CHAPTER 4: User Manual

4.1 User Manual

4.2 Operations Manual / Menu Explanation

4.3 Forms and Report Specifications

Drawbacks and Limitations

Proposed Enhancements

Conclusions

Bibliography

Annexure:

Annexure 1: Input Forms with data

Annexure 2: Output Reports with Data

Annexure 3: Sample Code

 

 

 

 

 

 

 

 

 

Academic Year: