Welcome to UC San Diego, Administrative Computing and Telecommunications developer guide. This site should provide you with all the information needed to understand and navigate systems, and build applications that will conform to the recommended architecture and guidelines.
Creating accounts and business systems
You will be expected to record hours worked each week in FootPrints for each task/project worked on. Please record hours and a brief note under the “Time Spent” tab for the appropriate task.https://actfp.ucsd.edu/
Used for managing communications within ACT, committees and projects that don’t conform to TeamForge.https://teamwork.ucsd.edu/act/SitePages/Home.aspx
User Experience & Technology
User Interface coding standards & examples
Most Wednesday’s there’s a Developers lunch time workshop from 12-1pm in conference room 255
Within ACT, we use Microsoft LYNC.
Monthly Time reporting
The general server architecture for web application development is Red Hat Enterprise Linux (RHEL), with Apache/Tomcat. There are separate environments for development (DEV), quality assurance and testing (QA), production staging (STAGE) and production (PROD). Each organizational team has their own instance of Tomcat (i.e. Financial, Student, Academic, …)
- Send to your Manager/Director for approval.
- Send to Director of ITAG for approval.
- Attach to ticket in FootPrints for UNAS team for confirmation and scheduling.
The basic software development architecture for applications is based upon standard Spring MVC and the J2EE stack. Legacy applications can include deprecated technologies such as Perl, Jlink, Macromedia Flex.
The database environment is IBM DB2.
The Mainframe is the heart of all business and data operations at UCSD. This environment supports all Financial (IFIS) and Student (ISIS) activity, transactions and data. Data from the mainframe is copied nightly (12am - 6am) to the data warehouse (dw_db).
Legacy Perl based applications use a custom framework/library built around ‘sptwad-services’, and can use either Java web services for data or DBI connections to DB2.
The overall architecture is guided by:
The Architect is responsible for creating, maintaining and advancing the IT architecture strategy that supports campus enterprise applications and information systems and aligns with campus and department business priorities.
Architecture Committee: [TeamForge site]
The ACT Architecture Committee is the primary ACT forum for developing a shared vision of how information technologies can best support UC San Diego Administrative Systems and Services. The ACT Architecture Committee carries out this charge through research, consultation, advice, and communication. The Architecture Committee reports to the ACT-AVC. The Architecture Committee consults with campus constituencies, including the technology experts in departmental units and outside technology experts.
This workgroup is comprised of technical leads from each software development area and is responsible for:
- Serve as new technology vetting committee
- Discuss best practices, documentation, how to use, how it fits into ACT’s blueprint
- Details and charter posted in SFEE
Server Environment (link to UNAS)
ACT Architecture Diagram.pdf
Database Environment (link to DBA/UNAS)