1 / 11

Ph.D. seminar for the software engineering group SEVO - project

Ph.D. seminar for the software engineering group SEVO - project. Anita Gupta anitaash@idi.ntnu.no Norwegian University of Science and Technology 23 rd November 2004. Agenda. Presentation of the projects: SJEF, SITT and EIAO Goals and metrics Research methods

donoma
Télécharger la présentation

Ph.D. seminar for the software engineering group SEVO - project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Ph.D. seminar for the software engineering groupSEVO - project Anita Gupta anitaash@idi.ntnu.no Norwegian University of Science and Technology 23rd November 2004

  2. Agenda • Presentation of the projects: SJEF, SITT and EIAO • Goals and metrics • Research methods • Research questions (temporary) • Related work • Future work • Discussion

  3. SJEF • Statoil have called their project for “SJEF”, and SJEF is a new reference architecture which is meant to become the basis for all new software systems. • Issues: • to evaluate the cost efficiency in development, integration and deployment of new systems using SJEF (vision vs reality). • to evaluate the possibilities for reuse (buy vs develop) with SJEF.

  4. SITT • Teleca have called their project for “SITT” and the focus in this project is on simplistic solutions. • Issues are: • how to link Bugzilla (used for bug tracking) to CVS (used for configuration management). • data amount/classifications vs. scalability and simplicity.

  5. EIAO • Høyskolen i Agder have called their project for “EIAO” (European Internet Accessibility Observatory), and the project is about web evolution. • Automatic assessment of website accessibility (ROBACC tool). • Issues • Goals and metrics both for ROBACC tool and web evolution.

  6. Goals and metrics • Come up with goals and software metrics (GQM approach), which will be helpful for the projects. • Come up with goals and software metrics (GQM approach) that will be helpful for us to collect some data on evolution and maybe see some similarities/differences between these projects.

  7. Research methods • For these 3 projects: Case study, we are going to collect data from the project. • For other possible projects: Experiment and data mining.

  8. Reserach questions (temporary) • What impact does software evolution has on quality attributes and on software processes? • Are there any similarities/differences between the projects? • What improvements issues are there, and what does it takes to handle these improvements? • How can software evolution improve some of the software processes?

  9. Related work • A student has made a summery over the topic of software evolution. He has done a study of changes (evolution) of different software architectures of 2-3 big industrial systems. The emphasize is on identifying the most important factors which can explain and maybe predict such evolution.

  10. Future work • Establish relations to other companies. • Next semester maybe perform an experiment in the subject ”Software architecture”. • Maybe combine software evolution with the systems the hospitals are using to perform their work. • Maybe combine software evolution with expansion of financial or other systems in Norway.

  11. Discussion • Which goals and software metrics could be useful for collecting data on software evolution? • Are there other research methods that I should be aware of, especially with respect to collecting data on software evolution? • Should I have any other research questions with respect to software evolution and possible software process improvement?

More Related