IGNOU Project MCA MCSP060

Spread the love

IGNOU Projects MCA MCSP060 is very important for your career & Job point 

IGNOU MCA MCSP060 is a final year project work. In 6th semester you have to perform ignou MCA MCSP060 project work. Mainly it is divided in two parts:

  1. Synopsis – MCA MCSP060 and
  2. Project Report – MCA MCSP060

MCA Synopsis & Project (IGNOU MCSP060)

Dear Ignou Learners, for the preparation of MCA synopsis you have to follow the below steps:

  • Suitable title selection for MCA project
  • Make all necessary details about MCA project which you want to developed.
  • Actually Synopsis is also known as project proposal, by the help of this you get permission from the university to developed proposed project.
  • Insert necessary diagram, platform, limitation, scope, bibliography in the synopsis.
  • It should be 15 to 20 pages approximately

Approval of Synopsis

  • After submission of synopsis, it is evaluated by university
  • After evaluation and getting synopsis approval you can prepare project report

Project Report 

  • After approval you can start project report preparation
  • for BCA MCA B.Tech Program it should be 90 to 150 pages and you have to develop any software/ website or any application. In project report source code must be inserted. After submission of project you called for viva. At the viva time must keep project report + CD (Source Code)
  • For other program project report should be 60 to 120 pages. you have to elaborate more about the topic with proper diagram, test case etc. After submission of project you called for viva. At the viva time must keep project report. we provide you some selected question answer to crack the viva

IGNOU MCA MCSP060 – Synopsis & Project submission date 

Session Type of Submission     Date
January

July

January

July

  Synopsis for MCA MCSP060

Synopsis MCA MCSP060

Project MCA MCSP060

Project MCA MCSP060

 1st April to 30th June

1st October to 31st December

1st January to 31st March

1st July to 30th September

source: www.ignou.ac.in

IGNOU MCA Project Approval Best Platform

Best Combination for WEB BASED PROJECT

=> PHP + My SQL + APACHE

=> ASP.Net With C# + SQL Server + IIS

=> JSP + My SQL + Apache

=> PHP + HTML + CSS + XAMPP + My SQL

GET BEST Support for IGNOU MCA MCSP060, Final Year Project Guidance

  • TOPIC SELECTION
  • SYNOPSIS Support for IGNOU MCA MCSP060 Program
  • PROJECT REPORT Support for IGNOU MCA MCSP060 Program
  • EXECUTABLE SOURCE CODE for IGNOU MCA MCSP060 Program –  We help you for Developing
  • VIVA SELECTED QUESTION ANSWERS for IGNOU MCA MCSP060 Program
  • STEP BY STEP GUIDANCE
  • We Maintain the quality for the best knowledge and Learning. So, in this program you must learn lots of new things for your career Growth. Performing this you are able to crack the viva & Complete the IGNOU Project work related to your MCA MCSP060 Program
  • Contact us for any query or doubt, We guide you to solve

Wish You Success

Navneet Vishwas & Team NiPSAR

Benefits : This Article is written for the complete overview to the ignou aspirants related to MCA MCSP060 synopsis & project work. This is also helpful for smu,jnu, du, ipu & other university aspirants related to BCA, MCA, IT, CSE & other computer Science Program. The author & Asst. Professor Navneet Vishwas is happy to solve your related query or doubt. Our aim to make the contribution to the society for the knowledge growth. Through the article you know about the process of ignou synopsis & project approval work. Synopsis & Project preparation process. And finally you are able to complete your MCA program. If you have some backlog or pending paper related to MCA proram the you can contact us for best notes and study guidance. You can also watch video lecture by Navneet Vishwas or follow the tips and technique provided by him.

Guidelines in Detail for IGNOU MCA Synopsis & Project work:

GUIDELINES FOR PROJECT FORMULATION

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

