13-08-2012, 03:35 PM
MASTER OF COMPUTER APPLICATIONS
[attachment=31319]
INTRODUCTION AND OBJECTIVES
The Project work constitutes a major component in most professional programmes. It needs to be carried out with due care, and should be executed with seriousness by the students. The project work is not only a partial fulfilment of the MCA requirements, but also provide a mechanism to demonstrate your skills, abilities and specialisation. The project work should compulsorily include the software development. Physical installations or configuring the LAN/WAN or theoretical projects or study of the systems, which doesn’t involve s/w development, are strictly not allowed.
Students are eligible to submit the project proposals after entering into the 5th semester of MCA, as per the calendar of the project.
OBJECTIVES
The objectives of the project is to help the student develop the ability to apply theoretical and practical tools/techniques to solve real life problems related to industry, academic institutions and research laboratories. After the completion of this project work, the student should be able to:
• Describe the Systems Development Life Cycle (SDLC).
• Evaluate systems requirements.
• Complete a problem definition.
• Evaluate a problem definition.
• Determine how to collect information to determine requirements.
• Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time feasibility and Operational feasibility for the project.
• Work on data collection methods for fact finding.
• Construct and evaluate data flow diagrams.
• Construct and evaluate data dictionaries.
• Evaluate methods of process description to include structured English, decision tables and decision trees.
• Evaluate alternative tools for the analysis process.
• Create and evaluate such alternative graphical tools as systems flow charts and state transition diagrams.
• Decide the S/W requirement specifications and H/W requirement specifications.
• Plan the systems design phase of the SDLC.
• Distinguish between logical and physical design requirements.
• Design and evaluate system outputs.
• Design and evaluate systems inputs.
• Design and evaluate validity checks for input data.
• Design and evaluate user interfaces for input.
• Design and evaluate file structures to include the use of indexes.
• Estimate storage requirements.
• Explain the various file update processes based on the standard file organizations.
• Decide various data structures.
• Construct and evaluate entity-relationship (ER) diagrams for RDBMS related projects.
• Perform normalization for the un-normalized tables for RDBMS related projects
• Decide the various processing systems to include distributed, client/server, online and others.
• Perform project cost estimates using various techniques.
• Schedule projects using both GANTT and PERT charts.
• Perform coding for the project.
• Documentation requirements and prepare and evaluate systems documentation.
• Perform various systems testing techniques/strategies to include the phases of testing.
• Systems implementation and its key problems.
• Generate various reports.
• Be able to prepare and evaluate a final report.
• Brief the maintenance procedures and the role of configuration management in operations.
• To decide the future scope and further enhancement of the system.
• Plan for several appendices to be placed in support with the project report documentation.
• Work effectively as an individual or as a team member to produce correct, efficient, well-organized and documented programs in a reasonable time .
• Recognize problems that are amenable to computer solutions, and knowledge of the tools necessary for solving such problems.
• Develop of the ability to assess the implications of work performed.
• Get good exposure and command in one or more application areas and on the software
• Develop quality software using the software engineering principles
• Develop of the ability to communicate effectively.
TYPE OF THE PROJECT AND ELIGIBILITY CRITERIA OF THE PROJECT GUIDE
The majority of the students are expected to work on a real-life project preferably in some industry/ Research and Development Laboratories/Educational Institution/Software Company. Students are encouraged to work in the areas listed at the end (Refer page no.15). However, it is not mandatory for a student to work on a real-life project. The student can formulate a project problem with the help of her/his Guide and submit the project proposal of the same. Approval of the project proposal is mandatory. If approved, the student can commence working on it, and complete it. Use the latest versions of the software packages for the development of the project.
Please do not undertake the topics/specifications from the MCS-044 (Mini Project). Problem selected and the specifications should be very much genuine.
POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT
1. Project Report Formulation:
The project report should contain the following:
(i) Original copy of the Approved Proforma and Project Proposal.
(ii) Bio-data of the guide with her/his signature and date.
(iii) Certificate of Originality (Format given on Page 23).
(iv) Project documentation.
(v) 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.
2. The 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. To be more specific, whatever the theory in respect of these topics is available in the reference books should be avoided as far as possible. The project documentation should be in respect of your project only. The project documentation should include the topics given below. Each and every component shown below carries certain weightage in the project report evaluation.
• Table of Contents/Index with page numbering
• Introduction/Objectives
• System Analysis
• Identification of Need
• Preliminary Investigation
• Feasibility Study
• Project Planning
[attachment=31319]
INTRODUCTION AND OBJECTIVES
The Project work constitutes a major component in most professional programmes. It needs to be carried out with due care, and should be executed with seriousness by the students. The project work is not only a partial fulfilment of the MCA requirements, but also provide a mechanism to demonstrate your skills, abilities and specialisation. The project work should compulsorily include the software development. Physical installations or configuring the LAN/WAN or theoretical projects or study of the systems, which doesn’t involve s/w development, are strictly not allowed.
Students are eligible to submit the project proposals after entering into the 5th semester of MCA, as per the calendar of the project.
OBJECTIVES
The objectives of the project is to help the student develop the ability to apply theoretical and practical tools/techniques to solve real life problems related to industry, academic institutions and research laboratories. After the completion of this project work, the student should be able to:
• Describe the Systems Development Life Cycle (SDLC).
• Evaluate systems requirements.
• Complete a problem definition.
• Evaluate a problem definition.
• Determine how to collect information to determine requirements.
• Perform and evaluate feasibility studies like cost-benefit analysis, technical feasibility, time feasibility and Operational feasibility for the project.
• Work on data collection methods for fact finding.
• Construct and evaluate data flow diagrams.
• Construct and evaluate data dictionaries.
• Evaluate methods of process description to include structured English, decision tables and decision trees.
• Evaluate alternative tools for the analysis process.
• Create and evaluate such alternative graphical tools as systems flow charts and state transition diagrams.
• Decide the S/W requirement specifications and H/W requirement specifications.
• Plan the systems design phase of the SDLC.
• Distinguish between logical and physical design requirements.
• Design and evaluate system outputs.
• Design and evaluate systems inputs.
• Design and evaluate validity checks for input data.
• Design and evaluate user interfaces for input.
• Design and evaluate file structures to include the use of indexes.
• Estimate storage requirements.
• Explain the various file update processes based on the standard file organizations.
• Decide various data structures.
• Construct and evaluate entity-relationship (ER) diagrams for RDBMS related projects.
• Perform normalization for the un-normalized tables for RDBMS related projects
• Decide the various processing systems to include distributed, client/server, online and others.
• Perform project cost estimates using various techniques.
• Schedule projects using both GANTT and PERT charts.
• Perform coding for the project.
• Documentation requirements and prepare and evaluate systems documentation.
• Perform various systems testing techniques/strategies to include the phases of testing.
• Systems implementation and its key problems.
• Generate various reports.
• Be able to prepare and evaluate a final report.
• Brief the maintenance procedures and the role of configuration management in operations.
• To decide the future scope and further enhancement of the system.
• Plan for several appendices to be placed in support with the project report documentation.
• Work effectively as an individual or as a team member to produce correct, efficient, well-organized and documented programs in a reasonable time .
• Recognize problems that are amenable to computer solutions, and knowledge of the tools necessary for solving such problems.
• Develop of the ability to assess the implications of work performed.
• Get good exposure and command in one or more application areas and on the software
• Develop quality software using the software engineering principles
• Develop of the ability to communicate effectively.
TYPE OF THE PROJECT AND ELIGIBILITY CRITERIA OF THE PROJECT GUIDE
The majority of the students are expected to work on a real-life project preferably in some industry/ Research and Development Laboratories/Educational Institution/Software Company. Students are encouraged to work in the areas listed at the end (Refer page no.15). However, it is not mandatory for a student to work on a real-life project. The student can formulate a project problem with the help of her/his Guide and submit the project proposal of the same. Approval of the project proposal is mandatory. If approved, the student can commence working on it, and complete it. Use the latest versions of the software packages for the development of the project.
Please do not undertake the topics/specifications from the MCS-044 (Mini Project). Problem selected and the specifications should be very much genuine.
POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT
1. Project Report Formulation:
The project report should contain the following:
(i) Original copy of the Approved Proforma and Project Proposal.
(ii) Bio-data of the guide with her/his signature and date.
(iii) Certificate of Originality (Format given on Page 23).
(iv) Project documentation.
(v) 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.
2. The 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. To be more specific, whatever the theory in respect of these topics is available in the reference books should be avoided as far as possible. The project documentation should be in respect of your project only. The project documentation should include the topics given below. Each and every component shown below carries certain weightage in the project report evaluation.
• Table of Contents/Index with page numbering
• Introduction/Objectives
• System Analysis
• Identification of Need
• Preliminary Investigation
• Feasibility Study
• Project Planning