SCMS SCHOOL OF TECHNOLOGY & MANAGEMENT Prathap Nagar , Muttom, Aluva , Cochin

TEMPLATE FOR SSTM MCA INTERIM PROJECT REPORT

MILESTONE 1 - SRS
This document lists the contents required for the academic project report done as part of the MCA curriculum. Section names have been listed with description. The descriptions have been provided in italics. Important: This page and the text in italics present throughout this document are to give you guidance. Please do not include them in your project report.

CONTENTS OF THE ACADEMIC PROJECT REPORT MILESTONE 1

1. Background 1.1. Existing System Describe the system that already exists. Please note that the system could be manual or automated or a combination of both. 1.2. Definition of Problem Proposed System Describe the problems/inadequacies of current setup. Explain how the system proposed by you will solve the problems. 2. Project Overview 2.1. Objective of the Project Describe the business benefits expected from this project. 2.2. Scope of the Project Mention in brief the system proposed to meet the objective. Mention clearly if any part of the work is not in your scope e.g. installation, or some data migration required for implementation of this system, integration with some other system etc. 2.3. Feasibility Analysis Give feasibility analysis process undertaken in terms of 2.3.1. Technical feasibility Technology and system feasibility - The assessment is based on an outline design of system requirements in terms of Input, Processes, Output, Fields, Programs, and Procedures. This can be quantified in terms of volumes of data, trends, frequency of updating, etc. in order to estimate whether the new system will perform adequately or not 2.3.2. Operational feasibility Is a measure of how well a proposed system solves the problems, and takes advantages of the opportunities identified during scope definition and how it satisfies the requirements identified in the requirements analysis phase of system development 2.3.3. Schedule feasibility Schedule feasibility is a measure of how reasonable the project timetable is. 2.3.4. Economic feasibility - Cost - Benefit Analysis If the company had already done the analysis before deciding on the project, then obtain the information from the company and just mention it here. If this analysis was performed by the student, then explanation of how the analysis was conducted should be provided.. The analysis aims to determine the benefits and savings that are expected from a candidate system and compare them with costs. 2.3.5.Constraints

List the constraints applicable to your project e.g. time constraints, budget constraints, resource constraints, any other constraints set by the customer. 2.4. Deliverables List all deliverables expected by the customer e.g. application, configuration files, source code, any 3rd party software packaged along with this, documents requirements, design, user manual, installation manual, tutorial as applicable for your project. 2.5. Assumptions and dependencies List the assumptions and dependencies made while planning the project, e.g .there could be an assumption that the required inputs will be given by users or that users will be available to review the documents or that the testing team will be available to test if required etc. 2.6. Process model Mention which process model you chose to develop this project and the justification for it. 2.7. Schedule Put the work breakdown structure here activities, dependencies, start and end dates. These can be arrived at using CPM/PERT techniques. 2.8. Risks List any risks you foresee in the execution of this project and describe the plan to mitigate it. 3. System Analysis 3.1. User characteristics Mention the different types of users or user groups of the proposed system and any special training needs they have in order to use this system. 3.2. Inputs and outputs List the user inputs in the form of text and file inputs to system (if any). Also give the format of input which the system will accept, with examples. If it is a file input, format of file and format of data within it (if relevant) have to be provided. Then list system outputs like reports, error messages and information texts. 3.3. Interface Requirements Describe the external interfaces required in this project e.g interface with other systems, hardware, users. Describe the requirements of each interface identified. In the case of user interface, format of the screens identified during analysis should be provided. 3.4. Functional requirements Detailed functional requirements should be listed. Each requirement should mention the input and output related to it.

3.5. Non functional requirements List the non functional requirements applicable to your project related to performance, security etc. 3.6. Operational requirements The hardware and software needed to operate the proposed system should be listed. 3.7. Use cases Give all the use case diagrams here and a brief description of each use case. 3.8. Class descriptions Give the analysis level class diagram here and a brief description of the analysis level class . 3.9. Sequence diagrams Give the sequence diagrams here if any were developed during analysis. 4. Annexure : 4.1. Organization profile Give a brief background of the organization where the student has developed the project 4.2. User Interview Questionnaires