Project Summary
To Help an Analyst plan his activities better and try to match A Designer's or an Architects Requirements so that the Model Can Be Finalised in the least possible Time.
Key Words
Data Modeler, Requirement Analysis, Entity Relationship Diagram, Enterprise Resource Planning, Low Code, Code Automator, SDLC, Software Development Life Cycle
Introduction
Data Modeling Happens to be an Important Step in the Initial Stage of Software Life Cycle Development. An attempt here is Being made to define the different Attributes that need to be assigned to the analysed Column Names and there by make sure that This Data is used Directly by the Descision Makers who finalise the Entity Relationship Diagram.
Origin Of Proposal
These days an kind of a minimum accepted requirements of Application Software Demands that it should be Online that is it must be Web Based. Often we find delays in Interpreting Client Requirements Understood by Analysts and Deigned by Architects to give a Solution.
Problem Definition
To reduce the Time Estimates and Resources in Software Development Life Cycle Irrespective of Platform Choosen to Finalise the Entity Relationship Diagram.
Work plan
A simple Language has been evolved and developed that will is in line with the RDBMS principles to allow people working at different levels in the Organisation to use the Attributes Analysed irresective of the Business Functionality. At present we will be Using this Application with MSSQL Server as a Back End. A Simple but very Powerful Application is Developed that needs to be Enhanced that Can Generate your Tables Directly on a Database once an Anlyst Defines the Requirements Understood.
Project Information
Review and Status of Research and Development in the Subject
Project Features / Product Catalog
Get Constraints of Data Analysed
- Define Your Data Constraint If Any. Here you end up just Defining weather it is a Repetitve Data Member or a Non Repetitive Data Member.
Just Define Data Type
- An Analyst Just Needs to Pick Up a Data Type Without much Hasseles of Analysing their Lengths And Other Parameters.
Name You Data
- Give a meaningful Name to your Data Analysed.
Generate
- Once you are done with Defining Data Analysed you can go Ahead and Generate the Table Necessary which will be shared Directly to the Concerned Members in the Organisation.
Near Future Mandatory Necessary Enhancements Planned
1. Connectivity to a preferred DB Server with a way to understand the Language Developed to the underlying Objects in the pre defined Server.
2. A Diagramming Support with preferred pointers to the Underlying Analysed Columns.
3. A report that can give an Idea to the Middle Management about the actual Field Requirements that have been brought by the Analysts that need to be looked into.
4. A near ready to Offer Solution to the Architects working in different fields of knowledge to come to a conclusion of what needs to be done in a given situation in the shortest period of time. This needs to be thought over keeping in mind the Horizontal and Vertical Levels in the Organisation and also the present state of Development of the underlying Application.
Sample Entity Relationship Diagram
Sample Entity Relationship Diagram
Time Schedule of Work Plan
| Sl No | Broad Work Element | Time Estimates In Months |
| 1 | A way to get to define the different Attributes that need to be assigned to the analysed Column Names | 2 |
| 2 | A simple Language has Been evolved and developed which needs some Fine Tuning that will be in line with the RDBMS principles to allow people working at different levels in the Organisation to use the Attributes Analysed irresective of the Business Functionality | 3 |
| 3 | Ask people in the Organisation to use a standard Naming Convention for Analysed Attributes so that the modeler can point out what are the eliminations necessary or what are the Normalisation Rules that have to be applied. | 2 |
| 4 | A simple Diagramming support must be given to lay them in a Layout that can be printed on a normal printer. | 3 |
| 5 | Processed information can then be connected on to a proper Diagramming support by an Architect to decide what is to be done to take a final call. | 2 |
Minimum Group Organisation
| Sl No | Group Code | Position Description | No Of Posts |
| 1 | 1 | Testing Administrator | 1 |
| 2 | 2 | Assistant DB Architect | 4 |
| 3 | 3 | Internal User Interface Administrator | 1 |
| 4 | 4 | Data Mapper Administrator | 2 |
| 5 | 5 | Process Experts | 2 |
| 6 | 6 | Programmers | 10 |
| 7 | 7 | Accountants | 1 |
| 8 | 8 | Process Designers | 2 |
| 9 | 9 | Internal Marketing Administrator | 1 |
| 10 | 10 | Internal Project Manager | 1 |
Suggested plan of action for utilization of Research Outcome Expected from the project
We are planning to Tie Up with Ramakrishna Mission Vivekananda Educational and Research Institute http://rkmvu.ac.in/ so that they can maintain the Entire Design, Source Code and Related Documentation necessary for it to Survive and Grow or Tie up with Microsoft Corporation / Microsoft Foundation so that A Team can be formed to Ensure that these Services and Upgrades are available to All Organisations in India freely to Develop and Enhance but not to Voilate the Set Statuatory and Predefined Standards.
Budget Estimates: Summary
| Item | BUDGET | (in Rupees) | |||
| 1st Year | 2nd Year | 3rd Year | Total | ||
| A. | Recurring | ||||
| Salary Expenses | 67500000 | 74250000 | 81675000 | 223425000 | |
| Printing and Stationery | 300000 | 330000 | 363000 | 993000 | |
| Travelling Expenses | 2400000 | 2640000 | 2904000 | 7944000 | |
| Others | 2400000 | 2640000 | 2904000 | 7944000 | |
| B. | Equipment To be Built If Applicable | 0 | 0 | 0 | 0 |
| Grand Total (A+B) | 72600000 | 79860000 | 87846000 | 240306000 |
Budget for Salaries/Wages
| Position Description | No Of Posts | Monthly Emoluments | BUDGET | (in Rupees) | ||
| 1st Year | 2nd Year | 3rd Year | Total | |||
| Testing Administrator | 1 | 250000 | 3000000 | 3300000 | 3630000 | 9930000 |
| Assistant DB Architect | 4 | 250000 | 12000000 | 13200000 | 14520000 | 39720000 |
| Internal User Interface Administrator | 1 | 250000 | 3000000 | 3300000 | 3630000 | 9930000 |
| Data Mapper Administrator | 2 | 250000 | 6000000 | 6600000 | 7260000 | 19860000 |
| Process Experts | 2 | 250000 | 6000000 | 6600000 | 7260000 | 19860000 |
| Programmers | 10 | 200000 | 24000000 | 26400000 | 29040000 | 79440000 |
| Accountants | 1 | 125000 | 1500000 | 1650000 | 1815000 | 4965000 |
| Process Designers | 2 | 250000 | 6000000 | 6600000 | 7260000 | 19860000 |
| Internal Marketing Administrator | 1 | 250000 | 3000000 | 3300000 | 3630000 | 9930000 |
| Internal Project Manager | 1 | 250000 | 3000000 | 3300000 | 3630000 | 9930000 |
| Totals | 67500000 | 74250000 | 81675000 | 223425000 |
Budget for Consumable Materials
| Item | BUDGET | (in Rupees) | ||
| 1st Year | 2nd Year | 3rd Year | Total | |
| Printing and Stationery | 300000 | 330000 | 363000 | 993000 |
Budget for Travelling Expences
| Item | BUDGET | (in Rupees) | ||
| 1st Year | 2nd Year | 3rd Year | Total | |
| Travelling Expenses | 2400000 | 2640000 | 3630000 | 8670000 |
Budget for Other Expenditures
| Item | BUDGET | (in Rupees) | ||
| 1st Year | 2nd Year | 3rd Year | Total | |
| Others | 2400000 | 2640000 | 2904000 | 7944000 |
Budget for Equipment If Applicable
| Item | BUDGET | (in Rupees) | ||
| 1st Year | 2nd Year | 3rd Year | Total | |
| Equipment To be Built If Applicable | 0 | 0 | 0 | 0 |
Infrastructural Facilities
| SrNo | Infrastructural Facility | Status |
| 1 | Workshop Facility | Yes – Sharing basis |
| 2 | Water & Electricity | Yes - Sharing basis |
| 3 | Laboratory Space/ Furniture | Yes - Sharing basis |
| 4 | Power Generator | No |
| 5 | AC Room or AC | No |
| 6 | Air Cooler If Tempratures are too High | Yes |
| 7 | Telecommunication including e-mail & fax | Yes |
| 8 | Transportation | Yes |
| 9 | Administrative/ Secretarial support | Yes – Sharing Basis |
| 10 | Information facilities like Internet/ Library | Yes – Sharing Basis |
| 11 | Computational facilities | Yes – Sharing Basis |
| 12 | Animal/ Glass House | No |
| 13 | Any other special facility being provided | Not Required |
Equipment available with the Institute/ Group/ Department/ Other Institutes for the project
| Sl No | Equipment Available | Generic Name Of Equipment | Qty Available | Model Make And Year Of Purchase | Remarks Including Accessories Available And Current Usage Of Equipment |
| 1 | With Group | Laptops | 1 | 2016-2016 | 60% capacity utilisation |
| 2 | With Group | Laptops | 1 | 2016-2016 | 60% capacity utilisation |
| 3 | With Group | Laptops | 1 | 2016-2016 | 60% capacity utilisation |
