 Feasibility Analysis • Feasibility study determines whether it is worth to carry out the intended work. A SWOT analysis can be done for the project. This stage includes identification of business value of the product, evaluation of technical resources /technology needed to solve existing problem, a cost benefit analysis is done in which the estimated cost is compared with the benefits of the work and an operational feasibility is conducted to discover the particular product is operational in the client environment. Under feasibility study an assessment of ethical factors are also considered.  Rational for choosing the methodology Report narrates a development methodology as a suitable approach to solve the problem. The methodology is compared with different alternatives and a clear rational is given for the suitability of the selected methodology. 2.1 Rationale of the Project Students are supposed to classify general problem and Specific problems from the present system and newly going to develop the system. A student has to provide a lot of ideas about why he or she is doing the project. 2.2 Proposed System Describe the description of the proposed system. More details about how the system improves objectives. Time and Resource cost including funding requirement for all activities of the project. Describe new equipment requirements and currently available equipment, if any. Recognize any additions or modifications to existing applications and support software in order to integrate them with the proposed system. A project methodology tells you what you have to do, to manage your projects from start to finish. It describes every step in the project life cycle in depth, so you know exactly which tasks to complete, when and how. Whether you're an expert or a novice, it helps you complete tasks faster than before. Methodology 3.1 Methodology Provide a comparative study of different methodologies and select a best methodology to develop the product. The reason for choosing the particular methodology must be justified properly. 3.2 Project plan Project plan section must include various planning documents which support in overall guidance of the project. Develop a Gantt chart which includes activities/tasks, timing, dependencies. Students are expected to develop communication plan, acceptance plan, and resource plan and risk management plan. [Gantt chart, communication plan, acceptance plan, resource plan, risk management plan] 3.3 Requirement Analysis Provide details of how data was collected and apply various techniques for data analysis. A clear requirement specification must be given which includes technical requirements, functional and nonfunctional requirements of the intended product. [Data collection methods, Data analysis, External interface requirements, Functional requirements, user characteristics, Performance requirements, Design constraints, Database requirements, Security requirements, Maintainability requirements, Usability requirements] 3.4 Initial design Create preliminary design diagrams for logic design, data design, process design, and interface design which match with product requirements. [Algorithms, DFDs, UML diagrams, screen prototype, ER diagrams, System flowcharts, Decision tables/Decision trees] Example: SDLC (Development life cycle), RAD (Rapid application development), Waterfall methodology. 4.0 Risk Management 4.1 Identified Risks Internal risks External risks Interviews and brainstorming sessions As project members, you can perform structured interviews and brainstorming sessions with experts to help gather information about project risks. 4.2 Strategy to overcome Risks After you have identified and documented the potential risks in your project, you need to consolidate and categorize them. By managing risks, you eliminate duplication and mediate the different views that are expressed. You then submit the results to the project team to obtain their concurrence for the data that was gathered. The feedback from the project team can then be used as input in the next phases of risk management process. The focus of the process can then shift to Risk Analysis, Risk Response Planning, and Risk Monitoring and Control.  Project requirement specification The requirements associated with the project are specified and clearly Eleven properly functional and Four nonfunctional requirements  Project plan & Project management Exhibits a professional level of planning and time management and complete Gantt chart and Work Breakdown structure  Detailed analysis The report contains a professional and complete analysis that the work will guide during the rest of the. Project The report contains ER case -diagram, Use diagram and description of each case. A complete -use class diagram is given in the report.  Initial design The idea of the project is clearly explored and elaborated contains a report correct relational schema. Sequence diagram for all usee-cases are given correctly  • ERD Diagrams. • Class diagram. • Sequence Diagrams. • Use case Diagrams and description of use case diagrams • Normalization  Software for Developments: 1. C#. 2. SQL Server. 3. StarUML 4. MS PROJECT