From intentions to code: exploring the life of user goals in two web-based systems

From intentions to code: exploring the life of user goals in two web-based systems

For access to this article, please select a purchase option:

Buy article PDF
(plus tax if applicable)
Buy Knowledge Pack
10 articles for £75.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Your details
Why are you recommending this title?
Select reason:
IET Software — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

Goal models have been found to be an effective way to represent, communicate and analyse stakeholder requirements. Once such models reach some degree of completeness, a software-intensive system is developed to support the achievement of the identified goals. A question that naturally arises in this process, though, is whether and how the way by which requirements are represented in goal models influences the structure of the design of the system to be built. Does the content and organisation of the resulting source code disclose anything about the stakeholder intentions that have led to its production, and how? In this study the authors focus on web-based systems and describe the experiences in developing two small, layered web applications using goal models as a requirements representation tool and without introducing any goal-model specific methodological, design or platform restrictions. The authors study the artefacts of this process in an effort to identify intentional categories to which different parts of the source code belongs. The results indeed suggest interesting characterisations of goals, source code and relationships thereof that could be useful in developing goal-oriented web engineering frameworks and methodologies.


    1. 1)
    2. 2)
      • Yu, E.S.K., Mylopoulos, J.: `Understanding ‘why’ in software process modelling, analysis, and design', Proc. 16th Int. Conf. Software Engineering (ICSE’94), 1994, p. 159–168.
    3. 3)
      • A. Strauss , J.M. Corbin . (1990) Basics of qualitative research: grounded theory procedures and techniques.
    4. 4)
      • K. Krippendorff . (2004) Content analysis.
    5. 5)
    6. 6)
      • Munro, S., Liaskos, S., Aranda, J.: `The mysteries of goal decomposition', Proc. Fifth Int. i* Workshop (iStar’11), 2011, p. 49–54.
    7. 7)
      • Kiczales, G., Lamping, J., Mendhekar, A.: `Aspect-oriented programming', Proc. European Conf. on Object-Oriented Programming (ECOOP’97), 1997.
    8. 8)
      • G. Blanco . Transparent PHP AOP.
    9. 9)
      • N. Curtis . (2009) Modular web design: creating reusable components for user experience design and documentation.
    10. 10)
    11. 11)
      • K. Czarnecki , U.W. Eisenecker . (2000) Generative programming – methods, tools, and applications.
    12. 12)
      • Schobbens, P.-Y., Heymans, P., Trigaux, J.-C.: `Feature diagrams: a survey and a formal semantics', Proc. 14th IEEE Int. Conf. on Requirements Engineering (RE’06), 2006, p. 139–148.
    13. 13)
    14. 14)
      • L. Bass , P. Clements , R. Kazman . (2003) Software architecture in practice.
    15. 15)
      • Wang, W., Tzerpos, V.: `Design pattern detection in Eiffel systems', Proc. Working Conf. Reverse Engineering (WCRE’05), 2005, p. 165–174.
    16. 16)
    17. 17)
      • Shtern, M., Tzerpos, V.: `Refining clustering evaluation using structure indicators', Proc. IEEE Int. Conf. on Software Maintenance (ICSM’09), 2009, Los Alamitos, CA, USA, p. 297–305.
    18. 18)
      • G. Spanoudakis , A. Zisman . (2004) Software traceability: a roadmap. Handbook of Software Engineering and Knowledge Engineering.
    19. 19)
      • Cleland-Huang, J., Settimi, R., BenKhadra, O., Berezhanskaya, E., Christina, S.: `Goal-centric traceability for managing non-functional requirements', Proc. 27th Int. Conf. on Software Engineering (ICSE ‘05), 2005, New York, NY, USA, p. 362–371.
    20. 20)
      • Pohl, K.: `PRO-ART: enabling requirements pre-traceability', Proc. Second Int. Conf. on Requirements Engineering (ICSE'96), 1996, p. 76–84.
    21. 21)
    22. 22)
      • L. Penserini , A. Perini , A. Susi , J. Mylopoulos . High variability design for software agents: extending Tropos. ACM Trans. Autonom. Adapt. Syst. (TAAS) , 4 , 1556 - 4665
    23. 23)
      • A. van Lamsweerde . From system goals to software architecture.
    24. 24)
      • Yu, Y., Lapouchnian, A., Liaskos, S., Mylopoulos, J., Cesar Sampaio do Prado Leite, J.: `From goals to high-variability software design', Proc. 17th Int. Symp. on Foundations of Intelligent Systems (ISMIS’08), (LNCS, 4994), 2008, p. 1–16.
    25. 25)
      • Yu, Y., Wang, Y., Mylopoulos, J.: `Reverse engineering goal models from legacy code', Proc. 13th IEEE Int. Conf. on Requirements Engineering (RE’05), 2005, Paris, France, p. 363–372.
    26. 26)
    27. 27)
      • Bolchini, D., Mylopoulos, J.: `From task-oriented to goal-oriented web requirements analysis', Proc. Fourth Int. Conf. on Web Information Systems Engineering (WISE’03), 2003, Washington, DC, USA, p. 166–175.
    28. 28)
      • I. Garrigós , J.-N. Mazón , J. Trujillo . A requirement analysis approach for using i* in web engineering.
    29. 29)
      • J. Alfonso Aguilar , I. Garrigós , J.-N. Mazón , J. Trujillo . An MDA approach for goal-oriented requirement analysis in web engineering. J. Univ. Comput. Sci. (JUCS) , 17 , 2475 - 2494
    30. 30)
      • P. Valderas , J. Fons , V. Pelechano . Transforming web requirements into navigational models: an MDA based approach.

Related content

This is a required field
Please enter a valid email address