WISE: Automated support for software project management and measurement. M.S. Thesis

One important aspect of software development and IV&V is measurement. Unless a software development effort is measured in some way, it is difficult to judge the effectiveness of current efforts and predict future performances. Collection of metrics and adherence to a process are difficult tasks in a software project. Change activity is a powerful indicator of project status. Automated systems that can handle change requests, issues, and other process documents provide an excellent platform for tracking the status of the project. A World Wide Web based architecture is developed for (a) making metrics collection an implicit part of the software process, (b) providing metric analysis dynamically, (c) supporting automated tools that can complement current practices of in-process improvement, and (d) overcoming geographical barrier. An operational system (WISE) instantiates this architecture allowing for the improvement of software process in a realistic environment. The tool tracks issues in software development process, provides informal communication between the users with different roles, supports to-do lists (TDL), and helps in software process improvement. WISE minimizes the time devoted to metrics collection, analysis, and captures software change data. Automated tools like WISE focus on understanding and managing the software process. The goal is improvement through measurement.

[1]  Norman E. Fenton,et al.  Software measurement: A conceptual framework , 1990, J. Syst. Softw..

[2]  Carma McClure,et al.  The CASE experience , 1989 .

[3]  Stephen Robertson,et al.  The methodology of information retrieval experiment , 1981 .

[4]  Tilmann F. W. Bruckhaus,et al.  TIM: a tool insertion method , 1994, CASCON.

[5]  M Barry.  Airborne Systems Software Acquisition Engineering Guidebook for Software Testing and Evaluation. , 1980 .

[6]  V. Basili.  Software modeling and measurement: the Goal/Question/Metric paradigm , 1992 .

[7]  Victor R. Basili,et al.  A Methodology for Collecting Valid Software Engineering Data , 1984, IEEE Transactions on Software Engineering.

[8]  Michael Daskalantonakis,et al.  A Practical View of Software Measurement and Implementation Experiences Within Motorola , 1992, IEEE Trans. Software Eng..

[9]  Gail E. Kaiser,et al.  Intelligent assistance for software development and maintenance , 1988, IEEE Software.

[10]  Gregory A. Hansen,et al.  Software Process Modeling , 1988 .

[11]  Leon J. Osterweil,et al.  Software processes are software too , 1987, ISPW.

[12]  M. D. Lubars,et al.  Representing design dependencies in an issue-based style , 1991, IEEE Software.

[13]  Nicholas J. Belkin,et al.  Information filtering and information retrieval: two sides of the same coin? , 1992, CACM.

[14]  Robert Kass,et al.  Modeling users' interests in information filters , 1992, CACM.

[15]  Shoshana Loeb,et al.  Architecting personalized delivery of multimedia information , 1992, CACM.

[16]  C. Landauer,et al.  Integrated software environments , 1992, Proceedings Eighth Conference on Artificial Intelligence for Applications.

[17]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[18]  Victor R. Basili,et al.  The Experience Factory and its Relationship to Other Improvement Paradigms , 1993, ESEC.

[19]  Curt Stevens,et al.  Automating the creation of information filters , 1992, CACM.

[20]  Victor R. Basili,et al.  Evaluating Software Development by Analysis of Changes: Some Data from the Software Engineering Laboratory , 1985, IEEE Transactions on Software Engineering.