Abstract
Software development life cycle (SDLC) is developed much prior to evolution of unified modeling language (UML) (design diagrams). The stages of SDLC are syllogized when design stage comprises single level design diagrams and is accepted by the software developers as de-facto standard life cycle. UML is a multilevel state-of-the-art design language comprises number of design diagrams to represent different perceptive views of the System. UML helps to design stratification grammar. Now the introduction of UML diagrams creates commotion across and within SDLC stages. Since both are de-facto standards and both are essential for au-courant software development process. Neither can be jettisoned at the cost of the other. Thus there is a need either resurrect the syllogism definition or to resuscitate UML to reestablish constellation within and across UML. This paper attempts to resuscitate the constellation within UML as it is a sub part of SDLC. The class diagram represents class name, attributes, object methods along with their visibility, signature and interrelationships. The object diagrams which also containing similar information except the additional object and state information. In the middle level the usecase diagram defines real world of an actor in terms of its needy usecases. This cannot constellate the class diagram as the cluster of syntactics and semantics of class diagram cannot represent pragmatics of usecase. Analogical to the data flow diagram at higher level and usecase diagram at the middle level justifies its existence. Since it cannot constellates higher level class diagram there is a need to develop a stereotype of use case diagram that constellates a class diagram. This paper desiderates this need by pulling down object diagram with mutatis-mutandis to suite the stereotype of usecase diagram and constellates the class diagram.
Published Version
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call