ACM Home Page
Please provide us with feedback. Feedback
Industrial software engineering: developing software systems
Full text PdfPdf (228 KB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 31 ,  Issue 2  (March 2006) table of contents
COLUMN: Software engineering education table of contents
Pages: 3 - 5  
Year of Publication: 2006
ISSN:0163-5948
Author
Jeremy T. Lanman  Lockheed Martin Corporation, Simulation
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 6,   Downloads (12 Months): 55,   Citation Count: 0
Additional Information:

abstract   references   index terms  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1118537.1118547
What is a DOI?

ABSTRACT

Software Engineering is an incredibly complex interdisciplinary subject that requires intense problem solving and communication skills. It is an art and a science which requires an open mind and adaptation to various domains. . . in essence, a software engineer must think outside of the box! I started my path in software engineering with the undergraduate computer science program at Butler University. There I learned the common fundamentals of computer science through studying algorithms and data structures, theory of computing, databases, and of course discrete mathematics. In addition to a traditional computer science program, a software engineering curriculum was introduced. Although, nearing graduation, I decided to take a couple of these software classes, and afterwards it was clear to me that my passion was to develop software systems. I decided to learn more and enrolled into a graduate program in software engineering at Embry-Riddle Aeronautical University. At ERAU, I had specific courses in each area of the software engineering development lifecycle, and collaborative corporate internships to apply my knowledge. My most profound internship was with the aerospace defense contractor, Lockheed Martin Corporation. It was there where I truly learned how to be an "Industrial Software Engineer".


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Moore, James W, et. al. SWEBOK: Guide to the Software Engineering Body of Knowledge IEEE-CS Los Alamitos CA 2004. Accessed January 16, 2006. Online: http://www.swebok.org/ironman/pdf/SWEBOK_Guide_2004.pdf
 
2
C4ISR - Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance protocol.