Type of the Project

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 PROPOSAL IGNOU MCA MCSP064

  1. Project Proposal Formulation
  • The project proposal should be prepared in consultation with your guide. The project proposal should clearly state the project objectives and the environment of the proposed project to be undertaken. The project work should compulsorily include the software development. The project proposal should contain complete details in the following form:
  • Proforma for Approval of Project Proposal (see page no.5) duly filled and signed by both the student and the Project Guide with date.
  • Bio-data of the project guide with her/his signature and date.
  • Synopsis of the project proposal (15-20 pages) covering the following aspects:
  • Title of the Project.
  • Introduction and Objectives of the Project.
  • Project Category (RDBMS/OOPS/Networking/Multimedia/Artificial Intelligence/Expert Systems etc.).
  • Tools/Platform, Hardware and Software Requirement specifications.
  • Problem Definition, Requirement Specifications (Detailed functional Requirements and Technical Specifications), Project Planning and Scheduling (Gantt chart and PERT chart).
  • Scope of the solution.
  • Analysis (Data Models like 0, 1 and 2 level DFDs, Complete ER Diagrams with cardinality, Class Diagrams etc. as per the project requirements).
  • A complete Database and tables detail with Primary and Foreign keys, and proper constraints in the fields (as per project requirements)
  • A complete structure which includes:
  • Number of modules and their description to provide an estimation of the student’s effort on the project. Along with process logic of each Module.
  • Data Structures as per the project requirements for all the modules.
  • Process Logic of each module.
  • Implementation methodology
  • List of reports that are likely to be generated.
  • Overall network architecture (if required for your project)
  • Implementation of security mechanisms at various levels
  • Future scope and further enhancement of the project.
  • Bibliography
  • A self-addressed envelope with duly affixed postage stamps (to send it by ordinary post only) on it.
  1. Project proposal completed in all aspects with necessary enclosures should be sent to the Regional Director of the Regional Centre concerned. While posting your proposal to your Regional Centre, on the top of the envelope you should mention “MCA Project Proposal (MCSP-060)”. Under no circumstances, should the project proposal be sent to SOCIS, IGNOU, New Delhi.
  2. A project proposal, once approved, is valid for one year (two slots). In case, a student is unable to submit her/his project report as per the slot, s/he may be given another chance for submission of the project report in the subsequent slot. If s/he still does not submit the project report, a fresh synopsis approval is needed.
  3. All entries of the proforma of approval should be filled up with appropriate and complete information. Incomplete approval-proforma in any respect will be summarily rejected.
  4. A photocopy of the complete Project Proposal (along with Project Proforma, Project Synopsis, Bio-data of the guide) submitted to your Regional Centre, should be retained by the student for future reference.
  5. The evaluated project proposal proforma along with the details of Approved/Disapproved will be sent to the student within 4-6 weeks after the proposal is received at Regional Centre concerned. In case if it is disapproved, the suggestions for reformulating the project will be communicated to the student. Revised project proposal proforma, synopsis, bio-data of the guide with her/his signature on it, should be sent along with the original copy/photocopy of the non-approved proforma of the earlier project proposal, to the Regional Centre Concerned.
  6. The project is a part of your final semester (6th semesters) curriculum. Students are eligible to submit the project proposals after entering the 5th semester of MCA as per the calendar.
  7. In case the students require any project trainee letter from the University for doing a project in any organization/software company, they can get a “Project Trainee letter” (Refer page 21) attested by the Project Coordinator/Regional Director / Asst. Regional Director.
  8. Please ensure that at any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU.
  9. Violation of the project guidelines will lead to the rejection of the project at any stage.

 

 POINTS TO REMEMBER WHILE PREPARING THE PROJECT REPORT

  1. 1. Project Report Formulation:

The project report should contain the following:

