The MSE technical seminars are the requirements of Studio reflection course for the 4th semester.
Each MSE student gives a talk on an approved subject dealing with your project or software engineering in general. Here are the abstract and the presenation material that we have had during Fall 2005:
| Date | Speaker | Topic | Abstract | Pictures |
| September 23, 2005 | Mike Hagen | Application of Earned Value Tracking in Iterative Software Projects Slides | Earned value tracking (EVT) is an important technique for monitoring the health and progress of a software project. However, in the face of changing requirements and available effort, it can give a false sense of reality. This seminar will present our team's experience with using earned value tracking, as well as discuss several techniques for adapting EVT to projects in which there varying risk and changing requirements. | |
| October 7, 2005 | Jinhee Lee | Planning and tracking techniques in a small software project Slides | Project planning and tracking is the foundation of all the software development activities. Planning project includes defining work products to be delivered, structuring the tasks, assigning resources, and scheduling the sequence of tasks. On the other hand, project tracking techniques let you know the current status of the project. This seminar will present our team's fresh experience with planning the project, estimating tasks, and tracking the progress as well as how the team used the tracking information. Moreover, The seminar will discuss the lessons learned from the project. | |
| October 14, 2005 | Lutz Wrage | Model-Driven Architecture (MDA) Slides | Model-driven development in general, and model-driven architecture in particular, promise to provide many kinds of benefits to software developers: MDA-developed systems will be cheap to produce, platform-independent, and interoperable. In my presentation I will give an introduction to the main MDA concepts and ideas. I will also highlight differences between vision and reality as well as open issues with MDA. | |
| October 28, 2005 | Min Wang | Establish the development process for the ACDM production stage Slides | The presentation will focus on how the software process is established for ACDM production stage in ArchE-II project and what lessons were learned by applying the process. There are three major parts: the first part will briefly introduce the ArchE project and the major problems encountered during its development. The second part will describe each step of the established software development process and how it worked in the project. The third part will analyze the how the process helped the team to solve the major problems in the project and the lessons learned from applying the process, and how would it be done differently in the future. | |
| November 11, 2005 | Luis Maya | Anticipating requirement changes Slides | Ever changing software requirements are the nightmare of software engineers. If requirements cannot stand still, can they be foreseen? The presentation evaluates how some simple requirement strategies can help anticipate requirement changes. The ArchE-II project will be used as case study to evaluate how those strategies would have improved, been innocuous or have hindered the project. | |
| November 18, 2005 | Gabe Zenarosa | Reflections on Encountering the Requirements-architecture GapSlides | Software architecture bridges the gap between requirements and detailed design. However, software architectures are treated more of an abstraction of detailed design and less of a refinement of requirements. Thus, a gap still exists between software requirements and architecture. Different authorities in the software engineering community have presented ways of bridging this smaller gap. Nuseibeh, et. al., proposed the Twin Peaks model as a process to overcome the artificial ordering on requirements and architecture design steps when addressed separately. Grunbacher, Egyed, and Medvidovic augmented to the Twin Peaks model their Component-Bus-System-Property (CBSP) approach that uses intermediate models to reconcile requirements and architectures. Hofmeister, Nord, and Soni, developed the Global Analysis approach (i.e., part of the Siemens Four Views architecture design approach) to reduce the requirements-architecture gap. | |
| December 2, 2005 | Zhen Zhang | Risk Management in Studio TeamsSlides | Everybody agrees that risk management, if done properly, is a good thing to do. However, there are many pitfalls which hamper the Studio teams to benefit from applying risk management. This presentation addresses the problems which Team Salsa! encountered of applying risk management and analyzes the possible solutions. | |
| December 7, 2005 | Bharat Gorantla | Building Distributed Software Projects using Agile MethodologiesSlides | Distributed development teams especially ones that are in a geographically distributed setting are becoming the norm for todays software projects. The increased globalization of software development has created many new software engineering challenges. Keeping software projects on track, maintaining the nominal amount of communication between teams, and as well as keeping these distributed teams on the same page are some of the challenges that distributed software projects are facing. In the past, many software projects that were in a distributed setting had failed, one which included Sapphires MSE project. The purpose of this presentation is to reflect back on the studio project and then provide a framework using Agile methodologies to perform distributed software projects. |