Supporting Software Development With Roles

Software development tools are very important in software engineering. Although roles have been acknowledged and applied for many years in several areas related to software engineering, there is a lack of research on software development tools based on roles. Most significantly, there is no complete and consistent consideration of roles in all the phases of software development. Considering the increasing importance and applications of roles in software development, this paper intends to discuss the importance of roles in software engineering and that of role-based software development; review the literature relevant to role mechanisms in software engineering; propose and describe a role-based software process; and implement a prototype tool for developing complex software systems with the help of role mechanisms

[1]  Blake E. Ashforth,et al.  Role Transitions in Organizational Life : An Identity-based Perspective , 2001 .

[2]  David R. Kuhn,et al.  Role-Based Access Control (RBAC): Features and Motivations | NIST , 1995 .

[3]  Mustaque Ahamad,et al.  Generalized Role-Based Access Control for Securing Future Applications , 2000 .

[4]  Elizabeth A. Kendall,et al.  Role model designs and implementations with aspect-oriented programming , 1999, OOPSLA '99.

[5]  David Notkin,et al.  Using role components in implement collaboration-based designs , 1996, OOPSLA '96.

[6]  Stephen R. Schach,et al.  Object-oriented and classical software engineering , 1995 .

[7]  Ramaswamy Chandramouli,et al.  The Queen's Guard: A Secure Enforcement of Fine-grained Access Control In Distributed Data Analytics Platforms , 2001, ACM Trans. Inf. Syst. Secur..

[8]  Mohamed Fayad.  Introduction to the computing surveys' electronic symposium on object-oriented application frameworks , 2000, CSUR.

[9]  Ben Shneiderman,et al.  The Future of Graphic User Interfaces: Personal Role Managers , 1994, BCS HCI.

[10]  D. Richard Kuhn,et al.  Role-Based Access Control ( RBAC ) : Features and Motivations , 2014 .

[11]  Elisa Bertino,et al.  A generalized temporal role-based access control model , 2005, IEEE Transactions on Knowledge and Data Engineering.

[12]  SethiVikram,et al.  The impact of socialization on the role adjustment of information systems professionals , 1998 .

[13]  Sarah A. Sheard.  THE VALUE OF TWELVE SYSTEMS ENGINEERING ROLES , 1996 .

[14]  Haibin Zhu,et al.  A Role Agent Model for Collaborative Systems , 2003, IKE.

[15]  Elisa Bertino,et al.  TRBAC , 2001, ACM Trans. Inf. Syst. Secur..

[16]  Capers Jones,et al.  Why software fails , 1996 .

[17]  Kasper Østerbye,et al.  Roles: Conceptual Abstraction Theory and Practical Language Issues , 1996, Theory and Practice of Object Systems.

[18]  Haibin Zhu,et al.  Implementing Agent Evolution with Roles in Collaborative Systems , 2006, 2006 IEEE International Conference on Networking, Sensing and Control.

[19]  Friedrich Steimann,et al.  A Radical Revision of UML's Role Concept , 2000, UML.

[20]  R.N. Charette,et al.  Why software fails [software failure] , 2005, IEEE Spectrum.

[21]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[22]  Sergio Bandinelli,et al.  Supporting Cooperation in the SPADE-1 Environment , 1996, IEEE Trans. Software Eng..

[23]  Liping Zhao,et al.  Role modelling for component design , 2000, Proceedings 33rd International Conference on Technology of Object-Oriented Languages and Systems TOOLS 33.

[24]  Ravi S. Sandhu,et al.  Role-Based Access Control Models , 1996, Computer.

[25]  R S Pressman,et al.  Software engineering: a practitioner's approach (2nd ed.) , 1986 .

[26]  MengChu Zhou,et al.  Role-based collaboration and its kernel mechanisms , 2006, IEEE Transactions on Systems, Man, and Cybernetics, Part C (Applications and Reviews).

[27]  Sylvia L. Osborn,et al.  The role graph model and conflict of interest , 1999, TSEC.

[28]  Starr Roxanne Hiltz,et al.  The Electronic Journal: A Progress Report , 1982, J. Am. Soc. Inf. Sci..

[29]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[30]  Robert P. Bostrom,et al.  Role conflict and ambiguity: Critical variables in the MIS user-designer relationship , 1980, SIGCPR '80.

[31]  B. Biddle,et al.  Role Theory: Concepts and Research , 1966 .

[32]  John M. Wilson,et al.  Business Processes: Modelling and Analysis for Re-engineering and Improvement , 1995 .

[33]  Als-Nscort.  Eclipse Platform Technical Overview , 2003 .

[34]  L. Richard Hoffman,et al.  Applying Experimental Research on Group Problem Solving to Organizations , 1979 .

[35]  Dirk Riehle,et al.  Pattern density and role modeling of an object transport service , 2000, CSUR.

[36]  Trygve Reenskaug,et al.  Working with objects - the OOram software engineering method , 1995 .

[37]  Martin C. Rinard,et al.  Role-based exploration of object-oriented programs , 2002, ICSE '02.

[38]  Murray Turoff,et al.  Computer‐mediated communication requirements for group support , 1991 .

[39]  Dirk Riehle,et al.  Role model based framework design and integration , 1998, OOPSLA '98.

[40]  Ruth C. King,et al.  The Impact of Socialization on the Role Adjustment of Information Systems Professionals , 1998, J. Manag. Inf. Syst..

[41]  Saul Greenberg.  Personalisable Groupware: Accommodating Individual Roles and Group Differences , 1991, ECSCW.

[42]  Natalia Juristo Juzgado,et al.  Assigning people to roles in software projects , 2004, Softw. Pract. Exp..

[43]  Haibin Zhu,et al.  Role mechanisms in collaborative systems , 2006 .

[44]  James Coplien,et al.  A role-based empirical process modeling environment , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

[45]  John A. McDermid,et al.  Modelling Engineering Design Processes with Role Activity Diagrams , 2000, Trans. SDPS.