Abstract
· Describe the need of your idea first i.e. the project definition.
· Its past work and present scenario should be mentioned.
· Explain your innovation in the concerning field.
· This abstract is just the brief introduction of your project.
Project Summary
· The purpose and goals of project
· Significance and relationship to goals and objectives
· Plan of work for grant period
System requirements (h/w)
· Minimum Hardware requirements
Specification(s/w)
· Minimum Software requirements
Analysis
· The goal of systems analysis is to determine where the problem is in an attempt to fix the system.
· This step involves breaking down the system in different pieces and drawing diagrams to analyze the situation, analyzing project goals, breaking need to be created and attempting to engage users so that definite requirements can be defined.
· The analysis phase of the project life cycle produces the detailed requirements and system architecture specifications for a project. Most importantly, it establishes what the end user wants the system to do.
During this phase, models of the application are developed.
· The development team uses these models to ensure that it understands the system requirements during the design phase and that the project meets the client's expectations.
· In order to produce the detailed requirements of the analysis phase, the analyst must be familiar with the components listed below.
· The inputs and tools are used to create the key activities which are then used to produce the outputs to meet the milestone for this phase.
The inputs required for this phase are the conceptual design
· , current system description, information plan, and project plan.
The tools needed for this phase are word processing software, presentation software, spreadsheets, and process and event modeling software.
· The key activities for this phase are the end user requirements, quality requirements, and requirements analysis.
· The outputs of this phase are the business process prototype and the requirements analysis.
· The only milestone for this phase is the requirements' sign-off.
· During the analysis phase, the analyst must establish what the system will do so that the designer—during the design phase—can create a plan that meets the client's expectations.
· To do this, analysts conduct the following three key activities.
· The first two key activities are documents you must prepare before you can conduct the third activity.
· The information you will need to create these documents is found in the documents from the inputs to the analysis phase.
1. Identify the end user requirements.
2. Identify the quality requirements.
3. Conduct the requirements analysis.
Project Risk
· The initial Risk Assessment attempts to identify, characterize, prioritize and document an improved approach relative to those risks which can be identified prior to the start of the project.
· The Risk Assessment will be continuously monitored and updated throughout the life of the project, with monthly assessments included in the status report.
Feasibility
· In this phase, the development team visits the customer and studies their system.
· They investigate the need for possible software automation in the given system.
· By the end of the feasibility study, the team furnishes a document that holds the different specific recommendations for the candidate system.
· It also includes the personnel assignments, costs, project schedule, target dates etc....
· The requirement gathering process is intensified and focussed specially on software.
· To understand the nature of the program(s) to be built, the system engineer or "Analyst" must understand the information domain for the software, as well as required function, behavior, performance and interfacing.
· The essential purpose of this phase is to find the need and to define the problem that needs to be solved.
· The feasibility study is sometimes used to present the project to upper management in an attempt to gain funding.
· Projects are typically evaluated in three areas of feasibility: economical, operational, and technical.
User Requirements
· Requirements of the User they want to implement in the Project with features and future enhancement.
Platform Specification
· MySQL, PHP, Asp.Net, C#, Ajax, Photoshop, Flash, CSS, OS
