Reusable process chunks

  • Colette Rolland
  • Naveen Prakash
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 720)


Reusability of project components, either at the code level or at the conceptual specification level, is considered a fundamental aspect in application development. More recently it as been argued that project histories can support reuse of design decisions. We propose a solution based on so-called process chunks which are generic process frames to resolve the issue stated by a generic requirements engineering (RE) situation. Chunks are classified into micro-chunks and macro-chunks. The latter support the decision making process whereas the former help in implementing the decision. The RE activity based on these chunks consists of (1) recognising a situation as belonging to the class of situations treated by a chunk and (2) the instanciation of the process frame. The benefit expected from this approach is threefold: (1) to speed up the requirements engineering process; (2) to improve the quality of the conceptual specifications; and (3) to offer an extensible way for capturing generic RE process knowledge.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [ACM1990]
    ACM Issue on Object-Oriented Design, 1990Google Scholar
  2. [Balasubramaniam1992]
    Balasubramaniam. R., Vasant. Dhar “Supporting Systems Development by Capturing Deliberations During Requirements Engineering”, IEEE Transactions of Software Engineering, Vol 18, No 6, 1992.Google Scholar
  3. [[Biggerstaff1987]
    Biggerstaff.T et al, “Information Management Challenges in the Software Design Process”, IEEE Database Engineering, Vol 10, 1987.Google Scholar
  4. [Boehm1988]
    Boehm B.W.: “A Spiral Model of Software Development and Enhancement”; IEEE Computer 21., 1988.Google Scholar
  5. [[Conklin&Begeman1992]
    Conklin. J., Begeman. M. “gIBIS: a hypertext tool for exploratory policy discussion”, ACM Trans. on Office Information System, Vol 6, 1988.Google Scholar
  6. [Dubois1989]
    Dubois E.,Hagelstein J, Rifaut A.: “Formal Requirements Engineering with ERAE”, Philips Journal Research, Vol 43, No 4, 1989.Google Scholar
  7. [Dowson1987]
    Dowson M.: “Iteration in the Software Process. Proc 9th Int Conf on Software Engineering”, Monterey, CA,1988.Google Scholar
  8. [Finkelstein et al. 1990]
    Finkelstein A., Kramer J., Goedicke M.; “ViewPoint Oriented Software Development”; Proc. Conf “Le Génie Logiciel et ses Applications”, Toulouse, p 337–351, 1990.Google Scholar
  9. [[Gibbes1990]
    Gibbes S, Tsichritsis.I, Casais.E, Nierstrazs. O, Pintado.X: “Class Management for Software Communities”, Com. ACM, Vol 33, No 9, 1990.Google Scholar
  10. [Grosz&Rolland1990]
    Grosz G., Rolland C.: “Using Artificial Intelligence Techniques to Formalize the Information System Design Process”; Proc Int Conf on Databases and Expert Systems Applications, 1990.Google Scholar
  11. [Henderson-Sellers and Edwards 1990]
    Henderson-Sellers B., Edwards J.M.; “The Object-oriented Systems Life-Cycle”; Comm. ACM, 09, 1990.Google Scholar
  12. [Jarke1988]
    Jarke. M., Rose. T., “Managing Knowledge about Information System Evolution”, Proc. ACM SIGMOD, 1988.Google Scholar
  13. [Jarke et al1992]
    Jarke M., Bubenko J, Rolland C., Sutcliffe A., Vassiliou Y.; “NATURE Initial Integration Report”, NATURE.D-1,1992.Google Scholar
  14. [Jarke et al.1992]
    Jarke M., Mylopoulos J., Schmidt J.W., Vassiliou Y.; “DAIDA: An environment for evolving information systems”, ACM Transactions on Information Systems, Vol. 10, No. 1, 1992.Google Scholar
  15. [Peugeot and Franckson 1991]
    Peugeot C., Franckson M.; “Specification of the Object and Process Modelling Language”, ESF Report n∘ D122-OPML-1.0, 1991.Google Scholar
  16. [Potts 1989]
    Potts C.; “A Generic Model for Representing Design Methods”; Proc. 11th International Conference on Software Engineering, 1989.Google Scholar
  17. [Rolland&Cauvet1991]
    Rolland C., Cauvet C.: “ALECSI: An Expert System for Requirements Engineering”, in “Advanced Information Systems Engineering”, R.Andersen, J.A.Bubenko, A.Solvberg (Eds), Springer Verlag, 1991.Google Scholar
  18. [Rolland&Proix1992]
    Rolland C., Proix C.: “A Natural Language Approach for Requirements Engineering”, in “Advanced Information Systems Engineering”, P. Loucopoulos, K; Jeffery, J.A Bubenko, A.Solvberg (Eds), Springer Verlag, 1992.Google Scholar
  19. [Rose et al1991]
    Rose T., Jarke M., Gocek M., Maltzahn C., Nissen H.: “ A Decision-Based Configuration Process Environment”, Software Engineering Journal, 6, 5.Google Scholar
  20. [Royce1970]
    Royce W.W.; “Managing the development of large Software Systems”; Proc. IEEE WESCON 08/1970.Google Scholar
  21. [Schmitt1993]
    Schmitt J.R., “Product Modelling for Requirement Engineering Process Modelling”, IFIP Int. Conf. on “Information System Development Process”, Rolland C., Prakash N., Pernici B. (eds), North Holland (pub), 1993.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Colette Rolland
    • 1
  • Naveen Prakash
    • 2
  1. 1.Université de Paris SorbonneParis Cedex 5France
  2. 2.Delhi Institute of TechnologyDelhiIndia

Personalised recommendations