Integrating Lightweight Systems Analysis into the United Process by Using Service Responsibility Tables

This paper is a step toward establishing direct, but non -automatic links between lightweight (semi -formal) analysis methods for business professionals and heavyweight analysis methods for IT professionals. After noting the impo rtance of user involvement in obtaining accurate and meaningful user requirements, the paper summarizes the Unified Process, a software development methodology that employs U nified Modeling Language (UML) . Another section in the paper summarizes previous e xtensions of the work system method that produced a lightweight analysis tool called Service Responsibility Tables (SRTs). This paper uses a straightforward example to demonstrate a set of heuristics for translating between service responsibility tables pr oduced by business professionals and UML diagrams that IT professionals can use as a partial basis for programming. This type of guideline -based link between lightweight and heavyweight methods could lead to more effective user involvement in requirements determination and reduce failure rate in IT projects .

[1]  Steven L. Alter,et al.  The Work System Method: Connecting People, Processes, and IT for Business Results , 2006 .

[2]  Anil Nigam,et al.  Business artifacts: An approach to operational specification , 2003, IBM Syst. J..

[3]  Keng Siau,et al.  Improving the quality of conceptual modeling using cognitive mapping techniques , 2005, Data Knowl. Eng..

[4]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[5]  Martin Glinz,et al.  Problems and deficiencies of UML as a requirements specification language , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[6]  Juhnyoung Lee Model-driven business transformation and the semantic web , 2005, CACM.

[7]  Steven L. Alter Service system fundamentals: Work system, value chain, and life cycle , 2008, IBM Syst. J..

[8]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[9]  Keng Siau,et al.  Using Cognitive Mapping Techniques to Supplement UML and up in Information Requirements Determination , 2006, J. Comput. Inf. Syst..

[10]  Cris Kobryn UML 2001: a standardization odyssey , 1999, CACM.

[11]  Keng Siau,et al.  Information Systems Requirements Determination and Analysis: A Mental Modeling Approach , 2003, AMCIS.

[12]  Karen Holtzblatt,et al.  Requirements Gathering: The Human Factors - Introduction to the Special Section , 1995, Commun. ACM.

[13]  Keng Siau,et al.  Identifying Difficulties in Learning Uml , 2006, Inf. Syst. Manag..

[14]  Steven L. Alter Service Responsibility Tables: A New Tool for Analyzing and Designing Systems , 2007, AMCIS.

[15]  Klaus Pohl,et al.  The three dimensions of requirements engineering: a framework and its applications , 1994, Inf. Syst..

[16]  Keng Siau,et al.  Theoretical vs. Practical Complexity: The Case of UML , 2005, J. Database Manag..

[17]  Steven L. Alter 18 Reasons Why IT-Reliant Work Systems Should Replace "The IT Artifact" as the Core Subject Matter of the IS Field , 2003, Commun. Assoc. Inf. Syst..

[18]  Karen Holtzblatt,et al.  Requirements gathering: the human factor , 1995, CACM.