PROJECT GUIDENCE LECTURE T Y B ScIT MARKING

PROJECT GUIDENCE LECTURE T. Y. B. Sc(IT)

MARKING SCHEME (MAXIMUM MARKS=200) PROJECT REPORT Que s Description Marks Q 1 Documentation and Content Presentation 50 Q 2 Problem Definition, Solutions Provided, Charts, Diagrams, Planning and Methodology, etc 50 TOTAL MARKS= VIVA VOCE 100 Questio n Description Marks Q 1 Presentation Skills 25 Q 2 Viva – voce 25 Q 3 Project Quality / User Presentation / Innovative Technologies 25 Q 4 Working and Functionality Testing 25

What is a PROJECT? �A project : 1. Is a research assignment. 2. Requires a large amount of efforts. 3. More independent work. 4. It requires students to undertake their own fact-finding analysis and conclusion. 5. A software project must accommodate with proper reports and documentation.

SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC) �It consist of important phases, essential for developers. �The oldest model of SDLC is the waterfall model. �In waterfall model output of each stage becomes the input for the next. �Not every project will require that the phases be sequentially executed. �The phases are interdependent.

SDLC WORK FLOW DIVIDED INTO PHASES INVESTIGATION ANALYSIS PHASE DESIGN PHASE CODING PHASE TESTING PHASE MAINTAINANCE AND EVALUATION PHASE BLACK BOOK SUBMISSION

TASK UNDER EACH PHASE OF SDLC : �PHASE 1: - INVESTIGATION. Step 1: -Project initiation and Planning. ØSearch your domain/ organization and client. ØIdentifying the problem statement. ØWriting down the problem statements. ØDecide upon the technology. Step 2: -Synopsis.

PREPARE A GOOD SYNOPSIS: �Synopsis is: 1. First step towards project plan. 2. Gives overall and brief idea about the project to be developed. 3. It should be simple. 4. Should not exceed more than 3 to 4 pages. 5. Submission of synopsis indicates the readiness of the student to undertake the project and his project requirement and specifications

CONTENT OF SYNOPSIS: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Project Name. Submitted To. Submitted By. Objective. (purpose of the project) Problem description. (Present state/existing system. ) Proposed system (your project) Scope. (boundary of your project like the number of users) Main features. Significant/benefits. Tools and technology used. Requirement gathering techniques. Hardware and software Requirements to run the project.

NOTE: �Don’t carry the myth that the big project will fetch you good marks. �Once the approval to the synopsis is received by the student from the project guide then the actual work towards the development can be started.

SEQUENCE FOR PROJECT DOCUMENTATION: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. COVER PAGE. CERTIFICATE FROM COLLEGE. CERTIFICATE FROM PROJECT GUIDE/COMPANY. ACKNOWLEDGMENT. SYNOPSIS OF THE PROJECT SECHEDULE-GANTT CHART. NETWORK DIAGRAM-PERT CHART. ANALYSIS PHASE. DESIGN PHASE. CODING PHASE. TEST PHASE. SYSTEM MAINTENANCE AND FUTURE ENHANCEMENT. USER MANUAL. ANNEXURE.

FIRST FEW IMPORTANT DATES: � 7/JUNE/14 - LECTURE ON SYNOPSIS. � 30/JUNE/14 – SYNOPSIS SUBMISSION