|
|
| [1] OUTSOURCING SOFTWARE MAINTENANCE: PROCESSES, NORMS & CRITICAL PRACTICES |
| Authors: |
Robillard, P.N., Tapp, M., Kerzazi, N. Hmima, H. |
| Reference: |
CCECE 2007, Vancouver |
| Page(s): |
x-x |
| Date/Year: |
Apr. 2007 |
| None available. |
|
| [2] Knowledge Conversion in Software Development |
| Authors: |
Gendreau, O. Robillard, P.N. |
| Reference: |
SEKE, Boston |
| Page(s): |
x-x |
| Date/Year: |
Jul. 2007 |
| None available. |
|
| [3] Process Activities in a Project Based Course in Software Engineering |
| Authors: |
Germain, E., Robillard, P.N., Dulipovici, M. |
| Reference: |
32nd ASEE/IEEE Frontier in Education conference, Boston |
| Page(s): |
S3G-7-S3G-12 |
| Date/Year: |
Nov. 2002 |
| None available. |
|
| [4] Papers: Optimizing software process control |
| Authors: |
Jacob Sukhodolsky |
| Reference: |
ACM SIGSOFT Software Engineering Notes, Volume 26 Issue 2 |
| Page(s): |
59-63 |
| Date/Year: |
March 2001 |
| This article presents a method for finding the optimal control actions the manager should take to meet a project's deadline in a situation when a schedule slip occurs. The method is based on using a discrete optimization technique, such as dynamic programming. Validation of the method's effectiveness is also included. |
|
| [5] Rules and Tools for Software Evolution Planning and Management |
| Authors: |
Meir M. Lehman |
| Reference: |
Annals of Software Engineering 11(1) |
| Page(s): |
15-44 |
| Date/Year: |
Nov 2001 |
| Based on all these and on the further results of the FEAST research projects this paper develops and presents some fifty rules for application in software system process planning and management and indicates tools available or that could usefully be developed to support their application. |
|
| [6] COTS, workflow, and software process management: an exploration of software engineering tool development |
| Authors: |
Barnes, A.; Gray, J. |
| Reference: |
Software Engineering Conference, 2000. Proceedings. 2000 Australian |
| Page(s): |
221-232 |
| Date/Year: |
2000 |
| Reports our initial investigations into the use of workflow technology for constructing a software process management tool. We examine some recent work undertaken in the fields of tool construction technologies and low-cost workflow engines. |
|
| [7] Process Management in Practice Applying the FUNSOFT Net Approach to Large-Scale Processes |
| Authors: |
Wolfgang Deiters |
| Reference: |
Automated Software Engineering 5(1): |
| Page(s): |
7-25 |
| Date/Year: |
Jan 1998 |
| Management of business and software processes are areas of increasing interest, which evolved nearly independently from each other. In this article we present an approach to process management that has been applied to business and software processes and which, thereby, enabled cross-fertilization between both areas. The goal of this article is to report lessons learned in industrial as well as academic business and software process management projects. |
|
| [8] Techniques for trusted software engineering |
| Authors: |
Devanbu, P.; Fong, P.W.-L.; Stubblebine, S.G. |
| Reference: |
Software Engineering, 1998. Proceedings of the 1998 International Conference on |
| Page(s): |
126-135 |
| Date/Year: |
1998 |
| Existing approaches have considered issues such as schedule, cost and efficiency; we argue that the traditionally software engineering issues of configuration management and intellectual property protection are also of vital concern. Existing approaches (e.g., Java) to this problem have used static type checking, run-time environments, formal proofs and/or cryptographic signatures; ETC. |
|
| [9] Integration of software process management and development history recording |
| Authors: |
Dissman, S.; Gruhn, V.; Ohrndorf, D. |
| Reference: |
Software Engineering Conference, 1995. Proceedings., 1995 Asia Pacific |
| Page(s): |
468-477 |
| Date/Year: |
1995 |
| The article describes how software process management could be improved by integration of development history recording. This idea is based on the observation that software process management focuses on activity patterns to be enforced, while the dependences between documents and document parts produced in these activities are not considered. Our approach is to combine both perspectives to enforce that software processes follow prescribed patterns and to manage dependencies between documents in order to ensure high quality software. |
|
|
|
