Mini Project Guideline
Mini Project Guideline
Mini Project Guideline
1. Title, Team Members Name & Reg.No., Signature of Team Members with Name,
Faculty In charge Sign with Name. (Cover Page)
2. Index (Sl.No, Title, Page.no)
3. Problem Definition (Aim of the Project)
4. Prepare Requirements Definition document (Customer requirement in Natural Language)
5. Vision Document with Stakeholders of the system, Use case Document, Glossary,
System Features & Supplementary features (Rational Requisite Pro)
6. Project Schedule (Gantt Chart) of RUP
7. Perform Requirement analysis, Risk Analysis (List of Sw, Hw, DB, Any tools/Sub
systems and list of risks)
8. Show a suitable development model (Process model) for your system. Mention why this
module is more suitable.
9. Construct the attribute matrices and traceability tables for the set of requirements.
(Requisite Pro)
10. All UML diagrams (Rational Rose)
11. Draw relevant ERD, DFD and CFD.
12. Generate the code for all these diagrams using forward engineering/Reverse Engineering.
13. Divide the system into modules. (Horizontal/Vertical Partitioning)
14. Mention your data acquisition. (Data Base/Repository of data/Data Dictionary- For
example data set can be obtained from Bench mark data from internet or from
meteorological department, etc.)
15. Give the user interface characteristics. (Type of users has to be mentioned and
categorized. It should not be generic).
16. Prepare System components (Exe files) and mention the design
category.(Conventional/Traditional/OOD)
17. Display various output screen shots of your application.
18. Identify the set of modules covered for each category of users using the concept of Pure
coverage.
19. Identify the set of modules leads memory leaks using Test Purify.
20. Generate different test plans for your application. For each test plan, identify the test
cases.
21. Test them using Rational Test Manager. (Manual/GUI)
22. Generate a pool of at least twenty sets of data for each screen. Feed this data to the
application.
23. Prepare a list of constraints to be satisfies in each field of the application. (Rational
Robot)
24. Test whether the set of constraints match using alphanumeric verification
points.(Rational Robot)
25. Distinguish Enhancement of the software product than existing one. (Any one of
Statistical Comparison/Graph/Table)
26. Mention the boundary conditions to be considered in your software. (Limitations)
27. Give suitable conclusions.
28. Narrate extension of your product (Future work).
29. References (Books, Websites, Magazine, periodicals, journals)
30. Acknowledgement
31. Paper Presentation/Publications/Copy Rights (if any)