A presentation summarizing a project undertaken at Texas Instruments to optimize the RAMP review system. The project involved logging user access to RAMP tabs and runmodes, benchmarking loading times, and scheduling cleanup of old log data. Implementation improved performance and provided insights into how RAMP is used. Unit testing validated the changes worked as intended before deployment.

1. Presented by
Madhusmita Roy
MCA 6th semester
Jorhat engineering college
Project undertaken by Texas instruments
Industry guide
Anushi Kotoky
Application Developer ,
ITS ,DSApps
Texas Instruments India

2. Contents
Project details
Challenges & Risks
Conclusion
Milestones
Key takeaways
5
4
3
2
1

3. Project Details
Domain overview Business value Tools & technologies Graphical design Screenshots
Contents

4. Texas Instruments
Texas Instruments is a semiconductor company
which is ranked 3rd in worldwide.
The ITS India is mainly providing IT support to the
TI analog and Embedded processing team for their
operation.
DSIT takes care of all the design related IT support
to TI business team.
DSApps helps in designing and maintaining
application needed by TI designers .
Texas Instruments
ITS
DSIT
DSApps
DSApps
DSIT
ITS
TI

5. Provides as a review system.
Stakeholders are design engineers and reviewers.
Ensures that chip has passed through every testing phase before going to fabrication unit.
Ramp review

6. Reviewers
Design engineers

7. RAMP
Fill up
questionaries'
Reviewed
by
pass
If scores high ?
Approved to fab
Reject
yes
No

8. RAMP Production Server
RAMP Test Server
Development
Server
Local Branch
Local Branch
Local Branch
Dallas Bangalore
LAMP Architecture

9. A design review management system that enforces design rule
checks for designs in production.
Business Values

11. User logged in
TABS SUBTAB
S
Drawbacks
Knowing of major tab usage
Page loading performance
Survey of application for change
request……………..

12. Logging of RAMP tab usage and benchmarkling

13. High level Analysis is a request that comes from the stack holders for a
change in the existing system.
 Stakeholder identification
 Stakeholder interviews
 Use Cases

14. Logging of user access to
RAMP’s runmodes.
Auto insertion of newly accessed
runmode information to the
system.
Error handling while
implementation.
Purging of old logging
information from the system
using cron script.
Benchmarking runmode loading
time.
Pre and post implementation
benchmarking.

16. Version control system

17. Bazaar is a version control system used for revision control. Bazaar is a
distributed version control system.
Repository 2
Repository 0
Repository 1 Repository 3

18. create trunk-mirror to get a back up.
configure to access browser through own branch.
create symbolic links to own branch.
pull the actual data into local branch.
create local branch.
Create folder in the centralized location.
Raise support ticket for group permission.

19. Table structure

20. runmodes
200 runmodes

21. cgiapp_prerun
cgiapp_postrun
Called before runmode gets loaded
Called after runmode gets loaded.
Loads http header data and send to browser
Track load request time
here
Track load
completion time
here
Calls subroutine to
track user access
1
2
3
Steps
Steps Involved

22. Included perl inbuild Packakge for benchmarking functionality in miliseconds
Insert all user access records along with benchmarking into table
Catches error If runmode is new->insert into db
Else notifies developer through
email message
Throws error if any
Catches error

23. CRONTAB
Linux Cron utility is an effective way to schedule a routine
background job at a specific time and/or day on an on-going
basis.

24. Linux Crontab Format
MIN HOUR DOM MON DOW CMD
Field Description Allowed Value
MIN Minute field 0 to 59
HOUR Hour field 0 to 23
DOM Day of Month 1-31
MON Month field 1-12
DOW Day Of Week 0-6
CMD Command Any command to be executed.

25. Delete those records which are more than 1
year.
Business Value
Removal of unnecessary old
information from the system
Increase searching efficiency
Lessen the overhead for manual
deletion periodically
Cron gets executed every month from a
centralized location.

26.  Implementing the subroutine into core modules help to catch over 200 runmodes.
 No affect to browser or application on error.
 Error handling.
 Benchmarking runmode loading helps to check performance of the application.
 Common implementation to all 21 .pm files.
 Less DB hits.
 Auto insert newly accessed runmodes.
 Saves time benchmarking every page manually.

27. Benchmarking the implemented functionality
Benchmarking 70 subtabs
Pre implementation:
Local branch 2
Post implementation:Local branch 1

28. 0
100000
200000
300000
400000
Total Average loading time(ms)
Total Average loading
time(ms)
Pre implementation
DIFFERENCE
Post implementation

29. Unit testing is done on the core implementation to check whether there is
exactness in expected result and output or not.

30. Modified file No of block changes File location status
• Merge the code to the original.
• Push the codes to trial server.
• Tested the functionality.
• If found ok, released to production with new version

31. The general release cycle of any company’s development team are as follows:
 Pushing the final code into development servers
 Creating code in self branch or code copy
 Pushing the code changes to the test or the staging servers
Version controlling
system
Code Copying

32. The analysis will help
to focus on
understanding uses
of ramp.
The developer will
get to know which
portion of ramp is
being used the
most by the
customer.
The developer of ramp can
check which subtab is taking
longer time and raise for
future enhancement
requests.
This gives a survey of
application usage.
To prioritize
service requests
for the
application.
Check benchmarking
standard after
migrating to oracle

33. Version control system :
Bazaar
Perl cgi, perl scripts,perl template tool kit
DBMS : Mysql Platform : Linux
Web server : Apache Putty
Microsoft Excel 2010

35. 0
Ramp
Optimization
Admin User
Login info Login info
Run mode data
Database
Logininfo
Runmodedata
User access data
Useraccessdata
Context Level

36. Login
View run
mode data
Admin
Username
Password
Username
Password
* *
Run mode data Log run mode
Login
1.1
1.2

37. LoginUser
Username
Password
*
Username
Password
*
User activity
Log run mode
1.3
1.4
run mode
User_id
1st Level DFD for user

38.  pgrep :Implementation of grep command in unix.
 Pfind : Im plementation of find command in unix.
 Json banking system : Menu based banking system.

39. Pfind.pl Account.pl
Pgrep.pl

40. How was my journey since I joined TI and what I achieve

41. JAN FEB MAR APR MAY
 Training on unix
and perl
 Domain overview
 Work on perl
utilities
 Completed perl
utilities
 Training on
bazaar and cm
tools
 Created local
branch
 Work on Ramp
 Ramp utilities
completed
 Presented to
ITLT
Perl + RAMP Utilities
HLA 004 Development
 HLA
requirements
 Coding

42. Challenges & Risks

43. Technical
 Code optimization
 Understanding tools
 Perstyle coding
 Presentation skills
 Domain
knowledge
Non Technical

44. Understand how the project fits to Team’s
objective
Planning a task is more crucial than doing the same
without planning.
Importance of Soft skills & time management
Smart work vs Hard work.
College vs corporate etiquettes
Communication exactness.