2. • Problem Statement
• Abstract and Scope
• Literature Survey
• Suggestions from Review – 3
• Design Approach
• Design Constraints, Assumptions & Dependencies
• Proposed Methodology / Approach
• Architecture
• Design Description
• Technologies Used
• Project Progress
• References
Agenda
3. Well defined problem statement
• It should clearly specify the problem
Problem Statement
4. Provide a basic introduction of the project and also
an overview of scope it entails.
Abstract and Scope
5. A critical assessment of the research that has been
conducted on the topic.
4 – 5 recently published research papers/products.
Summarize the individual papers/products with as
much detail as each deserves, depending up on its
relative importance in the overall literature on the
topic.
Literature Survey
6. Provide the suggestions and remarks given by the
panel members.
Mention the feasibility on the same showing the
progress.
Suggestions from Review - 3
7. Design Approach
What is the design approach followed? And Why?
Benefits of this approach & are there any drawbacks?
Alternate design approaches, if any.
Note: Applicable to prototype/product based project
8. Design Constraints, Assumptions & Dependencies
Discuss the design constraints and assumptions that you have
made to select the design approach.
Discuss any dependencies that your design approach has and
their impact on the project.
Note: Applicable to prototype/product based project
9. Design Details
Briefly describe all the platforms, systems, and processes that it
depends on and comprise any vital changes that need to be made to
them.
Below are some examples but it is not an exhaustive list:
Novelty, Innovativeness, Interoperability, Performance, Security,
Reliability, Maintainability, Portability, Legacy to Modernization,
Reusability, Application Compatibility.
Note: Applicable to Research project
10. Proposed Methodology / Approach
Add as many slides as required to cover the
following aspects:
1. Basic Approach and results obtained
2. Is there a need for changing the approach?
3. Details of the new approach-
benefits/drawbacks
11. Architecture (if applicable)
Provide high-level design view of the system.
Identify the logical user groups, application components,
data components, and interfacing systems. Illustrate the
collaboration and interaction between the major
components.
12. Design Description (if applicable)
Add as many slides as required to cover the following aspects:
1. Master class diagram
2. ER Diagram
3. User Interface Diagrams/ Use Case Diagrams
4. Report Layouts
5. External Interfaces
16. Any other information
Provide any other information you wish to add on.
Note: Changes can be made in the template, with the
consent of the guide for inclusion of any other information.