2006-1055: SOFTWARE DEVELOPMENT LABORATORY: A RETROSPECTIVEDeepti Suri, Milwaukee School of Engineering Deepti Suri is an Associate Professor in the Electrical Engineering and Computer Science Department at Milwaukee School of Engineering (MSOE). She primarily teaches courses in the Software Engineering program.Mark Sebern, Milwaukee School of Engineering Mark Sebern is a Professor in the Electrical Engineering and Computer Science Department at Milwaukee School of Engineering(MSOE) and is the Program Director for MSOE’s undergraduate Software Engineering (SE) program. Page 11.1136.1© American
AC 2008-1705: ENHANCING THE SOFTWARE VERIFICATION ANDVALIDATION COURSE THROUGH LABORATORY SESSIONSSushil Acharya, Robert Morris University Sushil Acharya, D.Eng. Assistant Professor of Software Engineering Acharya joined RMU in Spring 2005 after serving 15 years in the Software Industry. With US Airways Acharya was responsible for creating a Data Warehouse and using advance Data Mining Tools for performance improvement. With i2 Technologies he led the work on i2’s Data Mining product “Knowledge Discover Framework” and at CEERD (Thailand) he was the product manager of three energy software products (MEDEE-S/ENV, EFOM/ENV and DBA-VOID) which are currently in use in 26 Asian and 7
science and engineering. Page 24.56.1 c American Society for Engineering Education, 2014 A Hybrid Design Methodology for an Introductory Software Engineering Course with Integrated Mobile Application DevelopmentIntroductionThis paper discusses an experimental version of a core undergraduate software engineeringcourse at the University of Cincinnati (UC). EECE 3093C – Software Engineering is a 4-credithour undergraduate course with an integrated laboratory component. It is a required course forall computer science and computer engineering students
easy to gather. Proceedings of the 2007 American Society for Engineering Education Annual Conference & Exposition Copyright © 2007, American Society for Engineering EducationThis paper focuses on the design and application of two data management tools that supportsoftware project planning and tracking, based on defined measurement frameworks. One of thesetools, named LEIA (Laboratory Engineering Information Archive) was developed byundergraduate software engineering students at the Milwaukee School of Engineering (MSOE),and is used to manage team projects in MSOE’s Software Development Laboratory. The secondsuch tool is the open-source Process Dashboard (processdash.sourceforge.net) developed byDavid Tuma and his
, Fermi National Accelerator Lab Jerzy Nogiec is the Software Development and Support Group Leader at Fermi National Accelerator Laboratory and an adjunct professor of Computer Science at the Illinois Institute of Technology. His research interests, in addition to software engineering education, include distributed systems and data acquisition systems. Page 14.1152.1© American Society for Engineering Education, 2009 Teaching Software Development for Modern Real-Time Data Acquisition and ControlAbstractModern data acquisition and control systems, in the most demanding
Paper ID #15098Software Industry Experience for High School StudentsDr. Massood Towhidnejad, Embry-Riddle Aeronautical University, Daytona Beach Massood Towhidnejad is Director of NextGeneration ERAU Applied Research (NEAR) laboratory, and Professor of Software Engineering in the department of Electrical, Computer, Software, and Systems En- gineering at Embry-Riddle Aeronautical University. His research interest includes; Software Engineering, Software Quality Assurance and Testing, Autonomous Systems, and Air Traffic Management (NextGen). In addition to his university position, he has served as Visiting Research Associate
Paper ID #10496Creating Research Opportunities with Robotics across the UndergraduateSTEM CurriculaDr. Janusz Zalewski, Florida Gulf Coast University Janusz Zalewski, Ph.D., is a professor of computer science and software engineering at Florida Gulf Coast University. Prior to an academic appointment, he worked for various nuclear research institutions, including the Data Acquisition Group of Superconducting Super Collider and Computer Safety and Re- liability Center at Lawrence Livermore National Laboratory. He also worked on projects and consulted for a number of private companies, including Lockheed Martin, Harris, and
experience covering the full range ofsoftware process activities. The Software Enterprise shares the multi-semester approach with anemphasis on soft-skill development with the Studio. The Enterprise, however, introduces thesoftware phases in reverse order, and emphasizes soft-skills development through multi-yearstructured student collaborations. The Enterprise also introduces the sequence in theundergraduate, not graduate, program. Reverse ordering of the process phases is also introducedby the Software Development Laboratory at MSOE. Sebern acknowledges the difficulty newerstudents have grasping process and soft-skills concepts, and therefore students are led from“grave to cradle” through process phases. Unfortunately a further description of the
different institutions and their different approaches toteaching software verification, it is important to understand the differences in the institutions’profiles’ and activities. This section provides background information on the two programs’profiles in this article.Milwaukee School of Engineering (MSOE)The Milwaukee School of Engineering offers an accredited Bachelors of Science degree insoftware engineering, and has been accredited since 2002. As an institution, there is a strongemphasis on small class sizes (14:1 student to faculty ratio) and extensive laboratory experience.Students graduating from MSOE spend on average 600 hours in laboratories related to theirmajor. Institutionally, there is more square footage devoted to lab space than
, component-based software architectures, software and systems engineering process models, intelligent control, the semantic web, and real-time artificial intelligence. In 1999, Dr. Hawker joined the Computer Science Department at the University of Alabama as an Assistant Professor focusing on software engineering, and in 2004 he moved to the Software Engineering Department at RIT. Dr. Hawker is also co-director of the Laboratory for Environmental Computing and Decision Making, which focuses on modeling and understanding the impact of freight transportation and automotive industry activities and public policies. Dr. Hawker is a member of the ASEE, IEEE, IEEE Computer Society, and the
technology education focuses on applied science and engineering and application of theory in real-world problems. Courses are aimed at preparing graduates for practice in a specific field of the technological spectrum. Courses are laboratory based and have a high component of practical practice and practical application. Hands-on experience is stressed in an educational environment targeted at producing “job ready’ graduates. As a degree program in Software Engineering Technology, the developed curriculum offerslaboratory based courses in hardware construction and design and software construction anddesign. Class sizes are targeted at 20 students. Laboratories are taught by the professors givinglectures. All students
UnLecture furthers theunderstanding of concepts that students learn from traditional lectures and laboratory projects. “I do remember seeing a diagram (in my co-op) that was made during one of our meetings … I believe it was a class diagram, since it showed what some classes would contain and what methods we would need to implement. I didn’t know UML then…” “It does seem like it takes a lot of time to create models for a software project but it will force you to think and know how the software will be structured and designed. This can also lead to solving many issues that may arise before any coding is actually begun.” “Another point from this Unlecture I found interesting was when one student talked about his experience as
researchare free; two are commercial standalone tools. This prevents students from viewing the vul-nerabilities as a whole problem. We think this could be useful for a course that is focused onsecurity testing but not for an introductory course on software testing.Garousi7 presents open modern software testing laboratory courseware that is similar to theone we report in this paper, but he uses several tools and SUTs. One of his findings is thattesting educators should align the choices of SUTs and tools with the ultimate goal of thecourse at hand, the type of students, and the time and resources available to the students inthe course.Other forays into improving the teaching of software testing have been reported. For in-stance, Cowling5 describes how
and at Honeywell Industrial Automation and Controls), combat pilot decision support and mission management (at Honeywell Defense Avionics Systems), robotics (at AT&T Bell Laboratories), and surveillance (at AT&T Bell Laboratories). In these areas, he developed and applied technologies including distributed, component-based software architectures, software and systems engineering process models, intelligent control, the semantic web, and real-time artificial intelligence. In 1999, Dr. Hawker joined the Computer Science Department at the University of Alabama as an Assistant Professor focusing on software engineering, and in 2004 he moved to the Software Engineering
. 8To allow for testing of systems in a closely controlled laboratory environment, vehicles basedsolely on internal combustion power sources are not practical due to emissions and requiredmechanical infrastructure. These limitations were overcome through adaptation of electricvehicle (EV) technologies. EV platforms provide real-world components that are clean, easy forsoftware students to construct, and easy to scale from “toy” size platforms to full size vehicledeployments.Electric Vehicle IntegrationElectric vehicle technologies provide a clean platform for use in development of software basedvehicle projects. With minimal cost, a simulation and/or emulation environment can beconstructed allowing full development and deployment of an
Journal 50, 5, 1079-1106.21. Richards, B. 2000. Bugs as features: Teaching network protocols through debugging. In Proceedings of the 31st SIGCSE Technical Symposium on Computer Science Education (Austin, TX, Mar 8-12 2000), 256- 259. ACM.22. Sebern, M. 2002. The software development laboratory: Incorporating industrial practice in an academic environment. In Proceedings of the 15th Conference on Software Engineering Education and Training, 2002 (Covington, KY, Feb 25-27, 2002), 118-127.23. Seiter, L. 2009. Computer science and service learning: Empowering nonprofit organizations through open source content management systems. Integrating FOSS into the Undergraduate Computing Curriculum, Free and Open Source Software (FOSS
surveillance. In these areas, he developed and applied technologies including distributed, component-based software ar- chitectures, software and systems engineering process models, intelligent control, the semantic web, and real-time artificial intelligence. In 1999, Dr. Hawker joined the Computer Science Department at the University of Alabama as an Assistant Professor focusing on software engineering, and in 2004 he moved to the Software Engineering Department at RIT. Dr. Hawker is also co-director of the Laboratory for En- vironmental Computing and Decision Making, which focuses on modeling and understanding the impact of freight transportation and automotive industry activities and public policies. Dr. Hawker also
individual topics covered in the workshops, the students also 2experienced the incremental development process of a full-featured multi-tier system. Thecomplete case study worked well as an example for the team projects.Overall StrategyLectures and guided laboratories are common practices in teaching a wide range of computerscience and engineering courses. Lectures are a necessary component in teaching a softwareengineering course to present concepts, principles, and technologies, which are necessary tounderstand the background of a development scenario. But they are not efficient indemonstrating what artifacts are to be generated under the given scenario and how to use CASEtools to generate them. The
Journal, Volume 14, No 3, 2011.12. Greco, E. and Reasoner, J. (2010) Student Laboratory Skills and Knowledge Improved through Individual Lab Participation, Proc. ASEE Annual Conference, Louisville, KY, June 2010.13. Hilborn, R.B. (1994) “Team learning for engineering students,” IEEE Trans. Educ., vol. 37, no. 2, 1994, pp. 207–211.14. Neill, C.J., DeFranco, J.F., (2011) “Improving Team Learning in Systems Design”, Proc. ASEE Annual Conf, Vancouver, Canada, June 2011.15. Neill, C.J., DeFranco, J.F. (2011) “Problem-Solving Style and its Impact on Engineering Team Effectiveness.” Proc. 9th Conference on Systems Engineering Research, Redondo Beach, CA. April 201116. Nystrand, M. (1996). Opening dialogue: Understanding the dynamics of
Paper ID #7783Software and System Engineering Education: Commonalities and Differ-encesDr. Massood Towhidnejad, Embry-Riddle Aeronautical Univ., Daytona Beach Massood Towhidnejad is the director of NExtGeneration Applied Research Laboratory (NEAR), and a tenure full professor of software engineering in the department of Electrical, Computer, Software and System Engineering at Embry-Riddle Aeronautical University. His research and teaching interests include autonomous systems, and software and systems engineering with emphasis on software quality assurance and testing.Dr. Thomas B Hilburn, Embry-Riddle Aeronautical Univ
Page 13.34.1 Larry Bernstein is the Distinguished Service Professor of Software Engineering at Stevens Institute of Technology, Hoboken, NJ. He wrote “Trustworthy Systems Through Quantitative Software Engineering,” with C.M. Yuhas, Wiley, 2005, ISBN 0-471-69691-9. He had a 35-year executive career at Bell Laboratories managing huge software projects deployed worldwide. Mr.© American Society for Engineering Education, 2008 Bernstein is a Fellow of the IEEE and the Association for Computing Machinery for innovative software leadership. He is on the Board of Center for National Software Studies and Director of the NJ Center for Software Engineering and is an active speaker on Trustworthy
University, earned a bachelor's degree in Electrical Engineering from New Jersey Institute of Technology, an MSEE degree from Massachusetts Institute of Technology and a PhD from New York University. Dr. McDonald has an extensive industrial background in both software and electrical engineering. Prior to assuming his present position he worked at AT&T, Bell Laboratories, Bellcore and, most recently, at Lucent Technologies. He has taught numerous courses and workshops in the areas of operations research, microeconomics, quality management and project management. He has been responsible for systems engineering work on various types of telecommunications products, research in the areas of
geared towardsgraduate students. These students are described as professionals who are mature and responsibleto “self-direct their learning according to their individual learning style and pace” 10.Course DescriptionThe Software Specifications course (CEN 3073) presented in this paper is a 3-credit hourundergraduate course without a laboratory component. The CEN 3073 course is taught in thesecond semester of the junior year, after an ‘SE Fundamentals’ course in the previous semester,and before ‘Software Architecture & Design’ and ‘Software Testing’ courses in the followingsemesters. Students arrive at this course with intermediate knowledge of programming andexperience developing a group software project (from the SE Fundamentals course in
Page 25.754.11approach will be evaluated after our student cohorts finish their college education and enter theworkforce. This will be done through a longitudinal study by monitoring and tracking our then-alumni cohorts who attended classes covering software testing as undergraduates. We areconfident that even a partial success will cascade into software development and manifest itselfin the form of lower software defect rates and software maintenance costs.AcknowledgmentThis work is supported by the National Science Foundation's Transforming UndergraduateEducation in Science, Technology, Engineering and Mathematics (TUES) program (formerlyCourse, Curriculum, and Laboratory Improvement (CCLI) program) under Award No. DUE-1023071.Any opinions
. Fowler. UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley, 3rd edition, 2004. [7] R. France. A problem-oriented analysis of basic UML static requirements modeling concepts. In Proceedings of the 14th ACM SIGPLAN Conference on Object-oriented Programming, Systems, Languages, and Applications, pages 57–69. ACM Press, 1999. [8] P. Gagnon, F. Mokhati, and M. Badri. Applying model checking to concurrent UML models. Journal of Object Technology, 7(1):59–84, Jan. 2008. [9] M. Genero, M. Piattini, and C. Calero. A survey of metrics for UML class diagrams. Journal of Object Technology, 4(9):61–92, 2005.[10] S. Johnson. Lint, a C program checker. Technical Report 65, Bell Laboratories, Dec. 1977.[11
. 6. Felder, R.M., R. Brent, T.K. Miller, C.E. Brawner, and R.H. Allen. "Faculty teaching practices and perceptions of institutional attitudes toward teaching at eight engineering schools," in Proc. 1998 FIE Conf., Tempe, AZ, 1998, pp. 101-105. 7. Greco, E., and J. Reasoner. “Student Laboratory Skills and Knowledge Improved through Individual Lab Participation,” Proc. ASEE Annual Conference, Louisville, KY, 2010. 8. Witkin, H.A., and D.R. Goodenough, “Field Dependence and Interpersonal Behavior,” Psychological Bulletin, vol. 84, no. 4, 1977, pp. 661–689 9. Witkin, H.A., and D.R. Goodenough, Cognitive Styles: Essence and Origins, International Universities Press, Inc., NY, 1981. 10. Todd, R. H., S. P
applied technologies including distributed, component-based software architectures, software and systems engineering process models, intelligent control, the semantic web, and real-time artificial intelligence. Dr. Hawker has been a faculty member teaching software engineering and computing topics at the University of Alabama and RIT. His work with the NASA Technical Standards Program applying semantic web, formal modeling, information retrieval, and other advanced information technologies inspired his work to better create, manage, find, deliver, and use learning content in software engineering courses and projects. Dr. Hawker is also co-director of the Laboratory for
significant amount of time to be spent on introductory topics.Facilities needs are also challenging for these courses. As a group, these courses do not havededicated laboratory space for their offerings. This is especially problematic for networksecurity, as it is not possible for students to experiment in a “safe” networking environmentwhich is protected from outside entities. Network connectivity also poses issues. The lab spacetypically used for these courses is not equipped with wired network connections, instead relyingon 802.11g wireless networking. This poses significant connectivity issues when all students ina class are attempting to install a large binary for a commercial grade security tool.Software tool support is also a challenge for