Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

Thomas Reichlmayr, Rochester Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

softwareproducts. When used in an academic setting it provides the opportunity to introduce and practiceproject management skills involving planning, estimation, tracking and identifying opportunitiesfor continuous process improvement. As the ideal number of team members on a Scrum projectis 5-9 developers, Scrum maps well from a size perspective for the typical student teamcollaborating on a course or capstone project. While Scrum has specific project roles andceremonies, it is intentionally non-prescriptive on the development practices to be used in theexecution of the project. In a software development project these practices are realized in thefamiliar software engineering life-cycles activities of requirements-analysis-design-code-test-deploy. In an

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

Massood Towhidnejad, Embry-Riddle Aeronautical University, Daytona Beach; Thomas B. Hilburn, Embry-Riddle Aeronautical University, Daytona Beach; Joseph E. Urban, Texas Tech University; Gregory W. Hislop, Drexel University; Richard Stansbury, Embry-Riddle Aeronautical University, Daytona Beach

Tagged Divisions

Software Engineering Constituent Committee

vertical integration approach ofInspireCT; it shows all the InspireCT constituents and shows how they are related to the projectactivities. InspireCT information and material is available at http://www.inspire-ct.org/. InspireCT 2009-2010 ActivitiesIn 2009-2010, the InspireCT participants engaged in the following activities: Definition of evaluation instruments and detailed process; Planned for vertical integration across computing courses in the major; Began collaboration with non-computing courses; Secured pre-college partners for InspireCT; Developed and delivered an undergraduate InspireCT workshop; and Planned and designed pre-college activities

Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Massood Towhidnejad, Embry-Riddle Aeronautical University, Daytona Beach; Thomas B. Hilburn, Embry-Riddle Aeronautical University, Daytona Beach; Salamah Salamah, Embry-Riddle Aeronautical University, Daytona Beach

Tagged Divisions

Software Engineering Constituent Committee

Beach Dr. Thomas B. Hilburn is a Professor Emeritus of Software Engineering at Embry-Riddle Aeronauti- cal University. He has also worked on software engineering research and education projects with the FAA, General Electric, Harris Corp, the MITRE Corporation, DOD, FIPSE, the SEI and the NSF. His current interests include software processes, object-oriented design, formal specification techniques, and curriculum development. He is an IEEE Certified Software Developer, SEI-Certified PSP Developer, and currently chairs the Curriculum Committee of the IEEE-CS Educational Activities Board and Planning Committee of the IEEE-CS Professional Activities Board.Salamah Salamah, Embry-Riddle Aeronautical Univ., Daytona Beach

Conference Session

SE Tools and Techniques

Collection

2011 ASEE Annual Conference & Exposition

Authors

John C. Georgas, Northern Arizona University

Tagged Divisions

Software Engineering Constituent Committee

integrated manner than currentpractice, and (b) to introduce team- and project-based software engineering activities in a lowrisk, high student involvement setting in order to create a smoother learning curve for students.This paper contributes: • A discussion of the learning theory foundations for our approach, based on experiential learning targeted at increasing student motivation; • A minimally disruptive framework for better integrating software engineering education within a computer science curriculum by elaborating our course design plan, and providing a description of areas that required particular care; and, • A presentation of quantitative and qualitative evaluation results, based on student surveys, evaluation based

Conference Session

Accreditation and Assessment in SE Programs

Collection

2011 ASEE Annual Conference & Exposition

Authors

Janet E. Burge, Miami University; Paul V. Anderson, Miami University, Ohio; Michael Carter, North Carolina State University; Gerald C. Gannod, Miami University; Mladen A. Vouk, North Carolina State University

Tagged Divisions

Software Engineering Constituent Committee

Participate in team meetings– includingFind bugs in specifications making a technical argument in themRead someone else’s code Participate in a scrumRead training manuals Structure a plan for a small groupRead with a purpose (different purposes Collaborate with team members (rather than appropriate for different situations) competing as can happen in academe)Foraging for information Make the team’s goals your goalsRead e-mails Communicate across cultures— work with team members from cultures that doWriting

Conference Session

SE Tools and Techniques

Collection

2011 ASEE Annual Conference & Exposition

Authors

Shane Markstrum, Bucknell University; Gary M. Haggard, Bucknell University

Tagged Divisions

Software Engineering Constituent Committee

previouslyseen by all of the students, start up costs are minimal since students with experience using the toolshelp their classmates to learn them. As a result, the less experienced class members increase theirproficiency over the whole term. The instructor should also help to identify the target audience at the school for the visualizationtool. This should be done in collaboration with another instructor so that the students have a readyset of students who can act as subjects for a practical user study. The decision about the intendedaudience is important because it helps the students determine an appropriate test plan and keeps the Page

Conference Session

Software Engineering Projects

Collection

2011 ASEE Annual Conference & Exposition

Authors

James N. Long, Oregon Institute of Technology; Linda Sue Young, Oregon Institute of Technology

Tagged Divisions

Software Engineering Constituent Committee

Page 22.1091.5 project progress, changes in scope, changes in design, and defects.5. Assess risk, probability of the risk, triggers and formulate contingency plans.6. Construct a statement of work with appropriate acceptance criteria.7. Describe the relationship between Testing and Quality Assurance.8. Describe the Quality assurance practices appropriate for each part of the development life cycle.9. Create user based requirements and engineering requirements.10. Describe traceability and be able to map a requirement through all project artifacts.11. Describe different modeling techniques and where they apply.12. Describe the different architectural views and assign them to parts of the life-cycle.13. Asses risk and develop risk

Conference Session

SE Tools and Techniques

Collection

2011 ASEE Annual Conference & Exposition

Authors

Robert W. Hasker, University of Wisconsin, Platteville; Mike Rowe, University of Wisconsin, Platteville

Tagged Divisions

Software Engineering Constituent Committee

language, both for identifiers and libraries. This mechanism should allow users to specify identifier syntax and library classes. • Provide a course profile mechanism to enable or disable specific checks. • Revise how feedback is given so that issues appear as notes directly on the submitted diagrams. • Incorporate natural language processing tools to provide more semantic-oriented checks such as described in our previous work.19 For example, the tool could warn against using verbs to name classes. • Using metrics such as those surveyed by Genero9 to identify common design flaws such as concentrating all processing in one or two classes.As discussed above, we are also planning a careful evaluation of the tool’s