MASTER OF COMPUTER APPLICATIONS
(MCA)
MCSP-060
PROJECT GUIDELINES
(2012)
SCHOOL OF COMPUTER AND INFORMATION SCIENCES
BLOCK – C, NEW ACADEMIC COMPLEX
INDIRA GANDHI NATIONAL OPEN UNIVERSITY
MAIDAN GARHI, NEW DELHI – 110 068
MCSP-060
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community
Ask the community for help and clear up your study doubts
University Rankings
Discover the best universities in your country according to Docsity users
Free resources
Our save-the-student-ebooks!
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
MCS060 Project Guidelines, Assignments of Computer Programming
Project Guidelines For Ignou 6th Semester
Typology: Assignments
2019/2020
1 / 26
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download MCS060 Project Guidelines and more Assignments Computer Programming in PDF only on Docsity!
MASTER OF COMPUTER APPLICATIONS
(MCA)
MCSP-
PROJECT GUIDELINES
SCHOOL OF COMPUTER AND INFORMATION SCIENCES
BLOCK – C, NEW ACADEMIC COMPLEX
INDIRA GANDHI NATIONAL OPEN UNIVERSITY
MAIDAN GARHI, NEW DELHI – 110 068
MCSP-
MESSAGE FROM THE PROJECT CO-ORDINATOR
The Master of Computer Applications (MCA) programme prepares the students to take up positions as Systems Analysts, Systems Designers, Software Engineers, Programmers and Project Managers in any field related to information technology. We had therefore imparted you the comprehensive knowledge covering the skills and core areas of computer science courses with equal emphasis on the theory and practice. The MCA students are encouraged to spend at least six man-months working on a project preferably in a software industry or any research organization. The courses studied and the mini project handled by you the comprehensive background to work on diverse application domains. Approval of the project proposal is mandatory to continue and submit the project work. The theoretical background of various courses provides you the necessary foundation, principles, and practices to develop effective ways to solve computing problems. The hands on experience gained from the practical courses provides you the knowledge to work with various operating systems, programming languages, software tools and testing tools. The objective of the MCA project work is to develop quality software solution. During the development of the project, you should involve in all the stages of the software development life cycle like requirements engineering, systems analysis, systems design, software development, testing strategies and documentation with an overall emphasis on the development of reliable software systems. The primary emphasis of the project work is to understand and gain the knowledge of the principles of software engineering practices, so as to participate and manage a large software engineering projects in future. Students should take this project work very seriously , as these efforts will be considered as 6-months experience in most of the software companies. Topics selected should be complex and large enough to justify as a MCA project. Please do not undertake the topics/specifications from the MCS-044 (Mini Project) or don’t repeat the topic undertaken at BCA level, if you are from the BCA/MCA integrated mode. However, student can use MCS-044 guideline for reference. The project should be genuine and original in nature and should not be copied from anywhere else. If found copied, the project report will be forwarded to the Exam Discipline Committee of the University as an Unfair means case for necessary action. In case of project resubmission, please confirm the fees and other details with the Regional Centre/Study Centre/website. Students should strictly follow and adhere to the MCSP-060 project guidelines. I wish you all the success. Dr. Naveen Kumar MCA Project Coordinator
3 I CALENDAR FOR THE MCA PROJECT
Sl.No. Topic Date
- Submission of a guide’s bio-data and project proposal at the following address: The Regional Director of your Regional Centre Twice a year as shown below: 1 st^ April to 30th^ June or 1 st^ October to 31st^ December
- Approval of Project 30 days after the project proposal is received.
- Submission of the Project Report ( one copy ) in bound form to: The Regional Director of your Regional Centre Twice a year as shown below: 1 st^ July to 30th^ September (For Project Proposals that have been approved during the 1 st^ April to 30th^ June slot) or 1 st^ January to 31st^ March (For Project Proposals that have been approved during 1 st^ October to 31st^ December slot)
- Viva-Voce to be conducted In July (For project reports submitted during 1st^ January - 31 st^ March slot) In January (For project reports submitted during 1 st July – 30th^ September slot) 4
Ensure that you include the following while submitting the Project Proposal:
- Proforma for Approval of Project Proposal 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 (12-15 pages).
- A self-addressed envelope with duly affixed postage stamps (to send it by ordinary post only) on it. Note: i. At any given point of time, a guide should not provide guidance for more than 5 MCA students of IGNOU. ii. If you are a student of BCA/MCA integrated programme, don’t repeat the BCA project specifications. Select a different topic altogether. iii. Please donot undertake the topics / specifications from the MCS-044 (Mini Project). Problem selected and the specifications should be very much genuine. iv. Suggestions given for reformulating the project must be incorporated in the final project if project proposal is approved otherwise in the new project proposal. v. Violation of the project guidelines will lead to the rejection of the project at any stage. 6
A photocopy of the complete Project Proposal (along with Project Proforma,
Project Synopsis, Biodata of the guide) submitted to your Regional Centre,
should be retained by the student for future reference.
III 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 7
- A person having Ph.D./ M.Tech. in Computer Science with a minimum of one year of experience. Or
- A person having B.E./B.Tech. (Computer Science), MCA, M.Sc. (Computer Science) with minimum 2 years experience, preferably in software development. Steps involved in the project work The complete project work should be done by the student only. The role of guide should be about guidance wherever any problem encounters during project. The following are the major steps involved in the project, which may help you to determine the milestones and regulate the scheduling of the project: Select a topic and a suitable guide. Prepare the project proposal in consultation with the project guide. Submit the project proposal along with the necessary documents to the Regional Director of the Regional Centre concerned. Receipt of the project approval from the Regional Centre concerned. Carry out the project-work. Prepare the project report. Submit the project report to the Regional Director of the Regional Centre concerned Appear for the viva-voce as per the intimation by the Regional Director. Communication of the approval Communication regarding the project Approval/Non-approval will be sent to you within four to six 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 proforma, should be re-submitted along with a copy of the earlier synopsis and non-approval project proposal proforma 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 the reasons mentioned by the evaluator, s/he is eligible to resubmit the revised project synopsis only during the next slot i.e., 1st^ October to 31st^ December. If the student wants to change the project topic or software or the project guide, s/he may do so and can submit a fresh project proposal. The revised project proposal should be sent along with the original copy/ photocopy of the non-approved proforma of the earlier submitted proposal, to the Regional Centre Concerned. Resubmission of MCA project in case of failed students If the student is unsuccessful in the project, s/he should ‘re-do’ the whole cycle, right from the submission of the project proposal. Students are advised to select a new topic for the project and should prepare and submit the project proposal to the Regional Centre concerned as per the project guidelines. There are no separate slots for the submission of the project synopsis/project reports for the failed students. Respective submissions of the project synopsis and the project reports should be done strictly as per the “Calendar for the MCA project” given in the project guidelines. 9
In case of failed students, a pro-rata fee of Rs.2500/- by way of a Demand Draft in favour of IGNOU and payable at the city where you Regional Centre is located should be remitted along with the resubmission of the project report. Enquiries Enquiries regarding the project proposal approvals and the project reports should be addressed to the Regional Director of the Regional Centre concerned. In all correspondence with the University regarding your project, please quote your Enrolment No., Project Proposal No. and Project Report No. V POINTS TO REMEMBER WHILE PREPARING THE PROJECT PROPOSAL
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: (i) Title of the Project. (ii) Introduction and Objectives of the Project. (iii) Project Category (RDBMS/OOPS/Networking/Multimedia/Artificial Intelligence/Expert Systems etc.). (iv) Tools/Platform, Hardware and Software Requirement specifications. (v) Problem Definition, Requirement Specifications (Detailed functional Requirements and Technical Specifications), Project Planning and Scheduling (Gantt chart and PERT chart). (vi) Scope of the solution. (vii) Analysis (Data Models like 0, 1 and 2 level DFDs, Complete ER Diagrams with cardinality, Class Diagrams etc. as per the project requirements). (viii) A complete Database and tables detail with Primary and Foreign keys, and proper constraints in the fields (as per project requirements) (ix) 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. 10
VI 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 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 11
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) Glossary. Should attach a copy of the CD containing the executable file(s) of the complete project.
3. 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. 4. 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. 5. 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. 6. 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. 7. 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. 8. 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 students 12 13
(i) PERT chart: Proper decomposition of stages, and (ii) Gantt chart: Time, line structure and validity of chart. You may know that the software requirement specification (SRS) document is one of the important documents of your project. The indicators for SRS document is whether you have used some standardisation like IEEE standards or any other international standard, or whether your SRS has a proper structure based on sound software engineering concepts as given in unit 3 or it is given in a running text. Project analysis for DBMS/Application development projects should contain the ER diagram, Data Flow Diagram and Data Dictionary, so you should include these with the following requirements. However, for other categories of project you should prepare class diagrams, behaviour model and/or state transition diagram and details of various data structures used. The Entity Relationship diagram (ER Diagram) should have: o Proper symbol of attributes, entities, relationships, cardinality metioned, and o Relationship of ER diagram to SRS with strong association Data Flow Diagram (DFD) should have: o All Data flow should be levelled and should have proper input and output. o Relationship of data flow to data dictionary Context Diagram, Level 1 and Level 2. Data Dictionary: It should explain each entity and relationship in ER diagram and data flow in DFD. Design Project design should include the desired features and operations in detail, including user interface design, program structure, schema design and normalised tables and data integrity and constraints. You should include them with the requirements given below: Program Structure: It should have the proper modularisations of software and specification of each module. Schema Design and Normalised Tables: Normalise the table to minimum 3NF. If any demand of Demoralisations clearly explain the reasons. Data Integrity and Constraints: Explain the referential diagram. Define entity integrity, which should include keys, alternate keys and other keys, value constraints and ranges. Procedural Design: Explain using Flowchart / Pseudo code / PDL. User Interface Design: Coherence with dataflow and processor; Consistency of interface and naming convention. Validation checks should be kept wherever necessary. Architecture: Program architecture and explanation on suitability of data structure used. Coding Coding phase of software development includes different activities like refining the algorithms for individual components, transferring the algorithms into a programming language (coding), 15 14
translating the logical data model into a physical one and compiling and checking the syntactical correctness of the algorithm with these activities. You should include the comments and description in code, use the standardisation in coding, use the methodology for error handling and security implementation. These parameters ensure software quality and reliability. You should include them with the requirements given below: Comments and Description: Should have comments with functional description which include the input, output, total function calls to/from other functions, function parameters, description of main variables, Data type, logic description, etc. Standardisation of Coding: Use of naming convention of variable and functions, nested depth, naming constant, use of data structure and style. Error Handling: Explain exceptions handling and conditional checking. Parameter passing and calling: Check the technique used for this purpose, how it optimises the coding. Security Mecahnisms: Maintain confidentiality, integrity and authorisation according to the requirement and needs of the system. Also maintain database level security, use of Views, use of revoke and grant, user and access rights and ensure steps taken against hacking of the system. Testing Testing is a process of devising a set of inputs to a given piece of software that will cause the software to exercise some portion of its code. The developer of the software can then check if the results produced by the software are in accordance with his or her expectations. It includes, number of activities such as correcting syntactically and semantically erroneous system components, detecting as many errors as possible in the software system, and assuring that the system implementation fulfils system specification. It ensures the quality, efficiency and reliability of the software, which is measured by the testing methodology and techniques used for unit, integrated, system testing etc. The testing should not be too generic containing only definitions. You should give all the test case designs, reports and results of test cases for unit, integrated, system testing etc. How debugged your code is and what actions you have taken too improve the code, must, be explained. Good testing can be measured by criteria such as correctness, reliability, user friendliness, maintainability, efficiency and portability of software. System Security Measures The student should clearly emphasize the various levels of security measures implemented in the project. Report Generation The project report should include the various sample reports for ready reference. 16
VIII SOFTWARE AND BROAD AREAS OF APPLICATION FRONT END / GUI Tools Visual Basic, Power Builder, X-Windows (X/lib, X/motif, X/Intrinsic), Oracle Developer 2000,VC++, Jbuilder , NetBeans RDBMS/BACK END Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL Server, DB2, Point base LANGUAGES C, C++, Java, VC++, C#, eclipse SCRIPTING LANGUAGES PERL, SHELL Scripts (Unix), TcL/TK, RDBMS/BACK END Oracle, Ingres, Sybase, Progress, SQL Plus, Versant, MY SQL, SQL Server, DB .NET Platform VB.Net, C#. Net, Visual C#. Net, ASP.Net MIDDLE WARE (COMPONENT) TECHNOLOGIES COM/DCOM, Active-X, EJB, WINCE, MSMQ, BEA, MessageQ, MTS, CICS UNIX INTERNALS Device Drivers, RPC, Threads, Socket programming ARCHITECTURAL CONCEPTS CORBA, TUXEDO, MQ SERIES INTERNET TECHNOLOGIES DHTML, Java script, VB Script, Perl & CGI script, Java, Active X, RMI, CORBA, SWING, JSP, ASP, XML, EJB, Java Beans, Servlets, Visual Age for JAVA, UML, VRML, WML, Vignette, EDA, Broadvision, Ariba, iPlanet, ATG, BigTalk, CSS, XSL, Oracle ASP server, AWT, J2EE, LDAP, ColdFusion, Haskell 98, PHP,NetBeans NETWORK/WIRELESS TECHNOLOGIES Blue Tooth, 3G, ISDN, EDGE REALTIME OPERATING SYSTEM/ EMBEDDED SKILLS QNX, LINUX, OSEK, DSP, VRTX, RTXC, Nucleus OPERATING SYSTEMS WINDOWS 2000/ME, WINDOWS NT, WINDOWS XP, UNIX, LINUX, IRIX, SUN SOLARIS, HP/UX, PSOS, VxWorks, AS400, AIX, DOS APPLICATION AREAS Financial / Insurance / Manufacturing / Multimedia / Computer Graphics / Instructional Design/ Database Management System/ Internet / Intranet / Computer Networking-Communication Software development/ E-Commerce/ ERP/ MRP/ TCP-IP programming / Routing protocols programming/ Socket programming. NOTE: (i) Projects should not be developed using theOld packages like Dbase III plus, Foxpro, Visual Foxpro and MS- Access. Also, projects should not be developed using the combination of Visual Basic as the front end and MS-Access as the back end. The project work should compulsorily include the software development. Latest versions of the software are to be used. 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. (ii) C/C++ languages should not be used for any Information Management System Project for example Hospital/Reservation/Library/School/College Management System etc. (iii) Students can also develop applications using tools/languages/software not listed above, if they are part of latest technologies. Use the latest versions of the software packages for the project development. 17 18
XI REMUNERATION BILL FOR THE MCA PROJECT GUIDE INDIRA GANDHI NATIONAL OPEN UNIVERSITY MAIDAN GARHI, NEW DELHI – 110068 REMUNERATION BILL FOR THE MCA PROJECT GUIDE
- Course Code : MCSP-
- Name of the Guide :
- Residential Address :
- Designation :
- Office Address : This is to certify that I have Guided the following student/(s) for their project work: S.No. Enrolment Number of the student PR No. (to be filled by the Regional Centre) Name of the student Title of the Project Amount claimed (to be filled by the office) ………………………… Signature of the Guide Date :...... ……………………. NOTE: Project guide cannot guide more than five students at any given point of time. This form duly signed by the guide placed in a separate envelope, should be submitted along with the project report. Remuneration Bill not accompanied with the project report will not be considered for payment. The concerned authority will fill the amount.