(i)         Original copy of the Approved Proforma and Project Proposal.

  • Bio-data of the guide with her/his signature and date.
  • Certificate of Originality (Format given on Page 23).
  • 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.
  1. 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
  • Project Scheduling (PERT Chart and Gantt Chart both)
  • Software requirement specifications (SRS)
  • Software Engineering Paradigm applied
  • Data models (like DFD), Control Flow diagrams, State Diagrams/Sequence diagrams, Entity Relationship Model, Class Diagrams/CRC Models/Collaboration Diagrams/Use-case Diagrams/Activity Diagrams depending upon your project requirements
  • System Design
  • Modularisation details
  • Data integrity and constraints
  • Database design, Procedural Design/Object Oriented Design
  • User Interface Design
  • Test Cases (Unit Test Cases and System Test Cases)
  • Coding
  • Complete Project Coding
  • Comments and Description of Coding segments
  • Standardization of the coding
  • Code Efficiency
  • Error handling
  • Parameters calling/passing
  • Validation checks
  • Testing
  • Testing techniques and Testing strategies used
  • Testing Plan used
  • Test reports for Unit Test Cases and System Test Cases
  • Debugging and Code improvement
  • System Security measures (Implementation of security for the project developed)
  • Database/data security
  • Creation of User profiles and access rights
  • Cost Estimation of the Project along with Cost Estimation Model
  • Reports (sample layouts should be placed)
  • Future scope and further enhancement of the Project
  • Bibliography
  • Appendices (if any)
  • Should attach a copy of the CD containing the executable file(s) of the complete project.
  1. 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.
  2. If any project report is received in the absence of the approved project proposal proforma (in original), project synopsis, bio-data of the guide with her/his signature on it, certificate of originality and CD  it will be summarily rejected and returned to the student for compliance.
  3. Through out the project report, the title of the project should be the same as per the approved synopsis. Signature of the Project Guide in the Certificate of Originality should match with the signature in the Project Proposal proforma also.
  4. Only one copy 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 submitted to the Regional Director of the Regional Centre concerned through registered insured post by the date mentioned in the Calendar for the project. One photocopy of the same Project Report and the CD containing the executable file(s) must be retained by the student, which should be produced before the examiner at the time of viva-voce.
  5. A photocopy of the project report is not acceptable for submission. Kindly mention on the top of the envelope MCA PROJECT REPORT (MCSP-060). This will facilitate sorting out project reports received by the Regional Director.

 Preferably, not more than one student is permitted to work on a project. However, in case a project is comprehensive enough that requires one human–year or more time for its completion, then as per requirements of six human-months per student, at most two student may work on the same project. In this regard, prior recommendation is mandatory and must be obtained from the MCA Project Coordinator, SOCIS, Block-C, Visveswarayya Bhawan, IGNOU Academic Complex, Maidan Garhi, New Delhi – 110068 by sending the complete synopsis by both the students along with a hand-written application.

  1. If 2 students have been allowed to work on a project, the project synopsis and project reports by them must include only different modules undertaken/worked upon individually. Each student must submit a separate project proposal and a separate project reports related to her/his modules. Completely identical project synopsis and/or project reports are not allowed. Only introductory and possibly concluding remarks may be similar or common. Each student has to undergo all the phases/stages of the software project development life cycle. In this case, both the students must attach the prior recommendation obtained from the MCA Project Coordinator along with the synopsis should be sent to the Regional Centre concerned for evaluation. A single copy of the project synopsis and/or project report comprising of work of two or more students shall not be entertained. Violation of these project guidelines may lead to the rejection of the project                      at any stage.
  2. Students are advised not to pay any fees/remuneration to the Project Guide as the University has the provision for paying remuneration to the guide, for whom a format is being, enclosed (Refer Page 19).
  3. Student should be involved in each and every phase of Project Development. If it is found that student is not involved in any phase for example coding phase, it may lead to the rejection/disqualifying of the project at any stage.
  4. Title of the project should be kept the same through out the project.

 COMMUNICATION OF APPROVAL

Communication regarding the Approval / Non-approval of the project will be sent to you within four weeks after the receipt of the project proposal by the Regional Centre concerned.

RESUBMISSION OF THE PROJECT PROPOSAL IN CASE OF NON-APPROVAL

In case of non-approval, the suggestions for reformulating the project will be communicated to you. The revised project synopsis along with a new Performa, should be re-submitted along with a copy of the earlier synopsis and non-approval project proposal Performa in the next slot. For example, if the student submitted the synopsis during the 1st April to 30th June slot and is not approved due to some reasons, s/he is eligible to resubmit the revised project synopsis only during the next slot i.e., 1st October to 31st December. These guidelines are applicable for earlier batch students also whose project work is pending.

ELIGIBILITY OF PROJECT GUIDE
1. A person having Ph.D./M.Tech. in Computer Science.
OR
2. A person having B.E/B.Tech (Computer Science), MCA, M.Sc (Computer Science) with minimum 2 years experience in Industry / Teaching.

