Publication | Closed Access
The use of object-oriented models in requirements engineering: a field study
24
Citations
14
References
1999
Year
Software MaintenanceEngineeringInformation SystemsObject-oriented ModelingProject ManagementSoftware SystemsRequirement ModelingSoftware EngineeringRequirements SpecificationsSoftware AnalysisSoftware RequirementObject-oriented ModelsSystems EngineeringRequirements EngineeringObject-oriented DesignSoftware ConstructionRequirement AnalysisOrganizational SystemsBusiness Information SystemsField StudyRequirement EngineeringDesignUse CaseSoftware DesignSoftware TestingBusinessDesign ThinkingRequirements ModelingCase Studies
In many organizations, there has been a move toward the use of object-oriented methods for the development of information systems. Little is understood, or reported on the basis of research, of the use of object-oriented methods by practicing professionals in the production of requirements specifications for commercial or industrial sized projects. In this paper, we outline a conceptual framework of “what might be happening” in professional object-oriented requirements engineering based on the common characteristics of published, well known object-oriented methods. We then describe a research project and the findings from a set of six case studies that have been undertaken that examine professional practice from the standpoint of the epistemology contained in the conceptual model. In these studies, it was found that the more formal models of objectorientation were rarely used to validate, or even clarify, the specification with clients or users. Rather, analysts tended to use informal models, such as use cases or ad hoc diagrams, to communicate the specification to users. Formal models are more often used internally within the analysis team and for communicating the specification to the design team.
| Year | Citations | |
|---|---|---|
Page 1
Page 1