RESUMEN

e-Services are intangible products, provisioned via the Internet. Examples include Internet access and Internet radio. Because most e-services involve multiple enterprises, creating a shared understanding of the service under development is an issue. Such an e-service is more difficult to understand than a proposition just consisting of goods because services lack easily observable physical properties. Consequently, software engineers must first understand the e-service itself before they can build effective systems and support for these services. The authors present the complementary use of two requirements engineering techniques. Using i* modeling, they explore strategic goals that enterprises have, and using e3value modeling, they understand how these goals can result in profitable services for enterprises. They demonstrate their approach using a case study on Internet radio.This article is part of a special issue on requirements engineering.

RESUMEN

In three stages covering 12 years and 16 projects, a software development group worked on attaining visible schedule control and usable software design documentation. The first stage identified two major problems: unstable code and schedule delays. The group used code inspection to address the immediate issue of code construction. In the second stage, the group formulated and implemented a software development process that addressed the entire software development life cycle. The third stage improved that process. The major factor in process improvement was the group's willingness to identify its mistakes and problems.