Proposal to drop the word “ Systems ” from the name of “Software Systems Technical Committee”

1. Proposal to drop the word “Systems” from the name of “Software Systems Technical Committee” Rao Mannepalli June 6, 2010

2. Proposed Change • Current Name: Software Systems TC • Proposed Name: Software TC • Summary of change: Drop the word “Systems” from the TC name

3. Rationale • SOFTC suffers from identity crisis. • As of now, it does not operate as an independent entity. It always runs in unison with Computer Systems TC (Tele-cons, face to face meeting etc.) • It fails to make its mark felt.

4. Rationale • Its work products are minimal (both in terms of quantity and significance). For example I am also a member of AIAA’s Emerging Technologies Standing Committee (ETC). It has 3 sub committees (Space, Aero and Multidisciplinary). Each sub committee watches several emerging technologies and comes up with a top-10 list. The top entries from these lists are generally selected for additional exploration/funding by DOD, DARPA, NASA, AFRL etc. I have not seen an entry from “Software” area. I want our TC to work with ETC to watch, select and highlight Emerging Software (not software systems) related technologies

5. Rationale (contd.) 5. As of now SOFTC does not have a niche. • As mentioned in my TC Chair Vision Statement it is more software development process oriented “Move SSTC from the Software Engineering process centric (which is mostly sterile) approach to Actual Software Systems centric (Mostly creative (some thing Similar to IEEE Software)) focus” -- from my TC chair Vision Statement • It is not appealing to wider spectrum of people involved in the Software • R&D • Architecture • Education • Programming Languages • Algorithms • Security etc.

6. Rationale (contd.) • It is neither attractive nor useful to others involved in Software (Google, Microsoft, InfoSys, Wipro etc) • It is not on equal footing with others (like IEEE, ACM) • Cannot attract new and enthusiastic members • Suffers from chronic, low and stagnant membership • Does not attract young “Associate Members” who like graduate students are the source of unlimited energy and enthusiasm

7. Rationale (contd.) • Depends mostly on the monthly Tele-cons (very poorly attended) and face to face meetings to get most of the work done • Does not have dedicated sub-committees recommended by AIAA

8. Advantages • Helps me (new TC chair from May 2010) to get my vision for TC implemented (pl. see the backup slides) • Enlarges the scope of the TC and makes it more appealing to wider class of members • Will help me to make SOFTC one of the best TCs in AIAA TAC

9. Is the request uncommon? • Not having “Systems” in the name is not uncommon in AIAA TAC. For example: • Digital Avionics TC Information Systems Group • Aeronautics TC Aerospace Sciences Group • Materials TC Aerospace Design & Structures Group • Liquid Propulsion TC Energy & Propulsion

10. What exactly is a “Software System”? • We really don’t know what “software systems” mean • For example. AT&T’s 5ESS system has 100 Million lines of C code and another 100 Million lines of header and build files. • Navy’s Aegis combat system has comparable code size. • I am familiar with both these systems. • None of them are classified under “Software systems” • None of them call themselves “Software Systems”

11. BACKUP SLIDS

12. Software Systems Technical Committee Chair Vision Statement Rao Mannepalli Dec . 2009

13. My Vision for SSTC • Make SSTC as active as Solid Rockets TC which is one of the biggest and most active TCs. People wait in line for joining that. • Separate SSTC from CSTC. • Have full 30 – 35 members and another 30-35 non-voting members • Encourage and recruit members from other aerospace faring nations outside USA (India, China, Brazil, Russia, Korea, Israel, France and Germany etc.). I want to use my contacts in those countries to get members

14. My Vision for SSTC (contd.) • Move SSTC from the Software Engineering process centric (which is mostly sterile) approach to Actual Software Systems centric (Mostly creative (some thing Similar to IEEE Software)) focus. • Use the modern multi-media communications in-lieu of face-to-face meetings (which are the first on the chopping block in these days of tight travel/training budgets) • Make it possible for people to call in and/or e-mail. • Form sub-committees (again like Solid Rockets Subcommittee) • Make the work of the subcommittees equal in quality to that of Congressional fellows of AIAA

15. My Vision for SSTC (contd.) • Collaborate and cooperate more with IEEE (I have become an Editor of  IEEE Aerospace and Electronics Systems (AESS) magazine) and ACM. In fact AIAA and IEEE-AESS are co-sponsors of a joint conference. • Make it appealing and interesting  for Academics and Industrial Researchers (Google, CISCO, Microsoft, ISRO, HAL, NAL, InfoSys, Wipro etc.) • Bring an international character. • Arrange lectures by Distinguished people. Coordinate with the efforts like Lockheed Martin-IEEE webinar Series for Software and Systems Initiative.  I want to work with other such efforts from Boeing, Raytheon, GD, ING, Google etc.

16. My Vision for SSTC (contd.) • Start an “Angels Program” similar to the one existed in Bell Labs where deserving members will be encouraged and helped to advance their memberships in AIAA and other sister professional Societies, and also win Awards. • Start an effective Mentoring/Networking program. • Make SSTC a catalyst for collaborative Research efforts (e.g. smart Grid, Cyber Security etc.)