IMPORTANT POINTS WHILE PREPARING THE PROJECT REPORT

  1. The Project Report should be submitted in A-4 size typed in double space. The Project Report should be hard bound.
    2. Ensure that it contains the following:
    Project Proposal Proforma. All the items should be filled. The signatures of both student and Guide should be present. Project Synopsis. Both Guide and student should sign on the Project Synopsis. Guide‟s Bio data. The Biodata should consist of signature of the Guide. Certificate of Originality (Format given on Page no.13) All signatures should be accompanied by the date of signature.
    It should include all items mentioned in Section IV.
    3. If any project report is received in the absence of the items listed above, it will be rejected and returned to students for compliance. Also, violation of Project Guidelines may lead to rejection of the Project .
    4. Only One hard bound original copy of the project report is to be submitted to „The Regional Director, Concerned Regional Centre‟ by registered insured post. One copy of the same Project Report is to be retained with the student and the student is supposed to carry his copy while appearing for viva voce. Spiral binding of Project Report is not permitted.
    5. Xerox copy of the project report is not acceptable.
    6. Not more than one student is permitted to work on a Project.
    7. If the title of the Project differs from the title mentioned in the Project Proposal, the Project Report will be rejected and will be returned back to the student.
    8. Kindly mention on the top of the envelope “MCA PROJECT REPORT (BCSP-064)”. This will facilitate sorting out project reports at the Regional Centre.
    9. The envelope containing the remuneration form for the Project Guide duly signed by the Guide and the student, should be sent to “Regional Director, Concerned Regional Centre.”
    10. In case, students require any letter from the University for doing a project in any organization, they may request the Regional Director of the concerned Regional centre for the issuance of the same in the format indicated under Project Trainee in this document. (Refer to Page number : 15).

LIST OF BROAD AREAS OF APPLICATION AND RELATED TOOLS

FRONT END / GUI Tools :
Visual Basic, Power Builder, X-Windows (X/lib, X/motif, X/Intrinsic), Oracle Developer 2000,VC++, Jbuilder
RDBMS/BACK END :
Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL Server, DB2
LANGUAGES :
C, C++, Java, VC++, C#, Php, Java
SCRIPTING LANGUAGES :
PERL, SHELL Scripts(Unix), TcL/TK
RDBMS/BACK END :
Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL Server, DB2, My Sql
MIDDLE WARE (COMPONENT) TECHNOLOGIES :
COM/DCOM, Active-X, EJB, Rational Rose, MSMQ, BEA, Message Q, MTS, CICS
UNIX INTERNALS :
Device Drivers, Pipes, RPC, Threads, Sockets
ARCHITECTURAL CONCEPTS :
CORBA, TUXEDO
INTERNET TECHNOLOGIES :
DHTML, Java script, VB Script, Perl & CGI script, HTML, Java, Active X, RMI, CORBA, SWING, JSP, ASP, XML, EJB, Java Beans, Java Servlets, Visual Age for JAVA, UML, VRML, WML, iPlanet, ATG, BigTalk, CSS, XSL, Oracle ASP server, VB.Net, AWT, J2EE, LDAP, ColdFusion
NETWORKING TECHNOLOGIES :
ATM, Frame Relay, TCP/IP, SNMP, GSM, VoIP, PPP, IP-PSTN, SONET/SDH
WIRELESS TECHNOLOGIES :
Blue Tooth, 3G, ISDN, EDGE
REALTIME OPERATING SYSTEM/ EMBEDDED SKILLS :
QNX, LINUX, OSEK, DSP, VRTX, RTXC, Nucleus
OPERATING SYSTEMS :
WINDOWS 95/98/2000/ME, WINDOWS NT, UNIX, LINUX, IRIX, SUN SOLARIS, HP/UX, PSOS, VxWorks, AS400, AIX, WINDOWS XP, DOS
APPLICATIONS :
Financial/ Manufacturing/ Multimedia/ Computer Graphics/ Instructional Design/ Database Management System/ Internet/ Intranet/ Computer Networking-Communication Software/E-Commerce/ ERP / MRP/ TCP/IP Internals/ Routing protocols/ Socket Programming/ Implementation of Switches & Routers
Note: Projects should not be developed using the packages like Dbase, Foxpro, Visual Foxpro . Also, projects should not be developed using the combination of Visual Basic as the front end and MS-Access as the back end.

Source: www.ignou.ac.in | Author suggest you to also verify details from respective university website. This article has no legal validity and copyright protected by the concern website.

Leave a Reply

Your email address will not be published. Required fields are marked *