research paper on framework comparison.pdf

We cannot offer much validation for the first

This preview shows page 33 - 34 out of 78 pages.

We cannot offer much validation for the first assumption, we state that if a feature is present it will be listed in the documentation. If this is not the case the features will not be used since the application developer cannot find it. This validation was performed in step 2, abstraction types, where we examined the code deeper and identified if all features which we extracted from documentation were in fact present in the code or libraries. Following these interviews minor corrections were made to the feature diagram until both parties agreed on the validity. Step 2, abstraction types Several assumptions were made in this step, these assumptions were: Each package can be pinpointed to a single feature Abstractness, method to NCSS, method to doc and efferent coupling determine the abstraction type That each package can be pinpointed to a single feature is suggested by the package structure of point frameworks, however we cannot offer and validation for this. This is also one of the discussion points mentioned later in this thesis. The use of specifically these metrics originates in the literature, which can be seen as the validation for using these metrics Step 3, customisation identification The following assumptions were made in this step: If a customisation is possible it will be mentioned in the documentation If a customisation is possible, but it was already possible without the framework (for integrated features like Freemarker, Velocity, etc) in this care the features documentation will list this The feature type dictates how to identify the customisation The first assumption was made specifically due to the time constraints. Although the literature suggests it to be true. Some feature will be customisable while the documentation does not list it, there is nothing we can do about that. The second assumption followed during the fact collection for this step, almost every feature was customisable, we than realised most of those features were integrated products. The customisability of these integrated products does not count towards to customisability of the framework, this is in the same order as customisability for the final product does not count for the customisability of the framework.
Image of page 33

Subscribe to view the full document.

Anton Gerdessen, Master thesis Page 34 of 78 The last assumption is again supported by the literature for customisability. Step 4, tool support Assumptions made in this step were: Tools provide a faster way of customising than by hand. This assumption is supported by the literature. Step 5, ease of change The following assumptions were made: The ease of change depends on the number of steps to achieve the change The complex single step counts for less than two simple steps The number of steps will be validates by actually performing the customisation for the three scenario’s. The results confirm our assumption, the more steps it takes the more time is required, see figure 16.
Image of page 34
You've reached the end of this preview.
  • Winter '19
  • jollet
  • Domain-specific language, Domain-specific modeling, domain analysis, general-purpose programming language, Anton Gerdessen

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern