Object-oriented development in an industrial environment

JacobsonIvar,

doi:10.1145/38807.38824

Cited by 59 publications

(34 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For the case of components, their logical representation was modeled using UML subsystems and identified inside the use case diagrams as proposed by Houston and Norris (2001). Class diagrams were prepared using the criteria for finding objects as described in Jacobson's (1987) object-oriented method. This step was accomplished by reviewing each use case to find nouns that correspond to business entities or events (Jacobson 1987).…”

Section: Application Of the Conceptual Model Comparison Methodsmentioning

confidence: 99%

“…Class diagrams were prepared using the criteria for finding objects as described in Jacobson's (1987) object-oriented method. This step was accomplished by reviewing each use case to find nouns that correspond to business entities or events (Jacobson 1987). Not all the nouns in the use cases represent valid business objects.…”

Section: Application Of the Conceptual Model Comparison Methodsmentioning

confidence: 99%

See 1 more Smart Citation

A method for comparing traditional and component-based models in information systems re-engineering

Valverde

Toleman

Cater-Steel

2010

Inf Syst E-Bus Manage

View full text Add to dashboard Cite

Many organisations have become aware of the limitations of their legacy systems to adapt to new technical requirements. Trends towards e-commerce applications, platform independence, reusability of pre-built components, capacity for reconfiguration and higher reliability have contributed to the need to update current systems. Consequently, legacy systems, typically designed and developed using traditional methods, need to be re-engineered into new component-based systems. The objective of the study is to develop a method to compare traditional and component-based models of systems. Design science is the approach used to build and evaluate the method. The method incorporates and integrates existing methodologies for information systems re-engineering and conceptual model evaluation. A case study illustrating the comparison method revealed that a reengineered component-based conceptual model was capable of representing and enriching all the traditional conceptual model constructs. However, there was a conflict with the use of data flows as these can represent both events and also couplings between processes, data stores, and external agents. Thus, the project derived an additional set of rules to use when generating a component-based model to improve the re-engineering step.

show abstract

Section: Application Of the Conceptual Model Comparison Methodsmentioning

confidence: 99%

Section: Application Of the Conceptual Model Comparison Methodsmentioning

confidence: 99%

A method for comparing traditional and component-based models in information systems re-engineering

Valverde

Toleman

Cater-Steel

2010

Inf Syst E-Bus Manage

View full text Add to dashboard Cite

show abstract

“…Ericsson has a long tradition in model driven development: the company's use of software models with associated semantics dates back to 1967, with the AKE switch, first delivered in 1971, built using such [8]. Ericsson contributed to development of SDL [16] during the 1970s, and applied SDL extensively during the 1980s; use-case modeling was pioneered by Ericsson in the 1980s [8]; in the 1990s, Ericsson was an early adopter of RUP [1]; today, MDD plays a central role in several Ericsson product lines, and model based software engineering is recognized as a prioritized area of improvement.…”

Section: Our Case: a Design Unit Developing Base Station Softwarementioning

confidence: 99%

“…Ericsson contributed to development of SDL [16] during the 1970s, and applied SDL extensively during the 1980s; use-case modeling was pioneered by Ericsson in the 1980s [8]; in the 1990s, Ericsson was an early adopter of RUP [1]; today, MDD plays a central role in several Ericsson product lines, and model based software engineering is recognized as a prioritized area of improvement.…”

Section: Our Case: a Design Unit Developing Base Station Softwarementioning

confidence: 99%

Concern coverage in base station development: an empirical investigation

2011

View full text Add to dashboard Cite

Contemporary model driven development tools only partially support the abstractions occurring in complex embedded systems development. This article presents an interpretive case study in which architectural concerns important to seven engineers in a large product developing organization were compared to the views actually provided by the organization's models. The paper's main finding is an empirically grounded catalogue of architectural concerns for a large, complex embedded systems project, and an assessment of the degree to which the studied organization has managed to realize support for these concerns within economical and organizational constraints. In the studied case, 114 different architectural concerns were found to be important to the interviewed engineers. Of this sample, 75% were documented in models, structured text, or informal documentation, whereas 47% of all documented concerns were modeled. The paper's conclusion is that current modeling languages and methods inadequately address the full set of concerns that are important to engineers in base station development.

show abstract

“…Since the introduction of the use case by Ivar Jacobson (1987), the notation has become a ubiquitous tool for IT projects. Use cases have been applied in a variety of ways including the capture of functional requirements, planning task breakdown and required resources, performing domain analysis, creation of object and component models, designing test cases, and estimation (Jacobson 2004).…”

Section: Background and Related Workmentioning

confidence: 99%

Control case approach to record and model non-functional requirements

Zou

Pavlovski

2007

ISeB

View full text Add to dashboard Cite

While the functional requirements of a system can be effectively modeled through the use case driven approach, there is no standard or de facto method for modeling non-functional requirements (NFR) of the system architecture. Often such requirements are dealt with in a reactive manner, rather than proactively. Yet increasingly a contributing factor in project difficulty and failure are the NFR imposed on the solution architecture. This paper outlines a control case approach to record and model NFR. This technique enables the control case to represent the NFR from different perspectives, most typically the various operating conditions. We also propose an extension to the ''4 + 1'' view model for depicting software architecture by adding the control case view. In addition, a detailed control case modeling example is illustrated to demonstrate how these techniques may be applied during development. Taken together, we suggest that the combination of both the use case and control case views thus reflects the complete requirements across the collective system life cycle views: design, process, implementation and deployment.

show abstract

Object-oriented development in an industrial environment

Cited by 59 publications

References 7 publications

A method for comparing traditional and component-based models in information systems re-engineering

A method for comparing traditional and component-based models in information systems re-engineering

Concern coverage in base station development: an empirical investigation

Control case approach to record and model non-functional requirements

Contact Info

Product

Resources

About